On aurora-dx:latest
When I run rpm-ostree status I get this:
❯ rpm-ostree status
State: idle
Bus error (core dumped)
What is causing this?
It seems to be updating, but it’s nice to sse the output.
Never seen anything like this.
What do you get if you run rpm-ostree update?
Also are you on stable/stable-daily or latest image stream?
❯ rpm-ostree update
note: automatic updates (stage) are enabled
Pulling manifest: ostree-image-signed:docker://ghcr.io/ublue-os/aurora-dx:latest
No upgrade available.
I think it’s current at the moment. I am on latest image stream.
Oh sorry, you mentioned being on the latest image in the first post.
Atleast it looks that the whole rpm-ostree is not borked as seems it updates normally and doesn’t crash.
Does it give the same bland error if you do rpm-ostree status -v
Yes, same message…
The only remote idea I have is that I had a bad memory stick, I replaced it.
If I run a btrfs check I get errors, I need to boot to a USB stick to run it for the exact message.
~ btrfs check ~
root@localhost-live:~# btrfs check /dev/nvmexxxxx
Opening filesystem to check…
Checking filesystem on /dev/nvmexxxxx
UUID: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
[1/8] checking log skipped (none written)
[2/8] checking root items
[3/8] checking extents
ref mismatch on [509702152192 8192] extent item 140737488355329, found 1
ERROR: errors found in extent allocation tree or chunk allocation
[4/8] checking free space tree
[5/8] checking fs roots
unresolved ref dir 2859 index 516 namelen 67 name b9ecb9d1742bc4d80f86c73c175681e5f96de6adb3efe5306ee8e103a3ed43.file filetype 1 errors 4, no inode ref
unresolved ref dir 2859 index 516 namelen 67 name b9ecb9d1742bc�d80f86c73c175681e5f96de6adb3efe5306ee8e103a3ed43.file filetype 0 errors 3, no dir item, no dir index
ERROR: errors found in fs roots
found 663768059904 bytes used, error(s) found
total csum bytes: 202719488
total tree bytes: 2626912256
total fs tree bytes: 2178744320
total extent tree bytes: 204308480
btree space waste bytes: 560474952
file data blocks allocated: 1282914082816
referenced 683646259200
I am reluctant to run a repair because btrfs warns against it.
There are many btrfs forums that provide information on recovery but I have not had a lot of luck once the filesystem is corrupted. I don’t think there are many experts here that can help with that. I hope you have good luck trying to recover your disk.