On Mon, Jan 23, 2006 at 08:51:01PM +0100, Jack Malmostoso wrote: > Ok, this is funny. I doublechecked some things on my system, and here's a > couple of useful outputs: > > [EMAIL PROTECTED]:~$ cat /etc/mdadm/mdadm.conf > DEVICE partitions > ARRAY /dev/md2 level=raid1 num-devices=2 > UUID=9dae3f6b:a3e79fbb:6044c75b:9f1939bd > ARRAY /dev/md1 level=raid1 num-devices=2 > UUID=6f583480:58ae2560:eac2cfa7:882022da > ARRAY /dev/md0 level=raid1 num-devices=2 > UUID=877c34c4:dfed29c7:4338e75f:35082da1 > > So, /dev/md1 (the one created during installation for swap raid) exists, > but: > > [EMAIL PROTECTED]:~$ dmesg | grep md1 > md: md1 stopped. > > I asked myself why: > > [EMAIL PROTECTED]:~$ sudo /sbin/mdadm -Q /dev/md1 > Password: > /dev/md1: is an md device which is not active > /dev/md1: is too small to be an md component. > > And mdstat says: > > [EMAIL PROTECTED]:~$ cat /proc/mdstat > Personalities : [raid1] > md2 : active raid1 sda3[0] sdb3[1] > 229046656 blocks [2/2] [UU] > > md0 : active raid1 sda1[0] sdb1[1] > 14651136 blocks [2/2] [UU] > > unused devices: <none> > > I looked for bugs on Debian and this one looks quite right (and soooo long > to read): > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=294404
Yeah, udev and raid have a few problems to work out, although it works pretty well now. Mostly. For md0 anyway. I had a problem where my machine got power-outed, and when I booted it back up, the md0 raid device (root device) was running degraded. I never got the email, either ~:^) The tip off was that I was very used to the super fast read performance, which wasn't there anymore. When the box seemed "slow" I started poking around for the reason. Bottom line, you have to check your raid devices after a boot to make sure they're all up and running correctly. Cheers, a -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
