Hello,

 

Since about 18:00 today, nothing has been working for me in unraid.

 

Warning [TOWER] - pool BTRFS too many profiles (You can ignore this warning when a pool balance operation is in progress)

Fix Common Problems - TowerErrors have been found with your server (Tower).Investigate at Settings / User Utilities / Fix Common ProblemsAlarm

* **Unable to write to cache**

Fix Common Problems meldet auch:

Unable to write to cacheDrive mounted read-only or completely full. 

Unable to write to Docker ImageDocker Image either full or corrupted. Investigate Here:

 

When I start Homeassistant (Linux VM with Hassio), the following error occurs:

Error during execution

internal error: process exited while connecting to monitor: 2024-12-17T18:38:36.335640Z qemu-system-x86_64: -blockdev {"node-name":"libvirt-1-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"qcow2","file":"libvirt-1-storage","backing":null}: Could not open '/mnt/cache/domains/hassos_ova-4.7.qcow2': Read-only file system

 

Even if I want to start all other dockers, ‘Error during execution - SErver Error’ appears
I can also no longer update or restart the Docker.

I have not changed anything on the server. The discs are not full. I am at a loss right now and very dependent on Homeassistant. 
Does anyone have any idea how I can get it running again?
Router (FritzBox) has been restarted - unraid too, of course.

Thank you

 

tower-diagnostics-20241217-1934.zip

Edited December 17, 20241 yr by tOkra28

Please use English only in the general support forum, or you can also use the German forum if you prefer.

 

The pool is going read-only:

Dec 17 19:28:23 Tower kernel: BTRFS: error (device nvme0n1p1: state A) in __btrfs_free_extent:3074: errno=-2 No such entry
Dec 17 19:28:23 Tower kernel: BTRFS info (device nvme0n1p1: state EA): forced readonly

 

With btrfs, recommend backing up and reformatting the pool

 

 

Thanks for the first hint.
Can this just happen?
I haven't changed anything on the system - why is it suddenly read-only?

I have 2 cache discs in RAID-1 for absolute reliability. Is there a short step-by-step guide somewhere for clumsy users on the easiest way to do this?

 

Thank you very much

Is the affected SSD still OK (log in the appendix)?

If I have 2 Cashe discs and they are running as mirrors - why is a backup necessary?

Surely it should be easiest to format the faulty SSD somehow and copy the data back over from the mirrored Cashe disc?

Samsung_SSD_970_EVO_500GB_S5H7NS1N904314P-20241217-2120.txt

 

 

Edit: I have just tried to make a backup with appdata backup.
Unfortunately it doesn't work either: 

I [17.12.2024 21:28:00][ℹ️][Main] 👋 WELCOME TO APPDATA.BACKUP!!
[17.12.2024 21:28:00][ℹ️][Main] Backing up from: /mnt/user/appdata, /mnt/cache/appdata
[17.12.2024 21:28:00][ℹ️][Main] Backing up to: /mnt/user/Backup/unRaid/Appdata/ab_20241217_212800
[17.12.2024 21:28:00][❌][Main] Cannot create destination folder!
[17.12.2024 21:28:00][ℹ️][Main] Checking retention...
[17.12.2024 21:28:00][ℹ️][Main] DONE! Thanks for using this plugin and have a safe day
[17.12.2024 21:28:00][ℹ️][Main] ❤️
 

I still have an older backup, but it's all a bit worrying
 

 

Edited December 17, 20241 yr by tOkra28

This is a filesystem problem, not a device problem, so being a mirror doesn't help, both are affected.