I ran raider last night (raid 1 with 2 disks). Everything went well.
The disks synced and everything seem to be working.
Just not, after installing kernel-pae for openSUSE 12.1, I received an alert, after rebooting, that my md1 has a removed disk (dev/sdb3). The disk seems to be fine, as /dev/sdb2 on md0 is active and working. So I know the disk is good.
Can some one help?
After running raider-d I get:
Disk /dev/sda - 1T - Seagate: ST1000DM003-1ER162 - Z4Y81AX4
Partition Table: MBR/msdos
|--/dev/sda1 - Pri Linux swap / Solaris swap 10.7GB swap
|--/dev/sda2 *boot Pri Linux raid autodetect ( md0 ) 53.7GB none
`--/dev/sda3 - Pri Linux raid autodetect ( md1 ) 936GB none
Disk /dev/sdb - 1T - Seagate: ST1000DM003-1ER162 - Z4Y6DDY7
Partition Table: MBR/msdos
|--/dev/sdb1 - Pri Linux swap / Solaris 10.7GB none
|--/dev/sdb2 *boot Pri Linux raid autodetect ( md0 ) 53.7GB none
`--/dev/sdb3 - Pri Linux raid autodetect ( ) 936GB none
Last edit: Ray Eason 2015-10-23
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Update: So I did some digging online and deduced that I needed to remove the disk from the array.
I ran mdadm --zero-superblock /dev/sdb3 and readded the disk to /dev/md1. It took about 4 hours to resync.
I thing reinstalled kernel-pae and rebooted a few times to make sure everything was ok. It was.
I then when into yast and set the bootloader to use the kernel-pae as the default to load.
Bad move I guess, not the system is booting right to a grub menu.
I have tried booting off either disk but to no avail.
Can someone help me with this? I did not think selecting the kernel-pae as the default would cause opensuse 12.1 not to boot but, sence we are dealing with grub, I guess it did not like it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Update: It looks like yast wrote over my /boot/grub/menu.lst.
Fortunately I had a backup of a working copy and restored it. The system was back up and running.
This morning, I booted to kernal-pae again.
The first time, it wanted to boot into recovery. Seems like it could not find a disk.
So I rebooted.
Then I received an alert the array was degraded again on /dev/md1. This time it was not /dev/sdb3 but /dev/sda3 (my /SRV partitition on the array).
So I have zero-superblocked /dev/sda3 and added the drive back to the array. It is resyncing/recovering now.
I don't know why booting with certain kernels causes the issue. I also don't know why it's just the partitions on /dev/sdbX (even though while /dev/sdb3 is missing, /dev/sda3 is working fine and vice versa).
Any insight would be appreciated.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I ran raider last night (raid 1 with 2 disks). Everything went well.
The disks synced and everything seem to be working.
Just not, after installing kernel-pae for openSUSE 12.1, I received an alert, after rebooting, that my md1 has a removed disk (dev/sdb3). The disk seems to be fine, as /dev/sdb2 on md0 is active and working. So I know the disk is good.
Can some one help?
After running raider-d I get:
Disk /dev/sda - 1T - Seagate: ST1000DM003-1ER162 - Z4Y81AX4
Partition Table: MBR/msdos
|--/dev/sda1 - Pri Linux swap / Solaris swap 10.7GB swap
|--/dev/sda2 *boot Pri Linux raid autodetect ( md0 ) 53.7GB none
`--/dev/sda3 - Pri Linux raid autodetect ( md1 ) 936GB none
Disk /dev/sdb - 1T - Seagate: ST1000DM003-1ER162 - Z4Y6DDY7
Partition Table: MBR/msdos
|--/dev/sdb1 - Pri Linux swap / Solaris 10.7GB none
|--/dev/sdb2 *boot Pri Linux raid autodetect ( md0 ) 53.7GB none
`--/dev/sdb3 - Pri Linux raid autodetect ( ) 936GB none
Last edit: Ray Eason 2015-10-23
Update: So I did some digging online and deduced that I needed to remove the disk from the array.
I ran mdadm --zero-superblock /dev/sdb3 and readded the disk to /dev/md1. It took about 4 hours to resync.
I thing reinstalled kernel-pae and rebooted a few times to make sure everything was ok. It was.
I then when into yast and set the bootloader to use the kernel-pae as the default to load.
Bad move I guess, not the system is booting right to a grub menu.
I have tried booting off either disk but to no avail.
Can someone help me with this? I did not think selecting the kernel-pae as the default would cause opensuse 12.1 not to boot but, sence we are dealing with grub, I guess it did not like it.
Update: It looks like yast wrote over my /boot/grub/menu.lst.
Fortunately I had a backup of a working copy and restored it. The system was back up and running.
This morning, I booted to kernal-pae again.
The first time, it wanted to boot into recovery. Seems like it could not find a disk.
So I rebooted.
Then I received an alert the array was degraded again on /dev/md1. This time it was not /dev/sdb3 but /dev/sda3 (my /SRV partitition on the array).
So I have zero-superblocked /dev/sda3 and added the drive back to the array. It is resyncing/recovering now.
I don't know why booting with certain kernels causes the issue. I also don't know why it's just the partitions on /dev/sdbX (even though while /dev/sdb3 is missing, /dev/sda3 is working fine and vice versa).
Any insight would be appreciated.