Used SAS drives...No I/O?? Locked?

[AgentZero]

I bought a few used SAS drives - Hitachi DKR2H-K45SS 450GB SAS. I cannot for the life of me get any I/O on these drives. They show up in camcontrol, etc, but can't even dd to them - the other Hitachi (different part number) drives are fine...

<HITACHI HUS153030VLS300 A4C2> at scbus0 target 26 lun 0 (pass6,da6)
<HITACHI HUS153030VLS300 A4C2> at scbus0 target 27 lun 0 (pass7,da7)
<ATA TOSHIBA DT01ACA2 ABB0> at scbus1 target 3 lun 0 (pass8,da8)
<ATA TOSHIBA DT01ACA2 ABB0> at scbus1 target 4 lun 0 (pass9,da9)
<ATA TOSHIBA DT01ACA2 ABB0> at scbus1 target 5 lun 0 (pass10,da10)
<HITACHI DKR2H-K450SS D017> at scbus1 target 6 lun 0 (pass11,da11) <<<
<HITACHI DKR2H-K450SS D017> at scbus1 target 7 lun 0 (pass12,da12) <<<

Everything that tries to write, wipe, format, partition....anything on these drives comes back with an I/O error.
[root@ZFS] ~# dd if=/dev/zero of=/dev/da11
dd: /dev/da11: Invalid argument
1+0 records in
0+0 records out
0 bytes transferred in 0.000172 secs (0 bytes/sec)

I've tried booting into several things - DBAN, PMagic, Windows...nothing can touch these drives. What am I missing? The only thing I can think of is these drives are specific to the Hitachi AMS2X00 SAN and somehow locked in firmware...I'm at a loss.

Brief hardware: Supermicro X9SRL; 2x M1015 IT mode

 

[cyberjock]

I don't know what to say. Often if people turn off certain things like auto-spinup and such you have to have specific hardware to recover from that situation.

I *never* buy hard drives from anyone but my closest friends. No clue how you bought yours, but if you bought it from a friend he should be able to help you recover. If you didn't, well, either do an RMA or chalk this up to a lesson learned.

 

[AgentZero]

Audibly, auto-spinup is turned on as they do spin up to 15K, but I'm not sure that there isn't something else that is somehow disabled in firmware or hardware locked.

Agreed - this was from a reputable shop I have dealt with in the past - already have an RMA, but would have preferred to avoid all this nonsense of returning, etc.

 

[jyonke]

What was the result of this? I just picked up a couple used 15K4150's and they are combined with a IBM M5015. In the WEBIOS I get an unsupported flag. I don't think it is strictly a defective drive as I have 9 of these from different vendors and they all show the exact same thing.

Code:

[root@localhost:/opt/lsi/storcli] ./storcli /c0/e252/s0 show
Controller = 0
Status = Success
Description = Show Drive Information Succeeded.


Drive Information :
=================

--------------------------------------------------------------------------
EID:Slt DID State  DG       Size Intf Med SED PI SeSz Model            Sp
--------------------------------------------------------------------------
252:0    14 UGUnsp -  408.850 GB SAS  HDD N   N  512B DKR2H-K450SS     U
--------------------------------------------------------------------------

EID-Enclosure Device ID|Slt-Slot No.|DID-Device ID|DG-DriveGroup
DHS-Dedicated Hot Spare|UGood-Unconfigured Good|GHS-Global Hotspare
UBad-Unconfigured Bad|Onln-Online|Offln-Offline|Intf-Interface
Med-Media Type|SED-Self Encryptive Drive|PI-Protection Info
SeSz-Sector Size|Sp-Spun|U-Up|D-Down|T-Transition|F-Foreign
UGUnsp-Unsupported|UGShld-UnConfigured shielded|HSPShld-Hotspare shielded
CFShld-Configured shielded|Cpybck-CopyBack|CBShld-Copyback Shielded


[root@localhost:/opt/lsi/storcli] ./storcli -PDList -aALL
Adapter #0

Enclosure Device ID: 252
Slot Number: 0
Enclosure position: 0
Device Id: 14
WWN: 5000CCA0094C9737
Sequence Number: 1
Media Error Count: 0
Other Error Count: 0
Predictive Failure Count: 0
Last Predictive Failure Event Seq Number: 0
PD Type: SAS

Raw Size: 410.281 GB [0x33490000 Sectors]
Non Coerced Size: 409.781 GB [0x33390000 Sectors]
Coerced Size: 408.850 GB [0x331b3800 Sectors]
Sector Size: 512
Firmware state: Unconfigured(good), Spun Up
Device Firmware Level: D017
Shield Counter: 0
Successful diagnostics completion on :  N/A
SAS Address(0): 0x5000cca0094c9735
SAS Address(1): 0x0
Connected Port Number: 0(path0)
Inquiry Data: HITACHI DKR2H-K450SS    D017JMWB3TDD
FDE Capable: Not Capable
FDE Enable: Disable
Secured: Unsecured
Locked: Unlocked
Needs EKM Attention: No
Foreign State: None
Device Speed: 3.0Gb/s
Link Speed: 3.0Gb/s
Media Type: Hard Disk Device
Drive:  Not Supported
Drive Temperature : N/A
PI Eligibility:  No
Drive is formatted for PI information:  No
PI: No PI
Port-0 :
Port status: Active
Port's Linkspeed: 3.0Gb/s
Port-1 :
Port status: Active
Port's Linkspeed: Unknown
Drive has flagged a S.M.A.R.T alert : No

 

[AgentZero]

I ended up RMAing all of them - as CJ points out, recommend only buying from reputable if not new, so there were no questions asked about the RMA.

I have no idea what happened with that batch. Every other drive I used has not been a problem.

 

[jyonke]

Were yours all still under warranty? These things are not new by any means, haha. While I totally agree with CJ, the data on these is not going to be valuable and is strictly for a lab environment. All other servers at home that have invaluable data are on new drives, that are redundant and data is backed up off site.

 

[tvsjr]

If these drives came from a SAN, they're probably formatted for 520- or 528-byte sectors. They probably also will have write cache disabled by default.

To reformat them to 512-byte, try something like: http://pissedoffadmins.com/general/unsupported-sector-size-520.html
sg_format is the tool you'll want

For the write cache, you'll need to add a post-init script through the GUI. Look through my previous posts and you'll find the simple little script I created.

 

[AgentZero]

OMG Thank you! I picked up some Hitachi SLC SAS SSDs which came out of a 3PAR system. Was about to throw something....sure enough "Unsupported sector size 520". Running setblocksize now. I'm sure that this would have fixed my previous issues.