Wubi/Karmic boot: kernel panic - not synching: VFS

Bug #477169 reported by Gergely Imreh on 2009-11-07
276
This bug affects 62 people
Affects Status Importance Assigned to Milestone
Wubi
Undecided
Sriram
Nominated for 8.04 by Brianubuntu
Nominated for 8.10 by Brianubuntu
Nominated for 9.04 by Brianubuntu
Nominated for Trunk by Brianubuntu
lupin (Ubuntu)
Undecided
Colin Watson
Karmic
Undecided
Unassigned

Bug Description

I was using Karmic, installed with Wubi. For a week it worked like a charm, and I updated it with the latest fixes.
Since about 3 days ago every boot fails with kernel panic

Going without the "--quiet" option, the message is:

No filesystem could be mounted, tried: ext3 ext2 ext4 fuseblk
Kernel-panic - not syncing : VFS : Unable to mount root fs on unknown-block(0,6)

Eg. the grub entry for for the standard boot reads:
insmod ntfs
set root=(hd0,6)
search --no-floppy --fs-uid --set a2a40b74a40b4a6d
loopback loop0 /ubunu/disks/root.disk
set root=(loop0)
linux /boot/vmlinuz-2.6.31-14-generic root=/dev/sda6 loop=/ubuntu/disks/root.disk ro quiet splash
initrd /boot/initrd.img-2.6.31-14-generic

My /ubuntu directory is on (hd0,6). If I use the grub command line, I can:
- see the contents of the drive
- mount the root.disk as a loopback device and see its contents
- can find the files referenced in the menu.lst

Any ideas how to make it work again?
I had a previous install of Wubi/Karmic-rc, upgraded in place that had some kernel panics too after a few weeks of usage, but I just reinstalled it so not sure if it had the same issue.

ZliS (zlis) wrote :

I have this bug too, tried to reinstall, but after full update it caused again...
Affected 2 computers...

Agostino Russo (ago) wrote :

Can you manually mount sda6?
It could be that the ntfs partition is corrupted, boot into windows, run `chkdsk /r` within the drive where you installed wubi, check that C:\ubuntu\disks\root.disk is still there, and try to reboot into Ubuntu.

2009/11/9 Agostino Russo <email address hidden>:
> Can you manually mount sda6?
> It could be that the ntfs partition is corrupted, boot into windows, run `chkdsk /r` within the drive where you installed wubi, check that C:\ubuntu\disks\root.disk is still there, and try to reboot into Ubuntu.

The ntfs partition seems to be completely fine, windows works without a hitch.
In grub console I can do all the steps that are in the grub.cfg:
loopdevice, linux, initrd... (and it finds the files just fine, I can
see the contents of the whole drive in the the grub console with "ls
/"). But then boot fails.

Shouldn't there be ntfs listed in the "tried:" section?

Agostino Russo (ago) wrote :

Is this a grub error or a linux one? I understood it was the latter.
To be more precise I understood that from grub, without any change, you are able to load the Linux kernel and initrd, but the initrd scripts cannot locate the root device.

So I would expect you to end up in a busybox shell within linux (not grub).
In there can you try to mount the windows partition?

ZliS (zlis) wrote :

Can i ask a question, do you have a 64-bit architecture too?

Dave Morley (davmor2) wrote :

Running a 64 bit test now although I have a feeling that this could be the recent updates to grub but will check once installed

ZliS (zlis) wrote :

I used x86-64 on both computers, besides I see that few users have this problem (and i think the most of wubi users use x86).

Sorry for mistakes, i know Russian better=)

Dave Morley (davmor2) wrote :

Meh No issues here everything is running fine sorry :(

Gergely Imreh (imrehg) wrote :

I'm using i386 image (an older AMD)

>Is this a grub error or a linux one? I understood it was the latter.
> To be more precise I understood that from grub, without any change, you are able to load the Linux kernel and initrd, but the initrd scripts cannot locate the root device.

the "linux" and "initrd" commands work, I can load the files (and it returns with the values that it succeeds). But when the "boot" runs, finds sda6 (the one it supposed to), but throws a "kernel panic".....

Using a new install, separate directory, same wubi type of loopback device mount, exactly the same commands the bootup just works...

> So I would expect you to end up in a busybox shell within linux (not grub).
> In there can you try to mount the windows partition?

That's not the case at all...
the gnu grub 1.97~beta4 that is installed by ubuntu can give me a shell, with a prompt like
sh:grub>

This shell, however don't have the "mount" option at all... I can set the root of the system I'm checking (with "set root=(device)"), so I can find the files on the windows partitions as well as on the /ubuntu/disks/root.disk loopback device....

Anything else that I can check?

Agostino Russo (ago) wrote :

Gergely, I am well aware that grub has a built in shell you can always use, but what is relevant is what shell you end up into once you have your error.

If after the error you end up in a grub shell it means it is a grub issue. If you end up in a busybox shell it means it is a filesystem/initrd issue. Because the error you mentioned is about a kernel panic, I would expect a filesystem/initrd issue.

If so, you should be able to reproduce the error within the LINUX busybox shell, by issuing the same commands that made the initrd fail (basically try to mount the ntfs partition). Those commands happen to be similar to the ones you mentioned for the grub shell, but they are actually performed by the Linux kernel within a Linux environments, as opposed to being performed by grub.

Gergely Imreh (imrehg) wrote :

2009/11/9 Agostino Russo <email address hidden>:
> Gergely, I am well aware that grub has a built in shell you can always
> use, but what is relevant is what shell you end up into once you have
> your error.

Since it is a kernel panic, there is no shell at all....
As much as I can see the log (the screen does not scroll), it finds
the relevant partitions, and gives the above message, blinks the
scroll-lock and caps-lock lights on the keyboard indefinitely, and
nothing more.... Next: hard reboot.

> If after the error you end up in a grub shell it means it is a grub
> issue. If you end up in a busybox shell it means it is a
> filesystem/initrd issue. Because the error you mentioned is about a
> kernel panic, I would expect a filesystem/initrd issue.

It is not in a grub shell and not in busybox either. Running the boot
scripts then kernel panic. Nothing interactive about it.

> If so, you should be able to reproduce the error within the LINUX
> busybox shell, by issuing the same commands that made the initrd fail
> (basically try to mount the ntfs partition).

The problem is that no partitions are mounted, or I'm misunderstanding
the above error message?
If it would mount the ntfs volume, then it can do the loop device,
then it can do the whole process. But it kernel panics, because it
cannot mount, because it does not try ntfs, just: ext2, ext3, ext4,
fuseblk.....

> Those commands happen to be
> similar to the ones you mentioned for the grub shell, but they are
> actually performed by the Linux kernel within a Linux environments, as
> opposed to being performed by grub.

Not sure what you mean, because I don't even get a workable system to
start with.... Hard frozen every time.

Agostino Russo (ago) wrote :

The fact that it is frozen is relevant information.
I will check later on, but I do not think that the inability to mount the root file system will freeze the system.

Kech (kech) wrote :

I have the same problem with Wubi after update 9.10

gissi (zerinol) wrote :

Installed with wubi 9.10 and all semms to work fine. After an upgrade (apt-get upgrade) impossible to boot: kernel panic.... Need a rapido solution I cannot install once a day!

Agostino Russo (ago) wrote :

gissi, kech, does the system completely freeze AFTER the linux kernel is loaded?

Kech (kech) wrote :

Agostino Russo, YES! You can see my small video http://file.qip.ru/file/107310806/60bb36d6/MOV00820.html

Alexis Gaitan (alexistkd) wrote :

Same here Kernal panic not syncing VFS unable to mount root fs on unknown-block(8,2) Running windows 7 with wubi ubuntu 9.10 please someone have an solution for this? i dont want to reinstall i will lost everything :(

Thanks in advance.

Gergely Imreh (imrehg) wrote :

Agostino: okay, my bad, I assumed that all kernel panics are complete freezes. Yes, it works the very same way as on the video (booting the "recovery" version gives some more information), as I said in the original submission:
* kernel loaded well
* initrd loaded well
* boot started
* found correct partitions
* could not load root partition -> kernel panic -> freeze

Agostino Russo (ago) wrote :

Did you try to run chckdsk /r from windows?

Kech (kech) wrote :
Agostino Russo (ago) wrote :

Kech there is a call trace in there, but I cannot read it from the video, can you post it here please?

-S3B4- (jdlr07) wrote :

I have the same problem. I'm running Ubuntu 9.10 whit Wubi on Windows 7 system. This problem appeares after my Ubuntu updated past monday (09/11). It's the same problem that was shown on the video you posted!

I'm afraid I'm gonna loose all my data and I will have to resign and install Ubuntu 9.10 on a clean partition (not whith Wubi...)

ZliS (zlis) wrote :

I installed x86 and now all work fine. This problem only on 64-bit wubi systems.

-S3B4- (jdlr07) wrote :

I'm afraid not. I have installed an x86 distribution and the problem is also here

ZliS (zlis) wrote :

Hmm, i have interesting situation. I reinstalled ubuntu x86, updated to newest versions, it was working after restart... Then i installed additional repos (with ubuntu-tweak), added ubuntu-studio package, flashplayer, proprietary amd video drivers and have a kernel panic again.

Kech (kech) wrote :

Agostino Russo, i'l try. There the same video in best quality http://zalil.ru/upload/28191179

garik (garikgarik) wrote :

I have the same "kernel panic" unbootable Karma Koala (ubuntu-9.10-desktop-i386.iso) on windows XP computer with wubi.
Problemn is the same as on video above.
Thanks Igor
I have Installed recommended updates last night.

Gergely Imreh (imrehg) wrote :

Agostino: chkdsk /r on the partition does not make any difference.

ZliS: definitely not, both installs that broke for me this way were x86, I think it works for you now, because the problem package must been fixed in the meantime, so if you do a reinstall + update to the newest packages, then you don't have a problem.
The problem is to know what caused the kernel panic so not to repeat the same thing again later.

-S3B4-: if you can keep your root.disk file somewhere else, then you won't lose your data. When you reinstall things, there are easy ways to mount your root.disk in the working system so you can backup.

garik (garikgarik) wrote :

-S3B4 are you 100% sure?

ZliS (zlis) wrote :

Yes, i just tried to understand, what caused the problem: original packages or third-party.

garik (garikgarik) wrote :

does somebody need grubcnfg or initrd.img-2.6.31-14-generic or other files from boot folder?

garik (garikgarik) wrote :

I have read carefully wubiguide.

followed steps from chapter "How can I access my Wubi install and repair my install if it won't boot?"
ubuntu@ubuntu:~$ sudo fsck /win/ubuntu/disks/root.disk
fsck from util-linux-ng 2.16
e2fsck 1.41.9 (22-Aug-2009)
/win/ubuntu/disks/root.disk: recovering journal
/win/ubuntu/disks/root.disk: clean, 194774/1073152 files, 2092983/4286464 blocks

garik (garikgarik) wrote :

OK, so you guys are sure that saving root.disc will save data. But this root.disc is about 16.4 gb. Is it the only way to rescue data (pictures for example)?
Thanks

Gergely Imreh (imrehg) wrote :

2009/11/12 garik <email address hidden>:
> OK, so you guys are sure that saving root.disc will save data. But this root.disc is about 16.4 gb. Is it the only way to rescue data (pictures for example)?

You can boot from the Ubuntu CD, and mount your root.disk as a
loopback device, save all the data you want (on another partition or
USB ), then delete the root.disk...

The "How can I access my Wubi install and repair my install if it
won't boot?" you can also do by booting from the Ubuntu CD. I got to
try that method too, see what happens.

Agostino Russo (ago) wrote :

Kech I cannot see your last video. Can someone please boot in recovery mode and post the call trace?

garik (garikgarik) wrote :

Hi Agostino,
pls, if you provide me with how to, i'll be glad to post the call trace.
Thanks

garik (garikgarik) wrote :
garik (garikgarik) wrote :
garik (garikgarik) wrote :
Kech (kech) wrote :

Agostino Russo, say please how can i pause the booting to make screenshot.

Sriram (ultimatevikrant) on 2009-11-21
Changed in wubi:
assignee: nobody → Sriram (ultimatevikrant)
Changed in wubi:
status: New → Confirmed
Colin Watson (cjwatson) on 2009-12-01
affects: ubuntu → lupin (Ubuntu)
Colin Watson (cjwatson) on 2009-12-01
Changed in lupin (Ubuntu):
assignee: nobody → Colin Watson (cjwatson)
status: New → Fix Committed
187 comments hidden view all 267 comments
meow81 (whocares) wrote :

when will be available the next kernel version linux-image-2.6.31-17-generic ?

Confirming result of wubildr patch - .16 kernal boots without any further issues. Did not need to ferk around with insmod.

Thanx to all who helped out via this thread and elsewhere.

Is it now safe to take further upgrades?

Ricky Han (hzgdiyer) wrote :

This patch worked for me with removing the "insmod ntfs" line.
WinXP + wubi on Thinkpad R400.
Thanks so much!

BW (bwbiztemp) wrote :

Fix in #210 (Patch from #90) worked for me on HP Pavilion w/ Athlon 64 3800+ and nVidia GeForce 6150LE, w/ proprietary drivers; windows version is XP Media Center 2005, Ubuntu is 64-bit (new install, upgraded 2.6.31-14 to 2.6.31-16, only 14 would boot after the upgrade). All kernels boot correctly now.

Did not remove insmod ntfs lines.

Thanks a bunch!

[er, I presume this is the correct place to report patch success, despite the duplicate warning?]

Rupert Ford (rupert-w-ford) wrote :

Fix in #210 worked for me.
I deleted the insmod ntfs line as suggested.
I'm running Vista on a Dell XPSM1210 for my sins
Many thanks

Centaur (centaure) wrote :

Had the same problem after performing a ubuntu update. Fix in #210 worked for me. Note that I did not need to perform the steps indicated in B) (i.e. B) ensure that when you boot there is no command "insmod ntfs". Press "e" at the grub boot menu to edit the relevant entry and remove "insmod ntfs" before proceeding).

Thanks!

meow81 (whocares) wrote :

Now i can say that it works #210 method with the new updated kernel linux-image-2.6.31-17-generic amd64 in kubuntu karmic ,with insmod ntfs disabled, thank you.

meow81 (whocares) wrote :

installed : linux-image-2.6.31-17-generic, linux-headers-2.6.31-17, linux-headers-2.6.31-17-generic, linux-image-2.6.31-17-generic, linux-headers-2.6.31-17, linux-headers-2.6.31-17-generic
updated: linux-generic, linux-image-generic, linux-headers-generic, linux-libc-dev, linux-image-generic, linux-generic,
linux-headers-generic, linux-libc-dev

Installed the new wubildr, no need to remove the insmod ntfs, and -17 boots fine now.

It would be nice to provide a patch installer for Windows users and give a link on it from a place where non expert users can find easily.

Sébastien,

Amen to your prayer.

I salute the industry of Ubuntu developers and followers, but these
corrupting, recommended updates and upgrades are driving me to the
realization Ubuntu should not yet be in the public domain.

Like me, you have read that we should install Ubuntu straight in, that
is, avoid Wubi. A straight install displaces the Windows boot loader,
however. We would be dependent on GRUB to boot both OS. What are we to
do after the next GRUB or Linux kernel update, when GRUB fails to boot
Ubuntu /and/ Windows?

Exactly whose assurance am I, a programming neophyte, to accept that
GRUB is invulnerable to update subversion when integrated into a
straight Ubuntu install, be my external file system NTFS or no, be my
Ubuntu partition above or below 4 GIG? I detect no plainly trustworthy
Ubuntu authority. Rather, it is distributed over an ad hoc network of
volunteers.

Is like a leaderless, silent Quaker Meeting. Ubuntu is nearly as
inscrutable and amorphous. Is certainly better that Boeing produced my
777.

James Liebert
Akron, Ohio

On 2010-01-09 07:34, Sébastien GRIPON wrote:
> *** This bug is a duplicate of bug 477104 ***
> https://bugs.launchpad.net/bugs/477104
>
> It would be nice to provide a patch installer for Windows users and give
> a link on it from a place where non expert users can find easily.
>

Nico (ncornelisse3) wrote :

I can't find wubildr in C:\
There is a wubildr in Data/ubuntu/winboot which I have replaced, but it doesn't help.

Where can I find the right wubildr to replace?

sureau (heyeokah) wrote :

I am a newbie and really did not wish to mess with wubi/winblows so I have done this (found after days of searching so to whoever wrote it, many thanks) and it worked for me:

sh:grub>insmod ntfs
sh:grub>set root=(hd0,1)
sh:grub>loopback loop0 /ubuntu/disks/root.disk
sh:grub>set root=(loop0)
sh:grub>linux /boot/vmlinuz-2.6.31-17-generic root=/dev/sda1 loop=/ubuntu/disks/root.disk ro
sh:grub>initrd /boot/initrd.img-2.6.31-17-generic
sh:grub>boot

Once booted I went into terminal and did this:
sudo update-grub

No problems booting anymore.

This looks like an imaginative adaptation of the code underlying the
GRUB Menu. I surely will save it.

You allude to a grave problem, however, the time it took to find the
solution. Distributive responsibility for writing patches is the
egalitarian approach, but we (Gomer) end-users have no basis for
authenticating proposals, except long exposure to those who propose.
Are they not free to come or go, those who propose?

I think Ubuntu needs a central committee. I think with a central
committee there would not have been need of this fix in the first place.

James Liebert
Akron, Ohio, US

On 01/19/2010 01:01 AM, sureau wrote:
> *** This bug is a duplicate of bug 477104 ***
> https://bugs.launchpad.net/bugs/477104
>
> I am a newbie and really did not wish to mess with wubi/winblows so I
> have done this (found after days of searching so to whoever wrote it,
> many thanks) and it worked for me:
>
> sh:grub>insmod ntfs
> sh:grub>set root=(hd0,1)
> sh:grub>loopback loop0 /ubuntu/disks/root.disk
> sh:grub>set root=(loop0)
> sh:grub>linux /boot/vmlinuz-2.6.31-17-generic root=/dev/sda1 loop=/ubuntu/disks/root.disk ro
> sh:grub>initrd /boot/initrd.img-2.6.31-17-generic
> sh:grub>boot
>

Wubi patch and step A only worked for me on friend's HP laptop.

khaynes (hayneskr) wrote :

Wubi patch and step A only worked for me as well! Cheers!

Wubi patch and step (A) worked fine on my Ubuntu 9.10 dual boot (Vista) installation on the DELL XPS M1330. Thanks!

rod_w_morris (rod-w-morris) wrote :

Wubi patch and step A worked for me. Thanks!

Florian (soare-florian) wrote :

I have downloaded wubildir from here: https://bugs.edge.launchpad.net/ubuntu/+source/grub2/+bug/477104/comments/90 and worked like a charm....

Eric (eric-pub) wrote :

I had the boot error "You need to load the kernel first" after an ubuntu update.
Applied the path on #90 (only step A) and now it works.
Thanx

gloriphobia (gloriphobia) wrote :

Using Wubi, Windows Ubuntu Installer on an XP professional Latitude Dell D630. After installing some updates and being prompted to restart I found myself looking into the ugly face of:

GNU GRUB version 197(squiggle)beta4
[Minimal BASH-like line editing is supported. For first word, TAB lists possible command completions. Anywhere else TAB lists possible device/file completions]

sh:grub>

I got various "no loaded kernel" or "no kernel found" errors when I tried anything. I then went back over to windows searched various forums to find help at: https://help.ubuntu.com/community/Grub2#Rescue%20mode

I followed the steps 1-5 just fine:

1. ls
2. set prefix=(hdX,Y)/boot/grub
3. set root=(loop0)
4. set
5. ls /boot

with X = 0, Y = 1 but then at step

6. insmod /boot/grub/linux.mod

I got the error "file not found"

I continued however

7. linux /vmlinuz root=/dev/sd01 loop=/ubuntu/disks/root/disk ro

You may notice that I actually made a mistake here, it should've been sda1 instead of sd01...

8. initrd /initrd.img

9. boot

And then an error: "VFS: cannot open root device 'sd01' or unknown-block(0,0)" followed by a list of other drives, then the error noted by others on this forum
"Kernel Panic - not syncying: VFS: Unable to mount root fs on unknown-block(0,0)" etc.

but then I replaced C:\wubibldr by the one suggested in comment 10 and then booted up (it worked without deleting insmod ntfs). but then ubuntu seemed to freeze, so I rebooted and deleted the insmod ntfs - and it all seems to be working now, I'm writing this from ubuntu.

One thing which I did notice which was odd, was when I was in Windows immediately after the problem started, was a large section of my hard drive taken up by space reserved for MFT, which I had never noticed before... (I only noticed this because I had opened up defraggler) maybe it was related, maybe not, I'll check back in windows to see if it has gone now that I have seemingly resolved the problem - with your help, Agostino Russo.

Thanks guys.

#210 worked for me on kernel -19

ggg1 (cgcoss) wrote :

i have followed all instructions. replaced wubildr, update-grub2. i have reinstalled grub2 and updated from the karmic proposed.

nevertheless, every time i boot, i get the grub menu.

from there i am able to boot using:

linux /boot/vm...-17... root=/dev/sda1 loop=/ubuntu/disks/root.disk ro
initrd /boot/initrd.....-17...
boot

i do not know what else to do.

note: it was suggested to disable insmod ntfs by pressing e at the grub menu. i was not able to do that as pressing e while i see windows and ubuntu will not do anything. and selecting ubuntu goes into the grub console immidiately and i cant press e.

any ideas?

thanks

vvCephei (vvceph) wrote :

@ Agostino #210,

The patch worked for me; thanks!

Lenovo G550
Intel x86_64
Windows 7

Meoiswa (meoiswa) wrote :

EEE PC 1005HA with Windoze and Ubuntu via wubi. Failed to display Grub4DOS menu after updating a bunch (A BUNCH) of stuff.
Using the patched file didnt work at first. Reason was i was patching up the wrong file.
Newbies out there, Download the patched file and place it right on the root OF YOUR WINDOWS INSTALLATION PARTITION (AKA C:) NOT IN THE PARTITON YOU HAVE THE WUBI INSTALL.
(Capslock for ease of relevancy)
After doing so both -14 and -19 kernels booted perfectly.
Had no need to comment any line.
Please put this patched file in the Wubi release before more people have this terrible bug

Pascal Meillier (pmeillier) wrote :

Works fine with -20, without removing 'insmod ntfs'
thanks for the fix

Noel Scerri (nscerri) wrote :

@ Agostino #210,

The patch worked for me as well.

Thanks a lot. Much appreciated

Dell XPS M1330
Windows 7

hotswapster (hotswapster) wrote :

This did the trick magically. THANKS!!!

meow81 (whocares) wrote :

new wubi 10.4 is out, does the bug is also in this new version?

meow81 (whocares) wrote :

be careful when update (dist update) to kubuntu 10.4 lucid lynx you have to use Ctrl+c key combination when a repetitive line occours in terminal something about 'vmlinuz' to avoid it, and the update process will be completed successfully, this is a wubi issue.

meow81 (whocares) wrote :

i don't know why it says "no wubildr" after a grub upgrade before grub screen but the systems loads correctly !

peregrine (abrojos) wrote :

@ Agostino #210

The fix (within Windows, overwriting that one file in the root directory) also worked great for me.

Home-built AMD Sempron
Windows XP Pro

Thanks to all who contributed to this solution!

Joshua Hong (hetaowu) wrote :

To #210

Thank you. It works. My platform is Windows XP SP3 and my wubi version is 9.10.

But I only performed step A and skipped step B. And still, it works

Madmoose (desaad) wrote :

Hello,

When I got this problem with 9.10 installing the new file worked. Now, with 10.04, I have this issue again and installing the patch does not work. I always end up back in [Minimal BASH-like...] Is there an updated file for 10.04?

Displaying first 40 and last 40 comments. View all 267 comments or add a comment.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers