Ubuntu
linux package

linux 2.6.31.16 unable to boot, kernel panic unable to mount rootfs on unknown block

Bug #494654 reported by TobiasDomhan on 2009-12-09

This bug affects 6 people

Affects		Status	Importance	Assigned to	Milestone
	OEM Priority Project	Invalid	Undecided	Unassigned
	linux (Ubuntu)	Expired	High	Unassigned

Bug Description

I recently installed linux kernel version 2.6.31.16. which will not boot. right after grub I get the following error:
"kernel panic not syncing vfs. unable to mount root fs unkown block (0,0)"

2.6.31.15 worked and still works like it should.

I attached a screenshot of the problem.

ProblemType: Bug
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/pcmC0D0p: tobi 3152 F...m pulseaudio
/dev/snd/controlC0: tobi 3152 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf0600000 irq 22'
   Mixer name : 'Realtek ALC1200'
   Components : 'HDA:10ec0888,10250121,00100101 HDA:14f12c06,10250121,00100000'
   Controls : 24
   Simple ctrls : 14
Date: Wed Dec 9 19:32:16 2009
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=5e3cf18a-301d-415b-bdf9-4f0ce615b2a8
MachineType: Acer, inc. Aspire 5920G
NonfreeKernelModules: nvidia
Package: linux-image-2.6.31-16-generic 2.6.31-16.52
ProcCmdLine: root=UUID=4cbaf128-5166-43a5-afcc-b668a8030dbb ro quiet splash
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-15.50-generic
RelatedPackageVersions:
linux-backports-modules-2.6.31-15-generic N/A
linux-firmware 1.25
SourcePackage: linux
Uname: Linux 2.6.31-15-generic x86_64
WpaSupplicantLog:

dmi.bios.date: 05/22/2007
dmi.bios.vendor: Acer
dmi.bios.version: v0.3508
dmi.board.name: Chapala
dmi.board.vendor: Acer, Inc.
dmi.board.version: Not Applicable
dmi.chassis.type: 1
dmi.chassis.vendor: Acer, Inc.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAcer:bvrv0.3508:bd05/22/2007:svnAcer,inc.:pnAspire5920G:pvrNotApplicable:rvnAcer,Inc.:rnChapala:rvrNotApplicable:cvnAcer,Inc.:ct1:cvrN/A:
dmi.product.name: Aspire 5920G
dmi.product.version: Not Applicable
dmi.sys.vendor: Acer, inc.

Tags:

Revision history for this message

TobiasDomhan (tdomhan) wrote on 2009-12-09:

screenshot of the bug Edit (424.8 KiB, image/jpeg)
AlsaDevices.txt Edit (585 bytes, text/plain; charset="utf-8")
AplayDevices.txt Edit (277 bytes, text/plain; charset="utf-8")
ArecordDevices.txt Edit (274 bytes, text/plain; charset="utf-8")
BootDmesg.txt Edit (56.8 KiB, text/plain; charset="utf-8")
Card0.Amixer.values.txt Edit (2.6 KiB, text/plain; charset="utf-8")
Card0.Codecs.codec.0.txt Edit (10.9 KiB, text/plain; charset="utf-8")
Card0.Codecs.codec.1.txt Edit (146 bytes, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (4.2 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (1.2 KiB, text/plain; charset="utf-8")
IwConfig.txt Edit (602 bytes, text/plain; charset="utf-8")
Lspci.txt Edit (16.5 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (949 bytes, text/plain; charset="utf-8")
PciMultimedia.txt Edit (605 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.4 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.6 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (4.3 KiB, text/plain; charset="utf-8")
RfKill.txt Edit (124 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (128.9 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (238.0 KiB, text/plain; charset="utf-8")
WifiSyslog.txt Edit (2.9 KiB, text/plain; charset="utf-8")
XsessionErrors.txt Edit (971 bytes, text/plain; charset="utf-8")

Leann Ogasawara (leannogasawara) on 2009-12-11

Changed in linux (Ubuntu):
importance:	Undecided → High
status:	New → Triaged
tags:	added: regression-update

Revision history for this message

Leann Ogasawara (leannogasawara) wrote on 2009-12-11:

Hi Tobias,

Can you quickly confirm this remains with the 2.6.31-16.53 kernel which was recently released. You can verify the specific version of the kernel you are running with 'cat /proc/version_signature'. Thanks.

Revision history for this message

TobiasDomhan (tdomhan) wrote on 2009-12-11:

I now get further, than this error. I don't now if this is because of an update oder because I reinstalled the kernel package.

Now I see the white ubuntu logo on a blackscreen, some time after that a initramfs shell is presented to me.

Revision history for this message

Andy Young (a-c-joven) wrote on 2009-12-14:

Workaround: appending rootdelay=10 onto the kernel's GRUB options solved the problem for me. I guess the VFS partition isn't available early enough in the boot sequence for the *-16 kernel.

(ESC during bootup, press 'e' on *-16 kernel, press 'e' on "kernel..." line, append 'rootdelay=10' to kernel options, 'ENTER', then 'b')

Revision history for this message

Stefan Bader (smb) wrote on 2009-12-14:

Is likely as Andy suggested. There is also a BIOS bug present (_GTF (get task file) returns an integer and not a buffer), but that might just be coincidence. Tobias, please let us know whether the rootdelay helps. Alternatively when you get dropped into the shell check with dmesg, whether sda is present (or look for the /dev/sda7 entry). If that shows up, say exit and the boot should go on.
With a successful boot, also add the dmesg of that to this bug.

Andy Whitcroft (apw) on 2009-12-15

tags:

added: karmic

Revision history for this message

TobiasDomhan (tdomhan) wrote on 2009-12-15:

screenshot of the bug Edit (446.5 KiB, image/jpeg)

I added the rootdelay=10 to the kernel parameters in grub.
Now the kernel doesn't find my harddisk.

Revision history for this message

zed01 (ferqi01) wrote on 2010-02-14:

Hi!

I installed it wubi Ubuntu 9.10 version my AMD machine. Some weeks of usage this was receiving when in I wanted it to boot from him:

Kernel Panic VFS: unable to mount root fs on unknown-block (8,1)

I rehearsed the replanting, but the mistake recurred. It was the solution temporarily that I put it up likewise the wubi Kiwilinux, this works correctly. Probable the wubi and the grub 2 incompatible ones.

Greeting

Revision history for this message

zed01 (ferqi01) wrote on 2010-02-14:

...9.04 Kiwilinux....

Revision history for this message

quequotion (quequotion) wrote on 2010-03-14:

Could gdm failure be related to this bug? The 2.6.32-16 kernel from dnjl's ppa fails to boot and I get a mangled screen where I should see the gdm login. CTRL+ALT+DEL reboots the machine, and the system still responds to ACPI shutdown from the power switch. Booting without splash doesn't produce much output (in fact it might be that several steps of the booting process do not happen) I'll try to boot with more verbose output later and see if I can find the same error message as above...

Revision history for this message

Tony Espy (awe) wrote on 2010-03-31:

#10

I just ran into this yesterday on an OEM machine ( AMD Nile CPU, 5400RPM HDD, 2GB RAM ). Lucid was running fine on this machine, I than ran a full update last night, re-booted and hit this bug.

I just tried the suggested workaround ( rootdelay=10 ) and it still fails with the same kernel panic on boot:

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

Changed in oem-priority:
importance:	Undecided → Critical

Revision history for this message

Tony Espy (awe) wrote on 2010-03-31:

#11

I forgot to mention that the machine I'm running now has 2.6.32-18 installed. I tried to boot using 2.6.31-16, but that also failed in a different manner.

Revision history for this message

Tony Espy (awe) wrote on 2010-03-31:

#12

Quick update... I just installed today's daily build and the problem no longer occurs.

So, this was either caused by my upgrade ( which was partial... I left that part out ) *OR* the fact that the fglrx driver was activated.

I will activate fglrx next and see if the problem re-occurs.

Revision history for this message

Tony Espy (awe) wrote on 2010-03-31:

#13

OK, just enabled fglrx and the system still boots ( although there seem to be other issues with fglrx ).

Marking oem-priority task as Invalid.

Changed in oem-priority:
status:	New → Invalid

Brian Murray (brian-murray) on 2010-04-01

Changed in oem-priority:
importance:	Critical → Undecided

Revision history for this message

Gaston Boisvet (boisvgg) wrote on 2010-04-07:

#14

Hi,
I have the same problem with 2.6.31.20
Kernel panic - not syncing:VFS: Unable to mount root.fs on unknown block (8,19).
Using amd 64 with 3 Gb memory windows XP home sp3
Same thing with XP pro

Revision history for this message

Hugo Luiz Cruz (hugoluizcruz) wrote on 2010-04-22:

#15

Hi, repent the same with me on kernel 2.6.32-21, but I have also backtrack 3 installed in same HD and it show the same message.

Revision history for this message

Tobias Krais (tux-spam) wrote on 2010-10-20:

#16

Same here, but on i386...

tags:

removed: amd64

Revision history for this message

Brad Figg (brad-figg) wrote on 2011-04-15:

#17

@TobiasDomhan

There have been a number of updates to the karmic kernel since this bug was originally filed. Can you confirm that this issue still exists?

Changed in linux (Ubuntu):
status:	Triaged → Incomplete

Revision history for this message

TobiasDomhan (tdomhan) wrote on 2011-04-15:

#18

I can't really test this. I'm currently using a freshly installed maverick.
never had this issue in maverick though.

Revision history for this message

Launchpad Janitor (janitor) wrote on 2011-06-15:

#19

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status:	Incomplete → Expired

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

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

Ubuntulinux package

linux 2.6.31.16 unable to boot, kernel panic unable to mount rootfs on unknown block

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
linux package