ct1996 Posted August 11, 2018 Share Posted August 11, 2018 Hello, I have a 128GB SSD cache drive that I pretty much only use to hold my docker stuff (plex metadata, etc) I added two disks to the array, as my Disk 1 (HDD) is failing, and so I wanted to replace that disk and also add some more storage while I was in there. I may have jostled the cable for the SSD a little while I was installing it, but when I initially booted back up everything was 100%. All dockers running, the two new drives recognized as unassigned and I started my preclear. For the next 25 hours everything stayed normal while the pre-clear ran. So last night, I stop the array and remove Disk 1, setting it to be a different disk. (One of the unassigned devices I precleared).. The array began the parity rebuild and everything seems to be going peachy. However, this morning I noticed the cache drive is unmountable... I haven't physically opened the case since the drive WAS mountable... I really need the information from my dockers!!! I only have a Windows PC and a Mac besides the server - what is the best way (If its even possible?) to save my docker information? Another small thing - when I started the array rebuild, the "READS" on my unmountable SSD was like 600... now, it is up to 18,089, so it is somehow doing reads to the disk... I don't even know!! Please help! (Rebuild will be done in 11 hours) Quote Link to comment
ct1996 Posted August 11, 2018 Author Share Posted August 11, 2018 (edited) Attached my full diagnostics to this post. Here is the relevant information about the disk: Quote Aug 11 03:58:35 Tower kernel: ata4: SATA max UDMA/133 cmd 0x9880 ctl 0x9800 bmdma 0x9488 irq 19Aug 11 03:58:35 Tower kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)Aug 11 03:58:35 Tower kernel: ata4.00: ATA-8: LITEONIT LCS-128L9S-11 2.5 7mm 128GB, TW0XRV8D5508545S5737, HC7110B, max UDMA/133Aug 11 03:58:35 Tower kernel: ata4.00: 250069680 sectors, multi 16: LBA48 NCQ (depth 0/32)Aug 11 03:58:35 Tower kernel: ata4.00: configured for UDMA/133Aug 11 03:58:35 Tower kernel: sd 4:0:0:0: [sdi] 250069680 512-byte logical blocks: (128 GB/119 GiB)Aug 11 03:58:35 Tower kernel: sd 4:0:0:0: [sdi] Write Protect is offAug 11 03:58:35 Tower kernel: sd 4:0:0:0: [sdi] Mode Sense: 00 3a 00 00Aug 11 03:58:35 Tower kernel: sd 4:0:0:0: [sdi] Write cache: enabled, read cache: enabled, doesn't support DPO or FUAAug 11 03:58:35 Tower kernel: sdi: sdi1Aug 11 03:58:35 Tower kernel: sd 4:0:0:0: [sdi] Attached SCSI diskAug 11 03:58:35 Tower kernel: BTRFS: device fsid cb123f90-1e98-4714-81ca-1b918c43bac8 devid 1 transid 31796 /dev/sdi1Aug 11 03:58:49 Tower emhttpd: LITEONIT_LCS-128L9S-11_2.5_7mm_128GB_TW0XRV8D5508545S5737 (sdi) 512 250069680Aug 11 03:58:49 Tower emhttpd: import 30 cache device: (sdi) LITEONIT_LCS-128L9S-11_2.5_7mm_128GB_TW0XRV8D5508545S5737Aug 11 03:59:21 Tower emhttpd: LITEONIT_LCS-128L9S-11_2.5_7mm_128GB_TW0XRV8D5508545S5737 (sdi) 512 250069680Aug 11 03:59:21 Tower emhttpd: import 30 cache device: (sdi) LITEONIT_LCS-128L9S-11_2.5_7mm_128GB_TW0XRV8D5508545S5737Aug 11 03:59:46 Tower emhttpd: LITEONIT_LCS-128L9S-11_2.5_7mm_128GB_TW0XRV8D5508545S5737 (sdi) 512 250069680Aug 11 03:59:46 Tower emhttpd: import 30 cache device: (sdi) LITEONIT_LCS-128L9S-11_2.5_7mm_128GB_TW0XRV8D5508545S5737Aug 11 03:59:58 Tower emhttpd: shcmd (145): mount -t btrfs -o noatime,nodiratime /dev/sdi1 /mnt/cacheAug 11 03:59:58 Tower kernel: BTRFS info (device sdi1): disk space caching is enabledAug 11 03:59:58 Tower kernel: BTRFS info (device sdi1): has skinny extentsAug 11 03:59:58 Tower kernel: BTRFS info (device sdi1): enabling ssd optimizationsAug 11 03:59:58 Tower kernel: BTRFS warning (device sdi1): sdi1 checksum verify failed on 121503744 wanted 37C43971 found 27A47719 level 0Aug 11 03:59:58 Tower root: mount: /mnt/cache: can't read superblock on /dev/sdi1.Aug 11 03:59:58 Tower kernel: BTRFS error (device sdi1): open_ctree failedAug 11 04:10:38 Tower emhttpd: shcmd (214): /usr/sbin/hdparm -y /dev/sdiAug 11 04:10:39 Tower root: /dev/sdi:Aug 11 04:10:45 Tower emhttpd: shcmd (215): /usr/sbin/hdparm -S0 /dev/sdiAug 11 04:10:45 Tower root: /dev/sdi:Aug 11 13:11:13 Tower emhttpd: shcmd (1296): /usr/sbin/hdparm -y /dev/sdiAug 11 13:11:13 Tower root: /dev/sdi:Aug 11 13:31:49 Tower emhttpd: shcmd (1338): /usr/sbin/hdparm -y /dev/sdiAug 11 13:31:49 Tower root: /dev/sdi:Aug 11 17:44:20 Tower emhttpd: shcmd (1844): /usr/sbin/hdparm -y /dev/sdiAug 11 17:44:20 Tower root: /dev/sdi: tower-diagnostics-20180811-1743.zip Edited August 11, 2018 by ct1996 Quote Link to comment
JorgeB Posted August 12, 2018 Share Posted August 12, 2018 Cache filesystem is corrupt, you can use this to try and recover your data, don't bother with the docker image, that can and should be recreated, try to recover the appdata folder and any other important data. 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.