Kernel Panic after latest update.

Bug #484099 reported by brettdonahue
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
New
Undecided
Unassigned

Bug Description

Hi,

          I restarted my computer after updating it, then it appeared a "Kernel Panic" message: "Kernel panic - not syncing: VFS: unable to mount root fs on unknown-block (8,1)". It doesn't even start in recovery mode. Ubuntu is installed in Windows, with Wubi. I need help to know if I can solve this error without having to reinstall Ubuntu.

Steps to reproduce
* Select Ubuntu from Windows Boot Manager
* Select Current Version of kernel or Recovery Kernel
* Wait 2 seconds, Kernel Panic.

This is the error message:
[Linux-bzImage, setup=0x3400, size=0x3bef40]
[Initrd, addr=0x3782d000, size=0x7c2a54]
[1.971919] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,1)

Other information,
* I have an HP XW4600 (Standard factory configuration, no additional firmware updates)
* PC is running 64 bit Vista with a WUBI install 30GB
* Ubuntu version is 9.10
* Grub Version 1.97~beta4

These are the commands in grub:
insmod ntfs
set root=(hd0,1)
search --no-floppy --fs-uuid --set 9ee01c97e01c782b
loopback loop0 /ubuntu/disks/root.disk
set root=(loop0)
linux /boot/vmlinuz-2.6.31-41-generic root=dev/sda1 loop=/ubuntu/disks/root.disk ro quiet splash
initrd /boot/initrd.img-2.6.31-14-generic

Any help is appreciated.
Brett

Philip Muškovac (yofel)
affects: ubuntu → linux (Ubuntu)
Revision history for this message
Enran (enran21) wrote :

 Hello I´m new in Ubuntu and I have the same problem that Brett after update, (Ubuntu 9.10 also installed by Wubi in Windows), but the message that I have is:

[1.314855] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,2)

One of the problems seems to be that the Current Version of kernel and the Recovery mode Kernel are the same (2.6.31-14):

Ubuntu, Linux 2.6.31-14-generic
Ubuntu, Linux 2.6.31-14-generic (recovery mode)

The recovery mode should be the previous -generic version (eg: 2.6.31-13), to start right before the update. Then I could start Ubuntu and solve the problem by removing the conflictive software.

Please HELP!!

Revision history for this message
Enran (enran21) wrote :

check for the possible solutions at:

https://bugs.launchpad.net/ubuntu/+bug/477169

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.