March 28, 201610 yr Hi unRAID Community, I hope I can get some help here with my BTRFS Cache pool.. I never had any errors or issues and no changes to the system hardware or software wise in months. ( Just regular unRAID Updates) , Last week I had an issue with one my dockers, I went to restart it and the docker refused to come back online.. No errors seen at that time in the docker logs.. After trying a few more apps and all not wanting to restart.. I restarted the docker engine... My docker imaged seemed broken as if I pointed to a new image file the docker engine would start, not to concerned at the time I just kept the new image and re-installed a few dockers, took me only a few minutes.. Well yesterday I had the same issue, docker app was not working.. Went to restart and well I started to dig into different errors and I found a few on my Cache 2 and 3 drives.. I don't have the original errors anymore as I have rebooted but my SATA Link was restarting and speeds were changing from 6 Gbps on startup to 3 and then finally 1.5 , It was very strange.. The only 2 things in common between the 2 drives is they shared the same power split.. This being one of the mentioned symptoms of such errors I added a temp power supply for the 2 SSDs and it seems to of stopped as many errors in the 2 cache drive logs.. I have now ran a scrub , twice. I am still seeing some errors in the logs, I know some are from when I ran the scrub.. I think I should do another reboot to clear them again but I want to understand more about the errors and the nature of the corruption since I had 2 drives with issues that's the reason my docker image was corrupting ? Any way to use BTRFS Snapshots to recover next time? Edit: TL;DR Dockers crashed, Made a new img file, Reinstalled dockers pointed to existing paths, dockers crashed again last night. Errors on 2 SSD's out of the 4 Drive cache pool. The 2 drives do not share the same SATA Controllers one is in a PCI-E Card and the other is on the mobo. They did share the same daisy chained power source off of a some fans ( yea I know I was short for connections ) and now temporarily share power still but from a dedicated external molex power supply.. Just temp until I put a new PSU next week.. Drives 1 and 4 do not have any logs, only 2 and 3 are generating output. ------------ Cache Drive 2 Errors --------- Mar 28 17:37:59 CORE kernel: ata1: SATA max UDMA/133 abar m2048@0xf4712000 port 0xf4712100 irq 28 Mar 28 17:37:59 CORE kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Mar 28 17:37:59 CORE kernel: ata1.00: READ LOG DMA EXT failed, trying unqueued Mar 28 17:37:59 CORE kernel: ata1.00: failed to get NCQ Send/Recv Log Emask 0x1 Mar 28 17:37:59 CORE kernel: ata1.00: ATA-9: Samsung SSD 840 Series, S14CNEACA47078H, DXT09B0Q, max UDMA/133 Mar 28 17:37:59 CORE kernel: ata1.00: 234441648 sectors, multi 16: LBA48 NCQ (depth 31/32), AA Mar 28 17:37:59 CORE kernel: ata1.00: failed to get NCQ Send/Recv Log Emask 0x1 Mar 28 17:37:59 CORE kernel: ata1.00: configured for UDMA/133 Mar 28 17:37:59 CORE kernel: ata1.00: Enabling discard_zeroes_data Mar 28 17:37:59 CORE kernel: sd 1:0:0:0: [sdb] 234441648 512-byte logical blocks: (120 GB/112 GiB) Mar 28 17:37:59 CORE kernel: sd 1:0:0:0: [sdb] Write Protect is off Mar 28 17:37:59 CORE kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Mar 28 17:37:59 CORE kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Mar 28 17:37:59 CORE kernel: ata1.00: Enabling discard_zeroes_data Mar 28 17:37:59 CORE kernel: sdb: sdb1 Mar 28 17:37:59 CORE kernel: ata1.00: Enabling discard_zeroes_data Mar 28 17:37:59 CORE kernel: sd 1:0:0:0: [sdb] Attached SCSI disk Mar 28 17:38:11 CORE emhttp: Samsung_SSD_840_Series_S14CNEACA47078H (sdb) 117220824 Mar 28 17:38:11 CORE emhttp: import 5 cache device: sdb Mar 28 17:38:12 CORE emhttp: shcmd (7): /usr/sbin/hdparm -S0 /dev/sdb &> /dev/null Mar 28 17:38:12 CORE emhttp: Samsung_SSD_840_Series_S14CNEACA47078H (sdb) 117220824 Mar 28 17:38:12 CORE emhttp: import 5 cache device: sdb Mar 28 17:38:41 CORE emhttp: Samsung_SSD_840_Series_S14CNEACA47078H (sdb) 117220824 Mar 28 17:38:41 CORE emhttp: import 5 cache device: sdb Mar 28 17:38:41 CORE emhttp: Samsung_SSD_840_Series_S14CNEACA47078H (sdb) 117220824 Mar 28 17:38:41 CORE emhttp: import 5 cache device: sdb Mar 28 17:38:59 CORE emhttp: Samsung_SSD_840_Series_S14CNEACA47078H (sdb) 117220824 Mar 28 17:38:59 CORE emhttp: import 5 cache device: sdb Mar 28 17:38:59 CORE emhttp: shcmd (32): /usr/sbin/hdparm -S0 /dev/sdb &> /dev/null Mar 28 17:38:59 CORE kernel: BTRFS: device fsid 640b4483-c816-4562-b098-6b90c83f57ef devid 1 transid 376401 /dev/sdb1 Mar 28 17:39:00 CORE kernel: BTRFS info (device sdb1): disk space caching is enabled Mar 28 17:40:43 CORE kernel: BTRFS warning (device sdb1): failed to load free space cache for block group 1022909087744, rebuild it now Mar 28 17:40:45 CORE kernel: BTRFS (device sdb1): parent transid verify failed on 1017575800832 wanted 376102 found 376100 Mar 28 17:40:45 CORE kernel: BTRFS: read error corrected: ino 1 off 1017575800832 (dev /dev/sdb1 sector 81860160) Mar 28 17:40:45 CORE kernel: BTRFS: read error corrected: ino 1 off 1017575804928 (dev /dev/sdb1 sector 81860168) Mar 28 17:40:45 CORE kernel: BTRFS: read error corrected: ino 1 off 1017575809024 (dev /dev/sdb1 sector 81860176) Mar 28 17:40:45 CORE kernel: BTRFS: read error corrected: ino 1 off 1017575813120 (dev /dev/sdb1 sector 81860184) Mar 28 17:41:10 CORE kernel: BTRFS (device sdb1): parent transid verify failed on 1017576390656 wanted 376102 found 375923 Mar 28 17:41:10 CORE kernel: BTRFS: read error corrected: ino 1 off 1017576390656 (dev /dev/sdb1 sector 81861312) Mar 28 17:41:10 CORE kernel: BTRFS: read error corrected: ino 1 off 1017576394752 (dev /dev/sdb1 sector 81861320) Mar 28 17:41:10 CORE kernel: BTRFS: read error corrected: ino 1 off 1017576398848 (dev /dev/sdb1 sector 81861328) Mar 28 17:41:10 CORE kernel: BTRFS: read error corrected: ino 1 off 1017576402944 (dev /dev/sdb1 sector 81861336) Mar 28 17:48:08 CORE kernel: BTRFS: checksum/header error at logical 1018290290688 on dev /dev/sdb1, sector 83255648: metadata leaf (level 0) in tree 5 Mar 28 17:48:08 CORE kernel: BTRFS: checksum/header error at logical 1018290290688 on dev /dev/sdb1, sector 83255648: metadata leaf (level 0) in tree 5 Mar 28 17:48:08 CORE kernel: BTRFS: bdev /dev/sdb1 errs: wr 0, rd 0, flush 0, corrupt 1, gen 0 Mar 28 17:48:08 CORE kernel: BTRFS: checksum/header error at logical 1017705529344 on dev /dev/sdb1, sector 82113536: metadata leaf (level 0) in tree 7 Mar 28 17:48:08 CORE kernel: BTRFS: checksum/header error at logical 1017705529344 on dev /dev/sdb1, sector 82113536: metadata leaf (level 0) in tree 7 Mar 28 17:48:08 CORE kernel: BTRFS: bdev /dev/sdb1 errs: wr 0, rd 0, flush 0, corrupt 1, gen 1 Mar 28 18:04:18 CORE kernel: BTRFS: checksum/header error at logical 1018290290688 on dev /dev/sdb1, sector 83255648: metadata leaf (level 0) in tree 5 Mar 28 18:04:18 CORE kernel: BTRFS: checksum/header error at logical 1017705529344 on dev /dev/sdb1, sector 82113536: metadata leaf (level 0) in tree 7 Mar 28 18:04:18 CORE kernel: BTRFS: checksum/header error at logical 1017705529344 on dev /dev/sdb1, sector 82113536: metadata leaf (level 0) in tree 7 Mar 28 18:04:18 CORE kernel: BTRFS: bdev /dev/sdb1 errs: wr 0, rd 0, flush 0, corrupt 1, gen 2 Mar 28 18:04:18 CORE kernel: BTRFS: checksum/header error at logical 1018290290688 on dev /dev/sdb1, sector 83255648: metadata leaf (level 0) in tree 5 Mar 28 18:04:18 CORE kernel: BTRFS: bdev /dev/sdb1 errs: wr 0, rd 0, flush 0, corrupt 2, gen 2 Mar 28 18:22:28 CORE kernel: BTRFS warning (device sdb1): csum failed ino 1561639 off 323584 csum 3617176600 expected csum 3648121054 ------------ Cache Drive 3 Errors --------- Mar 28 17:37:59 CORE kernel: ata7: SATA max UDMA/133 abar m512@0xf4610000 port 0xf4610100 irq 30 Mar 28 17:37:59 CORE kernel: ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Mar 28 17:37:59 CORE kernel: ata7.00: supports DRM functions and may not be fully accessible Mar 28 17:37:59 CORE kernel: ata7.00: disabling queued TRIM support Mar 28 17:37:59 CORE kernel: ata7.00: ATA-9: Samsung SSD 850 PRO 128GB, S24ZNXAGB10425J, EXM02B6Q, max UDMA/133 Mar 28 17:37:59 CORE kernel: ata7.00: 250069680 sectors, multi 1: LBA48 NCQ (depth 31/32), AA Mar 28 17:37:59 CORE kernel: ata7.00: supports DRM functions and may not be fully accessible Mar 28 17:37:59 CORE kernel: ata7.00: disabling queued TRIM support Mar 28 17:37:59 CORE kernel: ata7.00: configured for UDMA/133 Mar 28 17:37:59 CORE kernel: sd 7:0:0:0: [sdh] 250069680 512-byte logical blocks: (128 GB/119 GiB) Mar 28 17:37:59 CORE kernel: sd 7:0:0:0: [sdh] Write Protect is off Mar 28 17:37:59 CORE kernel: sd 7:0:0:0: [sdh] Mode Sense: 00 3a 00 00 Mar 28 17:37:59 CORE kernel: sd 7:0:0:0: [sdh] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Mar 28 17:37:59 CORE kernel: sdh: sdh1 Mar 28 17:37:59 CORE kernel: sd 7:0:0:0: [sdh] Attached SCSI disk Mar 28 17:38:11 CORE emhttp: Samsung_SSD_850_PRO_128GB_S24ZNXAGB10425J (sdh) 125034840 Mar 28 17:38:11 CORE emhttp: import 6 cache device: sdh Mar 28 17:38:12 CORE emhttp: shcmd (: /usr/sbin/hdparm -S0 /dev/sdh &> /dev/null Mar 28 17:38:12 CORE emhttp: Samsung_SSD_850_PRO_128GB_S24ZNXAGB10425J (sdh) 125034840 Mar 28 17:38:12 CORE emhttp: import 6 cache device: sdh Mar 28 17:38:41 CORE emhttp: Samsung_SSD_850_PRO_128GB_S24ZNXAGB10425J (sdh) 125034840 Mar 28 17:38:41 CORE emhttp: import 6 cache device: sdh Mar 28 17:38:41 CORE emhttp: Samsung_SSD_850_PRO_128GB_S24ZNXAGB10425J (sdh) 125034840 Mar 28 17:38:41 CORE emhttp: import 6 cache device: sdh Mar 28 17:38:59 CORE emhttp: Samsung_SSD_850_PRO_128GB_S24ZNXAGB10425J (sdh) 125034840 Mar 28 17:38:59 CORE emhttp: import 6 cache device: sdh Mar 28 17:38:59 CORE emhttp: shcmd (33): /usr/sbin/hdparm -S0 /dev/sdh &> /dev/null Mar 28 17:38:59 CORE kernel: BTRFS: device fsid 640b4483-c816-4562-b098-6b90c83f57ef devid 3 transid 376401 /dev/sdh1 Mar 28 17:43:47 CORE kernel: BTRFS: checksum error at logical 1000221642752 on dev /dev/sdh1, sector 3925128, root 5, inode 1426592, offset 7262208, length 4096, links 1 (path: appdata/plexpassmediaserver/Plex Media Server/Media/localhost/e/4b7e5a96770f020794acd4624d6c7fce2c6a9dc.bundle/Contents/Indexes/index-sd.bif) Mar 28 17:43:47 CORE kernel: BTRFS: checksum error at logical 1000220659712 on dev /dev/sdh1, sector 3923208, root 5, inode 1426592, offset 6279168, length 4096, links 1 (path: appdata/plexpassmediaserver/Plex Media Server/Media/localhost/e/4b7e5a96770f020794acd4624d6c7fce2c6a9dc.bundle/Contents/Indexes/index-sd.bif) Mar 28 17:43:47 CORE kernel: BTRFS: bdev /dev/sdh1 errs: wr 0, rd 0, flush 0, corrupt 1, gen 0 Mar 28 17:43:47 CORE kernel: BTRFS: bdev /dev/sdh1 errs: wr 0, rd 0, flush 0, corrupt 2, gen 0 Mar 28 17:43:47 CORE kernel: BTRFS: checksum error at logical 1000221151232 on dev /dev/sdh1, sector 3924168, root 5, inode 1426592, offset 6770688, length 4096, links 1 (path: appdata/plexpassmediaserver/Plex Media Server/Media/localhost/e/4b7e5a96770f020794acd4624d6c7fce2c6a9dc.bundle/Contents/Indexes/index-sd.bif) Mar 28 18:07:41 CORE kernel: BTRFS: bdev /dev/sdh1 errs: wr 0, rd 0, flush 0, corrupt 3031, gen 0 Mar 28 18:08:42 CORE kernel: BTRFS: checksum error at logical 1178651320320 on dev /dev/sdh1, sector 202069232, root 5, inode 1561639, offset 323584, length 4096, links 1 (path: appdata/plexpassmediaserver/Plex Media Server/Plug-in Support/Databases/com.plexapp.plugins.library.db-wal) Mar 28 18:08:42 CORE kernel: BTRFS: bdev /dev/sdh1 errs: wr 0, rd 0, flush 0, corrupt 3701, gen 0 Mar 28 18:08:42 CORE kernel: BTRFS: bdev /dev/sdh1 errs: wr 0, rd 0, flush 0, corrupt 3702, gen 0 Mar 28 18:22:28 CORE kernel: BTRFS: read error corrected: ino 1561639 off 323584 (dev /dev/sdh1 sector 202069232)
March 28, 201610 yr Author Maxed out the post.. was going to edit... Well anyways I rebooted this is the latest logs from Cache Drives 2 / 3. Good news is no red so far? 3 Yellow errors I have put in bold. Drive 2 Mar 28 18:59:10 CORE kernel: ata1: SATA max UDMA/133 abar m2048@0xf4712000 port 0xf4712100 irq 28 Mar 28 18:59:10 CORE kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Mar 28 18:59:10 CORE kernel: ata1.00: READ LOG DMA EXT failed, trying unqueued Mar 28 18:59:10 CORE kernel: ata1.00: failed to get NCQ Send/Recv Log Emask 0x1 Mar 28 18:59:10 CORE kernel: ata1.00: ATA-9: Samsung SSD 840 Series, S14CNEACA47078H, DXT09B0Q, max UDMA/133 Mar 28 18:59:10 CORE kernel: ata1.00: 234441648 sectors, multi 16: LBA48 NCQ (depth 31/32), AA Mar 28 18:59:10 CORE kernel: ata1.00: failed to get NCQ Send/Recv Log Emask 0x1 Mar 28 18:59:10 CORE kernel: ata1.00: configured for UDMA/133 Mar 28 18:59:10 CORE kernel: ata1.00: Enabling discard_zeroes_data Mar 28 18:59:10 CORE kernel: sd 1:0:0:0: [sdb] 234441648 512-byte logical blocks: (120 GB/112 GiB) Mar 28 18:59:10 CORE kernel: sd 1:0:0:0: [sdb] Write Protect is off Mar 28 18:59:10 CORE kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Mar 28 18:59:10 CORE kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Mar 28 18:59:10 CORE kernel: ata1.00: Enabling discard_zeroes_data Mar 28 18:59:10 CORE kernel: sdb: sdb1 Mar 28 18:59:10 CORE kernel: ata1.00: Enabling discard_zeroes_data Mar 28 18:59:10 CORE kernel: sd 1:0:0:0: [sdb] Attached SCSI disk Mar 28 18:59:22 CORE emhttp: Samsung_SSD_840_Series_S14CNEACA47078H (sdb) 117220824 Mar 28 18:59:22 CORE emhttp: import 5 cache device: sdb Mar 28 18:59:23 CORE emhttp: shcmd (7): /usr/sbin/hdparm -S0 /dev/sdb &> /dev/null Mar 28 18:59:23 CORE emhttp: Samsung_SSD_840_Series_S14CNEACA47078H (sdb) 117220824 Mar 28 18:59:23 CORE emhttp: import 5 cache device: sdb Mar 28 19:00:01 CORE emhttp: Samsung_SSD_840_Series_S14CNEACA47078H (sdb) 117220824 Mar 28 19:00:01 CORE emhttp: import 5 cache device: sdb Mar 28 19:01:01 CORE emhttp: Samsung_SSD_840_Series_S14CNEACA47078H (sdb) 117220824 Mar 28 19:01:01 CORE emhttp: import 5 cache device: sdb Mar 28 19:02:01 CORE emhttp: Samsung_SSD_840_Series_S14CNEACA47078H (sdb) 117220824 Mar 28 19:02:01 CORE emhttp: import 5 cache device: sdb Mar 28 19:03:01 CORE emhttp: Samsung_SSD_840_Series_S14CNEACA47078H (sdb) 117220824 Mar 28 19:03:01 CORE emhttp: import 5 cache device: sdb Mar 28 19:04:01 CORE emhttp: Samsung_SSD_840_Series_S14CNEACA47078H (sdb) 117220824 Mar 28 19:04:01 CORE emhttp: import 5 cache device: sdb Mar 28 19:05:01 CORE emhttp: Samsung_SSD_840_Series_S14CNEACA47078H (sdb) 117220824 Mar 28 19:05:01 CORE emhttp: import 5 cache device: sdb Mar 28 19:06:01 CORE emhttp: Samsung_SSD_840_Series_S14CNEACA47078H (sdb) 117220824 Mar 28 19:06:01 CORE emhttp: import 5 cache device: sdb Mar 28 19:07:01 CORE emhttp: Samsung_SSD_840_Series_S14CNEACA47078H (sdb) 117220824 Mar 28 19:07:01 CORE emhttp: import 5 cache device: sdb Mar 28 19:08:01 CORE emhttp: Samsung_SSD_840_Series_S14CNEACA47078H (sdb) 117220824 Mar 28 19:08:01 CORE emhttp: import 5 cache device: sdb Mar 28 19:09:01 CORE emhttp: Samsung_SSD_840_Series_S14CNEACA47078H (sdb) 117220824 Mar 28 19:09:01 CORE emhttp: import 5 cache device: sdb Mar 28 19:10:01 CORE emhttp: Samsung_SSD_840_Series_S14CNEACA47078H (sdb) 117220824 Mar 28 19:10:01 CORE emhttp: import 5 cache device: sdb Mar 28 19:11:01 CORE emhttp: Samsung_SSD_840_Series_S14CNEACA47078H (sdb) 117220824 Mar 28 19:11:01 CORE emhttp: import 5 cache device: sdb Mar 28 19:12:01 CORE emhttp: Samsung_SSD_840_Series_S14CNEACA47078H (sdb) 117220824 Mar 28 19:12:01 CORE emhttp: import 5 cache device: sdb Mar 28 19:12:42 CORE emhttp: Samsung_SSD_840_Series_S14CNEACA47078H (sdb) 117220824 Mar 28 19:12:42 CORE emhttp: import 5 cache device: sdb Mar 28 19:12:46 CORE emhttp: Samsung_SSD_840_Series_S14CNEACA47078H (sdb) 117220824 Mar 28 19:12:46 CORE emhttp: import 5 cache device: sdb Mar 28 19:12:46 CORE emhttp: shcmd (68): /usr/sbin/hdparm -S0 /dev/sdb &> /dev/null Mar 28 19:12:46 CORE kernel: BTRFS: device fsid 640b4483-c816-4562-b098-6b90c83f57ef devid 1 transid 376462 /dev/sdb1 Mar 28 19:12:47 CORE kernel: BTRFS: bdev /dev/sdb1 errs: wr 0, rd 0, flush 0, corrupt 2, gen 2 Drive 3 Mar 28 18:59:10 CORE kernel: ata7: SATA max UDMA/133 abar m512@0xf4610000 port 0xf4610100 irq 30 Mar 28 18:59:10 CORE kernel: ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Mar 28 18:59:10 CORE kernel: ata7.00: supports DRM functions and may not be fully accessible Mar 28 18:59:10 CORE kernel: ata7.00: disabling queued TRIM support Mar 28 18:59:10 CORE kernel: ata7.00: ATA-9: Samsung SSD 850 PRO 128GB, S24ZNXAGB10425J, EXM02B6Q, max UDMA/133 Mar 28 18:59:10 CORE kernel: ata7.00: 250069680 sectors, multi 1: LBA48 NCQ (depth 31/32), AA Mar 28 18:59:10 CORE kernel: ata7.00: supports DRM functions and may not be fully accessible Mar 28 18:59:10 CORE kernel: ata7.00: disabling queued TRIM support Mar 28 18:59:10 CORE kernel: ata7.00: configured for UDMA/133 Mar 28 18:59:10 CORE kernel: sd 7:0:0:0: [sdh] 250069680 512-byte logical blocks: (128 GB/119 GiB) Mar 28 18:59:10 CORE kernel: sd 7:0:0:0: [sdh] Write Protect is off Mar 28 18:59:10 CORE kernel: sd 7:0:0:0: [sdh] Mode Sense: 00 3a 00 00 Mar 28 18:59:10 CORE kernel: sd 7:0:0:0: [sdh] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Mar 28 18:59:10 CORE kernel: sdh: sdh1 Mar 28 18:59:10 CORE kernel: sd 7:0:0:0: [sdh] Attached SCSI disk Mar 28 18:59:22 CORE emhttp: Samsung_SSD_850_PRO_128GB_S24ZNXAGB10425J (sdh) 125034840 Mar 28 18:59:22 CORE emhttp: import 6 cache device: sdh Mar 28 18:59:23 CORE emhttp: shcmd (: /usr/sbin/hdparm -S0 /dev/sdh &> /dev/null Mar 28 18:59:23 CORE emhttp: Samsung_SSD_850_PRO_128GB_S24ZNXAGB10425J (sdh) 125034840 Mar 28 18:59:23 CORE emhttp: import 6 cache device: sdh Mar 28 19:00:01 CORE emhttp: Samsung_SSD_850_PRO_128GB_S24ZNXAGB10425J (sdh) 125034840 Mar 28 19:00:01 CORE emhttp: import 6 cache device: sdh Mar 28 19:01:01 CORE emhttp: Samsung_SSD_850_PRO_128GB_S24ZNXAGB10425J (sdh) 125034840 Mar 28 19:01:01 CORE emhttp: import 6 cache device: sdh Mar 28 19:02:01 CORE emhttp: Samsung_SSD_850_PRO_128GB_S24ZNXAGB10425J (sdh) 125034840 Mar 28 19:02:01 CORE emhttp: import 6 cache device: sdh Mar 28 19:03:01 CORE emhttp: Samsung_SSD_850_PRO_128GB_S24ZNXAGB10425J (sdh) 125034840 Mar 28 19:03:01 CORE emhttp: import 6 cache device: sdh Mar 28 19:04:01 CORE emhttp: Samsung_SSD_850_PRO_128GB_S24ZNXAGB10425J (sdh) 125034840 Mar 28 19:04:01 CORE emhttp: import 6 cache device: sdh Mar 28 19:05:01 CORE emhttp: Samsung_SSD_850_PRO_128GB_S24ZNXAGB10425J (sdh) 125034840 Mar 28 19:05:01 CORE emhttp: import 6 cache device: sdh Mar 28 19:06:01 CORE emhttp: Samsung_SSD_850_PRO_128GB_S24ZNXAGB10425J (sdh) 125034840 Mar 28 19:06:01 CORE emhttp: import 6 cache device: sdh Mar 28 19:07:01 CORE emhttp: Samsung_SSD_850_PRO_128GB_S24ZNXAGB10425J (sdh) 125034840 Mar 28 19:07:01 CORE emhttp: import 6 cache device: sdh Mar 28 19:08:01 CORE emhttp: Samsung_SSD_850_PRO_128GB_S24ZNXAGB10425J (sdh) 125034840 Mar 28 19:08:01 CORE emhttp: import 6 cache device: sdh Mar 28 19:09:01 CORE emhttp: Samsung_SSD_850_PRO_128GB_S24ZNXAGB10425J (sdh) 125034840 Mar 28 19:09:01 CORE emhttp: import 6 cache device: sdh Mar 28 19:10:01 CORE emhttp: Samsung_SSD_850_PRO_128GB_S24ZNXAGB10425J (sdh) 125034840 Mar 28 19:10:01 CORE emhttp: import 6 cache device: sdh Mar 28 19:11:01 CORE emhttp: Samsung_SSD_850_PRO_128GB_S24ZNXAGB10425J (sdh) 125034840 Mar 28 19:11:01 CORE emhttp: import 6 cache device: sdh Mar 28 19:12:01 CORE emhttp: Samsung_SSD_850_PRO_128GB_S24ZNXAGB10425J (sdh) 125034840 Mar 28 19:12:01 CORE emhttp: import 6 cache device: sdh Mar 28 19:12:42 CORE emhttp: Samsung_SSD_850_PRO_128GB_S24ZNXAGB10425J (sdh) 125034840 Mar 28 19:12:42 CORE emhttp: import 6 cache device: sdh Mar 28 19:12:46 CORE emhttp: Samsung_SSD_850_PRO_128GB_S24ZNXAGB10425J (sdh) 125034840 Mar 28 19:12:46 CORE emhttp: import 6 cache device: sdh Mar 28 19:12:46 CORE emhttp: shcmd (69): /usr/sbin/hdparm -S0 /dev/sdh &> /dev/null Mar 28 19:12:46 CORE kernel: BTRFS: device fsid 640b4483-c816-4562-b098-6b90c83f57ef devid 3 transid 376462 /dev/sdh1 Mar 28 19:12:47 CORE kernel: BTRFS: bdev /dev/sdh1 errs: wr 0, rd 0, flush 0, corrupt 3702, gen 0
March 29, 201610 yr I had a corrupt BTRFS cache Pool after I let it run to 100% BUT apps were still trying to write to it. It was throwing errors all over the place. There was nothing wrong with the disks at all. I ran every test and tool on it that I could find / supported by unRAID. In the end I stopped Docker and VM services and moved all my apps from the Cache Drive. Run the Mover. Stopped all writes to the Cache drive (by disabling use of Cache in the share settings) and then removed the Cache Disks from their slots. Used Unassigned devices to remove their partitions. Added them back into the Cache Slots. Let unRAID format the drives and set up the Pool again. Then I copied back all my apps to the pool and re-enabled all the share settings and restarted Docker and VM services. It took me all of 20 mins to do. Since then I have not let the Cache disk get full and I have not had any corruption errors. For your consideration, (if you know it is not the disks) not sure if you want to try it. Alternatively if you want some more help, post a diagnostics file for us to look at: Tools>Diagnostics>Download
March 29, 201610 yr Author Yea, It seemed to be power related in my case, no errors for 24 hours now and none of the links have reset so I think things are looking good.. I'll go and upgrade the PSU to 750W from the 500W I have it in currently..
Archived
This topic is now archived and is closed to further replies.