Description of problem: The upgrade process hangs when booting the upgrade kernel. Version-Release number of selected component (if applicable): fedup-0.7.2-1.fc17.noarch How reproducible: Upgrade an F17 system with ntfs partitions in /etc/fstab Steps to Reproduce: 1. Ensure that there are windows partitions in /etc/fstab 2. Run "fedup --network 18" 3. Reboot with the upgrade kernel Actual results: The upgrade process should have been continued Expected results: The upgrade process is halted at mounting the windows partition and an emergency shell is emitted. Additional info: The workaround was to simply comment the following lines in my /etc/fstab: #UUID=E6625E89625E5DFD /win/system ntfs rw,nodev,nosuid,exec,auto,nouser,sync,uid=1000,gid=100,umask=022,dmask=022 0 0 #UUID=C2B4D871B4D86A05 /win/programs ntfs rw,nodev,nosuid,exec,auto,nouser,sync,uid=1000,gid=100,umask=022,dmask=022 0 0 #UUID=0CECE24EECE2321E /win/multimedia ntfs rw,nodev,nosuid,exec,auto,nouser,sync,uid=1000,gid=100,umask=022,dmask=022 0 0 Re-run fedup and now the upgrade has been completed successfully. On the maintenance shell, I've seen that the windows partitions were not mounted and the "systemctl status" on them printed an error that the kernel fuse module was not loaded.
The issue can cause either a hang and if you press ESC you see only printed stars in the screen or to drop you a single user shell: Welcome to emergency mode. Use "systemctl default" or ^D to activate default mode. Give root password for maintenance:
This issue is caused by the same storage startup problems seen in 958586 and its duplicates and is fixed in fedup-0.7.3-5. *** This bug has been marked as a duplicate of bug 958586 ***