Ubuntu 10.04 RAID/grub blues continue:

I returned back to my server and decided to upgrade to the new kernel,
from ...-23 to ...-24, now:

r...@thor:~# uname -a
Linux thor 2.6.32-24-generic #39-Ubuntu SMP Wed Jul 28 05:14:15 UTC 2010 x86_64 
GNU/Linux

The opposite scenario (see the description above) happened:

my system now boots from /dev/sdd (not from /dev/sda as previously in
...-23)

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Ubuntu, with Linux 2.6.32-24-generic' --class ubuntu --class 
gnu-linux --class gnu --class os {
        recordfail
        insmod ext2
        set root='(hd3,2)'
        search --no-floppy --fs-uuid --set e29745e3-11df-4986-87a0-c018462ec99d
        linux   /boot/vmlinuz-2.6.32-24-generic 
root=UUID=e29745e3-11df-4986-87a0-c018462ec99d ro   quiet splash
        initrd  /boot/initrd.img-2.6.32-24-generic


r...@thor:~# df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/sdd2             31720384   8341092  21767980  28% /
none                   8228800       388   8228412   1% /dev
none                   8233444       820   8232624   1% /dev/shm
none                   8233444       344   8233100   1% /var/run
none                   8233444         0   8233444   0% /var/lock
none                   8233444         0   8233444   0% /lib/init/rw
/dev/sdd1             31215552  11340452  18263836  39% /CentOS_5.5
/dev/sdd4             57743556  10632936  44130064  20% /home

/dev/sdb1, /dev/sdc1, /dev/sdd1, which were (see above) in ...-23 my
raid devices are not any more:

 r...@thor:~# !520
mdadm --misc --examine /dev/sda1
mdadm: No md superblock detected on /dev/sda1.
r...@thor:~# mdadm --misc --examine /dev/sdb1
mdadm: No md superblock detected on /dev/sdb1.
r...@thor:~# mdadm --misc --examine /dev/sdc1
mdadm: No md superblock detected on /dev/sdc1.
r...@thor:~# mdadm --misc --examine /dev/sdd1
mdadm: No md superblock detected on /dev/sdd1.
r...@thor:~# mdadm --misc --examine /dev/sdc
mdadm: No md superblock detected on /dev/sdc.

Like I said, in 10.04 RAID arrays survive from one kernel update to the other,
which seems a severe problem.

Could please anyone knowledgeable triage this bug to a proper place so
as an appropriate action can be taken? Thanks!

-- 
 GRUB writes to wrong MBR and destroys RAID setup
https://bugs.launchpad.net/bugs/601305
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to