February 4, 20224 yr I've recently made some changes to my unraid server. I used to have an HBA with a 16 port SAS expander, but then also used onboard SATA ports to fill out my 24 drive bays. I recently purchased and installed a 24-port SAS expander to eliminate my need to use onboard SATA ports as they seemed to be flaky/inconsistent. I also installed a new 8TB drive. Unraid is reporting errors on that drive now and i'm also receiving parity errors on that drive as well. I've checked all the physical connections and have reseated the sata cable on the backplane. Is there anything else I might check? Here are what the recent errors look like: Quote Feb 4 01:00:21 TyRaid kernel: blk_update_request: I/O error, dev sdaa, sector 2937188552 op 0x0:(READ) flags 0x0 phys_seg 79 prio class 0 Feb 4 01:00:21 TyRaid kernel: sd 8:0:25:0: [sdaa] tag#1522 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=0x00 cmd_age=0s Feb 4 01:00:21 TyRaid kernel: sd 8:0:25:0: [sdaa] tag#1522 CDB: opcode=0x88 88 00 00 00 00 00 57 54 3c e0 00 00 00 38 00 00 Feb 4 01:00:21 TyRaid kernel: blk_update_request: I/O error, dev sdaa, sector 1465138400 op 0x0:(READ) flags 0x0 phys_seg 7 prio class 0 Feb 4 01:00:21 TyRaid kernel: sd 8:0:25:0: [sdaa] tag#1521 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=0x00 cmd_age=14s Feb 4 01:00:21 TyRaid kernel: sd 8:0:25:0: [sdaa] tag#1521 CDB: opcode=0x88 88 00 00 00 00 00 57 54 29 40 00 00 00 10 00 00 Feb 4 01:00:21 TyRaid kernel: blk_update_request: I/O error, dev sdaa, sector 1465133376 op 0x0:(READ) flags 0x0 phys_seg 2 prio class 0 Feb 4 01:00:21 TyRaid kernel: sd 8:0:25:0: [sdaa] tag#1524 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=0x00 cmd_age=0s Feb 4 01:00:21 TyRaid kernel: sd 8:0:25:0: [sdaa] tag#1524 CDB: opcode=0x88 88 00 00 00 00 00 ae a8 52 70 00 00 00 10 00 00 Feb 4 01:00:21 TyRaid kernel: blk_update_request: I/O error, dev sdaa, sector 2930266736 op 0x0:(READ) flags 0x0 phys_seg 2 prio class 0 Feb 4 01:33:15 TyRaid emhttpd: spinning down /dev/sdaa Feb 4 01:58:42 TyRaid kernel: sd 8:0:25:0: [sdaa] tag#1525 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00 Feb 4 01:58:46 TyRaid kernel: sd 8:0:25:0: [sdaa] tag#1504 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=0x00 cmd_age=0s Feb 4 01:58:46 TyRaid kernel: sd 8:0:25:0: [sdaa] tag#1504 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 98 00 Feb 4 01:58:46 TyRaid emhttpd: read SMART /dev/sdaa Feb 4 01:58:46 TyRaid kernel: sd 8:0:25:0: [sdaa] tag#1518 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=0x00 cmd_age=19s Feb 4 01:58:46 TyRaid kernel: sd 8:0:25:0: [sdaa] tag#1518 CDB: opcode=0x88 88 00 00 00 00 00 00 7b 83 d0 00 00 00 08 00 00 Feb 4 01:58:46 TyRaid kernel: blk_update_request: I/O error, dev sdaa, sector 8094672 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Feb 4 02:35:48 TyRaid emhttpd: spinning down /dev/sdaa Feb 4 14:02:23 TyRaid emhttpd: read SMART /dev/sdaa Any ideas as to what I might check next? I super appreciate any help! tyraid-diagnostics-20220204-1359.zip
February 16, 20224 yr Author Just wanted to revisit this and report that I did disable spindown for a few days and after doing so, there were no more errors. I conducted further testing by re-enabling spindown, letting the disk spin down, then initiating a transfer to the array and since this disk was nearly empty, it transferred to this drive. It immediately threw all sorts of errors. I then disabled spindown on the disk again and since then I've had no issues. For that reason, I'm going to conclude that this disk just doesn't play nicely with spinning down. Thanks @Vr2Io!
February 17, 20224 yr You may try update expander firmware and test does problem fix. https://forums.servethehome.com/index.php?threads/hp-sas-expander-wiki.146/page-3 Download at post #57 Edited February 17, 20224 yr by Vr2Io
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.