March 29, 20233 yr I'm receiving the error: Unraid Cache disk SMART health [187]: 28-03-2023 17:12 Warning [TOWER] - reported uncorrect is 14 M4-CT256M4SSD2_00000000130309265B2B (sdh) BTRFS Scrub: UUID: af9fa197-4f10-4658-b89b-002599ca51e2 Scrub started: Tue Mar 28 17:16:28 2023 Status: finished Duration: 0:05:27 Total to scrub: 78.45GiB Rate: 245.67MiB/s Error summary: read=4 Corrected: 0 Uncorrectable: 0 Unverified: 0 Should I assume my cache drive has bad data (I don't know what BTRFS is actually telling me)? Should I assume my cache drive is going bad, and needs to be replaced? Thank you. tower-diagnostics-20230329-0025.zip Edited March 29, 20233 yr by Jaybau
March 29, 20233 yr Author 10 hours ago, JorgeB said: Run another scrub and post the output. UUID: af9fa197-4f10-4658-b89b-002599ca51e2 Scrub started: Wed Mar 29 11:24:22 2023 Status: finished Duration: 0:05:11 Total to scrub: 78.46GiB Rate: 258.37MiB/s Error summary: read=4 Corrected: 0 Uncorrectable: 0 Unverified: 0
March 29, 20233 yr Author Found some more information within the Disk Log: Mar 29 11:24:53 Tower kernel: ata1.00: exception Emask 0x0 SAct 0x1ffc0 SErr 0x0 action 0x0 Mar 29 11:24:53 Tower kernel: ata1.00: irq_stat 0x40000008 Mar 29 11:24:53 Tower kernel: ata1.00: failed command: READ FPDMA QUEUED Mar 29 11:24:53 Tower kernel: ata1.00: cmd 60/00:30:50:36:24/05:00:01:00:00/40 tag 6 ncq dma 655360 in Mar 29 11:24:53 Tower kernel: ata1.00: status: { DRDY ERR } Mar 29 11:24:53 Tower kernel: ata1.00: error: { UNC } Mar 29 11:24:53 Tower kernel: ata1.00: configured for UDMA/100 Mar 29 11:24:53 Tower kernel: sd 2:0:0:0: [sdh] tag#6 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Mar 29 11:24:53 Tower kernel: sd 2:0:0:0: [sdh] tag#6 Sense Key : 0x3 [current] Mar 29 11:24:53 Tower kernel: sd 2:0:0:0: [sdh] tag#6 ASC=0x11 ASCQ=0x4 Mar 29 11:24:53 Tower kernel: sd 2:0:0:0: [sdh] tag#6 CDB: opcode=0x28 28 00 01 24 36 50 00 05 00 00 Mar 29 11:24:53 Tower kernel: I/O error, dev sdh, sector 19150984 op 0x0:(READ) flags 0x4000 phys_seg 89 prio class 0 Mar 29 11:24:53 Tower kernel: ata1: EH complete Mar 29 11:24:53 Tower kernel: ata1.00: exception Emask 0x0 SAct 0x7f8007c0 SErr 0x0 action 0x0 Mar 29 11:24:53 Tower kernel: ata1.00: irq_stat 0x40000008 Mar 29 11:24:53 Tower kernel: ata1.00: failed command: READ FPDMA QUEUED Mar 29 11:24:53 Tower kernel: ata1.00: cmd 60/08:b8:88:38:24/00:00:01:00:00/40 tag 23 ncq dma 4096 in Mar 29 11:24:53 Tower kernel: ata1.00: status: { DRDY ERR } Mar 29 11:24:53 Tower kernel: ata1.00: error: { UNC } Mar 29 11:24:53 Tower kernel: ata1.00: configured for UDMA/100 Mar 29 11:24:53 Tower kernel: sd 2:0:0:0: [sdh] tag#23 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Mar 29 11:24:53 Tower kernel: sd 2:0:0:0: [sdh] tag#23 Sense Key : 0x3 [current] Mar 29 11:24:53 Tower kernel: sd 2:0:0:0: [sdh] tag#23 ASC=0x11 ASCQ=0x4 Mar 29 11:24:53 Tower kernel: sd 2:0:0:0: [sdh] tag#23 CDB: opcode=0x28 28 00 01 24 38 88 00 00 08 00 Mar 29 11:24:53 Tower kernel: I/O error, dev sdh, sector 19150984 op 0x0:(READ) flags 0x800 phys_seg 1 prio class 0 Mar 29 11:24:53 Tower kernel: ata1: EH complete Mar 29 11:24:53 Tower kernel: BTRFS warning (device sdh1): i/o error at logical 165618454528 on dev /dev/sdh1, physical 9804255232, root 5, inode 260, offset 3305271296, length 4096, links 1 (path: system/docker/docker.img) Mar 29 11:24:53 Tower kernel: BTRFS error (device sdh1): bdev /dev/sdh1 errs: wr 0, rd 36, flush 0, corrupt 0, gen 0 Mar 29 11:24:53 Tower kernel: ata1.00: exception Emask 0x0 SAct 0x87ff0147 SErr 0x0 action 0x0 Mar 29 11:24:53 Tower kernel: ata1.00: irq_stat 0x40000008 Mar 29 11:24:53 Tower kernel: ata1.00: failed command: READ FPDMA QUEUED Mar 29 11:24:53 Tower kernel: ata1.00: cmd 60/08:40:90:38:24/00:00:01:00:00/40 tag 8 ncq dma 4096 in Mar 29 11:24:53 Tower kernel: ata1.00: status: { DRDY ERR } Mar 29 11:24:53 Tower kernel: ata1.00: error: { UNC } Mar 29 11:24:53 Tower kernel: ata1.00: configured for UDMA/100 Mar 29 11:24:53 Tower kernel: sd 2:0:0:0: [sdh] tag#8 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Mar 29 11:24:53 Tower kernel: sd 2:0:0:0: [sdh] tag#8 Sense Key : 0x3 [current] Mar 29 11:24:53 Tower kernel: sd 2:0:0:0: [sdh] tag#8 ASC=0x11 ASCQ=0x4 Mar 29 11:24:53 Tower kernel: sd 2:0:0:0: [sdh] tag#8 CDB: opcode=0x28 28 00 01 24 38 90 00 00 08 00 Mar 29 11:24:53 Tower kernel: I/O error, dev sdh, sector 19150992 op 0x0:(READ) flags 0x800 phys_seg 1 prio class 0 Mar 29 11:24:53 Tower kernel: ata1: EH complete Mar 29 11:24:53 Tower kernel: BTRFS warning (device sdh1): i/o error at logical 165618458624 on dev /dev/sdh1, physical 9804259328, root 5, inode 260, offset 3305275392, length 4096, links 1 (path: system/docker/docker.img) Mar 29 11:24:53 Tower kernel: BTRFS error (device sdh1): bdev /dev/sdh1 errs: wr 0, rd 37, flush 0, corrupt 0, gen 0 Mar 29 11:29:33 Tower kernel: BTRFS info (device sdh1): scrub: finished on devid 2 with status: 0 All the error logs involve "path: system/docker/docker.img".
March 29, 20233 yr Author I performed a BTRFS scrub on my docker volume: Label: none uuid: 4978b6f9-7639-4a2f-9f94-40584c81e9c2 Total devices 1 FS bytes used 31.73GiB devid 1 size 40.00GiB used 36.00GiB path /dev/loop2 UUID: 4978b6f9-7639-4a2f-9f94-40584c81e9c2 Scrub started: Wed Mar 29 12:07:03 2023 Status: finished Duration: 0:03:43 Total to scrub: 32.87GiB Rate: 150.92MiB/s Error summary: read=4 Corrected: 0 Uncorrectable: 0 Unverified: 0
March 29, 20233 yr Author I wonder if any of this can be related to another potential problem I am having with the docker image? https://forums.unraid.net/topic/137109-troubleshooting-docker-image-file-is-getting-full/
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.