Emergency mode after reboot
bug
I was trying to get a design tablet to work following instructions from ublue community and other discord posts here. I ran
I believe all the errors (in red) in my journalclt line up with the poster here - 🛟bazzite-helpSystem booting to emergency mode, seemingly not file system related
I have followed the pinned comment relating to btrfs errors (and saw no mention of BTRFS in red prior or post instructions) - gparted cleaned, reboot and still having the issues with all grub bazzite images.
Emergency mode output on proceeding is -
I'm a little over my head, is this related to the command I ran, or something else? @biebel Thank you for your assistance so far.
(I'll be back tomorrow), as is mentioned in the linked thread, there was a suggestion to keep the home directory while merging new boot. If that is the only option open to me, how do I go about doing this (I am dual booted on single nvme currently)
rpm-ostree kargs --append=modprobe.blacklist=hid_uclogicI believe all the errors (in red) in my journalclt line up with the poster here - 🛟bazzite-helpSystem booting to emergency mode, seemingly not file system related
I have followed the pinned comment relating to btrfs errors (and saw no mention of BTRFS in red prior or post instructions) - gparted cleaned, reboot and still having the issues with all grub bazzite images.
Emergency mode output on proceeding is -
'Failed to connect to the system scope bus via local transport: No such file or directory'. ostree-prepare-root[1193]: ostree- prepare-root: couldn't find specified ostree root - - then the directory its looking inI'm a little over my head, is this related to the command I ran, or something else? @biebel Thank you for your assistance so far.
(I'll be back tomorrow), as is mentioned in the linked thread, there was a suggestion to keep the home directory while merging new boot. If that is the only option open to me, how do I go about doing this (I am dual booted on single nvme currently)
