I've just seen this problem --- but in possibly a more useful context... I am building a machine. It's got one DVD drive and one disk. I am repeatedly installing a disk, booting a livecd, and examining the disk to see what's on it, deciding I don't want to wipe this one, and moving on to the next one in the pile.
I get this error with *one specific drive*. With other disks installed in its place, everything is fine. So it's got nothing to do with the SATA settings or graphics card, because they haven't changed. The one peculiarity of the disk that failed is that it doesn't have a partition table --- the filesystem occupies the entire disk. Zeroing out the first few kilobytes of the disk solves the problem and everything boots. So I'd suggest that there's something wrong with the way the boot script is probing the disk. The filesystem had been correctly found; I was able to mount it using the file in /dev/disk/by-uuid. However, there wasn't an entry for the DVD. I don't know enough about how /dev/disk/by-uuid is populated to be able to point at a specific component, but I bet it's getting terminally confused by an invalid MBR partition table. I'd be really interested to know whether the other people who've ran into this were using brand new disks or disks with a GPT partition table. Addendum for the desperate: The disk can be zeroed from the initramfs prompt, using this command: dd if=/dev/zero of=/dev/sda Let it run for a few seconds and reboot (you can't ctrl+C it). THIS IS INCREDIBLY DANGEROUS and do not do it on a machine with ANY data on it you want to keep! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1241589 Title: ubuntu 13.10 unable to boot on live usb (busy box - initramfs) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1241589/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
