May 22, 20188 yr Greetings, today I received a notification that one of my disks has read errors (13). I wanted to investigate but looking at the smart values, but I can't spin up the drive. The disk log information: May 21 19:59:05 sirbear kernel: sd 9:0:0:0: [sdg] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB) May 21 19:59:05 sirbear kernel: sd 9:0:0:0: [sdg] 4096-byte physical blocks May 21 19:59:05 sirbear kernel: sd 9:0:0:0: [sdg] Write Protect is off May 21 19:59:05 sirbear kernel: sd 9:0:0:0: [sdg] Mode Sense: 00 3a 00 00 May 21 19:59:05 sirbear kernel: sd 9:0:0:0: [sdg] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA May 21 19:59:05 sirbear kernel: sdg: sdg1 May 21 19:59:05 sirbear kernel: sd 9:0:0:0: [sdg] Attached SCSI removable disk May 21 19:59:15 sirbear emhttpd: WDC_WD40EZRX-00SPEB0_WD-WCC4EPA9UX7P (sdg) 512 7814037168 May 21 19:59:15 sirbear kernel: mdcmd (6): import 5 sdg 64 3907018532 0 WDC_WD40EZRX-00SPEB0_WD-WCC4EPA9UX7P May 21 19:59:15 sirbear kernel: md: import disk5: (sdg) WDC_WD40EZRX-00SPEB0_WD-WCC4EPA9UX7P size: 3907018532 May 21 19:59:17 sirbear emhttpd: shcmd (33): /usr/local/sbin/set_ncq sdg 1 May 21 19:59:17 sirbear root: set_ncq: setting sdg queue_depth to 1 May 21 19:59:17 sirbear emhttpd: shcmd (34): echo 128 > /sys/block/sdg/queue/nr_requests May 21 20:01:17 sirbear emhttpd: shcmd (176): /usr/local/sbin/set_ncq sdg 1 May 21 20:01:17 sirbear emhttpd: shcmd (177): echo 128 > /sys/block/sdg/queue/nr_requests May 22 03:33:07 sirbear kernel: sd 9:0:0:0: [sdg] Stopping disk May 22 03:33:07 sirbear kernel: sd 9:0:0:0: [sdg] Start/Stop Unit failed: Result: hostbyte=0x04 driverbyte=0x00 The strange thing: the unRaid webGui shows the disk as spun up in the Main and Dashboard view, but when I click on the disk to get to the SMART values it says the disk must be spun up. I also attached my diagnostics, but the SMART for the disk sdg isn't present. sirbear-diagnostics-20180522-2006.zip
May 22, 20188 yr Community Expert Disk dropped offline and reconnected with a different identifier, but since there's no parity it wasn't disabled, power down, check/replace cables, power back on and post new diags.
May 22, 20188 yr Author Thanks for the fast reply! I just checked the cables, couldn't find anything amiss but changed the SATA-cable just to be sure. Booted the server back up and got a dia before and after I started the array. The disk behaves fine right now and I for my noob knowledge the SMART-values don't look that bad. sirbear-diagnostics-20180522-2038_before_Array_start.zip sirbear-diagnostics-20180522-2039_after_Array_start.zip
May 23, 20188 yr Author Thanks for looking over it, as stated above, I changed the SATA cable. Will look at this drive the next couple of days more carefully and if it acts up again I will post here. Thanks for the ultra fast help ❤️ Edited May 23, 20188 yr by Dr_Cox1911
Archived
This topic is now archived and is closed to further replies.