jerseyknoll Posted December 14, 2018 Share Posted December 14, 2018 I recently uninstalled a MineOS-Node docker and i can't delet the remaining appdata folder. After failing to delete with Krusader and the CA appdata cleanup plugin i tried with the terminal and got the error message that it is a read only filesystem. Any help would be greatly appreciated. I checked the log and found the following. Dec 13 20:23:56 Tower kernel: print_req_error: I/O error, dev loop2, sector 15422648 Dec 13 20:23:56 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 184, rd 0, flush 0, corrupt 0, gen 0 Dec 13 20:23:56 Tower kernel: loop: Write error at byte offset 7896920064, length 4096. Dec 13 20:23:56 Tower kernel: print_req_error: I/O error, dev loop2, sector 15423672 Dec 13 20:23:56 Tower kernel: loop: Write error at byte offset 7897444352, length 4096. Dec 13 20:23:56 Tower kernel: print_req_error: I/O error, dev loop2, sector 15424696 Dec 13 20:23:56 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 185, rd 0, flush 0, corrupt 0, gen 0 Dec 13 20:23:56 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 186, rd 0, flush 0, corrupt 0, gen 0 Dec 13 20:24:27 Tower kernel: lo_write_bvec: 3 callbacks suppressed Dec 13 20:24:27 Tower kernel: loop: Write error at byte offset 12746752, length 4096. Dec 13 20:24:27 Tower kernel: print_req_error: 3 callbacks suppressed Dec 13 20:24:27 Tower kernel: print_req_error: I/O error, dev loop2, sector 24896 Dec 13 20:24:27 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 187, rd 0, flush 0, corrupt 0, gen 0 Dec 13 20:24:27 Tower kernel: loop: Write error at byte offset 7892725760, length 4096. Dec 13 20:24:27 Tower kernel: print_req_error: I/O error, dev loop2, sector 15415480 Dec 13 20:24:27 Tower kernel: loop: Write error at byte offset 7894036480, length 4096. Dec 13 20:24:27 Tower kernel: print_req_error: I/O error, dev loop2, sector 15418040 Dec 13 20:24:27 Tower kernel: loop: Write error at byte offset 7894560768, length 4096. Dec 13 20:24:27 Tower kernel: print_req_error: I/O error, dev loop2, sector 15419064 Dec 13 20:24:27 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 188, rd 0, flush 0, corrupt 0, gen 0 Dec 13 20:24:27 Tower kernel: loop: Write error at byte offset 7894822912, length 4096. Dec 13 20:24:27 Tower kernel: print_req_error: I/O error, dev loop2, sector 15419576 Dec 13 20:24:27 Tower kernel: loop: Write error at byte offset 7895347200, length 4096. Dec 13 20:24:27 Tower kernel: print_req_error: I/O error, dev loop2, sector 15420600 Dec 13 20:24:27 Tower kernel: loop: Write error at byte offset 7895871488, length 4096. Dec 13 20:24:27 Tower kernel: print_req_error: I/O error, dev loop2, sector 15421624 Dec 13 20:24:27 Tower kernel: loop: Write error at byte offset 7896395776, length 4096. Dec 13 20:24:27 Tower kernel: print_req_error: I/O error, dev loop2, sector 15422648 Dec 13 20:24:27 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 189, rd 0, flush 0, corrupt 0, gen 0 Dec 13 20:24:27 Tower kernel: loop: Write error at byte offset 7896920064, length 4096. Dec 13 20:24:27 Tower kernel: print_req_error: I/O error, dev loop2, sector 15423672 Dec 13 20:24:27 Tower kernel: loop: Write error at byte offset 7897444352, length 4096. Dec 13 20:24:27 Tower kernel: print_req_error: I/O error, dev loop2, sector 15424696 Dec 13 20:24:27 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 190, rd 0, flush 0, corrupt 0, gen 0 Dec 13 20:24:27 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 191, rd 0, flush 0, corrupt 0, gen 0 Dec 13 20:40:24 Tower login[9517]: ROOT LOGIN on '/dev/pts/0' Quote Link to comment
trurl Posted December 14, 2018 Share Posted December 14, 2018 Go to Tools - Diagnostics and attach the complete diagnostics zip to your next post. Quote Link to comment
jerseyknoll Posted December 14, 2018 Author Share Posted December 14, 2018 Here they are. tower-diagnostics-20181213-2103.zip Quote Link to comment
trurl Posted December 14, 2018 Share Posted December 14, 2018 You have corruption on you docker image. You will have to delete and recreate it then reinstall all your dockers using the Previous Apps feature on the Apps page. https://forums.unraid.net/topic/57181-real-docker-faq/#comment-564309 And corruption of your cache pool. You will have to back it up and reformat. https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?page=2#comment-543490 Quote Link to comment
JorgeB Posted December 14, 2018 Share Posted December 14, 2018 There were previous read errors on one of your cache devices: Dec 9 20:39:33 Tower kernel: BTRFS info (device sdd1): bdev /dev/sdd1 errs: wr 0, rd 3, flush 0, corrupt 0, gen 0 This is a hardware problem, and while there were very few looks like it was enough to cause problems, see here for more info on how to monitor the pools for the future: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=700582 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.