Hello List,
I'm having some issues with my mdraid. The system is Fedora 10, x86_64. I installed the system with two Seagate drives in a RAID 1 configuration. I let the configuration utility automatically setup the RAID configuration. I believe each drive is configured a single partition with this partition being part of the RAID device.
About a week ago, device 0 reported errors and was dropped from the array by mdraid. The RAID continued in a degraded state with no problems. I finally had time to work on it so I shut down the PC and tried to run some disk drive utilities on it. The BIOS isn't even seeing the drive, so I'll RMA it to Seagate. Drive 0 is unplugged and not in the system, leaving Drive 1. When I try to boot, I get just a message of "GRUB". I'm assuming that my problem is that GRUB was installed to drive 0 and drive 0 was set to be my primary.
I've tried booting to the FC10 Install media in recovery mode, but when it attempts to mount the device, I receive a message that the device must be initialized, which will cause a loss of all data.
How do I resolve the problem booting to drive 1? Second, once I install my replacement device, how do I rebuild the array? I assume I'll need to some how get my current Drive 1 set to primary and then install the second drive, and use mdadm to add it.
Thank you for your help
Law
http://radu.rendec.ines.ro/howto/raid1.html
http://www.linuxjournal.com/article/8874
Recoveries just never seen simple...
Bob
On 05/02/2009 07:17 PM, Law Barstow wrote:
Hello List,
I'm having some issues with my mdraid. The system is Fedora 10, x86_64. I installed the system with two Seagate drives in a RAID 1 configuration. I let the configuration utility automatically setup the RAID configuration. I believe each drive is configured a single partition with this partition being part of the RAID device.
About a week ago, device 0 reported errors and was dropped from the array by mdraid. The RAID continued in a degraded state with no problems. I finally had time to work on it so I shut down the PC and tried to run some disk drive utilities on it. The BIOS isn't even seeing the drive, so I'll RMA it to Seagate. Drive 0 is unplugged and not in the system, leaving Drive 1. When I try to boot, I get just a message of "GRUB". I'm assuming that my problem is that GRUB was installed to drive 0 and drive 0 was set to be my primary.
I've tried booting to the FC10 Install media in recovery mode, but when it attempts to mount the device, I receive a message that the device must be initialized, which will cause a loss of all data.
How do I resolve the problem booting to drive 1? Second, once I install my replacement device, how do I rebuild the array? I assume I'll need to some how get my current Drive 1 set to primary and then install the second drive, and use mdadm to add it.
Thank you for your help
Law
On Sat, May 02, 2009 at 19:17:32 -0400, Law Barstow LBarstow@cfl.rr.com wrote:
not in the system, leaving Drive 1. When I try to boot, I get just a message of "GRUB". I'm assuming that my problem is that GRUB was installed to drive 0 and drive 0 was set to be my primary.
At the grub prompt you can try something like: configfile (hd1,0)/grub/grub.conf If /boot is the first partition on the drive this should work. It is a later one increase the second 0. This also assumes the bad drive is still be detected by grub so that the good drive is known to it as hd1.
You could also pull the bad drive.
How do I resolve the problem booting to drive 1? Second, once I install my replacement device, how do I rebuild the array? I assume I'll need to some how get my current Drive 1 set to primary and then install the second drive, and use mdadm to add it.
Use some partitioning tool to create a software raid partition the same size as the previous one. (If the drive is the same size as the other one, you might just copy of the partition table.) You can add the partition as an element in the array using mdadm. It would be something like: mdadm /dev/md0 -a /dev/sda1 You need to do that for each array. Typically /boot and / are separate arrays.
-
Bruno Wolff III -
Law Barstow -
Robert L Cochran