so i got 2 used but very clean sas HGST. My jbod has everything attached and has been running perfect for months. i added these 2 new drives and nothing. I checked with unassigned and i see they are they're but unmountable. I update everything, i try other hardrives, other bays. nothing works. i try a smart test and it comes back with "device type not detected".     What do i need to do? cant imagine that both drives are dead.

 

i should also mention that when the drive bay is slotted into the JBOD, it has vary steady slow blink. not a flashing or solid but very consistent slow blink. only happens to these two new drives.

 

Edited May 23, 20242 yr by Neuron89

Please post the complete diagnostics. 

@JorgeB any help would be super appreciated. Ive been struggling hard with this but very curious to learn more about this!

tower-diagnostics-20240524-0727.zip

Bothe are even failing to read the capacity

 

May 23 17:41:15 Tower kernel: sd 8:0:8:0: [sdp] Read Capacity(16) failed: Result: hostbyte=0x00 driverbyte=DRIVER_OK
May 23 17:41:15 Tower kernel: sd 8:0:8:0: [sdp] Sense Key : 0x2 [current] [descriptor] 
May 23 17:41:15 Tower kernel: sd 8:0:8:0: [sdp] ASC=0x4 ASCQ=0x1b 
May 23 17:41:15 Tower kernel: sd 8:0:8:0: [sdp] Read Capacity(10) failed: Result: hostbyte=0x00 driverbyte=DRIVER_OK
May 23 17:41:15 Tower kernel: sd 8:0:8:0: [sdp] Sense Key : 0x2 [current] [descriptor] 
May 23 17:41:15 Tower kernel: sd 8:0:8:0: [sdp] ASC=0x4 ASCQ=0x1b 
May 23 17:41:15 Tower kernel: sd 8:0:8:0: [sdp] 0 512-byte logical blocks: (0 B/0 B)
May 23 17:41:15 Tower kernel: sd 8:0:8:0: [sdp] 0-byte physical blocks
May 23 17:41:15 Tower kernel: sd 8:0:8:0: [sdp] Test WP failed, assume Write Enabled
May 23 17:41:15 Tower kernel: sd 8:0:8:0: [sdp] Asking for cache data failed
May 23 17:41:15 Tower kernel: sd 8:0:8:0: [sdp] Assuming drive cache: write through

 

They could both be bad, or have some kind of protection active, or SED, with SAS disks it's rather common if they are used, but they generally still give the SMART report, see if this helps:

https://forums.unraid.net/topic/110835-solved-help-with-a-sas-drive/?do=findComment&comment=1011689

 

ok so it is that both are bad or have some weird encryption. I thought that was the issue but i figured it was super unlikely that both would be bad. Thank you so much @JorgeB!!

I doubt this is the problem, but recently I discovered that at least some newer SAS drives have a feature on the power connector, that actually inhibits the drive, and if so, is NOT compatible with the SATA power connection from many power supplies.  The 3.3 volts from the SATA power supply, if present, is applied to the same pin that is for disabling the SAS drive.  Solution is to use a MOLEX to SATA power adapter to only supply 12 and 5 volts to the SATA power connector going to the SAS drive, or a combination SAS DATA/POWER cable that also would not connect the 3.3 v to the inhibit pin.