With no surprise the update from Interpid Ibex to** Jaunty Jackalope** was not as easy as I hoped. After booting the fresh 2.6.28 kernel I was welcomed with “Press enter for maintenance (or type Control-D to continue)” and errors when trying to mount my RAID0. After some investigations found that the devices are now named md_d* and there are some devices in /dev/md/. Because of this change I had to do the following things to get my raid up and running:
- Reassemble the raid (check if it is inactive with less /proc/mdstat) – in my case the command looked like this:
mdadm --assemble /dev/md_d1 /dev/sdb2 /dev/sda5
mdadm --detail --scan >> /etc/mdadm/mdadm.conf
and comment your previous ARRAY definition in the config file- Modify
/etc/fstab
if needed
Also if DKMS fails to build the new NVIDIA driver be sure to check that you have installed the headers files (the upgrade process did not install them for me).
Again : I’m NOT responsible for any damage or data loss you might experience. Backup often, backup soon!
Comments
Comment by steve on 2009-04-24 18:49:07 +0300
I’m in the same boat, but… I have no references to /dev/md0 in /etc/mdadm/mdadm.conf – in fact, aside from comments, it is quite empty.
Using mdadm -As finds the array, but brings it up with only 1 disk (i’m using raid-1)
Ideas?
Comment by steve on 2009-04-24 19:11:56 +0300
Found solution! Work around is posted in following bug report:
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/330298
Comment by Hans Jørgen on 2009-04-24 20:20:42 +0300
BIG thanks :-)
Comment by Hety on 2009-04-26 16:38:01 +0300
/HUG Спасибо большое. Не Бог весть какая трабла, но меньше воскресного времени ушло на эту фигню :)
Comment by Josh on 2011-01-05 07:05:35 +0300
Thanks! Saved my day!