ValiDrive False negative?

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

vincent1

Member
Jul 19, 2025
5
0
HI
The app reads a 1 TB flash drive as having a validated size of 1.05 MB yet i've copied over 1.44 GB of files and am able to open the last few PDFs and documents that were copied.
Ran it twice, once newly formatted and the second time with the added files.

Any suggestions for what i should do differently?

test date and time 2025-07-19 at 9:49 PM
declared drive size 1,048,576,000,000 (1.05TB)
validated drive size 1,048,576 (1.05MB)
highest valid region 1,048,576 (1.05MB)
hub or drive vendor general
hub or drive product udisk
serial number 6
 
Validrive is agnostic to any file structure and tests only the hardware.

File systems do funky stuff, such as compression, allowing a cup and
a half of flavor, so to speak, and NTFS stores small files directly in
the directory, modern Windows systems compress 'sparse' files, and
everything that reports space uses a different scheme.

You can open a properties window for each file and compare the 'size'
versus 'size on disk' to see if your files are being automatically
compressed.

However for thousands of files, checking each one is a challenge, but
there are programs and scripts that might help explain what's going
on and help raise your confidence that you know what's happening,
see:

https://www.google.com/search?q=How+can+I+compare+file+size+to+size+on+disk+for+thousands+of+files?

I just looked at an 8 GB USB drive, ChkDsk says 7,675,888 KB total
disk space, yet Computer Management says 7.34 GB, and Properties
says 7,860,109,312 bytes AND 7.31 GB - one drive, with 4 different
measurements from Microsoft.

You can fill the drive and compare the copied files to the originals,
perhaps use free TeraCopy in VERIFY mode.

You can also try free h2testw, but it tests partitions, not drives.

What does the manufacturer say about their drive?

What's the drive make and model and vendor, and item reference
number and the packaging bar code number, and any other details?

Thanks.
 
Last edited:
The app reads a 1 TB flash drive as having a validated size of 1.05 MB yet i've copied over 1.44 GB of files and am able to open the last few PDFs and documents that were copied.
Ran it twice, once newly formatted and the second time with the added files.

Any suggestions for what i should do differently?

test date and time 2025-07-19 at 9:49 PM
declared drive size 1,048,576,000,000 (1.05TB)
validated drive size 1,048,576 (1.05MB)
highest valid region 1,048,576 (1.05MB)
hub or drive vendor general
hub or drive product udisk
serial number 6
vincent1,

As Peter Blaise noted, ValiDrive is file system agnostic. ValiDrive neither knows or cares what file system is on the drive.

ValiDrive seems to be telling you that your flash drive is a "fake". You may be writing over 1.44 GB of files but you are apparently NOT storing over 1.44 GB of files on that flash drive.

First clue: The declared size of 1.05 TB. That is an impossible size for flash NAND storage. 1.0 TB (or a little less) - yes. 1.05 TB - NO!

Second clue: The validated size of 1.05 MB is also an impossible size for flash NAND storage. Typical storage capacities are 2, 4, 8, 16, 32, etc. GB.

Thus, either the drive's NAND has simply failed, and/or the (possibly faked or perhaps failed) firmware is not reporting write errors.

Either way, that flash drive is useless.

Can you see or copy off any files other than the last one written? Even of you can, that drive is in serious trouble and should never, ever be used - toss it!

ValiDrive is correctly telling you NOT to trust/use that drive.
 
  • Like
Reactions: SeanBZA
Oy, thanks, @DanR, I just looked at the numbers:

1
1.05​
1.44​
1,048,576,000,000
1,048,576​
1,048,576​

... not the value of the numbers:

TB
GB​
GB​
MB
MB​
MB​

Doh!

I just looked at all the leading 1s and thought, "OK".

My bad - number blindness - there are stories cascading about that.

I presume it's got a LILO last in last out buffer, overwriting FI first in
data, and should always show the most recent 1 GB of data as
accurately stored.

Good luck with the prior data - it's GONE.

So, sorry, @vincent1, but you've got a fake drive.

Please share the purchase details so we can all shake our fingers at
the vendor.
 
Last edited:
Peter Blaise and DanR
Thank you for your notes and suggestions.
Per DanR -I just skimmed through 3 PDFS from the drive - an 11MB, 22MB and 73MB, (all part of the 1.44 GB), they all appear complete.
I borrowed this drive to make a Windows installation drive, but the tool i was using could not validate the completed install- so I suspected there was a problem with the hardware and don't trust it.

This drive was bought from Ali Express (which explains the low quality) and is labeled Lenovo.

What i still find odd is that if there is only 1.05 MB validated (by ValiDrive) how could the 3 large PDFs be opened? ... I think now that there is more than 1.05 MB of usable space but those sectors weren't tested and that the suggestions above would help me map the whole drive. (Which seems like too much work at this point)

Thanks again for your input.
 
ValiDrive map:

ValiDrive only reports the contiguous validated
sectors from the 'front' of the drive when filling
in the 'validated drive size'.

ValiDrive also reports the 'highest valid region'.

Here's a sample of a drive that might have
storage randomly available in spite of failing
to have full storage:

1753068820893.png


ValiDrive says 31.4GB is valid, but there are
green blocks further on, so I might be able to
write more than 31.4GB to the drive, as you
have written more than 1GB on yours.

That may be what's happening on your drive,
though if the SSD chip controller is gaming the
system, there may be no way to predict if any
file will land on a 'real' block and ever come
back.

SSDs map their sectors on 'pages', so any part
of any block or any part of any file could be
anywhere on the chips.

The lowest invalid sector on your drive is after
1 GB, but your drive might have 32 GB spread
all over a 1 TB map, just to game the system.

You may not 'lose' data until after trying to
write 32 GB - I'm just guessing.

So looking at a ValiDrive map may help us
interpret what's happening on any specific
drive.

Or not - ValiDrive only tests 576 'regions'
( declining to reveal the exact size and location
for any tested drive so that vendors can't
'game' ValiDrive ).

It's possible that your drive has usable
storage outside the 576 regions that
ValiDrive tests, so a more-thorough test
might help reveal and explain.

- - - - -

File Size, Size on Disk, Compressed, and
Sparse Attribute:


Or, your 1.44GB of data may actually 'fit' in
1GB of storage space.

If you look at the properties for each file,
compare the Size versus the Size on disk or
Compressed:

1753068118818.png


1753066888724.png


My examples aren't extreme, but any file
could be more 'sparse', check yours.

Or look for attributes indicating the file is
Sparse, the free FAR File And Archive Manager
will show and allow toggling the Sparse
attribute and function, see
https://www.farmanager.com/download.php?l=en

1753067763868.png


Though merely copying the file with an
unaware program should eliminate the Sparse
attribute and return a Sparse file to full size on
disk

- - - - -

Broad spectrum examination:

Not-free SpinRite 6.1 may be able to check the
drive if the BIOS and USB ports allow.

This might a good command line to use:

SPINRITE NORAMTEST NOREWRITE DYNASTAT 0 LEVEL 5

SpinRite is NOT designed to find fakes drives,
but can be pressed into service to show us
something.

I suggest LEVEL 5 because I have a fake
drive that passes LEVEL 3 and LEVEL 4 .

It would be interesting to know if your fake
drive passes or fails under SpinRite 6.1 scrutiny.

ValiDrive exists because SpinRite was designed
to recover data and maintain reputable drives,
not discover vendors who lie.

- - - - -

Free h2testw checks partitions, and can do a
full write and compare test, see:
https://h2testw.org/

It's destructive, best applied to a freshly
re-partitioned and re-formatted empty drive,
and it takes a lot more time than ValiDrive.

- - - - -

Free HDDScan checks drives, and can also do
a full write and compare test, also destructive,
and also takes a long time, see:
https://hddscan.com/

- - - - -

Check out any responses to a web search and
let us know if you discover any additional tools,
see:
https://www.google.com/search?q=How+can+I+test+a+USB+drive+to+confirm+its+capacity?

- - - - -

Note, we're just trying to understand the drive,
not use it.

Lonovo makes no drives, ( other than CD ) see:
https://www.lenovo.com/us/en/d/acce...eDatas=773:Memory%20%26%20Storage;1008:Lenovo

This is a great insight for everyone to check
the OEM original equipment manufacturer
for the same model we see offered for sale
elsewhere.

If the vendor doesn't even sell such a thing,
that's a clue that the thing being offered is
fake.

If the vendor does sell such a thing, then
buy with return privileges, because the
cheapie deal is probably fake.

Your non-Lonovo drive seems to be a
'smarter' fake drive than the prior fake drives
we've seen, so we'd love to know more
about it's behavior.

It is not trustworthy, so never never never put
anything on it that is the only copy of precious
data.

Let us know what you find.

Good luck.
 
Hi
I hope the following is of value:

H2testw -I cancelled write after about 25 minutes with 21 hours to go:

Warning: Only 26654 of 999981 MByte tested.
The media is likely to be defective.
483.5 MByte OK (990336 sectors)
25.5 GByte DATA LOST (53597056 sectors)
Details:0 KByte overwritten (0 sectors)
0 KByte slightly changed (< 8 bit/sector, 0 sectors)
25.5 GByte corrupted (53597056 sectors)
0 KByte aliased memory (0 sectors)
First error at offset: 0x000000000e484000
Expected: 0x000000000e484000
Found: 0x029f029e029b029a
H2testw version 1.3
Reading speed: 8.33 MByte/s
H2testw v1.4


From properties of 3 files that would not open ( the pdfs i was able to open had same size and size on disk):
Type of file MP4 Video (VLC) (mp4)
Size147 MB (154,672,975 bytes)
Sze on disk 147 MB bytes (154,927,104 bytes

Type of file MP4 Video (mp4)
Size: 90.9 MB (95,404,189bytes)
Sze on disk 91.0 MB (95,420,416bytes)

Type of file: JPG File (.jpg)
Size 8.73MB (9,158,288 bytes
Size on disk: 8.75MB (9,175,040 bytes)


Flash Drive Information Extractor
Volume: D:
Controller: ChipsBank
Possible Memory Chip(s):
Toshiba TC58NVG2S0FTA00
Memory Type: SLC
Flash ID: 98DC9026 7616
Flash CE: 1
Firmware Date: 2018-12-01
VID: 048D
PID: 1234
Manufacturer: General
Product: UDisk
Query Vendor ID: General
Query Product ID: UDisk
Query Product Revision: 5.00
Physical Disk Capacity: 1048576000000 Bytes
Windows Disk Capacity: 1048556077056 Bytes
Internal Tags: DGA7-8P3L
File System: EXFAT
Relative Offset: 1024 KB
USB Version: 2.00
Declared Power: 100 mA
ContMeas ID: 1E1E-01-99
------------------------------------
antspec.com/usbflashinfo/
Program Version: 9.4.0.645


TC58NVG2S0FTA00 = NAND Flash 4Gb 32nm SLC NAND (EEPROM)

(Edited)
 
Last edited:
What i still find odd is that if there is only 1.05 MB validated (by ValiDrive) how could the 3 large PDFs be opened? ... I think now that there is more than 1.05 MB of usable space but those sectors weren't tested and that the suggestions above would help me map the whole drive. (Which seems like too much work at this point)
ValiDrive will stop when it encounters the first unwritable area. Thus, there could be a valid area beyond the first bad area that contains some files..

TC58NVG2S0FTA00 = NAND Flash 4Gb 32nm SLC NAND (EEPROM)
It appears that the NAND is failing BIG time. :(
 
Just thinking, as the only memory chip the Information Extractor reporting is SLC - maybe its the cache that it sees?
 
"... ValiDrive will stop when it encounters the
first unwritable area ..."​

No, as far as I understand, ValiDrive
pseudo-randomly checks 576 'regions' ( of
unpublished unspecified size, determined by
@Steve and the pretest results ) and will
report the readability and writability and
rewritability of each 'region'.

I think the philosophy is to not presume that
one 'bad' region is all there is to report, so
ValiDrive chugs on for the entire 576 'regions'
regardless of the qualities of any prior
'regions' tested.

Hence the map I shared where there were
'good' 'regions' spread across the drive
among 'bad' 'regions'.

Note, I use ' quotes for the jargon words
because they deserve deeper explanation than
I am giving them, and are not used in any
technical industry standard way, so 'bad' 'good'
and 'region' mean something specific here, but
may not correlate to those words used in other
programs.

For example, a 'good' region in one test may
be 'bad' in another test of the same media:

1753165450510.png


So, even though the fakery has been verified,
there is more to learn about how the drive
behaves.

Why are there random 'good' regions in
places we are reasonably confident there is no
storage media?

That's a clue to the trickery involved, where a
user may read the contents of a file ... once ...
and think it's there forever.

ValiDrive reveals that, no, it may not be there
on a second inspection.

I would love to see the results of a full SpinRite
Level 5 under DOS, but apparently h2testw
under Windows already confirmed the most
important reveal:

"... The media is likely to be defective ..."​
 
Last edited:
"... h2testw ... The media is likely to be
defective ... Flash Drive Information
Extractor ... ChipsBank ..."​

Oy my, I'd say, not just fake, but fried!

I've only ever see 'ChipsBank' on fried USB
drives.

What does ValiDrive say now?

And what size drive does Windows find,
especially when repartitioning and reformatting?
 
Since a lot of testing tools were mentioned here, I want to add one that I posted about earlier this year in another thread.
I found that "MediaTester" on GitHub that "is similar to h2testw" but improved in some ways.
 
Attached are ValiDrive reports, before and after(2) repartitioning and formatting.
The 26GB of data from H2testw were on the drive when the first test was run.
Windows properties shows 1,048,556,077,056 bytes 976GB both before and after partitioning.
I've returned the drive to the original owner.
Thank you all for your ideas and suggestions.

Vincent
 
What?

You returned a fake drive for a refund?!?

What are we gonna play with now, then?

;-)

Actually, that's probably the ONLY legitimate sale of any fake drive -
send them directly to fake-finder programmers, to so see how long
either can reign supreme over the other - fake programmers or
fake-finder programmers, a contest of wits.

Thanks for exploring this problem and sharing your experience - it is
helping and confirming for others that we are not crazy, but that
there really are fake drives, INTENTIONALLY fake drives, and Amazon
has zero incentive to stop it because Amazon gets a significant
commission ( one of may reasons I buy from alternatives ).