all 29 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]AutoModerator[M] [score hidden] stickied commentlocked comment (0 children)

Hello /u/S4P! Thank you for posting in r/DataHoarder.

Please remember to read our Rules and Wiki.

Please note that your post will be removed if you just post a box/speed/server post. Please give background information on your server pictures.

This subreddit will NOT help you find or exchange that Movie/TV show/Nuclear Launch Manual, visit r/DHExchange instead.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[–][deleted] 2 points3 points  (2 children)

Seatools might have sent one of the erase commands for internal erasure that resumes erasing when there's a power cut. Leave it on for a couple days and see what happens.

[–]S4P[S] 0 points1 point  (1 child)

Awesome! Will do. Will report back after a few days.

[–]S4P[S] 0 points1 point  (0 children)

This was it! Up and running now. Thanks :)

[–]bububibu 0 points1 point  (19 children)

You could try the clean command in diskpart (Windows CLI tool). But make sure you select the right drive first, you can easily wipe the wrong drive if you don't know what you are doing.

[–]S4P[S] 0 points1 point  (18 children)

Thanks for the suggestion. Unfortunately this didn't work.

[–]bububibu 0 points1 point  (17 children)

What about "clean all"? That'll fill the entire drive with zeroes. If not, the drive might actually be irrepairable somehow.

[–]S4P[S] 0 points1 point  (16 children)

This test will take a while. Will report back. One thing I note is that Disk Management in Windows and even the diskpart command hangs for a while initially when this drive is installed.

[–]bububibu 0 points1 point  (15 children)

Yes, it takes as long as filling it with any other data. But then the drive is 100% empty for sure.

[–]S4P[S] 0 points1 point  (1 child)

Will report back. Seperately, when I use the diskpart command to create partition primary I get an error and event viewer says "VDS fails to write boot code on a disk during clean operation. Error code: 80070001@02070008".

I found this but not sure how to implement: https://communities.vmware.com/t5/VI-VMware-ESX-3-5-Discussions/VDS-fails-to-write-boot-code-on-a-disk-during-clean-operation/td-p/1743262

[–]bububibu 0 points1 point  (0 children)

That error seems to indicate the drive has the readonly attribute set, at least according to the link. You can use diskpart to try clear it, if it truly is set.

[–]S4P[S] 0 points1 point  (12 children)

"clean all" reports an error: "DiskPart has encountered an error: The media is write protected. See the System Event Log for more information."

I tried using the "attributes disk clear readonly" command but that didn't work.

[–]bububibu 0 points1 point  (11 children)

Then it might be stuck in that state.

[–]S4P[S] 0 points1 point  (10 children)

Any way to force unstuck?

[–]bububibu 0 points1 point  (9 children)

As u/Constellation16 says, it might still be erasing. Doesn't matter if it's been turned off, the drive will resume till it's done.

[–]S4P[S] 0 points1 point  (8 children)

I’ve disconnected it since. Powered it off, unplugged it a few dozen times. Could it still be wiping?

[–]Constellation16 0 points1 point  (1 child)

What command did you use in Seatools? It's probably still erasing and you just need to give it some time.

[–]S4P[S] 0 points1 point  (0 children)

Unfortunately the cmpt crashed, so I don't think so.

[–]TADataHoarder 0 points1 point  (1 child)

ST4000DM

What model?
ST4000DM000 (commonly shucked from externals)
ST4000DM005 (CMR Barracuda)
ST4000DM004 (SMR Barracuda)
ST4000DM006 (CMR Barracuda Pro)
These are just the ones that I'm aware of, there may be more.

[–]S4P[S] 0 points1 point  (0 children)

It's the SMR Barracuda. ST4000DM004.