On Monday June 4, linux-raid@xxxxxxxxxxxxxxxx wrote: > I have a RAID6 array. 1 drive is bad and now un-plugged because the system > hangs waiting on the disk. > > The system won't boot because / is "not clean". I booted a rescue CD and > managed to start my arrays using --force. I tried to stop and start the > arrays but they still required --force. I then used "echo repair > > sync_action" to make the arrays "clean". I can now stop and start the RAID6 > array without --force. I can now boot normally with 1 missing disk. > > Is there an easier method? Some sort of boot option? This was a real pain > in the @$$. > > It would be nice if there was an array option to allow an "un-clean" array > to be started. An option that would be set in the md superblock. Documentation/md.txt search for 'clean' - no luck. search for 'dirty' | |So, to boot with a root filesystem of a dirty degraded raid[56], use | | md-mod.start_dirty_degraded=1 | NeilBrown - 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
