Created attachment 887212 [details] journalctl -xb Hi All, I am not able to load my Live USB flash drive on two or the same Supermicro motherboards. Symptom is drop to maintenance mode with a request to run "journalctl -xb" (attached). Motherboards (both the same): Supermicro x10ssl-f, bios-1.1b http://www.supermicro.com/products/motherboard/Xeon/C220/X10SLL-F.cfm I am able to load the corresponding Live CD used to create this Live USB on this motherboard. And, I am able to test my Live USB flash drive from KVM. The live CD was created under Fedora Core 20, 64 bit with # livecd-iso-to-disk --label LIVE -overlay-size-mb 4095 /home/Fedora-Live-Xfce-x86_64-20-1.iso /dev/sda1 $ rpm -qa \*livecd\* livecd-tools-20.4-1.fc20.x86_64 Many thanks, -T
What does blkid show? It should have the UUID matching the 'root=live:UUID=2966-4464' entry. Also, you shouldn't need to pass --label, that will be set to LIVE by default. And does it work without overlay? eg. re-init the stick with: livecd-iso-to-disk --format --reset-mbr /home/Fedora-Live-Xfce-x86_64-20-1.iso /dev/blah
Hi Brian, Will "--format --reset-mbr" ruin anything on my stick? I have it pretty cherried out the way I want. I will start over if necessary to troubleshoot. I will wait for you word before proceeding. (I need the stick for my afternoon appointment.) Booted from KVM (inside the virtual machine): $ blkid /dev/vda1: LABEL="XFCE-LIVE" UUID="2966-4464" TYPE="vfat" PARTUUID="fddba570-01" /dev/vda2: UUID="4731df5a-e3ab-423d-922c-39d78aeaf1a6" TYPE="ext4" PARTUUID="fddba570-02" /dev/loop0: TYPE="squashfs" /dev/loop1: TYPE="DM_snapshot_cow" /dev/loop2: TYPE="squashfs" /dev/loop3: LABEL="_Fedora-Live-Xfc" UUID="7d2d4c30-add7-4d1b-ab41-18510678492b" TYPE="ext4" /dev/loop4: TYPE="DM_snapshot_cow" /dev/mapper/live-rw: LABEL="_Fedora-Live-Xfc" UUID="7d2d4c30-add7-4d1b-ab41-18510678492b" TYPE="ext4" /dev/mapper/live-base: LABEL="_Fedora-Live-Xfc" UUID="7d2d4c30-add7-4d1b-ab41-18510678492b" TYPE="ext4" /dev/mapper/live-osimg-min: LABEL="_Fedora-Live-Xfc" UUID="7d2d4c30-add7-4d1b-ab41-18510678492b" TYPE="ext4" From the host system (KVM virtual machine powered off): # blkid | grep -i sdc /dev/sdc1: LABEL="XFCE-LIVE" UUID="2966-4464" TYPE="vfat" /dev/sdc2: UUID="4731df5a-e3ab-423d-922c-39d78aeaf1a6" TYPE="ext4" I will see the two new X10ssl-f system this evening and I can run some more tests on them. -T
Yes, --format will wipe it. The UUID looks correct, so I really have no idea why it isn't working. Try adding rd.debug to the cmdline and then attach the journalctl output -- it should be much more verbose about what it is trying to mount.
$ rd.debug bash: rd.debug: command not found $ journalctl -xb --rd.debug journalctl: unrecognized option '--rd.debug' Note sure how to use "rd.debug" I will see the computers again probably next Monday or Tuesday
Sorry, you add it to the kernel cmdline when you boot.
"--format --reset-mbr" corrected the problem.