Hi all - I'm trying to dig through the system logs on this but they're a little over my head.

 

I installed a SAS expander card (HP 24 Bay 3GB SAS Expander Card 487738-001 468405-002 w 2x 28" + 1x 33" Mini-SAS) and 2 8TB SAS drives (GST HE8 8TB SAS 12Gb/s Nearline HDD).

 

Everything I had before the SAS card (4 x 2TB drives, 3 x 4TB drives) is recognized and working, but it can't seem to detect the new ones. I tried a few reboots, but nothing shows up in the unassigned devices.

 

*Update:* It was the drive. It was toast.

oracle-diagnostics-20191110-1957.zip

Edited December 24, 20196 yr by vanik

Anyone willing to help with this? 😕

How about other existing drive under expander ?

All the existing drives are there, it just can't see the new ones.

Try this, but I am not sure it ( 468406-B21 a.k.a. 487738-001 ) suitable for your expander or not, your one show firmware ver 1.0

https://serverfault.com/questions/631574/how-to-upgrade-the-firmware-of-hp-sas-expander-card-without-smart-array-controll

Edited November 13, 20196 yr by Benson

Are the disks detected if connected directly to the HBA? If not check the 3.3v line, some WD/HGST drives won't power up if there's 3.3v on the SAS/SATA plug, google "wd 3.3v pin"

Yes, forget that, check the 3.3v first.

Ah, ok. Thanks for the response!

 

I updated the firmware but that didn't work. By connecting directly to the HBA, do you mean bypassing the SAS card and going right to the motherboard's connection?

 

And if it's a 3.3v, would the tape trick work?

1 minute ago, vanik said:

By connecting directly to the HBA, do you mean bypassing the SAS card and going right to the motherboard's connection?

Bypassing the expander, in your case connecting to LSI onboard ports.

 

3 minutes ago, vanik said:

And if it's a 3.3v, would the tape trick work?

Yep

Great! Thanks @johnnie.black!!

I'm halfway there! I got one device to read fine, but the other one is kind of recognized but doesn't seem to be working right:

Nov 18 21:30:59 oracle kernel: sd 7:0:4:0: [sdg] Spinning up disk...
Nov 18 21:32:38 oracle kernel: sd 7:0:4:0: [sdg] Read Capacity(16) failed: Result: hostbyte=0x00 driverbyte=0x08
Nov 18 21:32:38 oracle kernel: sd 7:0:4:0: [sdg] Sense Key : 0x2 [current] [descriptor]
Nov 18 21:32:38 oracle kernel: sd 7:0:4:0: [sdg] ASC=0x4 ASCQ=0x2
Nov 18 21:32:38 oracle kernel: sd 7:0:4:0: [sdg] Read Capacity(10) failed: Result: hostbyte=0x00 driverbyte=0x08
Nov 18 21:32:38 oracle kernel: sd 7:0:4:0: [sdg] Sense Key : 0x2 [current] [descriptor]
Nov 18 21:32:38 oracle kernel: sd 7:0:4:0: [sdg] ASC=0x4 ASCQ=0x2
Nov 18 21:32:38 oracle kernel: sd 7:0:4:0: [sdg] 0 512-byte logical blocks: (0 B/0 B)
Nov 18 21:32:38 oracle kernel: sd 7:0:4:0: [sdg] 0-byte physical blocks
Nov 18 21:32:38 oracle kernel: sd 7:0:4:0: [sdg] Write Protect is off
Nov 18 21:32:38 oracle kernel: sd 7:0:4:0: [sdg] Mode Sense: f7 00 10 08
Nov 18 21:32:38 oracle kernel: sd 7:0:4:0: [sdg] Write cache: enabled, read cache: enabled, supports DPO and FUA
Nov 18 21:32:38 oracle kernel: sd 7:0:4:0: [sdg] Spinning up disk...
Nov 18 21:34:19 oracle kernel: sd 7:0:4:0: [sdg] Read Capacity(16) failed: Result: hostbyte=0x00 driverbyte=0x08
Nov 18 21:34:19 oracle kernel: sd 7:0:4:0: [sdg] Sense Key : 0x2 [current] [descriptor]
Nov 18 21:34:19 oracle kernel: sd 7:0:4:0: [sdg] ASC=0x4 ASCQ=0x2
Nov 18 21:34:19 oracle kernel: sd 7:0:4:0: [sdg] Read Capacity(10) failed: Result: hostbyte=0x00 driverbyte=0x08
Nov 18 21:34:19 oracle kernel: sd 7:0:4:0: [sdg] Sense Key : 0x2 [current] [descriptor]
Nov 18 21:34:19 oracle kernel: sd 7:0:4:0: [sdg] ASC=0x4 ASCQ=0x2
Nov 18 21:34:19 oracle kernel: sd 7:0:4:0: [sdg] Attached SCSI disk
Nov 18 21:36:28 oracle emhttpd: device /dev/sdg has size zero

I bought a couple of molex to SATA power cables and I have both drives connected to the same sleeved power supply cable (if that matters)

8 hours ago, vanik said:

I bought a couple of molex to SATA power cables

Google

molex to sata fire

and make sure the models you have are ok.

9 hours ago, vanik said:

'm halfway there! I got one device to read fine, but the other one is kind of recognized but doesn't seem to be working right:

Assuming the devices are the same model try swapping cables/backplane slot between both, if the error stays with the disk that's likely the problem.