Sudden corruption (i think) on cache disk, need help backing up docker/appdata and setting back up (*newbie alert*)

[yourguybob]

Hello - This is my first post, and I am loving unraid, but please know that I only have about 9 days of experience under my belt, so please hang with me! I've searched and searched and feel like I am getting about 80 percent of what I need to do, but need help getting me over the hump.

 

Basically, I noticed after a reboot that Plex was not running, which was odd since I set a number of my docker containers to autorun. Poking around I found that of the 7 containers I had, most would simply refuse to start at all and two would only occasionally, then stop, then not start again. I took a look at the system log (from the icon in the GUI....top right) and saw what I thought was a pretty clear indication of file, file system, or disk corruption.

 

Sensing that whatever the solution is that an extra unassigned disk may be handy, I pre-cleared a spare 500gb HDD with the intention of having handy to possibly back up to (once I figured/figure out how to do that 😄).

 

Obviously, if there is a solution, please share, however, would following this guide solve my problem (if I moved everything to the slower new HDD), formatted the original SSD, and then did the operation in reverse? What if things are degenerated enough that I can't recover the data - am i out of luck?

 

Primary concerns:

• I really want to avoid starting my tedious docker setup over from scratch
• I really, really, really want to retain my plex appdata!
• That I have something fundamentally wrong with my setup that caused this, although I just don't know what that could be.

 

Thank you in advance!

 

server-diagnostics-20210315-1826.zip

[JorgeB]

There are issues with the cache device:

 

Mar 14 20:51:13 hafer kernel: sd 1:0:1:0: [sdc] tag#3509 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s
Mar 14 20:51:13 hafer kernel: sd 1:0:1:0: [sdc] tag#3509 Sense Key : 0x3 [current]
Mar 14 20:51:13 hafer kernel: sd 1:0:1:0: [sdc] tag#3509 ASC=0x11 ASCQ=0x0
Mar 14 20:51:13 hafer kernel: sd 1:0:1:0: [sdc] tag#3509 CDB: opcode=0x28 28 00 00 be a7 e0 00 00 20 00
Mar 14 20:51:13 hafer kernel: blk_update_request: critical medium error, dev sdc, sector 12494816 op 0x0:(READ) flags 0x0 phys_seg 4 prio class 0
Mar 14 20:51:13 hafer kernel: BTRFS warning (device sdc1): direct IO failed ino 260 rw 0,0 sector 0xbea7e8 len 0 err no 10
Mar 14 20:51:13 hafer kernel: BTRFS warning (device sdc1): direct IO failed ino 260 rw 0,0 sector 0xbea7f0 len 0 err no 10
Mar 14 20:51:13 hafer kernel: BTRFS warning (device sdc1): direct IO failed ino 260 rw 0,0 sector 0xbea7f8 len 0 err no 10
Mar 14 20:51:13 hafer kernel: BTRFS warning (device sdc1): direct IO failed ino 260 rw 0,0 sector 0xbea800 len 0 err no 10
Mar 14 20:51:13 hafer kernel: blk_update_request: I/O error, dev loop2, sector 11925472 op 0x0:(READ) flags 0x1000 phys_seg 1 prio class 0
Mar 14 20:51:13 hafer kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 293, flush 0, corrupt 48, gen 0

 

Try connecting it to the onboard SATA ports instead, then run a scrub.