Hmmmm

Just wanted to say that I recreated the disk and that the restore of the backup is nearly finished. Thanks, it seems to work now. Fingers crossed that I don't get this strange problem again...

Thanks. I will do the recreating after the backup is completed. Is ZFS a valid option? I saw some videos of SpaceInvaderOne and it seemed interesting. Would like to have a good mix between stability and features, although stability is slightly more important to me.

Thanks for your answer, no problem! Since I haven't done this at all in Unraid: can you point me to a tutorial/manual about this? Do I have to stop the array and take the disk out of slot 1 and put it back in so that I can reformat it? Will parity be affected or is it still available as 'last resort' when the backup and restore process from that unassigned disk fails for some reason? There is no option to 'backup' the shares (settings etc.), is it? One last question: which Filesystem should I choose for the fresh start? BTRFS seems quite fragile, is there a better one for complete disk encryption? Thanks for your time, Jorge!

Can I do something with the parity to solve the problem of being unable to write to disk 1?

I totally messed up now, my cache drive is now unmountable, I attached new logs... The cache now says "not mountable: not supported or no filesystem" Problem is that I don't have any backups of this cache drive. It started with the error message: luks error 5. I then (maybe this was a big mistake) shutdown the array and removed the cache from the cache slot, started the array and tried to put the cache back in the slot. Now I have the error message above. Damn... Edit: will a reboot fix this problem that Unraid can't detect the filesystem? I tried to btrfs check the cache, but was unable to (altough in the maintenance mode, the cache drive seems to be mounted (??)) Reboot seems to have fixed the problem. Sorry for the confusion. The array disk 1 non writable problem still is there though...

Done. I get no errors after the check:

I get the following output: Seems to be problematic? What can I do now?

Thanks for your your time. New diags:

I get:

Thanks in advance for taking the time to help me!

When I take a look in the syslog, can the following lines help? Thanks!

Hello there. I use BTRFS (encrypted) for my cache and array as filesystem. For some reason my disk1 (only 'usable' Array disk in my setup next to a parity drive of the same size, 20TB) is in read-only mode since Oct. 5 (Fix Common Problems Error: 'Unable to write to disk1', when I try to create a file or a folder on a share on disk1 the file manager in Unraid prompts: 'mkdir: cannot create directory ### Read-only file system'). My drive still has a lot of space available, more than 40% is empty. I tried to troubleshoot with some of the old reports and threads of a 'unable to write' message, but my case seems to be different - the cache data SSD seems to be perfectly usable and all of my docker containers (as long as they don't need to write stuff to disk1) are running totally fine. I scrubbed disk1 and there were no errors at all. Currently I'm running an advanced SMART test, which is not yet finished. I was not able to fix my problem with the older threads. I'm not sure whether that's possible or not, but I think that I somehow misconfigured something with the shares or with permissions - I had a very annoying Nextcloud problem with those permission problems, probably this was the starting point... Anyway, I can upload diagnostic files - but which of those .txt files in the .zip are helpful to find the cause of the problem? Currently I'm backing up the files to an unassigned device and this process is running fine so far. But overall I'd like to avoid re-formatting the whole device, especially because I'm not totally sure how to reconfigure everything to get back on track. BTW: I'm not sure whether this can be part of the problem but there was a power outage maybe 2 weeks ago. I had no UPS, so the server died instantly. There seemed to be no immediate issues after the power came back, but now I have some doubts about that... Edit: Interestingly, the Main Tab shows at least some writing operations on disk1 and the parity drive. Which is odd, because the file system is read-only currently??