Description of problem: Fedup command completes OK, reboot and upgrade fails due to problems unmounting /boot and /usr, fails with coredump (photo, journal doesn't contain this boot for some reason). Version-Release number of selected component (if applicable): fedup-0.9.0-2.fc21.noarch systemd-216-16.fc21.x86_64 How reproducible: Always Steps to Reproduce: 1. Clean Fedora 21 installation onto Btrfs. Post-install conversion to mount usr suvolume at /usr, which boots and updates using yum, dnf, and pk-offline. 2. Update Fedora 21 to current. Install fedup. 3. fedup --network 22 --instrepo https://kojipkgs.fedoraproject.org/mash/rawhide-20150124/rawhide/x86_64/os/ --debuglog fedup.log 4. Run grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg due to bug 864198, this adds fedup boot entry. 5. Reboot Actual results: Fails to upgrade, system hangs, can switch to debug shell but typing does nothing. System has to be forced off. Expected results: Should update. Additional info: The first problem is /boot is busy, before getting to the /usr part. I don't know why it's busy and can't be moved. It is a btrfs subvolume but that shouldn't matter. Ideally a separate /usr can be supported now that usrmove is a done deal, and also for stateless systems arranged as this suggests: http://0pointer.net/blog/revisiting-how-we-put-together-linux-systems.html
Created attachment 984113 [details] photo of failed upgrade This matches with journal1.txt attached after this. The only thing the photo contains that the journal doesn't is the failure to log coredump.
Created attachment 984114 [details] journal1.txt journalctl -b-1 -l -o shortmonotonic Taken after rebooting from the failed boot-upgrade.
Created attachment 984115 [details] fedup.log
Created attachment 984116 [details] fstab
Created attachment 984117 [details] grub.cfg
Created attachment 984120 [details] journal-debug.txt journal with systemd.log_level=debug rd.debug Explains the lack of debug shell [ 40.406717] f21t.localdomain systemd[1]: Stopped Debug shell on tty2.
Created attachment 984124 [details] proc mounts from rd.break=clean set rd.break=cleanup, unfortunately /boot isn't mounted yet so I can't figure out what's busy in there, unless moving /boot/efi still hasn't happened yet and that's causing /boot to be stuck. Of course /usr has a bunch of libraries using it. /proc/mounts /proc/self/mountinfo
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.