March 6, 20179 yr Unraid 6.3.2 HITACHI_HUA721010KLA330 drive - from SMART: 10 Spin retry count 0x0013 100 100 060 Pre-fail Always Never 0 12 Power cycle count 0x0032 100 100 000 Old age Always Never 74 192 Power-off retract count 0x0032 100 100 000 Old age Always Never 96 193 Load cycle count 0x0012 100 100 000 Old age Always Never 96 194 Temperature celsius 0x0002 157 157 000 Old age Always Never 38 (min/max 15/49) 196 Reallocated event count 0x0032 100 100 000 Old age Always Never 0 197 Current pending sector 0x0022 100 100 000 Old age Always Never 0 198 Offline uncorrectable 0x0008 100 100 000 Old age Offline Never 0 199 UDMA CRC error count 0x000a 200 200 000 Old age Always Never 0 Soon after I added this drive (preclear was fine, only one pass though) my array now shows this drive with 96 errors onthe Main page. No Smart errors report on the dashboard. I've asked Google and she seems to suggest that these are no cause for concern as the counter increases each time the drive parks the heads. I have other similar drives which I was going to add to my array and they all have the same thing in power off and load cycle. Do we think that Unraid should be reporting these values as errors?
March 6, 20179 yr Community Expert If by errors on the main page you mean the disk error counter those have nothing to do with those attributes, if the disk is still enable they are read errors, post your diagnostics.
March 6, 20179 yr Author Diag attached. After a restart the error counter is increasing again, disk still enabled. server-diagnostics-20170306-2239.zip
March 7, 20179 yr That's Disk 19, sds, and there was a read error of a contiguous block of sectors near the very start of the drive, which probably resulted in 32 read errors showing on the Main page for Disk 19. The SMART report is nearly perfect, no errors at all. Its only problem is the age of the drive, with over 66000 hours on it. But its aging well, no VALUE's below 100. I don't know why the read error occurred. It indicates an issue with the physical media, but the SMART data in this diagnostics is not reporting any problems. Try a SMART short test, then a SMART long test (follow the instructions on how long to wait for each). Edited March 7, 20179 yr by RobJ correction
March 11, 20179 yr Author I thought SMART look clean too - no more errors reported. How / where in the diag so I see teh read errors you mention, I'm interested.. I ran a log SMART test and nothing reported.
March 11, 20179 yr Community Expert 42 minutes ago, fysmd said: How / where in the diag so I see teh read errors you mention, I'm interested.. On the syslog: Mar 6 21:42:17 server kernel: ata14.03: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Mar 6 21:42:17 server kernel: ata14.03: failed command: READ DMA Mar 6 21:42:17 server kernel: ata14.03: cmd c8/00:00:28:0f:00/00:00:00:00:00/e0 tag 19 dma 131072 in Mar 6 21:42:17 server kernel: res 51/40:47:e1:0e:00/00:01:00:00:00/e0 Emask 0x9 (media error) Mar 6 21:42:17 server kernel: ata14.03: status: { DRDY ERR } Mar 6 21:42:17 server kernel: ata14.03: error: { UNC } Mar 6 21:42:17 server kernel: ata14.03: configured for UDMA/133 Mar 6 21:42:17 server kernel: sd 14:3:0:0: [sds] tag#19 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Mar 6 21:42:17 server kernel: sd 14:3:0:0: [sds] tag#19 Sense Key : 0x3 [current] Mar 6 21:42:17 server kernel: sd 14:3:0:0: [sds] tag#19 ASC=0x11 ASCQ=0x4 Mar 6 21:42:17 server kernel: sd 14:3:0:0: [sds] tag#19 CDB: opcode=0x28 28 00 00 00 0f 28 00 01 00 00 Mar 6 21:42:17 server kernel: blk_update_request: I/O error, dev sds, sector 3880 Mar 6 21:42:17 server kernel: md: disk19 read error, sector=3816 Mar 6 21:42:17 server kernel: ata14: EH complete Mar 6 21:42:17 server kernel: md: disk19 read error, sector=3824 Mar 6 21:42:17 server kernel: md: disk19 read error, sector=3832 Mar 6 21:42:17 server kernel: md: disk19 read error, sector=3840 Mar 6 21:42:17 server kernel: md: disk19 read error, sector=3848 Mar 6 21:42:17 server kernel: md: disk19 read error, sector=3856 Mar 6 21:42:17 server kernel: md: disk19 read error, sector=3864 Mar 6 21:42:17 server kernel: md: disk19 read error, sector=3872 Mar 6 21:42:17 server kernel: md: disk19 read error, sector=3880 Mar 6 21:42:17 server kernel: md: disk19 read error, sector=3888 Mar 6 21:42:17 server kernel: md: disk19 read error, sector=3896 Mar 6 21:42:17 server kernel: md: disk19 read error, sector=3904 Mar 6 21:42:17 server kernel: md: disk19 read error, sector=3912 Mar 6 21:42:17 server kernel: md: disk19 read error, sector=3920 Mar 6 21:42:17 server kernel: md: disk19 read error, sector=3928 Mar 6 21:42:17 server kernel: md: disk19 read error, sector=3936 Mar 6 21:42:17 server kernel: md: disk19 read error, sector=3944 Mar 6 21:42:17 server kernel: md: disk19 read error, sector=3952 Mar 6 21:42:17 server kernel: md: disk19 read error, sector=3960 Mar 6 21:42:17 server kernel: md: disk19 read error, sector=3968 Mar 6 21:42:17 server kernel: md: disk19 read error, sector=3976 Mar 6 21:42:17 server kernel: md: disk19 read error, sector=3984 Mar 6 21:42:17 server kernel: md: disk19 read error, sector=3992 Mar 6 21:42:17 server kernel: md: disk19 read error, sector=4000 Mar 6 21:42:17 server kernel: md: disk19 read error, sector=4008 Mar 6 21:42:17 server kernel: md: disk19 read error, sector=4016 Mar 6 21:42:17 server kernel: md: disk19 read error, sector=4024 Mar 6 21:42:17 server kernel: md: disk19 read error, sector=4032 Mar 6 21:42:17 server kernel: md: disk19 read error, sector=4040 Mar 6 21:42:17 server kernel: md: disk19 read error, sector=4048 Mar 6 21:42:17 server kernel: md: disk19 read error, sector=4056 Mar 6 21:42:17 server kernel: md: disk19 read error, sector=4064
Archived
This topic is now archived and is closed to further replies.