System randomly goes into read-only mode can not pin point exact cause

After a fresh install of GNOME Nvidia open trying to setup podman quadlet I get this error for jellyfin Error systemd logs for Jellyfin: https://paste.centos.org/view/849746a0 After trying to start Jellyfin through normal troubleshooting the system enters a read-only state which I have never seen before rpm-ostree status:
max@reicurse:~$ rpm-ostree status
Error: error returned from database: (code: 8) attempt to write a readonly database

Caused by:
(code: 8) attempt to write a readonly database

Location:
crates/atuin/src/command/client/history.rs:321:9
State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-gnome-nvidia-open:stable
Digest: sha256:44711a2bf270a7e222b5992ee4ded7ba2d22f1d36d0a837fed2ac9267a7bb6d1
Version: 41.20241104 (2024-11-04T05:11:23Z)
LayeredPackages: sunshine

ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-gnome-nvidia-open:stable
Digest: sha256:44711a2bf270a7e222b5992ee4ded7ba2d22f1d36d0a837fed2ac9267a7bb6d1
Version: 41.20241104 (2024-11-04T05:11:23Z)
max@reicurse:~$ rpm-ostree status
Error: error returned from database: (code: 8) attempt to write a readonly database

Caused by:
(code: 8) attempt to write a readonly database

Location:
crates/atuin/src/command/client/history.rs:321:9
State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-gnome-nvidia-open:stable
Digest: sha256:44711a2bf270a7e222b5992ee4ded7ba2d22f1d36d0a837fed2ac9267a7bb6d1
Version: 41.20241104 (2024-11-04T05:11:23Z)
LayeredPackages: sunshine

ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-gnome-nvidia-open:stable
Digest: sha256:44711a2bf270a7e222b5992ee4ded7ba2d22f1d36d0a837fed2ac9267a7bb6d1
Version: 41.20241104 (2024-11-04T05:11:23Z)
1 Reply
Max
MaxOP3mo ago
Update: seems to be just with Jellyfin for some reason which is weird since Jellyfin is working fine on my mini amd PC

Did you find this page helpful?