Upgrade stops after "Mounting /boot"

Sam Varshavchik mrsam at courier-mta.com
Mon Dec 23 11:57:29 UTC 2013


Chris Murphy writes:

>
> On Dec 22, 2013, at 10:35 AM, Sam Varshavchik <mrsam at 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

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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.fedoraproject.org/pipermail/users/attachments/20131223/a3c40bc4/attachment.sig>


More information about the users mailing list