Same here… I know if you had an HPE shelf, you’d need an active support agreement for “anything” with HPE, they don’t check specific entitlements just in general.
This wouldn’t be pretty, but you should be able to directly connect a drive to the controller for a brief test:
I wonder… is your 1T drive single port, and the 6T drives dual-port? Maybe they’re upset you only have one IOM connected to the host?
Thanks for the suggestion… the more reading I do the more I am being led down the path of replacing the iom6 controller with a generic like the HB-SBB2-E601-COMP 0952913-07, should maybe make it easier to upgrade firmware? not sure
do you have enough cables to connect both IOM to the host?
no I dont…
I went ahead and moved the LSI card to a linux machine to see if its some sort of BSD thing… but got the same result.
2.146395] sd 0:0:23:1: [sdd] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 2.146398] sd 0:0:23:1: [sdd] Sense Key : Aborted Command [current] [descriptor]
[ 2.146400] sd 0:0:23:1: [sdd] Add. Sense: Internal target failure
[ 2.146523] sd 0:0:23:1: [sdd] 0 512-byte logical blocks: (0 B/0 B)
[ 2.146531] sd 0:0:23:1: [sdd] 0-byte physical blocks
[ 2.146618] sd 0:0:23:1: [sdd] Write Protect is off
[ 2.146620] sd 0:0:23:1: [sdd] Mode Sense: bf 00 00 08
[ 2.146661] sd 0:0:22:2: [sdc] Unit Not Ready
[ 2.146663] sd 0:0:22:2: [sdc] Sense Key : Aborted Command [current] [descriptor]
[ 2.146666] sd 0:0:22:2: [sdc] Add. Sense: Internal target failure
[ 2.146796] sd 0:0:23:1: [sdd] Write cache: disabled, read cache: enabled, doesn’t support DPO or FUA
[ 2.146859] sd 0:0:22:2: [sdc] Read Capacity(16) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 2.146861] sd 0:0:22:2: [sdc] Sense Key : Aborted Command [current] [descriptor]
[ 2.146863] sd 0:0:22:2: [sdc] Add. Sense: Internal target failure
[ 2.147064] sd 0:0:22:2: [sdc] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 2.147066] sd 0:0:22:2: [sdc] Sense Key : Aborted Command [current] [descriptor]
[ 2.147069] sd 0:0:22:2: [sdc] Add. Sense: Internal target failure
[ 2.147309] sd 0:0:23:1: [sdd] Unit Not Ready
[ 2.147311] sd 0:0:23:1: [sdd] Sense Key : Aborted Command [current] [descriptor]
[ 2.147314] sd 0:0:23:1: [sdd] Add. Sense: Internal target failure
[ 2.147511] sd 0:0:23:1: [sdd] Read Capacity(16) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 2.147513] sd 0:0:23:1: [sdd] Sense Key : Aborted Command [current] [descriptor]
[ 2.147515] sd 0:0:23:1: [sdd] Add. Sense: Internal target failure
[ 2.147583] sd 0:0:22:2: [sdc] Attached SCSI disk
[ 2.147709] sd 0:0:23:1: [sdd] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 2.147711] sd 0:0:23:1: [sdd] Sense Key : Aborted Command [current] [descriptor]
[ 2.147714] sd 0:0:23:1: [sdd] Add. Sense: Internal target failure
[ 2.148180] sd 0:0:23:1: [sdd] Attached SCSI disk
On the other forum, you indicated the drives work fine on a different controller. Has anything changed since then?
Actually I was mistaken, I have tried the drive on another backplane with an adaptec raid card and im getting the same results
[ 2.139614] sd 1:0:23:1: [sdd] 0 512-byte logical blocks: (0 B/0 B)
[ 2.139616] sd 1:0:23:1: [sdd] 0-byte physical blocks
[ 2.139705] sd 1:0:23:1: [sdd] Write Protect is off
[ 2.139707] sd 1:0:23:1: [sdd] Mode Sense: bf 00 00 08
[ 2.139868] sd 1:0:23:1: [sdd] Write cache: disabled, read cache: enabled, doesn’t support DPO or FUA
[ 2.140043] sd 1:0:22:2: [sdc] Unit Not Ready
[ 2.140046] sd 1:0:22:2: [sdc] Sense Key : Aborted Command [current] [descriptor]
[ 2.140048] sd 1:0:22:2: [sdc] Add. Sense: Internal target failure
[ 2.140245] sd 1:0:22:2: [sdc] Read Capacity(16) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 2.140247] sd 1:0:22:2: [sdc] Sense Key : Aborted Command [current] [descriptor]
[ 2.140249] sd 1:0:22:2: [sdc] Add. Sense: Internal target failure
[ 2.140458] sd 1:0:22:2: [sdc] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 2.140461] sd 1:0:22:2: [sdc] Sense Key : Aborted Command [current] [descriptor]
[ 2.140464] sd 1:0:22:2: [sdc] Add. Sense: Internal target failure
[ 2.140593] sd 1:0:23:1: [sdd] Unit Not Ready
[ 2.140595] sd 1:0:23:1: [sdd] Sense Key : Aborted Command [current] [descriptor]
[ 2.140598] sd 1:0:23:1: [sdd] Add. Sense: Internal target failure
[ 2.140791] sd 1:0:23:1: [sdd] Read Capacity(16) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 2.140793] sd 1:0:23:1: [sdd] Sense Key : Aborted Command [current] [descriptor]
[ 2.140795] sd 1:0:23:1: [sdd] Add. Sense: Internal target failure
[ 2.140987] sd 1:0:23:1: [sdd] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 2.140989] sd 1:0:23:1: [sdd] Sense Key : Aborted Command [current] [descriptor]
[ 2.140991] sd 1:0:23:1: [sdd] Add. Sense: Internal target failure
[ 2.141172] sd 1:0:22:2: [sdc] Attached SCSI disk
[ 2.141528] sd 1:0:23:1: [sdd] Attached SCSI disk
is it possible that running badblocks -wsv -b 4096 on these disks caused something to go haywire on reading their size?
Are these old netapp appliance drives by chance? Im currently converting the last of mine to a normal sector size and got the same errors in my log on bootup. If so I used a guide on serve the home " How to reformat HDD & SSD to 512B Sector Size"
tldr
install sg-utils
sg_scan -i
sg_format --format --size=512 /dev/sgX <–drive number
edit: ps this worked for me but but I dont know jack(afayk) and im using an ebay sas cable no shelf(yet)
I’ve seen errors like this (not quite the same) when the controllers are configured for multipath but the drives are missing interposers. Do you have any days drives to try? If sas works but not SATA the shelf expects multipath and won’t ok the disk till it can shake hands properly
Thanks to both of you for getting back to me, Ive done a bit more troubleshooting in the past couple of days. I feel like the problem is that these disks are not spinning up in this disk shelf.
Wendell: The drive that is working is an (older) WD SAS 1tb,
The Drives that are not working (in this shelf) are Seagate ST6000NM0095’s (Exos 6tb)
I just put in a SATA disk to try your suggestion, and it come up fine.
[264785.375599] scsi 1:0:29:0: Processor MARVELL LUIGI_V2_STSB_DB 2015 PQ: 0 ANSI: 5
[264785.375608] scsi 1:0:29:0: SSP: handle(0x001d), sas_addr(0x500a0980024b2db5), phy(28), device_name(0x0000000000000000)
[264785.375611] scsi 1:0:29:0: enclosure logical id (0x500a0980024cfdc8), slot(20)
[264785.375684] scsi 1:0:29:0: Power-on or device reset occurred
[264785.376365] scsi 1:0:29:0: Attached scsi generic sg33 type 3
[264785.404907] scsi 1:0:29:1: Direct-Access HITACHI HUS724040ALE64DB NA01 PQ: 0 ANSI: 5
[264785.404914] scsi 1:0:29:1: SSP: handle(0x001d), sas_addr(0x500a0980024b2db5), phy(28), device_name(0x0000000000000000)
[264785.404916] scsi 1:0:29:1: enclosure logical id (0x500a0980024cfdc8), slot(20)
[264785.405010] scsi 1:0:29:1: Power-on or device reset occurred
[264785.405694] sd 1:0:29:1: Attached scsi generic sg34 type 0
[264785.405738] sd 1:0:29:1: [sde] Spinning up disk...
[264786.436204] .
[264787.460267] .
[264788.484276] .
[264789.508238] .
[264789.508326] sd 1:0:29:1: Inquiry data has changed
[264789.508580] ready
[264789.508751] sd 1:0:29:1: [sde] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[264789.508753] sd 1:0:29:1: [sde] 4096-byte physical blocks
[264789.508773] sd 1:0:29:1: [sde] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[264789.508775] sd 1:0:29:1: [sde] 4096-byte physical blocks
[264789.508832] sd 1:0:29:1: [sde] Write Protect is off
[264789.508834] sd 1:0:29:1: [sde] Mode Sense: bf 00 00 08
[264789.508883] sd 1:0:29:1: [sde] Write Protect is off
[264789.508885] sd 1:0:29:1: [sde] Mode Sense: bf 00 00 08
[264789.509028] sd 1:0:29:1: [sde] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[264789.509075] sd 1:0:29:1: [sde] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[264789.509285] sde: detected capacity change from 0 to 1000204886016
[264789.588154] sde:
[264789.590116] sd 1:0:29:1: [sde] Attached SCSI disk
I have posted a new thread as to not confuse the troubleshooting direction:
Do those drives need the same power pin fix that the white label drives people shuck from the WD Elements externals?
I have tried taping off pins 1-3 with a thin strip of Kapton tape, but that has not helped to get the drives spinning. see below
[332939.859646] sd 1:0:32:1: [sdf] Spinning up disk...
[332940.864363] .
[332941.888373] .
[332942.912384] .
[332942.912692] not responding...
[332942.913003] sd 1:0:32:1: [sdf] Read Capacity(16) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSEActually just took it a step further and removed Power pin 3 from one of the drives, still did not spin up in the 4486 disk shelf
Thanks ! I appreciate it, will give it a look over.
So I actually have the same problem. Using a LSI 9207-8e and the DS4486. Realized that SATA drives show up fine, but not SAS drives. What I tried doing is bypassing the caddy and plugging the drive directly to the SAS backplane and the drives seem to show up. My prediction is that the caddies do a SAS dual lane to split to dual single lane SATA. As a result there is probably of only the potential for 24 bay SAS.
I found the same thing to be true… How did you plug in the SAS drives and ‘bypass’ the caddies, its pretty deep!
For testing I temporarily just hung it off the SAS port with one on top of each other. I’m considering on trying to 3d print some caddies or some sort.
I was about to try something like this with a 4246. I have 2 suggestions :
Definitely remove the IOM6 and install HB-SBB2-E601 instead. If you connect only one cable, you only need the top controller, that would using one out of the two SAS ports.
Remove the interposer in the caddy in order to install the drive further in. These interposers are designed to allow a SATA drive on a SAS backplane; if the drive is SAS already, no need for the interposer.
You may have to drill holes in the caddy. On older Dell caddies, there are two positions : one to mount the drive with the interposer, and one without.
This topic was automatically closed 273 days after the last reply. New replies are no longer allowed.