September 21, 20196 yr Im having issues with my unraid dockers. I cant remove or create new ones and the ones that work only work for a while until the read only file system errors come up. /var/lib/docker/containers/239ec48e7a114bcfeac65ca2836282ddfeebb83699543499b70425c1c5a717c1/239ec48e7a114bcfeac65ca2836282ddfeebb83699543499b70425c1c5a717c1-json.log: read-only file system"} e":"open /var/lib/docker/containers/239ec48e7a114bcfeac65ca2836282ddfeebb83699543499b70425c1c5a717c1/239ec48e7a114bcfeac65ca2836282ddfeebb83699543499b70425c1c5a717c1-json.log: read-only file system"} e":"open snippet from the log Sep 18 19:28:16 Tower kernel: BTRFS error (device sdh1): parent transid verify failed on 967524352 wanted 4235659 found 41355 Sep 18 19:28:16 Tower kernel: BTRFS: error (device sdh1) in btrfs_finish_ordered_io:3071: errno=-5 IO failure Sep 18 19:28:16 Tower kernel: BTRFS info (device sdh1): forced readonly Sep 18 19:28:16 Tower kernel: BTRFS error (device sdh1): pending csums is 3932160 Sep 18 19:28:16 Tower kernel: loop: Write error at byte offset 65536, length 4096. Sep 18 19:28:16 Tower kernel: print_req_error: I/O error, dev loop2, sector 128 Sep 18 19:28:16 Tower kernel: print_req_error: I/O error, dev loop2, sector 128 Sep 18 19:28:16 Tower kernel: BTRFS warning (device loop2): lost page write due to IO error on /dev/loop2 Sep 18 19:28:16 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 1, rd 0, flush 0, corrupt 0, gen 0 Sep 18 19:28:16 Tower kernel: BTRFS error (device loop2): error writing primary super block to device 1 Sep 18 19:28:16 Tower kernel: BTRFS: error (device loop2) in write_all_supers:3848: errno=-5 IO failure (1 errors while writing supers) Sep 18 19:28:16 Tower kernel: BTRFS info (device loop2): forced readonly Sep 18 19:28:16 Tower kernel: BTRFS: error (device loop2) in btrfs_sync_log:3161: errno=-5 IO failure Sep 18 19:28:16 Tower kernel: BTRFS error (device loop2): pending csums is 2252800 Sep 18 19:28:17 Tower kernel: loop: Write error at byte offset 12811825152, length 4096. Sep 18 19:28:17 Tower kernel: print_req_error: I/O error, dev loop2, sector 25023096 Sep 18 19:28:17 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 2, rd 0, flush 0, corrupt 0, gen 0 Sep 18 19:28:17 Tower kernel: loop: Write error at byte offset 3483185152, length 4096. Sep 18 19:28:17 Tower kernel: print_req_error: I/O error, dev loop2, sector 6803096 Sep 18 19:28:17 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 3, rd 0, flush 0, corrupt 0, gen 0 thankful for the help. Im sure its something simple tower-syslog-20190920-2101.zip
September 21, 20196 yr Community Expert Cache filesystem is corrupt with a fatal problem, you'll need to backup data and re-format, some recovery options here if needed.
September 21, 20196 yr Author Can I just use Krusader to move everything off the Cache SSD, stop the array, remove the cache drive, then re-add the cache drive and put the data back with krusader? the stuff in the link doesnt exactly look straight forward.
September 21, 20196 yr Author Is this what I should do? Stop the array. Main, Cache Device, Change the format type to what you want. If its already what you want and just want to reformat it, then: Change it to anything else. Start the array. Format the drive Stop the array Change the format type to what you want Start the array Format the drive Edited September 21, 20196 yr by cptfbi
September 22, 20196 yr Community Expert You might be able to still copy the data normally form the pool, using Krusader or any other toll, if you can't then see the recovery options.
Archived
This topic is now archived and is closed to further replies.