Raid 1 problem

volvoguy volvoguy at gmail.com
Mon Aug 29 14:07:58 UTC 2005


On 8/29/05, Dennis Kaarsemaker <dennis at kaarsemaker.net> wrote:

> The OP (me) was a bit too nervous to sound all comprehensive all the
> time. The problem seems to be (according to the bugreports in the ubuntu
> and debian BTSes) that device nodes are created too late and mdadm gets
> confused by that. Adding a 'sleep 3s' to the appropriate initscript
> works around this problem for me. Not too elegant, but it works.
> 
> By the way: I am not booting from raid :)

I'm going to have to keep an eye on that bug. Because of my success
with the RAID1 storage space, I was going to convert more of the
system to RAID as well. I have a demo machine running Breezy that has
everything but /boot and swap on an array and so far it performs
great. It seems like booting from the RAID array is a lot more
complicated (unless you can just point GRUB at one of the disks in a
RAID1 array to boot?). The hand-me-down fileserver (I seem to get lots
of hand-me-downs) seems ideal for using RAID for the majority of the
system, as it has two identical ultra-whatever SCSI drives in it. When
I got the machine I wasn't sure what I was going to do with it, so
Win2k is currently on the second SCSI disk but needless to say, I've
only booted into Windows once. :o)

Hopefully RAID support will be even better when Breezy is final. I may
just have to move Windows on my main workstation to an older IDE drive
and use Breezy with the SATA RAID controller. :o)

*Power outages are notorious here, so the more redundancy, the better!

-- 
Aaron

Ubuntu SVG Artwork - www.volvoguy.net/ubuntu
-------------------------------------------------------------------------------
Art, like morality, consists of drawing the line somewhere. ~ G.K. Chesterton


More information about the ubuntu-users mailing list