I have been trying to get Bazzite to update for some time now and have been going between posts that I can find but come up short.
I believe the issue has something to do with ostree being labeled as a read-only file, but I might be missing something. I have tried telling the consel to reset ostree, tried using the usroverlay command, even tried looking at making a new sysroot path to try and be able to update, only for every command to be shut down with the file being read-only.
The photo is the majority of what I repeatedly get when trying to update, though this time it actually tried to fetch the update instead of telling me it couldn’t change anything. I also do not know a lot about bazzite or Linux code in general, so I may have severally missed something.
It should also be noted that things have slowly began to stop working. Steam will not launch games and Mozzila says that it is running an instance despite there not being one open, and it is bad enough to where my computer even gives a message before letting me shut it off, and I am fairly certain it is connected to the issue since they appeared when I started trying to update before actually trying to change things.
It even says in red, ‘upgrade’ components failed. Try running “ujust upgrade” to update Bazzie revision, and then update components to latest versions with ‘ujust update’. And don’t forget the restarts.
From what I can tell, it isnt layered. rpm-ostree search gives the error “bash: syntax error near unexpected token ‘newline’”. The uninstall command gives the same result, but doing rpm-ostree reset gives me the message “No change.”
Looked at your picture again, it seems your file system is read-only, it tried to delete a stuck file. Try these command to check what is causing it
# Find the file
sudo find /sysroot/ostree/deploy/default/deploy/ba9d53eb602f94484e77cd* -name 'yaml-indent-strict.yaml.txt'
# use the file path to check/clear its immutable attribute
sudo lsattr <path-to-file>
sudo chattr -i <path-to-file>
# can also try to clean you deployment and try again.
sudo rpm-ostree cleanup -p
sudo rpm-ostree upgrade
# check if the entire subvolume is set to read only or if btrfs saw an error and locked itself
sudo btrfs property get /sysroot ro
sudo btrfs device stats /sysroot
# if that returns true, set it to false and retry upgrade
sudo btrfs property set -f /sysroot ro false
sudo rpm-ostree upgrade
Oh, I missed that aswell. I thought he just had removed file access for writing.
Just to clarify, you didn’t accidentally install the package/live version of it, right? Cause if it is a new install or a packaged/live one, it would have been easier and faster to just ‘repair’ for a non-packaged/live version of bazzite.
I guess, i’ll add it here. If you get the file system fixed, and want to install custom software. But it either fails completely or gives you the blank screen. Try using Flatseal to give the program rights to some (either system or account) folders. Cause, of course, that is a thing.
ro is already set to false, however the device stats says “[/dev/nvme0n1p3].corruption_errs 48”
Also something to add, I thought about rolling back the version to maybe be able to update from an older version. It will not let me because its an invalid argument (?) Rebasing also fails, same reason.
More to add, looked in fastfetch, thinking maybe that would give me something, and it says btrfs is set to read-only. Trying to set it to false gets refused for it being read-only file system.
I do not know, but I’ve had the software installed for a while now, at least 3-6 months, if not longer, so it seems weird that it would remove access now of all times. I should also note that it started happening in the middle of using the computer, not upon booting it up, so it would be extra weird if that was the cause.
From what I can tell, SSD health is fine. Everything looks correct, no errors or reports, literally everything is in working order as far as hardware goes.
All honesty, I just went and saved everything I needed to a Hard Drive and reinstalled Bazzite. Whatever I went and did just completely Fd it over. Thanks for trying, though.
