Aloha everyone,

I don't know what happened in the night but there seems to be a problem with a FS now Read-only?

My Docker-Containers wouldn't start and when I sshd into my Server and started the Mover i got this:

create_parent: /mnt/disk1/appdata/plex/Library error: Read-only file system
create_parent: /mnt/disk1/appdata/plex error: Read-only file system
create_parent: /mnt/disk1/appdata error: Read-only file system
create_parent: /mnt/disk1/appdata/tautulli error: Read-only file system
create_parent: /mnt/disk1/appdata error: Read-only file system
move_object: /mnt/disk1/appdata: Read-only file system
create_parent: /mnt/disk2/appdata/mariadb error: Read-only file system
create_parent: /mnt/disk2/appdata error: Read-only file system
move_object: /mnt/disk2/appdata: Read-only file system
create_parent: /mnt/disk3/appdata error: Read-only file system
file: /mnt/disk3/appdata/qbittorrent/config/ipc-socket

I don't know what to do, please help, I am mildly panicking.

Best Regards,
Stefan
 

hal9000-diagnostics-20250328-0904.zip

Mar 28 08:50:21 HAL9000 kernel: BTRFS info (device sdc1): bdev /dev/sdc1 errs: wr 0, rd 0, flush 0, corrupt 11, gen 0
Mar 28 08:50:21 HAL9000 kernel: BTRFS info (device sdc1): bdev /dev/sdd1 errs: wr 0, rd 0, flush 0, corrupt 13, gen 0

 

Btrfs is detecting data corruption on both pool devices, and other issues, recommend running memtest first, then scrub the pool (correct=on) and post the results

Getting the corruption on the pool sorted has to be first priority, but I also notice that you have your docker.img file set to 60GB - any reason it is that large?

39 minutes ago, JorgeB said:

scrub the pool (correct=on) and post the results

Log:

Mar 28 10:50:54 HAL9000 ool www[11428]: /usr/local/emhttp/plugins/dynamix/scripts/btrfs_scrub 'start' '/mnt/cache' ''

Webui:

UUID:             5b0d419c-f792-49d6-b3b8-a34c1789274b
Scrub started:    Fri Mar 28 10:50:54 2025
Status:           aborted
Duration:         0:00:00
Total to scrub:   419.33GiB
Rate:             0.00B/s
Error summary:    no errors found

Or do I need to stop the array first or something else?

Assuming you also ran memtest and no errors were found, and because the pool still has other issues, that's why it went read-only, I would recommend backing up the pool, then reformat and restore the data.

 

 

Then also recommend monitoring the new pool for new errors, if more show up, there's still a problem:

 

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#findComment-700582

 

20 hours ago, JorgeB said:

Assuming you also ran memtest and no errors were found, and because the pool still has other issues, that's why it went read-only, I would recommend backing up the pool, then reformat and restore the data.

And how do I do that? Is there a how-to somewhere?

Thanks for your help.

Edited March 29, 20251 yr by Moppen

Just need to copy the data somewhere, you can use your favorite tool, if VM and Docker services use the pool, disable both before starting, once it's done copying, click on the pool device and then "erase pool", then reformat and restore the data.

Okay, my System is back up. Phew! Thanks everybody for your support.

After I formated the Pool, while copying the original data back to /mnt/cache something strange happened: I was told there was not enough space to copy the Files?!?! What? How?

I did not knew how to help myself so I started the Mover and when there was enough space on the Pool I continued to copy the files back.

But that seems to have f*cked up my containers because after I started the Docker-Environment evey container was acting like it was newly installed. I stopped them all, restored a backup of /mnt/appdata from 3 days ago and now everything seems to be running fine again.