Yes. The bug is present in Edgy.. I haven't tried upgrading to Feisty
yet.
I created a raid array:
mdadm --create -l5 -n 14 /dev/md10 /dev/sd[bcdfghijklqrst]1
Added it to /etc/mdadm/mdadm.conf:
[EMAIL PROTECTED]:/# cat /etc/mdadm/mdadm.conf
DEVICE partitions
ARRAY /dev/md0 level=raid1 num-devices=2
UUID=75fa8aad:ebad7171:fab782c2:128dd001
ARRAY /dev/md1 level=raid1 num-devices=2
UUID=4962386b:4220a6b0:52362aed:e8177a98
ARRAY /dev/md2 level=raid1 num-devices=2
UUID=211c8f5b:d8854afd:33626b06:0fce6c77
ARRAY /dev/md3 level=raid1 num-devices=2
UUID=a389ea68:820de8ac:50f8d391:6a1e5bfc
ARRAY /dev/md4 level=raid1 num-devices=2
UUID=4d4021dc:5a1d718e:c72beddc:a40274b6
ARRAY /dev/md5 level=raid1 num-devices=2
UUID=aaeb5e70:58768c4f:b218283e:86a35d4c
ARRAY /dev/md10 level=raid5 num-devices=14
UUID=b68f200f:c99aa697:ec26162e:580f6e07
Rebuilt my initramfs (not sure if this is actually necessary or not):
update-initramfs -k all -u
Added it to /etc/fstab:
[EMAIL PROTECTED]:/# fgrep export /etc/fstab
UUID=378b2a0d-66f6-4228-9772-6edc387b2dad /export ext3 defaults
0 2
But it still gets started as /dev/md6:
[EMAIL PROTECTED]:/# cat /proc/mdstat
Personalities : [raid1] [raid5] [raid4]
md6 : active raid5 sdb1[0] sdt1[13] sds1[12] sdr1[11] sdq1[10] sdl1[9] sdk1[8]
sdj1[7] sdi1[6] sdh1[5] sdg1[4] sdf1[3] sdd1[2] sdc1[1]
462172672 blocks level 5, 64k chunk, algorithm 2 [14/14] [UUUUUUUUUUUUUU]
... (md0-md5 pruned for brevity)
While everything DOES gets started and mounted correctly using the
UUIDs, if I set a RAID volume to start up as /dev/md10, it's my belief
that it should remain there after rebooting even if it uses the UUIDs to
start them.
--
initramfs/mdrun doesn't honor preferred minor when starting RAID volumes
https://bugs.launchpad.net/bugs/49914
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
