Formatting Error - If test duration is long

  • Be sure to checkout “Tips & Tricks”
    Dear Guest Visitor → Once you register and log-in please checkout the “Tips & Tricks” page for some very handy tips!

    /Steve.
  • 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.)

Mike Williams

New member
Jan 31, 2024
2
0
Hi, Just used ValiDrive on a slow USB stick and there is a formatting error when displaying total write time.
I can't remember what time I started the test, but it took ages to finish.

See report below

Code:
Report #1
  test date and time     31/01/2024  at  09:25
  declared drive size     15,676,211,200 (15.7GB)
  validated drive size     15,676,211,200 (15.7GB)
  highest valid region     15,676,211,200 (15.7GB)
  hub or drive vendor     jetflash
  hub or drive product     transcend_16gb
  serial number     c095dd5b

 
performance details
                 read                write
  samples             1,152             1,152
  minimum             1,101             3,456
  maximum             4,974         4,333,416
  average             1,504         3,880,214
  median             1,339         3,841,579
  std dev               440           713,726
  variance             0.293             0.184
  total time         1,732,675    =overflowed=
  percent             0.04%            99.96%
time measurements in microseconds
 
Thanks for your report, Mike. That total time was likely a 32-bit value, so it would have overflowed after around 4,294,967,296 microseconds, which would be 4,295 seconds, which is 71.58 minutes, thus one hour and 12 minutes... before the 32-bit time would overflow. So, yeah... that would be a LONG test!!
 
Yep it sure was a VERY LONG TEST.
Sorry but I can't be sure of exactly how long the test took...

/Mike
 
Through a USB 2.0 hub, I tested a 32 GB TF card, that took about an hour to finish.
That might mean that the 256 GB and 512 GB TF cards I want to test might take 8 hours and 16 hours to complete?
And they might not even get valid results?

Is ValiDrive 2.0 going to have 64-bit math?
Should I wait for ValiDrive 2.0, or try my luck with 1.01, just to get the drive map?
 
ValiDrive tests the same number of sectors in each drive, regardless of size. The only thing that makes ValiDrive take a long time is low quality flash memory, since each sector takes a long time to respond. In other words, it is very unlikely that any card will take 8 hours.