After formatting with InitDisk, an 8GB Kingston DataTraveller "100 G2" drive reports zero size and cannot be read by Windows 10.
I have a 2012-vintage Kingston USB flash drive. I recently used it to create a Linux boot disk, with the Rufus utility. And that worked fine.
But Win10 couldn't read the drive anymore.
So, I tried to recover it with GRC's InitDisk utility.
And InitDisk worked fine. I ran it under Win10, with "Run as administrator", I plugged in the drive, InitDisk identified the drive, and formatted the drive.
But, after formatting with InitDisk, the drive isn't recognized as storage media anymore.
InitDisk no longer recognizes the drive when it's plugged in.
Win10 takes a long time (just over 20 seconds) to assign the drive a letter after it's plugged in.
When it does assign a drive letter, the drive shows up with zero size.
And the "INITDISK" volume label is not present on the drive.
So, the two questions are:
#1: What's up with this?
And, #2: How can I recover the drive?
(My traditional answer to #2 has been: Plug it in to a Linux system and use gparted to blow away the partition table and write a new one.
But, I'll hold off on that in case any other InitDisk/SpinRite users find this case interesting.)
I'm attaching several screenshots. These are:
Win10 drive Properties, showing zero size.
Device Manager's Device Properties view of the drive, showing that it's populated with one, zero MB volume.
DiskPart (Win10's new replacement for fdisk), showing listings of my drives and volumes (note: no volume label on the USB drive).
DiskPart's "detail disk" output, showing "Status: No Media".
DiskPart's "detail volume" output, showing "Virtual Disk Service error: There is no media in the device."
Those strike me as very strange errors. This drive does not have removable media. It is a removable drive, with fixed flash media.
Any advice? Any additional diagnostics I should collect?
Let me know...
I have a 2012-vintage Kingston USB flash drive. I recently used it to create a Linux boot disk, with the Rufus utility. And that worked fine.
But Win10 couldn't read the drive anymore.
So, I tried to recover it with GRC's InitDisk utility.
And InitDisk worked fine. I ran it under Win10, with "Run as administrator", I plugged in the drive, InitDisk identified the drive, and formatted the drive.
But, after formatting with InitDisk, the drive isn't recognized as storage media anymore.
InitDisk no longer recognizes the drive when it's plugged in.
Win10 takes a long time (just over 20 seconds) to assign the drive a letter after it's plugged in.
When it does assign a drive letter, the drive shows up with zero size.
And the "INITDISK" volume label is not present on the drive.
So, the two questions are:
#1: What's up with this?
And, #2: How can I recover the drive?
(My traditional answer to #2 has been: Plug it in to a Linux system and use gparted to blow away the partition table and write a new one.
But, I'll hold off on that in case any other InitDisk/SpinRite users find this case interesting.)
I'm attaching several screenshots. These are:
Win10 drive Properties, showing zero size.
Device Manager's Device Properties view of the drive, showing that it's populated with one, zero MB volume.
DiskPart (Win10's new replacement for fdisk), showing listings of my drives and volumes (note: no volume label on the USB drive).
DiskPart's "detail disk" output, showing "Status: No Media".
DiskPart's "detail volume" output, showing "Virtual Disk Service error: There is no media in the device."
Those strike me as very strange errors. This drive does not have removable media. It is a removable drive, with fixed flash media.
Any advice? Any additional diagnostics I should collect?
Let me know...
Attachments
Last edited: