There might be several causes for busybox. A common one is that the
Windows file system has the dirty flag set, in which case you need to
clear it by booting into Windows, running chkdsk /r and rebooting
cleanly.
That said if you can boot with an older kernel (press ESC at boot after
selecting "Ubuntu") but not with a newer one, the issue is probably
different.
Andrew the message
/dev/disk/by-uuid/2E0E-0CE2 on /root failed: No such device
is a good lead. You can interrupt the boot process using the kernel
argument:
break=mount
You will end up in a busybox at the point where the device has to be
mounted and investigate why the root device is not available.
It would be also interesting to have confirmation from other users
whether in their experience the issue is also due to the root device not
being available.
** Changed in: wubi
Assignee: (unassigned) => Agostino Russo (ago)
--
kernel updates get hardy boot stuck in busy box
https://bugs.launchpad.net/bugs/236307
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
