BeaverTerror Posted February 21, 2019 Share Posted February 21, 2019 (edited) I received a 4TB HGST server take-off (used) SAS drive in the mail today. Plugged it into my server, and it is not initializing. The disk log indicates the following warning: UnRAID kernel: sd 8:0:2:0: [sdj] Read Capacity(10) failed: Result: hostbyte=0x00 driverbyte=0x08 UnRAID emhttpd: device /dev/sdj has size zero The smart report indicates: device is NOT READY (e.g. spun down, busy) A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. My configuration zip file is attached. The device is sdj. This is in a fully operational machine that has been running without problems for years. There are no issues with the server hardware. The HBA is an LSI 9211-8i. I tried the disk on two different ports, same result. The hard drive itself is spinning. Please help me confirm this isn't some kind of configuration issue with SAS drives, before I send it back to the seller. Thank you. Quote Feb 22 04:49:45 UnRAID kernel: sd 8:0:2:0: [sdj] Spinning up disk... Feb 22 04:51:21 UnRAID kernel: sd 8:0:2:0: [sdj] Read Capacity(16) failed: Result: hostbyte=0x00 driverbyte=0x08 Feb 22 04:51:21 UnRAID kernel: sd 8:0:2:0: [sdj] Sense Key : 0x2 [current] [descriptor] Feb 22 04:51:21 UnRAID kernel: sd 8:0:2:0: [sdj] ASC=0x4 ASCQ=0x2 Feb 22 04:51:21 UnRAID kernel: sd 8:0:2:0: [sdj] Read Capacity(10) failed: Result: hostbyte=0x00 driverbyte=0x08 Feb 22 04:51:21 UnRAID kernel: sd 8:0:2:0: [sdj] Sense Key : 0x2 [current] [descriptor] Feb 22 04:51:21 UnRAID kernel: sd 8:0:2:0: [sdj] ASC=0x4 ASCQ=0x2 Feb 22 04:51:21 UnRAID kernel: sd 8:0:2:0: [sdj] 0 512-byte logical blocks: (0 B/0 B) Feb 22 04:51:21 UnRAID kernel: sd 8:0:2:0: [sdj] 0-byte physical blocks Feb 22 04:51:21 UnRAID kernel: sd 8:0:2:0: [sdj] Write Protect is off Feb 22 04:51:21 UnRAID kernel: sd 8:0:2:0: [sdj] Mode Sense: f7 00 10 08 Feb 22 04:51:21 UnRAID kernel: sd 8:0:2:0: [sdj] Write cache: enabled, read cache: enabled, supports DPO and FUA Feb 22 04:51:21 UnRAID kernel: sd 8:0:2:0: [sdj] Spinning up disk... Feb 22 04:53:01 UnRAID kernel: sd 8:0:2:0: [sdj] Read Capacity(16) failed: Result: hostbyte=0x00 driverbyte=0x08 Feb 22 04:53:01 UnRAID kernel: sd 8:0:2:0: [sdj] Sense Key : 0x2 [current] [descriptor] Feb 22 04:53:01 UnRAID kernel: sd 8:0:2:0: [sdj] ASC=0x4 ASCQ=0x2 Feb 22 04:53:01 UnRAID kernel: sd 8:0:2:0: [sdj] Read Capacity(10) failed: Result: hostbyte=0x00 driverbyte=0x08 Feb 22 04:53:01 UnRAID kernel: sd 8:0:2:0: [sdj] Sense Key : 0x2 [current] [descriptor] Feb 22 04:53:01 UnRAID kernel: sd 8:0:2:0: [sdj] ASC=0x4 ASCQ=0x2 Feb 22 04:53:01 UnRAID kernel: sd 8:0:2:0: [sdj] Attached SCSI disk Feb 22 04:53:31 UnRAID emhttpd: device /dev/sdj has size zero unraid-diagnostics-20190221-2056.zip Edited February 21, 2019 by BeaverTerror Quote Link to comment
JorgeB Posted February 22, 2019 Share Posted February 22, 2019 Seems like a disk issue, though you might want to try again after updating the LSI firmware to latest, you're on 15.00.00.00, current one is 20.00.07.00 Quote Link to comment
Robert. Posted October 10, 2019 Share Posted October 10, 2019 I have the same problem. What was the solution? Quote Link to comment
cbr600ds2 Posted November 23, 2020 Share Posted November 23, 2020 @BeaverTerror @Robert. Just ran in to this. Did you guys get any answers or did you just give up? Quote Link to comment
trurl Posted November 23, 2020 Share Posted November 23, 2020 43 minutes ago, cbr600ds2 said: Did you guys get any answers or did you just give up? This is an old thread and neither of those users have visited the forum in over a year. Can you explain the specifics of your problem? Quote Link to comment
cbr600ds2 Posted November 23, 2020 Share Posted November 23, 2020 1 hour ago, trurl said: This is an old thread and neither of those users have visited the forum in over a year. Can you explain the specifics of your problem? Saw this after I started a new post or before. Anyways. Quote Link to comment
Robert. Posted December 2, 2020 Share Posted December 2, 2020 Hello, yes of course. It seems that the purchased record really had a defect. I exchanged it at the dealer and the new one worked without problems. Also all other new SAS disks I bought worked immediately. Kind regards, Robert 1 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.