Update kills Ubuntu option on bootloader 2nd screen

Are you running release 10.04? There is a bug in the grub updates as you suspected that is causing all 10.04 Wubi installs to fail. It happens even on a fresh install of 10.04.1 with the latest grub-pc and grub-common updates applied.

See here for a discussion of the problem and a workaround to get it booting followed by a permanent fix:
http://ubuntuforums.org/showpost.php?p=10183394&postcount=87

More details around the permanent fix here: http://ubuntuforums.org/showpost.php?p=10180520&postcount=78

If you require additional info or help with the fix, let me know.

Hello,

thanks for responding; I am using 10.4.1 with the cursed updates and I am still lost;

I am not sure how to extract Wubi root.disk from a download and I have not created a Viao recovery disc before or after Ubuntu installation, plus I have no idea (or if it is even possible) to get a terminal to open before the wubi boot has done its stuff

I gather that if I do a fresh installation of 10.10 all my troubles will be over?
if I do a fresh installation does it recognise that 10.4.1 is there - or should I remove 10.4.1 first to avoid the same issue?

I am begining to think that a new installation may save me the hassle of getting the fix wrong and probably save me time overall as I am such a novice at the Linux and its derivatives.

I can live with a re-installation of VLC, Audacity and Jack.

What do you think?

I think this is beginning to make sense; I need to boot using a stick or CD then open a terminal, then whack in the code.
I have a boot stick I downloaded to run Ubuntu on an eeepc; however the eeepc's native system is debian so it will probably not work on a windows (*coughs up phlem and spits*) machine.

I will have a go tonight but would appreciate any pointers on a full re-installation as I may have to go down that route.

Thanks for taking the time to respond.

Richard.

If you reinstall wubi it will remove the current installation and all the data.

You can use a tool like ext2read (http://ext2read.blogspot.com/) from Windows to copy data off the root.disk before uninstalling. Then installing 10.10 will be OK. If you reinstall 10.04 avoid updating packages grub-pc and grub-common (they're normally buried way down in the Recommended list of updates). You can lock them in Synaptic and they won't show up at all in Update manager too (opes Synaptic, select each package, click on Package menu, then Lock version). Then it doesn't matter which version you run.

That's by far the simplest.

Regarding using your Ubuntu USB stick on the Vaio - that will work except if your USB stick contains a 64-bit version of Ubuntu and your Vaio is 32-bit only. Otherwise there is no concept of a debian computer versus a Windows computer. They're the same.

Hello there,

I am still trying the fix but I am still getting stumped; so far used a Ubuntu 10.10 disc to allow me to open a terminal (control+alt+t) first line of code ok, second line ok but third line "sudo mount -o loop /mnt/windows/ubuntu/disks/root.disk /mnt/wubi" brings up a not found type message. Could this be that sda1 is not the right mount point - and if so how do I find the right one for windows? I am assuming that I don't have to physically remove the files - the code does that? finally I assume that the script will give me a save option Y/N? rather than having to enter a command? - My apologies for trying your patience - perhaps I should stick to wrestling alligators rather than trying to fix wubi.

Richard.

There are more questions than answers - the more I find out the less I know

Run the bootinfoscript (http://bootinfoscript.sourceforge.net/) - it will tell you where the root.disk is. Or paste the results to http://pastebin.ubuntu.com/ and then the pastebin address back here and I'll take a look.

Dear bcbc,

I tried sda2 as a shot in the dark, and that worked; gedit it bought up the file to edit; at that point my laptop froze up.
I will have another crack at it tonight; I am getting there. I have made a copy of the text of the file in case I delete too much or not enough - I can then go back and re-edit

I do like the fact it says "DO NOT EDIT THIS FILE" at the top.

but still a few more questions;

What command line to manually boot once I have edited the file and rebooted?

I assume the final part of the fix is opening the folder and physically deleting all files except grub.cfg, grub,env from /boot/grub - rather than editing individual lines?

If I get through this I will try to word this solution in complete novice language; If I can do it anyone should be able to and that could address your concerns mentioned in #88

Again thanks for your help

Richard.

("A little knowledge is a dangerous thing. So is a lot." — Albert Einstein)

Yes... it says "DO NOT EDIT THIS FILE". If grub was working that would be true :)

So, the fix you are doing is to avoid a few lines that are bad - and set up grub.cfg so Ubuntu will boot. No manual commands necessary to boot Ubuntu after the edit.

But, grub.cfg gets regenerated automatically in certain circumstances e.g. removing or installing a new kernel. (That's why there's that message). And that's why there is a separate permanent fix to remove those extra files from /boot/grub

Good luck!

PS there is now a new support thread (http://ubuntuforums.org/showthread.php?t=1639198) that is hopefully more understandable. If not please add comments to that thread so that it can be updated. Thanks

Dear bcbc,

Thank you;
it worked despite my inexperience of all things linux;
fear of doing the wrong thing must hold back a lot of newbies like me; editing the file with "DO NOT EDIT" on it was a high point!

Thank you for your incredible patience and willingness to explain this step by step.
It is comforting to know that there are experts out there like yourself to support open source systems; this is what the internet should really be all about.

Kudos to you
I am truly chuffed!

Richard.

Great, you're welcome! I'm glad to hear you got it sorted out.

Dear Luke,

If you free are that would be good.

Kind regards,

Richard.

Dear Paul,

I think that the intention was going to be barrier
activation by passive loop to control one way traffic flow, rather than provide
secure parking.

I don't know who suggested the brief.

Kind regards,

Richard.