Bug 1044076
| Summary: | fedup 19->20 fails | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Tommi Kyntola <kynde> |
| Component: | fedup | Assignee: | Will Woods <wwoods> |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 19 | CC: | jan.public, mbooth, tflink, wwoods |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-12-18 17:10:20 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Pretty sure these are red herrings. They appear to be failing because the initrd doesn't contain the relevant kernel module. However, apart from creating untidy errors in the logs, they don't seem to have any negative impact. I had exactly the same, and I forcefully disabled proc-sys-fs-binfmt_misc.mount. The result was that the boot still failed, but I could now see the real error messages without the binfmt_misc spam. I suspect you're hitting bug 1044086. Indeed they are. I'll mark this a dupe. *** This bug has been marked as a duplicate of bug 1044086 *** |
Description of problem: fedup from 19 to 20 runs smoothly and then shortly after a reboot things go sour. All I see is a whole lot of complaints about binfmt_misc mount failing. It drops to a rescue shell after which it reboots back to f19 where everything is thankfully still ok. Version-Release number of selected component (if applicable): fully updated f9 How reproducible: every time, I tried four times Steps to Reproduce: 1. fedup-cli --network 20 2. reboot 3. fails, reboot back to 19 Additional info: Lenovo X1 carbon, encrypted /home, hundreds of lines like these clutter the logs: Dec 17 20:02:09 musta mount[1009]: mount: unknown filesystem type 'binfmt_misc' Dec 17 20:02:09 musta systemd[1]: proc-sys-fs-binfmt_misc.mount mount process exited, code=exited status=32 Dec 17 20:02:09 musta systemd[1]: Failed to mount Arbitrary Executable File Formats File System. Here's what journalctl said: proc-sys-fs-binfmt_misc.mount - Arbitrary Executable File Formats File System Loaded: loaded (/usr/lib/systemd/system/proc-sys-fs-binfmt_misc.mount; static) Active: failed (Result: exit-code) since Tue 2013-12-17 20:14:21 EET; 1min 17s ago Where: /proc/sys/fs/binfmt_misc What: binfmt_misc Docs: https://www.kernel.org/doc/Documentation/binfmt_misc.txt http://www.freedesktop.org/wiki/Software/systemd/APIFileSystems Process: 1185 ExecMount=/bin/mount binfmt_misc /proc/sys/fs/binfmt_misc -t binfmt_misc (code=exited, status=32) Dec 17 20:14:21 musta systemd[1]: Failed to mount Arbitrary Executable File Formats File System. Dec 17 20:14:21 musta systemd[1]: Unit proc-sys-fs-binfmt_misc.mount entered failed state. Dec 17 20:14:21 musta systemd[1]: Mounting Arbitrary Executable File Formats File System... Dec 17 20:14:21 musta systemd[1]: proc-sys-fs-binfmt_misc.mount mount process exited, code=exited status=32 Dec 17 20:14:21 musta systemd[1]: Failed to mount Arbitrary Executable File Formats File System. Dec 17 20:14:21 musta systemd[1]: Unit proc-sys-fs-binfmt_misc.mount entered failed state.