You are not currently logged in. If you do not have a user account then please consider creating one and logging in before you post your comment. This will allow you to track replies to your comment, and take part in the site much more freely.

To add your comment, fill in all the boxes below and then preview it to make sure you're happy with the way that it looks.

This is the comment you were replying to, attached to the article Software RAID5 and LVM with the Etch Installer:

#4 Re: Software RAID5 and LVM with the Etch Installer Posted by cef (59.167.xx.xx) on Fri 23 Mar 2007 at 02:23 If you mean that the boot drive won't boot, then it depends on what the failure is. If the drive is totally dead, and you have specificed in the bios the other drives as part of the boot order, you should be fine. If the drive is alive but corrupted, then you are pretty much seriously out of luck. This is the one real disavantage with software RAID. I could be wrong here, but I do not believe that GRUB actually knows too much about RAID, and may not know how to handle a non-fresh (eg: failed) disk in an array. Hence why I was suggesting to be cautious with rotating out sda1 in the axample above from an active drive to a spare, as the data will effectively still be on there, but it will be out of date. Note that is an artifact of Software RAID, not specifically the Linux implementation of same. BTW: I've had no problems with my software RAID 1's and 5's with the above setups, so I'm wondering what distro and versions of the kernel/raidtools you have, as that may explain some of the issues.

Username:	Anonymous
Title:
Your Comment:
Posting Format:	BBCode HTML Text Plain Text Textile

Inappropriate comments will be removed.

Username:

Password:

[ Advanced Login ]

Register Account