The drive was hollow in the middle.

  • SpinRite v6.1 is Released!
    Guest:
    That's right. SpinRite v6.1 is finished and released. For the full story, please see this page in the "Pre-Release Announcements & Feedback" forum.
    /Steve.
  • Be sure to checkout “Tips & Tricks”
    Dear Guest Visitor → Once you register and log-in:

    This forum does not automatically send notices of new content. So if, for example, you would like to be notified by mail when Steve posts an update to his blog (or of any other specific activity anywhere else), you need to tell the system what to “Watch” for you. Please checkout the “Tips & Tricks” page for details about that... and other tips!

    /Steve.
  • Announcing “BootAble” – GRC's New Boot-Testing Freeware
    Please see the BootAble page at GRC for the whole story.
  • BootAble – FreeDOS boot testing freeware

    To obtain direct, low-level access to a system's mass storage drives, SpinRite runs under a GRC-customized version of FreeDOS which has been modified to add compatibility with all file systems. In order to run SpinRite it must first be possible to boot FreeDOS.

    GRC's “BootAble” freeware allows anyone to easily create BIOS-bootable media in order to workout and confirm the details of getting a machine to boot FreeDOS through a BIOS. Once the means of doing that has been determined, the media created by SpinRite can be booted and run in the same way.

    The participants here, who have taken the time to share their knowledge and experience, their successes and some frustrations with booting their computers into FreeDOS, have created a valuable knowledgebase which will benefit everyone who follows.

    You may click on the image to the right to obtain your own copy of BootAble. Then use the knowledge and experience documented here to boot your computer(s) into FreeDOS. And please do not hesitate to ask questions – nowhere else can better answers be found.

    (You may permanently close this reminder with the 'X' in the upper right.)


walthouser

Helping people be more secure online through train
I ran validrive on a no-name "8GB" USB drive that had only 4KB valid. It reported valid regions at the beginning and end but missing regions spread throughout the drive.

test date and time 10/23/2023 at 11:18 AM
declared drive size 8,053,063,680 (8.05GB)
validated drive size 4,096 (4.10KB)
highest valid region 8,053,063,680 (8.05GB)
hub or drive vendor generic
hub or drive product flash_disk
serial number 7a0d99f9

Maybe we should start posting these findings as user reviews on Amazon and other vendors,
Thanks, Steve, for this valuable tool.
 
  • Like
Reactions: Steve
I ran validrive on a no-name "8GB" USB drive that had only 4GB valid. It reported valid regions at the beginning and end but missing regions spread throughout the drive.

declared drive size 8,053,063,680 (8.05GB)
validated drive size 4,096 (4.10KB)
highest valid region 8,053,063,680 (8.05GB)
4 KB not 4 GB.

I think it's more likely the drive is broken than fake, but okay.
 
Yes 4k says the flash is failed, probably the die has massive defects, or is cracked. But can be a fake, where the firmware uses the firmware area to return a valid FAT partition and then has 4k as the start of the FAT, and the final 4k block as the end of drive, which is all the quick format looks for. Only needs 8k of working flash, as most OS systems will not actually verify the second copy of the FAT in any operation, just write to update it, using the first copy info, and only aborting if there is a write error returned by the drive.
 
Yes 4k says the flash is failed, probably the die has massive defects, or is cracked. But can be a fake, where the firmware uses the firmware area to return a valid FAT partition and then has 4k as the start of the FAT, and the final 4k block as the end of drive, which is all the quick format looks for. Only needs 8k of working flash, as most OS systems will not actually verify the second copy of the FAT in any operation, just write to update it, using the first copy info, and only aborting if there is a write error returned by the drive.
It hasn't have to be any of the more far fetched theories, it's a common failure mode for USB flash drives.