I'm stuck in grub menu
I can't boot into bazzite at all and get put into emergency mode, of which tells me it can't even open the console since it says "can not open access to console the root account is locked"
looked this issue up and it said to press e in the grub menu and add a line to boot into commands, tried passwd and then touch ./autorelabel but soon found out it won't work cuz this is an immutable system, so I'm here to ask what to do next?
What happened to cause this was I booted into the windows option in grub menu, flashed windows2go from Rufus onto the emmc from steam deck in an enclosure. Had the thought that since I have no computers with a USB c port(except one in my main PC but it's very slow, which is why I opted to not use it originally). booted from that on my steam deck since it does have one, but then realized after I got to the windows desktop that I was going to need to bring the files so I tried plugging it into my desktop with a USB c to a adapter (same speed as bad USB c port so idk why I didn't just use that) and in bios menu put as boot #1 (tried boot manager but I pressed the wrong key) and then windows blue screened saying
registry_error and when I tried going back to bazzite after changing boot order again and now I'm here with my issue95 Replies
When you get into terminal from your grub menu, If you run
fdisk -x which will give you disk info for all your disks and partitions, the UUIDs is the important part. Then open your /etc/fstab file and check that everything matches up. I'd guess that you might have added an external disk to Bazzite and there is something wrong in the fstab config now that that drive is no longer there
If you need any more assistance, Nick added my video guide for getting out of emergency mode into the Bazzite docs https://universal-blue.discourse.group/docs?topic=970#emergency-mode-after-following-this-guide-29 Check the section at the end "Emergency Mode After Following This Guide?" Hopefully that will help toohaven't tried yet as I just ate but I did try booting on the steam deck afterwards and again blue screen for registry error so that confuses me
I will try what you told me now
I do have auto mount enabled in bazzite, but I hadn't booted into bazzite after putting windows on it, so adding windows broke it and it broke windows
great it also broke my surface pro 6 from booting AuroraðŸ˜
cuz I had tried booting from that first and it wasn't showing up in boot menu, but the error isn't even the same as with bazzite
ok
I'm in
you might need to run fdisk from it's actual location
/usr/sbin/fdisk -xI plugged in my rom external hard drive instead of changing fstab
the video gave me the idea
ðŸ˜
oh nvm, good news, glad you are sorted
I just got in rn
but I have one more issue
I can't login
I had tried changing the root password according to this one guide that I eventually found out wouldn't work for me cuz it's immutable when I tried doing touch ./autoreload and that failed and now the original password I had and the one I changed it to won't work
should I redo the steps I did to change it?
or did it break
since what I changed it to isn't working
Fedora Docs
How to Reset the root Password
A root password may be set up while installing Fedora Linux, although it is now suggested to leave the root account locked and use sudo. This article describes how to…
what I followed for context
I would go back to terminal and type the password into the terminal. It might be a keyboard layout thing
Rather follow Nick's guide here https://universal-blue.discourse.group/docs?topic=161
Universal Blue
Reset Your Forgotten Password
Note: Bazzite Handheld/HTPC users: Press Esc on a physical keyboard. Follow this guide at your own discretion because you can break your system attempting any of this. [Edit the command for the latest boot entry] Reboot your device and edit the last deployment by presssing E on your keyboard. [Boot with init=/bin/bash] Boot with init=/b...
sigh
right back to bash
Yeah, sometimes Linux really sucks
Good luck, hope you come right
I'ma be asking for help with my Aurora another day
esp cuz screen is broken so I can barely read what it says rn
Yeah, one problem at a time, let's get your Bazzite sorted for now
followed all steps in the guide
login failed
somethings wrong
😔
mine was also less than 8 characters and my only difference was I mistyped sbin as sbiu and then retyped it and continued
Are you back in now?
no I can't login
login failed for all 3 passwords I've now had
Try type the password in the terminal and see if it matches what you are typing, as it might be a keyboard layout issue
Also see if you can press CTRL+ALT+F2 and then log into terminal
I saw it type the correct numbers the first time when I accidentally put it as my username thinking I did passwd (password) not passwd (user)
did this again
at what point do I do this?
in bash?
grub?
See if you can get to a TTY session from the login screen
then try and log in with username and password there
what's tty
I'm on this rn still
Try that other guide but instead of typing "init=/bin/bash" in grub. Type "3" without the quotes, see if your login works from terminal
If so you might be able to log in with
/usr/bin/startplasma-wayland or /usr/bin/startplasma-x11okay I'll try this right now
it does not work
I can see my password correctly if I type it as the login
can I just straight up remove the password?
or no that's a bad idea right
could you try changing it to a password that is longer than 8 characters? https://discord.com/channels/1072614816579063828/1253202856505512036/1253225651687657482 in your image here, it is giving you an error message when you try and change the password
I can try in a bit but my first two passwords were 8+
It might not like the complexity of the password
just got windows working on my small drive and am installing the one game I intend to use it for
I'm out of ideas. Will let you know if I think of anything
idk man I can't even get into bash now
init=/bin/bash
says it's gonna let me do commands, like it does before showing bash
and then it tries to boot bazzite
It looks like it's failing to load the kernal there. At this point your best bet is probably to run a Live USB, mount your disk, connect to your home/user and backup your user and re-install
but before you do that, if you try and select one of the other boot options in grub, that fails too right?
there's 4 bazzites, two are the usual duplicates that don't work. first two are 0 and 1 and give what I sent
and it's weird that I was able to get to the login screen when I added 3, but after I got this new error(what I sent in image)
The top error says it cannot find your disk. Check that the UUID in /etc/fstab and what is on the kernel commandline are correct.
I checked the fstab before like he told me to and everything was everything I have (my external hdd wasn't plugged in at first causing the fstab to not be correct, but then I plugged in the HDD and then the fstab was correct
however I'll try what you said in a bit
and if that doesn't work I'll try live usb
does pretty much any distro work for live usb?
or does it have to be specific ones
^for the ones that have liveusb
fedora's works fine
I'm in the fstab
the uuid for
/boot is different from /, /boot/efi,/home, and /var
all those are the same except /boot/efi is a short set of numbers instead of a longer string
should I change the uuid for /boot to match the others?You need to compare what's your disk partition uuids to the ones in your fstab
The image you posted before ending with cc6f did not match one of your actual disks at boot time
none of the of the uuids in fstab match this
The /boot/EFI will be shorter since its fat32 filesystem.
/boot will be its own.
And the rest should all match
they all end in cafe not cc6f
That uuid was attempted during boot.
Are you using LUKS?
idk what luks is
Are you using disk encryption
not that I'm aware of
I have always tried unencrypted if I was given the option
I'm still in bash rn haven't left fstab
Okay. If /etc/fstab matches your disk, the only other thing is making sure the boot entry has the right root uuid specified.
For some reason an errant uuid was being attempted on boot
okay so instead of adding init=/bin/bash I change the uuid?
You can check uuids for you disk with blkid
command not found
Lsblk
ok that's what I was trying to do earlier
I did lsdisk
I don't see uuid
lsblk -o uuid,name,maj:min,rm,size,ro,type,mountpoints
try thatthe thing thing?
as one line?
the highlighted one, hence why it is highlighted
replicates the default output but adds uuid
And I think lsblk -f
thats much better
lsblk -fthe whole thing you sent is highlighted so I guess that's a yes
try
lsblk -f insteadthat is
if lucky you might even do
ls -la /dev/disk/by-uuid
forgot the part that populates that
how does your fstab look like?
no idea why it is complaining about that other mount
idk either
Does fstab break if a mount flag is repeated? noatime is repeated twice on the /var/mnt/steam line
would changing the uuids to this work?
bad idea, as
/dev/sda can change to /dev/sdb by a simple change called "i plugged in a usb and rebooted"
i have many disks on my system, whenever a plug in a disk it might become sdi, sdg, sdh or sdj and if i reboot one of my other disks might take the spot of sdi, sdg, etc insteadinteresting
well I have no further ideas
still learning linux
only thing I'd try is comment out the line /var/mnt/steam entry (even though it has the nofail), it's the only one left without a matching entry from the uuid list
rebooting now
booted to login and none of the 3 passwords I've had during all these problems don't work
this is what shows when I press e in the grub
shows the correct uuid, not what it said it tried to boot from before
So no longer in emergency mode?
no emergency mode for ostree 0
but also no working password
yes emergency mode for ostree 1
but root account is locked
oh cuz of fstab being different probably
as was the original issue
I'M IN
ðŸ˜
I'm guessing some password hash file got corrupted on ostree 0 or something
ostree 1 was a slightly older update as I luckily updated recently
otherwise I'd have to have reinstalled
what's the grub cleanup command again
so you cleaned up the fstab entries in 1 but you had not done any password changes? so you could get in?
correct
i changed it trying to fix the issues
rpm-ostree cleanup -p this should remove the broken deployment 0thanks
then do
rpm-ostree upgrade and you'll be back up to date againit's upgrading
Might be worth pinning your working image with no automounted drives
sudo ostree admin pin 0 then if you encounter this again you can always get back to this image without a bad fstab. You'll need to redo your mountings but at least you can get a booting system easilywell the cause for the bad fstab was my external hdd not being plugged in. so is it possible to have that not stay in the fstab as I intend to use it around different computers?
Use udisks2 as the mount helper for external drives.
this built in app? or a command? or do I install it manually
It's part of both gnome and kde.
It's how external drives show up by default in the file manager
For gnome it will automount them.
Kde I think you have to authorize automount.
When mounted they show up in /run/media/$USER
The command line tool is udiskie