The last kernel upgrade (I think it was 2.6.31-21) installed without
problem so I'd say whatever the problem was has been fixed.
--
Boot failure after kernel upgrade, unable to mount root fs
https://bugs.launchpad.net/bugs/517638
You received this bug notification because you are a member of
** Changed in: linux (Ubuntu)
Status: Incomplete = Fix Released
--
Boot failure after kernel upgrade, unable to mount root fs
https://bugs.launchpad.net/bugs/517638
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Hi Brian,
This bug was reported a while ago and there hasn't been any activity in it
recently. We were wondering if this is still an issue? Can you try with the
latest development release of Ubuntu? ISO CD images are available from
http://cdimage.ubuntu.com/releases/ .
If it remains
I was able to solve the problem by simply reinstalling the kernel
package but after another kernel update it's broken again so there seems
to be a problem with the kernel install process. Is there something I
can check for to find out what hasn't installed correctly?
--
Boot failure after kernel
The kernel panic error message reads:
VFS: Unable to mount root fs on unknown-block(8,2)
--
Boot failure after kernel upgrade, unable to mount root fs
https://bugs.launchpad.net/bugs/517638
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
If I boot using the recovery mode grub menu entry I get to see a bit
more. Before the kernel panic I get:
RAMDISK: gzip image found at block 0
uncompression error
List of all partitions:
0800312571224 sda driver: sd
08012096451 sda1
0802 310472190 sda2
0b00 1048575 sr0 driver: sr
No
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/38796375/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/38796377/AplayDevices.txt
** Attachment added: ArecordDevices.txt
http://launchpadlibrarian.net/38796378/ArecordDevices.txt
