Trying to upgrade F19-F20 using fedup --iso with luks-encrypted partitions.
The upgrade stops after "Mounted /boot", and does not proceed, no further errors. Nothing appears to be running.
I did run into bug 1043981, and applied the patch to fix fedup barfing.
Sam Varshavchik writes:
Trying to upgrade F19-F20 using fedup --iso with luks-encrypted partitions.
The upgrade stops after "Mounted /boot", and does not proceed, no further errors. Nothing appears to be running.
I did run into bug 1043981, and applied the patch to fix fedup barfing.
… aaaand, this looks like a bone-fida bug with fedup 0.8. Multiple LUKS- encrypted partitions are a problem. After rebooting, a prompt gets issued to unlock the root LUKS partition. Then there's another prompt issued to unlock /home, but that prompt gets lost, and the boot continues with the systemctl jobs stuck in 'running' state. Things don't get very far before everything stops, due to the stuck systemd job.
Documented in bug 1045864. Temporary workaround noted.
On Dec 22, 2013, at 10:35 AM, Sam Varshavchik mrsam@courier-mta.com wrote:
Sam Varshavchik writes:
Trying to upgrade F19-F20 using fedup --iso with luks-encrypted partitions.
The upgrade stops after "Mounted /boot", and does not proceed, no further errors. Nothing appears to be running.
I did run into bug 1043981, and applied the patch to fix fedup barfing.
… aaaand, this looks like a bone-fida bug with fedup 0.8.
If it's just stuck on /home you can edit /etc/fstab to comment out the /home entry, since it's not needed for the upgrade. Then restore fstab after reboot, and reboot again (or mount it manually). Also this case of failure doesn't yet have a work around, and is actually a bug in the F19 installer which was fixed in F20. If it applies to your case, it's best to just reinstall from scratch because the layout is wrong.
https://bugzilla.redhat.com/show_bug.cgi?id=1044551
Chris Murphy
Chris Murphy writes:
On Dec 22, 2013, at 10:35 AM, Sam Varshavchik mrsam@courier-mta.com wrote:
Sam Varshavchik writes:
Trying to upgrade F19-F20 using fedup --iso with luks-encrypted
partitions.
The upgrade stops after "Mounted /boot", and does not proceed, no further
errors. Nothing appears to be running.
I did run into bug 1043981, and applied the patch to fix fedup barfing.
… aaaand, this looks like a bone-fida bug with fedup 0.8.
If it's just stuck on /home you can edit /etc/fstab to comment out the /home entry, since it's not needed for the upgrade. Then restore fstab after reboot, and reboot again (or mount it manually). Also this case of failure doesn't yet have a work around, and is actually a bug in the F19 installer which was fixed in F20. If it applies to your case, it's best to just reinstall from scratch because the layout is wrong.
In my case I was able to succesfully upgrade by systemctl cancel-ing the stuck password prompt job from an alternate console. This started the upgrade, which completed without issues.
My bug might be the same one here, at least insofar as the LUKS password prompting itself goes. However after kicking the upgrade, I ended up with a working system, unlike this bug. The difference might be that in my case I had regular, individual disk partitions; LVM was never in the picture.
On Dec 22, 2013, at 8:30 AM, Sam Varshavchik mrsam@courier-mta.com wrote:
Trying to upgrade F19-F20 using fedup --iso with luks-encrypted partitions.
I suggest posting the results of lsblk.
Chris Murphy
-
Chris Murphy -
Sam Varshavchik