Windows 10: "The disk you specified is not valid." message from diskpart

I have this drive that I wanted to reformat, simple operation, but somehow it did not complete. After that, the drive was no longer visible in MiniTool Partition manager or the Disk Management part of Administrative tools. So I thought *Sick that I could use diskpart and then clean the problem drive. No such luck.

The drive is in an external case with USB 3. When I plug the USB cable into my system, I get a"new device connected" sound from windows and then a "device remove" sound about a second later. This cycle repeats itself many times, and disdkpart never actually sees that drive.

Here is a diskpart screenshot. Disks 0 through 3 are in normal use on my Windows 10 desktop. The problem drive would be drive 4.




So my question is, is there any way to "zap" the drive? I can hear the drive spinning and making some clicking noises, which I assume is the sound of the head assembly moving back and forth.

Or is this drive hosed? (1 TB 2.5" HGST.)

:)

 

Hard disk not recognize - default boot device missing

Administrator: X:\windows\system32\cmd.exe

DISKPART> list disk

There are no fixed disks to show

DISKPART> sel disk 0

The disk you specified is not valid

There is no disk selected

 

Hard disk not recognize - default boot device missing

i have this same error

Administrator: X:\windows\system32\cmd.exe

DISKPART> list disk

There are no fixed disks to show

DISKPART> sel disk 0

The disk you specified is not valid

There is no disk selected

But on Surface Pro

how to do ?

tanks

 

Take the Disk out of the Enclosure, the USB controller inside the enclosure may be failing, or not getting enough power.
Attach the drive directly to a desktop motherboard. Boot into Setup (Bios) if the drive is viewable in the Bios, then Diskpart and Disk Management will see the drive and you can Initialize and create a new Simple Volume/Partition and Format it etc.

 

Drive worked normally in a different enclosure and connected to a different system. After some trial and error, the problem turned out to be a failing or failed USB 3 port connected to the motherboard. The drive wasn't getting enough power through the USB cable, which was the apparent cause of the connect-disconnect sounds I mentioned in the first message in this thread.