|
Home > Archive > Linux Debian support > June 2006 > Why is mdadm.conf ignored on Kubuntu?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Why is mdadm.conf ignored on Kubuntu?
|
|
| Daniel Buus 2006-06-20, 1:12 pm |
| Hey there 
Really puzzled by this. I had md0 used for /, md1 used for /boot, and
md2 used for swap space. Worked fine.
Okay, so I'm setting up additional arrays using mdadm. I create md5, 6,
7, and 8, and reboot just to make sure things are still up to code. I
get a shell as the system won't boot. I check out my arrays, and
suddenly md0 is no longer the old / array, but one of the newer ones,
which aren't even formatted. So, I edit fstab to use "LABEL=/" and
"LABEL=/boot" instead of hard paths to determine what to mount where.
This lets me boot the system ok, but I still can't figure out how to
tell mdadm where to assemble what array. The arrays are still assigned
randomish numbers under /dev/md*. I'm going to use md5 thru md20 for
RAID5 arrays and use those for an LVM2 volume, and I would really
prefer it if I could set it up so that I know exactly what array is
where, just from the number, and be sure that it won't juggle them
around, should I choose to make some change somewhere.
I edited mdadm.conf to look like this,
DEVICE partitions
ARRAY /dev/md2 level=raid1 num-devices=2
UUID=ea2a365f:583bca30:acdfe40d:d5ec5dc3
ARRAY /dev/md1 level=raid1 num-devices=2
UUID=56a5fb98:72ac6d7d:1bf0aa25:911457ad
ARRAY /dev/md0 level=raid5 num-devices=3
UUID=f71c5d0c:aa49c676:040e18cb:05985f6e
ARRAY /dev/md5 level=raid5 num-devices=7
UUID=1f6133f1:e7fd76f3:c351bf78:0dad0ec3
ARRAY /dev/md6 level=raid5 num-devices=7
UUID=f6d5819a:22cf8e4d:b22a89da:cab84bdf
ARRAY /dev/md7 level=raid5 num-devices=7
UUID=55353e69:d71df70d:ae1d03aa:3854bcb4
ARRAY /dev/md8 level=raid5 num-devices=7
UUID=2e3bfc0a:5756a312:f1f44515:53d451ef
- but the arrays still aren't assembled as instructed here. Why not?
man mdadm.conf doesn't say anything about mdadm.conf being ignored or
me having to update something for it to work on a subsequent boot...
I'm confused, please help
Thanks in advance,
Daniel
| |
| Lars Boegild Thomsen 2006-06-21, 1:12 am |
| Daniel Buus wrote:
> Really puzzled by this. I had md0 used for /, md1 used for /boot, and
> md2 used for swap space. Worked fine.
Assuming that Kubuntu works a bit like Debian you probably have to rebuild
your initrd image.
--
Lars
| |
| Daniel Buus 2006-06-21, 7:15 am |
|
Lars Boegild Thomsen wrote:
> Daniel Buus wrote:
>
> Assuming that Kubuntu works a bit like Debian you probably have to rebuild
> your initrd image.
>
Hey Lars, thanks for your reply
Is there a howto on this that you know of?
Cheers,
Daniel
> --
> Lars
|
|
|
|
|