Ask Your Question
1

Unbootable VM after upgrading Fedora 27 >> 28

asked 2018-05-03 03:43:40 -0500

Albyv gravatar image

updated 2018-05-04 06:44:28 -0500

Hi everybody,

I am new to this group and I would like to thank you for your time! My Linux knowledge is very limited so I think that my chances of solving the issue are close no null... but how knows!

I run a guest Fedora 27 VM with VirtualBox 5.2.10 on a Windows 7 Enterprise 64-bit host OS.

The issue happened when I tried to upgrade to Fedora 28 (guess what... whitout backing up my files :| ).

After making sure my kernel was updated with sudo dnf upgrade --refresh. I installed the DNF plugin and started the update with sudo dnf install dnf-plugin-system-upgrade followed by sudo dnf system-upgrade download --releasever=28. So far, no issues at all.

Finally I tried to reboot in upgrade mode with sudo dnf system-upgrade reboot. After quite a few minutes of installation (I think the system processed ~1500 operations out of ~3800), I have been projected into emergency mode, in a minimal shell with a :/# prompt. The system suggested to save /run/initramfs/rdsosreport.txt to a bug report... as now my platform has no access to any USB stick or to my host/guest shared folders, I saved 26 screenshots in a .doc (...), which unfortunately I cannot attach here as I am new to the group.

Finally, I have typed journalctl from the emergency command line (another 15 pages) and - among others - I can see two errors highlighted in red:

fsck failed with error code 4 #and:
Failed to start File System Check on /dev/mapper/fedora-root

Sorry for the long message... any idea? Thanks!

Alberto

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted
1

answered 2018-05-05 06:14:28 -0500

ozeszty gravatar image

Hi Alberto, when you boot your VM, on grub boot screen press e, and at the end of line beginning with linux add rd.break=pre-mount, then press Ctrl+X. When you get to command prompt, run fsck -c /dev/mapper/fedora-root - it should ask you about fixing errors whenever it finds them - get them all fixed. After it's finished, you should be able to access your data from Live system booted from ISO image attached to your VM. From there you can either copy your files or try to fix your system with unfinished upgrade.

edit flag offensive delete link more

Comments

Thanks, an upgrade of a VMWare guest from Fedora 28 to Fedora 29 was hung up for me today. The rd.break=pre-mount was useful! Actual name of the image in this case was /dev/mapper/fedora_localhost--live-root, but fsck -c was able to complete the recovery.

vsfoote gravatar imagevsfoote ( 2018-10-30 10:39:35 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower

Stats

Asked: 2018-05-03 03:43:40 -0500

Seen: 382 times

Last updated: May 05 '18