Yes very true. Sorry, case of the Mondays. I don't know why I was thinking the drive was physically dead vs working - just corrupt. This is an area where you'd have to know that it was failing to boot and manually shift BIOS to boot from the next drive. Thank you for brining me back into reality! -----Original Message----- From: Daniel O'Connor [mailto:darius@xxxxxxxxxxx] Sent: Wednesday, February 28, 2007 11:03 PM To: Hall, Eric R Cc: ATARAID (eg, Promise Fasttrak, Highpoint 370) related discussions; Darrick J. Wong Subject: Re: Intel ICH8R chipset On Thursday 01 March 2007 16:43, Hall, Eric R wrote: > I agree. BIOS hasn't a clue about the raid configuration. But in > regards to md, couldn't an initrd be used to mount "/" on the raid from > the next disk from that raid? > > Once md is loaded at initrd, you would then have access to the raid and > would be able to continue boot. It'll be in degraded mode, but it > should boot. (I could be very wrong though!) That's not the point.. If there is an error part way through the boot loader the BIOS will start reading the dud disk but then not be able to finish. I doubt it will try loading from the other disk.. No matter what, Murphy is there! :) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C _______________________________________________ Ataraid-list mailing list Ataraid-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/ataraid-list
