Is it possible to get these SAS Hitachi drives to work on a "normal" system?
- Thread starter BackupProphet
- Start date
Yes. I dumped flash from EMC and write dump to the flash of DKR5C controler board. It not working.
This will not work, the data in the flash only for the initial download main firmware is stored on magnetic disks.
Read this document point 7.0 https://www.seagate.com/staticfiles/support/disc/manuals/enterprise/savvio/10K.4/100539221c.pdf About self-encrypting drive, I think this applies to HGST DKR5C.
If the disk is encrypted, it goes into read-only mode.
If the disk is encrypted, it goes into read-only mode.
I watched all the encryption settings. There is no encryption on my disk. TCG settings are also not active.
Confirm this! i also can't find any flags that reports about active encryption!
Also this HDD's perfectly can reformatted with any bytes per sector - 512, 520, 528 - look like drive is not read only mode.
Out of roughly a hundred of CobraE (HUC1090) drives I have bought on ebay there was maybe a dozen that I had to send back for a refund because of this specific problem where the drive could be successfully formatted and self-tested but could not be written to.
I had no reason to investigate any further since it was easier to return the problematic drives and buy working ones at the same price ($15-20 for 600Gb model depending on the order size) instead.
Even if I were to find those drives available for much lower price (let's say under $5ea) I would not bother because I moved on to higher capacity drives now. I mean I like to tinker as much as the next guy but in the end I would like to be able to show something for it.
So my question to people still looking to solve this problem - how many drives like this are you still sitting on?
I had no reason to investigate any further since it was easier to return the problematic drives and buy working ones at the same price ($15-20 for 600Gb model depending on the order size) instead.
Even if I were to find those drives available for much lower price (let's say under $5ea) I would not bother because I moved on to higher capacity drives now. I mean I like to tinker as much as the next guy but in the end I would like to be able to show something for it.
So my question to people still looking to solve this problem - how many drives like this are you still sitting on?
New to the site. I've been led here by google due to having just received 6 of the HUC106060CSS600 EMC drives from Ebay for my Dell R610. Sadly, they aren't seen at all by the PERC H200i controller (or BIOS for that matter). You guys are talking WAY over my head, but it sounds like this is a complete "no go" in spite of Dell owning EMC? I was hoping a simple firmware update would do the trick.
This thread is discussing very specific problem where
which is completely unrelated to
Everyone else's drives are fully functional (if used in their intended system) whereas yours might be just plain dead. As there is no reason for a non broken drive not to get recognized when connected to a plain HBA.
The thread is about getting otherwise functional OEM drives to work outside of their intended ecosystem.
The thread is about getting otherwise functional OEM drives to work outside of their intended ecosystem.
How were you going to update firmware on a device not being recognized by the system if you do not mind me asking?
Last edited:
The drives are not in their intended ecosystem. I believe they would work if plugged into an EMC Isilon system. I do not have an EMC system; or at least I did not think I did. They were working pulls from EMC. The thought of flashing them was the part I was hoping there was an answer to. How to hook them up somehow in a manor they will be sensed. I cannot just connect them to a normal PC since they are SAS. Any suggestions?
I've found someone who'd try connecting directly to the 25U4032E to reflash the drive. If anyone's got standard firmware - please share. Normal versions seem to be A440, A5B0, B5B0
This is not how it works. The HDD firmware updates are not just raw images ready to be flashed to the EEPROM chip. But you are more than welcome to ask your friend to dump the existing contents of the chip and post it online.
Indeed it isn't: firmware is 900k, while the size of the chip is 512k - it'd not fit.
He has, it's around 500kb. I'll post it tomorrow. You think you'll know what to edit manually to unlock it?
Here it is, from DKR5D-J60SS. By the trays, these drives were in the HP P9000 unit, part #s on the trays S5E-J600SS and 5541892-A