To reproduce: 1. Do a clean install of F17 into a VM, using all defaults, enabling the main F17 repo and F17 updates repo (but not updates-testing) so you wind up with a clean, fully-updated F17 system. Used a single disk and LVM, nothing fancy. 2. Install latest fedup from updates-testing - 0.7.3-4.fc17 3. Run 'fedup --network 18' 4. Wait until it tells you to reboot. Reboot 5. Watch boot of the second stage fail It looks like it times out trying to mount a drive. I see: [ TIME ] Timed out waiting for device dev-disk-by\x2duuid-5db...d3d31c4.device. [DEPEND] Dependency failed for /boot. [DEPEND] Dependency failed for Local File Systems.
I'm not even sure where to add my comments as this seems to be an issue effecting a lot of people in many ways across several bugs. My disk layout: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 465.8G 0 disk ├─sda1 8:1 0 500M 0 part /boot └─sda2 8:2 0 465.3G 0 part ├─vg_sterling-lv_swap (dm-0) 253:0 0 9.8G 0 lvm [SWAP] ├─vg_sterling-lv_root (dm-1) 253:1 0 162.5G 0 lvm / └─vg_sterling-lv_home (dm-2) 253:2 0 293G 0 lvm └─luks-5faa44a4-788c-40e2-b6e2-b48e6e5e861e (dm-3) 253:3 0 293G 0 crypt /home After rebooting from `sudo fedup-cli --network 18 --debuglog fedupdebug.log` and after entering password for /home I get dropped into emergency shell and /home is not mounted. I have tried removing rhgb and plymouth.splash=fedup. I have enforcing=0. Nothing seems to work.
I have the exact same situation as the OP, with the exception that my machine is not a VM guest. The upgrade shell timed out waiting for /dev/disk/by-uuid/(/boot partition UUID). I could get to a maintenance shell to mount the partition manually but at that point I didn't know what to do next. After exiting into a previous environment (I guess systemctl default?) and looking over the various systemd targets I tried 'systemctl isolate system-upgrade.target' but that failed with so many 'mismatch' errors I did a CTRL-C to end the script and gave up. Currently upgrading via 'fedora-upgrade' and it looks like all vestiges of the previous fedup-cli run are gone but if there is anywhere I could look to see any debug messages I can try and have a look.
Here is my partition layout. The first few partitions contain WinXP and Debian, you can see the Fedora stuff at /dev/sda7 and /dev/sda8. lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 149.1G 0 disk ├─sda1 8:1 0 5.9G 0 part ├─sda2 8:2 0 75.1G 0 part ├─sda3 8:3 0 1K 0 part ├─sda5 8:5 0 12.3G 0 part ├─sda6 8:6 0 2G 0 part ├─sda7 8:7 0 500M 0 part /boot └─sda8 8:8 0 53.4G 0 part ├─vg_fedora-lv_swap (dm-0) 253:0 0 2G 0 lvm [SWAP] ├─vg_fedora-lv_root (dm-1) 253:1 0 34.3G 0 lvm / └─vg_fedora-lv_home (dm-2) 253:2 0 17.1G 0 lvm /home
dominique: we're pretty sure the fedup in updates-testing for F17 is just busted, I don't think it's system-dependent. So we probably don't need a lot of detail on specific systems hitting the bug. Thanks for contributing!
*** This bug has been marked as a duplicate of bug 958586 ***