I have an enterprise class SATA 14TB Ultrastar DC H530 WUH721414ALE6L4 drive.
If it was SAS, it could be easy to force-enable the drive, but it’s the SATA version; I need to know how to re-enable it after an USB failure.
Seagate SeaTools says:
Security Supported: Yes
Security Enabled: No
TCG Supported: No
Security Locked: Yes
Frozen: No
diskpart says that the disk is read-only with attribute disk
It happened at a time where dfwe destroyed files in another machine, and conhoy too entered the 32-bit Windows 7 machine this 14TB disk was, with powershell.
When spinning up, the drive test seeks several times each 0.5 seconds and then a fast final seek.
Now this final seek is the only thing that the drive no longer does and instead stays as inaccessible.
I think that if the drive was able to do this final seek, which doesn’t since it became inaccessible, it would give me access to the files.
It seems that this fast final seek is not done as part of some preventive security after a power/link failure and I need to know how to re-enable the drive after this failure, like some SAS drives that no longer spin after a power failure and you need a different, simpler HBA, with regular SATA data cables and SAS socket power/data molex adapter, to make it spin and online it again.
It also makes a normal seek sound every 5 seconds, but it seems that after some minutes, now it stops doing those seeks, which is abnormal for this drive.
It lasted less than a year.
It became inaccessible after an enclosure failure. I have seen that happen also with Seagate Constellation SAS 1TB 2.5" drives, after an abrupt power failure, but I don’t know if it’s the same situation, although it seems so with this SATA drive.
It shows as unknown, Unititialized and shows around 13000 GB (12/14 TB) in diskmgmt.msc
It shows as unknown in CrystalDiskInfo.
Windows Server 2019 and Windows 7 show the same symptoms.
All sectors show read errors when reading with ddrescue and a “buffer error” when booting Linux SystemRescue 10.00.
It seems as if the drive became locked by a power failure, as I have seen with some SAS drives.
What commands, procedures, HBAs, etc., do I need to unlock the drive from this damage-preventive lock after an enclosure fail?
What Linux commands or sg3_utils commands could I run to unlock an enterprise class hard drive that became inaccessible after a communication/power failure?
I have tried all my machines and 2 SAS HBAs, LSI, Microsemi 2100, Seagate Dashboard, sg_scan, but they can’t force enable the drive to give me access to the media, only to the identification model, capacity and unknown S.M.A.R.T. status that was perfect right before becoming inaccessible.
If it’s offline in hardware in a special way, I need to know how to make it online again from the power/link failure.
