any resolution ?
I am facing exactly the same problem after upgrading F31 => F32 including ââallowerasingâ.
Same sysroot error , and in emergency console the â/sysrootâ is completely empty. Even if I create some folders/files in there, after reboot it is empty again
Thanks !!
@gkoenig No, no resolution yet, Iâm still looking into it. I could just reinstall the whole of Fedora after backing up but is not really an acceptable solution for me right nowâŠ
@pauld Thanks for the link, I actually already tried that. But when I try mount -o remount,rw /sysroot I get mount point not mounted or bad option. Not sure what to do with that I must say.
same here, upgrading from f31 to f32.
it seams strange, that initrd-mount-sysroot.service doesnât fail, bc ofc there is no sysroot/etc/os-release, bc std root is not mounted
Here tooâŠ
And I also encrypted my home folder (not with LUKS) and donât know how to acces the my files now from a live stick
Iâm having a LUKS encrypted LVM and inside that the root partition and my home partition. But since someone else might use this computer too, I also set the flag to encrypt my home directory as I created it with the KDE Plasma user dialog.
Has someone any ideas how I can access them again?
Maybe Iâm trying out sliverblue the next time ?_?
there are instructions somewhere in the internet on how to decrypt and mount encrypted lvm partitions from the commandline.
But I have a simpler solution.
Live-Stick with Peppermint OS
boot
run gnome-disks
there you can easily decrypt your partition in gui.
then
sudo su
cd /
mount /dev/mapper/fedora*root /mnt/
for d in dev sys tmp proc ; do { mount --rbind /$d /mnt/$d ; mount --make-rslave /mnt/$d ; } ; done
chroot /mnt/ /bin/bash
. /etc/profile
mount -a
now at this point you are running your unbootable system from under another system, nearly like after normal boot, and you can do whatever backups you want.
you may mount some external harddrive lets say at /mnt/ and do
rsync -aAXv --exclude=lost+found /home /mnt/
to verify that files are copied correctly you may additionally run
rsync -aAXcv --exclude=lost+found /home/mnt/
PS:
If you need something to install or access the internet, then after you connect Peppermintos to the internet, run
Found this thread with a similar problem and an encrypted system, so maybe it helps.
@pauld Thanks for the suggestion, I tried fsck my partitions and they all return âcleanâ.
As for the journalctl -b I might be missing something obvious, but if I generate the file on the Live media wonât it return the boot journal of the Live Fedora version, and not the broken one? If I generate the file in emergency mode, will it be accessible via Live Media so I can copy paste it?
What you have tried to do other did it this way (in the time with success) [in the emergency shell]:
mount - o remount,rw /sysroot
rm -rf /sysroot/etc/os-release
cp /usr/lib/os-release /sysroot/etc
exit
My guess is that your case is different⊠you would have to do mkdir -p /sysroot/etc before doing the cp⊠because /sysroot/etc does not exist⊠because /sysroot is empty⊠which I guess is a problem (seems /sysroot is what will become your / filesystem I think⊠after a chroot there⊠at least this is my feeling)
Hi there, as you can guess Iâve just tried updating Fedora from 31 to 32 and here I am
Something I should note is that I had the exact same problem last week when I installed the proprietary nvidia drivers. My system wouldnât boot and I would get the error â[FAILED] Failed to start Switch Root.â.
I then uninstalled the faulty driver using a live-usb to chroot on the partition where my system is.
Unfortunately I donât have enough knowledge to relate the two instances of this problem but some of you might.
Hey again, as mentioned before, when I try mount -o remount,rw /sysroot I get mount point not mounted or bad option . Not sure what to do with that I must say.
Now we might have a lead with @deadgnom32 Grubâs issues as I had in the past many issues with Grub on this system, already when I upgraded to Fedora 30, in the past.
Edit: investigating further the issue, I have exactly the same values that @pauld pointed out, with the EFI loader partition unknown and weird Grub entry looking the same.
To also share my journalctl entry so we can see if I have the same issue, can I generate the file from Fedora live media? If I generate the file in emergency mode, will it be accessible via Live Media so I can copy paste it?
I had issues when upgrading to F30 with nvidia drivers breaking my grub as well and following instructions there did the trick at the time (it was a year ago so Iâm a bit blurry on the details). I had to fix my grub at some point.
i tried to reinstall everything from under chroot and yet, it looks different.
i will investigate this issue later today.
i have a couple ideas on what may cause this problem.
UPD:
I updated the system from chroot. and got grub entries fixed.
I reached the graphical login screen, but couldnt login neither on graphical login nor on tty. root or my user. both fail.
ON tty screen gets reloaded, and i land on
