Validrive results differ each run

  • SpinRite v6.1 Release #3
    Guest:
    The 3rd release of SpinRite v6.1 is published and may be obtained by all SpinRite v6.0 owners at the SpinRite v6.1 Pre-Release page. (SpinRite will shortly be officially updated to v6.1 so this page will be renamed.) The primary new feature, and the reason for this release, was the discovery of memory problems in some systems that were affecting SpinRite's operation. So SpinRite now incorporates a built-in test of the system's memory. 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 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.)

marky1124

New member
Sep 25, 2020
4
2
I have a pretty old 1GB USB stick. I don't suspect it of being a fake. I've run Validrive on it twice and both times it's reported about half a dozen different locations marked in red for 'no storage'. The marked locations differ between the two runs. One is potentially the same. Is this normal behaviour?
 
I have a pretty old 1GB USB stick. I don't suspect it of being a fake. I've run Validrive on it twice and both times it's reported about half a dozen different locations marked in red for 'no storage'. The marked locations differ between the two runs. One is potentially the same. Is this normal behaviour?
It definitely should not be doing that. ValiDrive would be showing "No Storage" when it wrote some random data but did not get the same data back when it read it back. So I would definitely not trust this drive with anything important. The reason you're seeing differing locations is that ValiDrive's testing sequence is truly randomized and will never be the same twice. So whatever flaky thing is going on, it might also be about the pattern of the sequence (which is also not good!)
 
  • Like
Reactions: marky1124
But sequence does not explain why 'block 23' (for example) has different outcome in different runs. Or am I missing something obvious now?
Correct. That part is still very strange. Actually, I think I may have encountered something similar on one of my drives. I'll do some digging.
 
Correct. That part is still very strange. Actually, I think I may have encountered something similar on one of my drives. I'll do some digging.
Found it! It's my Sansumg SD card. However, I found something even stranger when I did some further testing. I'm going to reopen my ticket.


ValiDrive-v1.0.0_2023-10-05_23-02-10.png


ValiDrive-v1.0.1_2023-10-30_20-21-00.png
 
Did you check if ValiDrive is active in task manager after stopping it? I seen that happen.

And if so, does closing that instance eliminate the need for a reboot?
I just watched Task Manager while reproducing the issue, and there was only ever 1 instance of ValiDrive running. I also verified there were 0 instances after closing it. Thanks for the suggestion though. I doubt I ever would have thought to check for that :)