Hi! Whew, I have googled around a lot w/this but can't quite seem to come up w/the right answer. This system works beautifully w/nothing wrong w/it. But my goal is to be able to test the raid system by just unplugging hda to mimic a faulty drive and have it just carry on and boot from hdc. md0 = hda1/hdc1 /boot (primary boot partitions on both drives) md1 = hda2/hdc2 / is it possible to just edit /boot/grub.conf??? I am really not sure of this Thx in advance. John Rose
rado wrote:>But my goal is to be >able to test the raid system by just unplugging hda to mimic a faulty >drive and have it just carry on and boot from hdc. > >md0 = hda1/hdc1 /boot (primary boot partitions on both drives) >md1 = hda2/hdc2 / >Can't you just do a software test: raidsetfaulty /dev/md1 /dev/hdc2 (for example) Check out the LDP http://www.tldp.org/HOWTO/Software-RAID-HOWTO-6.html#ss6.3 for details including how to add the disk back to the array. -- Paul (ganci at nurdog.com)
Reasonably Related Threads
- e2fsck: Bad magic number in super-block
- did CentOS x86 5.3 migrate to another hard drive, but console login keeps prompting even with correct password
- Raid 1 newbie question
- 4.2 install w/250GB raid arrays won't boot
- Sharing Partitions between Linux and Windows