jc179 Posted April 28, 2020 Share Posted April 28, 2020 (edited) Hi New around here, but hoping to get some help with another unusual issue with unraid in 6.8.3 and seagate SMR hard drives ST8000AS0002 (/dev/sdg and /dev/sdh), and unraid's disk settings. What's currently happening is in dmesg/ syslog, I find the below error messages by: 1. allowing things to idle on unraid, and either logging in to, or refreshing the webUI and experiencing long hangs populating "Unassigned Devices" - where these two SMR hdd's are currently mounted. 2. by running /usr/bin/dd bs=1 count=48 skip=462 if=/dev/sdh 2>/dev/null | /bin/sum | / bin/awk '{print }' ... on a terminal when those disks have been inactive for some time. Messages found related to hard drive commands rx/td'd : Syslog: Apr 27 10:24:02 Tower unassigned.devices: Error: shell_exec(/usr/bin/dd bs=446 count=1 if=/dev/sdg 2>/dev/null | /bin/sum | /bin/awk '{print }') took longer than 5s! Apr 27 10:24:07 Tower kernel: sd 15:0:5:0: [sdg] tag#8357 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x00 Apr 27 10:24:07 Tower kernel: sd 15:0:5:0: [sdg] tag#8357 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 00 00 00 00 20 00 00 Apr 27 10:24:07 Tower kernel: print_req_error: I/O error, dev sdg, sector 0 Apr 27 10:24:07 Tower unassigned.devices: Error: shell_exec(/usr/bin/dd bs=1 count=48 skip=462 if=/dev/sdg 2>/dev/null | /bin/sum | / bin/awk '{print }') took longer than 5s! Apr 27 10:24:14 Tower unassigned.devices: Error: shell_exec(/usr/bin/dd bs=446 count=1 if=/dev/sdh 2>/dev/null | /bin/sum | /bin/awk '{print }') took longer than 5s! Apr 27 10:24:19 Tower kernel: sd 15:0:6:0: [sdh] tag#8259 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x00 Apr 27 10:24:19 Tower kernel: sd 15:0:6:0: [sdh] tag#8259 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 00 00 00 00 20 00 00 Apr 27 10:24:19 Tower kernel: print_req_error: I/O error, dev sdh, sector 0 Apr 27 10:24:19 Tower unassigned.devices: Error: shell_exec(/usr/bin/dd bs=1 count=48 skip=462 if=/dev/sdh 2>/dev/null | /bin/sum | / bin/awk '{print }') took longer than 5s! dmesg [Mon Apr 27 10:24:07 2020] sd 15:0:5:0: [sdg] tag#8357 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x00 [Mon Apr 27 10:24:07 2020] sd 15:0:5:0: [sdg] tag#8357 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 00 00 00 00 20 00 00 [Mon Apr 27 10:24:07 2020] print_req_error: I/O error, dev sdg, sector 0 [Mon Apr 27 10:24:19 2020] sd 15:0:6:0: [sdh] tag#8259 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x00 [Mon Apr 27 10:24:19 2020] sd 15:0:6:0: [sdh] tag#8259 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 00 00 00 00 20 00 00 [Mon Apr 27 10:24:19 2020] print_req_error: I/O error, dev sdh, sector 0 [Mon Apr 27 18:53:49 2020] sd 15:0:5:0: [sdg] tag#7400 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x00 [Mon Apr 27 18:53:49 2020] sd 15:0:5:0: [sdg] tag#7400 CDB: opcode=0x88 88 00 00 00 00 00 00 04 09 60 00 00 00 20 00 00 [Mon Apr 27 18:53:49 2020] print_req_error: I/O error, dev sdg, sector 264544 [Mon Apr 27 18:54:35 2020] sd 15:0:6:0: [sdh] tag#7681 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x00 [Mon Apr 27 18:54:35 2020] sd 15:0:6:0: [sdh] tag#7681 CDB: opcode=0x88 88 00 00 00 00 00 00 04 09 60 00 00 00 20 00 00 [Mon Apr 27 18:54:35 2020] print_req_error: I/O error, dev sdh, sector 264544 [Mon Apr 27 21:42:55 2020] sd 15:0:6:0: attempting task abort! scmd(0000000026d5a722) [Mon Apr 27 21:42:55 2020] sd 15:0:6:0: [sdh] tag#704 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 4 0 e5 00 I do have unraid "Default spin down delay: to never", and I don't have anything setup per disk to spin down either. I have managed to repeat it somewhat using hdparm -Y /dev/sdh or /dev/sdg, followed by -C to check the state. When the reported state comes back as "standby" and I make an attempt to read the hard drive (eg use the DD command above, or anything else, such as a ls, it hangs for ~10 seconds before it responds, followed by those messages in the syslog/dmesg. root@Tower:~# hdparm -Y /dev/sdh /dev/sdh: issuing sleep command root@Tower:~# hdparm -C /dev/sdh /dev/sdh: drive state is: standby root@Tower:~# hdparm -C /dev/sdh /dev/sdh: drive state is: active/idle root@Tower:~# hdparm -Y /dev/sdh /dev/sdh: issuing sleep command gets from dmesg [Mon Apr 27 21:45:57 2020] sd 15:0:6:0: [sdh] tag#1021 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 [Mon Apr 27 21:45:57 2020] sd 15:0:6:0: [sdh] tag#1021 Sense Key : 0x2 [current] [Mon Apr 27 21:45:57 2020] sd 15:0:6:0: [sdh] tag#1021 ASC=0x4 ASCQ=0x2 [Mon Apr 27 21:45:57 2020] sd 15:0:6:0: [sdh] tag#1021 CDB: opcode=0x88 88 00 00 00 00 00 00 59 92 38 00 00 01 c8 00 00 [Mon Apr 27 21:45:57 2020] print_req_error: I/O error, dev sdh, sector 5870136 [Mon Apr 27 21:47:02 2020] sd 15:0:6:0: attempting task abort! scmd(000000002be3a761) [Mon Apr 27 21:47:02 2020] sd 15:0:6:0: tag#913 CDB: opcode=0x0 00 00 00 00 00 00 [Mon Apr 27 21:47:02 2020] scsi target15:0:6: handle(0x0010), sas_address(0x50019400005e6207), phy(7) [Mon Apr 27 21:47:02 2020] scsi target15:0:6: enclosure logical id(0x50019400005e623f), slot(7) [Mon Apr 27 21:47:03 2020] sd 15:0:6:0: task abort: SUCCESS scmd(000000002be3a761) [Mon Apr 27 21:47:03 2020] sd 15:0:6:0: Power-on or device reset occurred [Mon Apr 27 21:47:04 2020] sd 15:0:6:0: Power-on or device reset occurred [Mon Apr 27 21:47:18 2020] sd 15:0:6:0: [sdh] tag#1337 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x00 [Mon Apr 27 21:47:18 2020] sd 15:0:6:0: [sdh] tag#1337 CDB: opcode=0x88 88 00 00 00 00 00 00 c8 2a 00 00 00 07 a8 00 00 [Mon Apr 27 21:47:18 2020] print_req_error: I/O error, dev sdh, sector 13117952 [Mon Apr 27 21:47:18 2020] sd 15:0:6:0: [sdh] tag#1334 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 [Mon Apr 27 21:47:18 2020] sd 15:0:6:0: [sdh] tag#1334 Sense Key : 0x2 [current] [Mon Apr 27 21:47:18 2020] sd 15:0:6:0: [sdh] tag#1334 ASC=0x4 ASCQ=0x2 [Mon Apr 27 21:47:18 2020] sd 15:0:6:0: [sdh] tag#1334 CDB: opcode=0x88 88 00 00 00 00 00 00 c8 31 a8 00 00 02 58 00 00 [Mon Apr 27 21:47:18 2020] print_req_error: I/O error, dev sdh, sector 13119912 Both of these hard drives pass smart tests and diags, and didn't have issues when coping the data off them to the array, nor in the previous enclosure - this has just started appearing after they've been 'idle'. Unable to disable any "seagate" related power down stuff: root@Tower:~# hdparm -Z /dev/sdg /dev/sdg: disabling Seagate auto powersaving mode HDIO_DRIVE_CMD(seagatepwrsave) failed: Input/output error root@Tower:~# hdparm -Z /dev/sdh A friend has suggested to try them on an onboard controller, as mine is a LSI SAS2308 PCI-Express Fusion-MPT SAS-2 with already the latest firmware. Any other ideas? thanks, Jonathan Edited April 28, 2020 by jc179 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.