Take the 2-minute tour ×
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free, no registration required.

Followed direction listed at: https://help.ubuntu.com/community/Boot-Repair

Used live USB installer > try ubuntu > downloaded Boot-Repair

Boot-Repair started automatically after install.

Used "Recommended repair" option that ended with successful repair, "reboot your system".

Report at URL: (paste.ubuntu.com/6726786)

neither Wubi versions started.

Previous stable version ( 3.8.0-34~generic) and new (that was unsuccessfully installed which missed-up the OS) ended up with missing modules (cat/proc/nodules; ls /dev)

Alert! /dev/disk/by-uuid/xxxxxxx) does not exist.

Dropping to a shell!

BusyBox v1.18.5 built-in shell ...... (initramfs)_ _

Although, I can get to Gnu Grub v.1.99-21ubuntu3.14 command line before selecting OS version to boot from.

I had the older one rescued yesterday with generic graphic driver but it went all-bad after attempting > system sittings > additional drivers.

Now, Can I fix one of the two installed versions from this command line?

If no, what maybe my best option before a full deleting of Wubi and new installation that will delete a few files left since last back-up.

share|improve this question
Wubi uses the windows boot loader so boot repair is not going to help you. What problem did you have ? What made you think boot-repair would help ? –  bodhi.zazen Jan 10 at 16:56
If a new kernel isn't booting, just boot the previous one: hold down Shift key at boot, Advanced options, that should give you a list of old kernels. Then remove or repair the latest kernel. –  bcbc Jan 10 at 21:03
Wubi was partially loaded: I had current and previous Ubuntu versions listed as booting option. I thought boot-repair will start at this point and fix or reload missing files. –  user176105 Jan 12 at 14:53

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.