Comment 4 for bug 974765

Here are the results of the "debugging kernel boot." Due to the nature of the issue, the best I could do is camera shots.

If there is a trick in this situation for obtaining a full boot log, I would be interested to hear.

-------------------------------
Case 1: (default as per https://wiki.ubuntu.com/DebuggingKernelBoot)

recordfail
gfxmode text
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd0,msdos3)'
search --no-floppy --fs-uuid --set=root 862bcf01-fc44-4c29-8d08-f8be78763567
linux /boot/vmlinuz-3.2.0-22-generic root=/dev/sda3 ro

http://www.tshack.net/tmp/debug.jpg [158 KB]

-------------------------------
Case 2: (case 1 with raid=noautodetect)

recordfail
gfxmode text
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd0,msdos3)'
search --no-floppy --fs-uuid --set=root 862bcf01-fc44-4c29-8d08-f8be78763567
linux /boot/vmlinuz-3.2.0-22-generic raid=noautodetect root=/dev/sda3 ro

http://www.tshack.net/tmp/debug_noraidauto.jpg [187 KB]
-------------------------------

Note that using root=UUID=378367a0-4aac-4e08-b078-e708b24ac4d9 does not work either. For kernel 3.2.0-20, update-grub still generates root= using UUID on the kernel line. For 3.2.0.21+ update, root= is more explicitly specified using /dev/xxxyy entries for some reason. Neither specification works for kernels >= 3.2.0.21 on my system.

I will perform an upstream kernel build as soon as time permits.