Live USB with persistent boot options fails to boot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
usb-creator (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: usb-creator
I've been trying to get Ubuntu Jaunty to install a live CD to my thumbdrive for several days. I've been doing the same thing for a while:
1. Go to System > Administration > USB Startup Disk Creator
2. Select an Ubuntu image (tried jaunty beta i386 and jaunty daily i386)
3. Choose to store some amount of data in reserved extra space (created as casper-rw in the root of the thumbdrive, and also adds the "persistent" boot option to the kernel tags)
4. Reboot, boot from thumbdrive, and choose the first option labeled "Try Ubuntu without any change to your computer."
5. Press ctrl+alt+f1 to see what's happening
6. Watch various logs repeat over and over, which are different depending on the computer.
6a. When booting from a computer with a floppy drive and Windows installed, I get messages about IO errors on fd0.
6b. On computers running jaunty + ext4, messages refer to ext4fs mballoc.
6c. From Qemu in Windows, messages refer to a DRDY IRQ ERR
7. Drop to BusyBox shell at (initramfs) shortly after attempting to load the persistent file.
8. Reboot and press F6 to change the boot options. Delete the word persistent. Problem solved.
I've tested this with both the Ubuntu USB Creator and with Unetbootin on Jaunty, while trying to create a Jaunty Live USB.
ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 9.04
NonfreeKernelMo
Package: usb-creator 0.1.15
PackageArchitec
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: usb-creator
Uname: Linux 2.6.28-11-generic x86_64
description: | updated |
summary: |
- Live USB created on OCZ ATV / Rally 2 fails to boot + Live USB with persistent boot options fails to boot |
I'm also getting dropped to a busybox shell on an Jaunty daily i386 live CD for a EeePC 901. I also used usb-creator as well, however I didn't see any of the error messages as stated by the bug reporter.