wubi - kernel panic - not syncing VFS...

[hhh81]

Yes it's the fix/patch that will be integrated in wubi.exe, if u don't want to wait until new modified wubi.exe you can use the current wubi to install ubuntu and then manually replace the old wrong c:\wubildr file with new one that can be obtained from https://bugs.edge.launchpad.net/ubun...04/comments/90
as written in https://bugs.launchpad.net/ubuntu/+s...9?comments=all comment number #210



"For a patch/workaround:

A) get the wubildr in https://bugs.edge.launchpad.net/ubun...04/comments/90 and copy it over C:\wubildr
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

New ubuntu/wubi installations do not contain the patch yet. The patch will only be applied once there is a clear confirmation (from you) that it actually solves the problem. Hence your feedback is appreciated."

[macsdev]

^^ It did work. Thanks a lot

[nhbob]

I need "DUMMY" like instructions to repair this error. I like many others just used the regular automatic upgrade path and got the kernel panic. I can execute the older version of Ubuntu from the start menu but I do not know how to get rid of the damaged versions or how to input a fix. All instructions in the thread seem to assume a general knowledge of Linux and terminal use that I just do not have. I assure you all that there are many, many, others out here that try out Ubuntu and Linux and then are forced to retreat and then probably surrender in the face of these challenges.

The fact that Ubuntu and Wubi provide packaged support and upgrade paths for Linux certainly should provide the mass population of computer users a path for that will allow them to take advantage of the many benefits of Linux but it is my opinion that Linux will remain a tool for a very small (comparatively) number of specialist users (something I suspect a number of people secretly like) unless more is done to attract general computer users like myself. Releasing upgrades that result in a mess like this is bad enough, but not providing a rapid, concise set of solutions is worse.

If there is anyone out there from Ubuntu, WUBI and others who seem to at least philosophically agree with my position, please discuss this at the highest level and provide a real "For Dummis" solution to this and future problems.

[hhh81]

I reply here to your pm: You must try to replace the file wubildr (without extension) located in C:\
(you can try from windows)
with the new one that can be obtained from this link https://bugs.edge.launchpad.net/ubun...04/comments/90
this should works

[nhbob]

Thanks for this response.

I have multiple copies of wubildr (79KB) and wubldr.mbr(8KB) and a single copy of wubild.cfg (2KB).

I take it I somehow delete some and then add the new file by saving it somewhere - where is that?

As I said I need "Dummy" help. I am nor linux proficient.

[meierfra.]

I take it I somehow delete some

You don't have to deleted it. It will be overwritten by the new file.

and then add the new file by saving it somewhere - where is that?

Directly on "C:\". Go to "My Computer" (or "Computer") and then double click the icon for the "C:" drive.

[nhbob]

Thank You. I will try this method.

[BinaryBrother]

I reply here to your pm: You must try to replace the file wubildr (without extension) located in C:\
(you can try from windows)
with the new one that can be obtained from this link https://bugs.edge.launchpad.net/ubun...04/comments/90
this should works

This did not work for me directly... However, booting into recovery mode worked and from there I ran dpkg repair and after about 45 mins of fixing packages, it worked. Thanks!

[Dale61]

I had to revert to my SIL's Windoze machine (shudders down spine) to find a fix when I first encountered this problem. Then, what I did was to download the new wubidr file to a flash drive, then go back to my pc, and once I got it running as per normal, I swapped the old wubidr file with the new, and haven't had a problem since.

However, I have now upgraded to 10.04, and haven't had any semblance of a similar problem, so I'm thinking (hoping) it is just a 9.10 problem, and not an on-going issue.

[mikerip]

Sorry, it does happen with 10.04. It seems to depend on the chipset. I have been unable to get 10.04 livecd or a finished install to boot on one system I have with a Sis chipset. I can boot the ALT cd and install from that but grub is most unhappy when trying to boot the finished install. The interesting thing is that if I move the hard drive to another system with an Intel chipset, it boots just fine.

I'm guessing, but I think it has to do with the kernel masking the IDE drives as /dev/sdX instead of /dev/hdX

manually booting into grub, it says that (hd0,0) does not exist but it can see (hd0,1) which I consider very odd. I don't think it is specifically the 2.6 kernel as I have Centos5.4 running just fine on the same box (different hard drive). Something is very broken in the way ubuntu is handling the disk structure in their kernels (in my humble opinion).

Waiting for a fix.....