Comment 22 for bug 631795

OK, here's what I did.
Managed to get the system running by doing a rescue from the alternate install CD. Dropped into a root session, installed as much packages from ubuntu-desktop by hand (several attempts) and rebooted. At first I got the same errors, but to my surprise when I left it standing for a while, it got on with a reasonably normal boot and a X/Gnome login. Had to go back to the CD and re-add myself as user. Could log on then, but with no sudo or other rights. Back to the CD and added myself to sudoers and admin group.
This was all on kernel 2.6.35.19.

Yesterday I saw kernel 2.6.35.20. arrive. Updated, rebooted and found that it wouldn't boot. Lots of errors on udev and the kernel disagreeing about devices called dm-5, dm-2 etc ,then busibox from initramfs. So rebooted with 2.6.35.19 which worked.
This morning there was an update to udev, which rang a bell with this bug (I thought). Installed it, rebooted 2.6.25.19, all fine. Decided to reinstall 2.6.35.20, in order to force update-initramfs on that kernel as well. Install didn't really work out without errors, but could boot kernel 2.6.35.20. In fact running it right now.

Apart from the kernel install failing partly, update-grub starts complaining now as well about not being able to find its devices:
====
thomas@tomdesktop:~$ sudo update-grub
[sudo] password for thomas:
Generating grub.cfg ...
/usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/mapper/pdc_jcchiiab5. Check your device.map.
====

I can not really reproduce this error, and I'm not sure whether it's the kernel, udev, dmraid or grub that's not working well, or all of them not playing nice. I do know however that booting off a dmraid set has been very broken since 10.04 (which is a LTS).

I'll be checking on this whenever I feel I see something relevant, and do my updates twice a day. I'll try the latest kernel some time next weekend and report on that.

If there's anything else, like more log files, let me know.

cheers
Tom