Bricked my HGST HUH721010AL5200

[rsumperl]

Hello everyone,
Just looking for an "out" here, foolish me had a new HGST HUH721010AL5200 and attempted to convert to 4096, well I got impatient as the Hugo software was taking forever, so I killed the process which killed the drive. Is there any repair that can be done or did I just waste my money?

Thanks
Ray

 

[kapone]

Now...(sorry), the only thing left is...



Humor aside. Does the drive even show up now? Does Hugo see it at all?

 

[rsumperl]

Hugo sees it, SG-3 sees it, Windows Server sees it in disk management, however, Windows cannot initialize the drive.
Hugo and SG-3 fail immediately on trying to "reformat".
Long story short, if it ain't broken don't fix it AND patience is a virtue, cause after 4 or so hours it was only 35% done.

 

[CyklonDX]

you can still fix it

first check the disk if there's pending operation - often disks do remember running you have format running - and it will run until it finishes.
sg_turs -p /dev/diskname
sg_requests /dev/diskname
(*in my exp some disks need 12-30h to complete full reformat)

(else if you are in the us, you can send it to me - if i manage to fix it, you can pay for postage back or let me keep it.)

 

[rsumperl]

Could the disk still think the operation is happening even if I killed the hugo process?
If the drive still thinks the process is going is there a way to "reset" the drive?
Is there a way with SG-3 to force the update?
In the past I have done the following in an administrator PowerShell:
1) .\sg_scan to get the physical drive number.
2) .\sg_format --format --size=4096 -v pdx

I should add that .\sg_scan sees the drive as pd2

Thanks

 

[napalm_atx]

More easy way is to use wdckit with --fastformat option

 

[CyklonDX]

Could the disk still think the operation is happening even if I killed the hugo process?
If the drive still thinks the process is going is there a way to "reset" the drive?
Is there a way with SG-3 to force the update?
In the past I have done the following in an administrator PowerShell:
1) .\sg_scan to get the physical drive number.
2) .\sg_format --format --size=4096 -v pdx

I should add that .\sg_scan sees the drive as pd2

Thanks

just use sg_turs or requests to see if its doing something first. It doesn't matter if you kill the software thats "doing" it. The disk formats itself internally. You only call upon those functions.

 

[rsumperl]

Should I just power up the server and wait a day or two and see what the end result is?

 

[Marsh]

Should I just power up the server and wait a day or two and see what the end result is?

Yes, boot the system, let it run overnight or longer ( time to take formatting a 10tb drive ).
It happened to me with a 6TB SAS drive.
Wait over a day, while I am busy with life stuff.
Came back and try sg_format again, then all is well.

 

[rsumperl]

Perhaps I have dodged a bricked drive. I powered up the server and kicked off (.\sg_format --format --size=4096 -v pd2) instead of the Hugo app, and it seems to be running. All equipment is on a UPS, so hopefully no issues.

 

[rsumperl]

Thank you to everyone who responded, it is alive and well. Sg_format worked, along with leaving it alone.

Thanks
Ray