Years ago I had a problem booting with a failed disk. I was told to add this to the kernel command line. md-mod.start_dirty_degraded=1 For me the file to edit is this: /boot/grub/grub.conf I think the above should be the default. During a failure is not the time to learn this! Or it should be an attribute of the array, so you can have some arrays that can start degraded and some that can't. Guy } -----Original Message----- } From: linux-raid-owner@xxxxxxxxxxxxxxx [mailto:linux-raid- } owner@xxxxxxxxxxxxxxx] On Behalf Of Troy Cauble } Sent: Sunday, February 01, 2009 12:35 AM } To: linux-raid@xxxxxxxxxxxxxxx } Subject: problem growing raid-1 } } I want to replace both disks in a RAID-1 with larger ones using the } instructions here: } http://linux- } raid.osdl.org/index.php/Growing#Extending_an_existing_RAID_array } } It looks straightforward: mdadm -f, mdmadm -r, swap a drive, etc., etc. } } Except if I -f & -r a drive, I won't know which physical drive to pull. } (And I have no spare SATA ports.) } } So I figure I'll pull a drive first, then -f & -r whatever mdadm tells } me is missing. } But when I pull the drive, connect a new one and boot, I get dropped } into a repair } shell with: } } fsck.ext3: Unable to resolve 'UUID=806153bf-6917-440d-ae48-553418cfbbeb' } } which is the UUID of the raid filesystem. } } I put the drive back in and reboot, and everything is fine. } } 1) So why doesn't my RAID-1 survive pulling a drive? } Seems like a standard failure mode. } } 2) How do I proceed with the upgrade? } } Thanks, } -troy } -- } To unsubscribe from this list: send the line "unsubscribe linux-raid" in } the body of a message to majordomo@xxxxxxxxxxxxxxx } More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
