Validate Byte-for-Byte fails under Win10 but not Win7

User discussion and information resource forum for Image products.

Re: Validate Byte-for-Byte fails under Win10 but not Win7

Postby Triplehammer » Wed Aug 31, 2016 10:12 pm

DrTeeth wrote:
> Try chkdsk /r. That fixes read/write errors. It fixed an issue here on
> a drive that chkdsk /f passed as fit.

Log Name: Application
Source: Microsoft-Windows-Wininit
Date: 8/31/2016 10:04:15 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: Ulukyi
Description:


Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.

Stage 1: Examining basic file system structure ...
311552 file records processed.

File verification completed.
6193 large file records processed.

0 bad file records processed.


Stage 2: Examining file name linkage ...
366602 index entries processed.

Index verification completed.
0 unindexed files scanned.

0 unindexed files recovered to lost and found.


Stage 3: Examining security descriptors ...
Cleaning up 104 unused index entries from index $SII of file 0x9.
Cleaning up 104 unused index entries from index $SDH of file 0x9.
Cleaning up 104 unused security descriptors.
Security descriptor verification completed.
27526 data files processed.

CHKDSK is verifying Usn Journal...
40627048 USN bytes processed.

Usn Journal verification completed.

Stage 4: Looking for bad clusters in user file data ...
311536 files processed.

File data verification completed.

Stage 5: Looking for bad, free clusters ...
103482483 free clusters processed.

Free space verification is complete.

Windows has scanned the file system and found no problems.
No further action is required.

449516871 KB total disk space.
35068816 KB in 112614 files.
83120 KB in 27527 indexes.
0 KB in bad sectors.
435003 KB in use by the system.
65536 KB occupied by the log file.
413929932 KB available on disk.

4096 bytes in each allocation unit.
112379217 total allocation units on disk.
103482483 allocation units available on disk.

Internal Info:
00 c1 04 00 56 23 02 00 1a 41 04 00 00 00 00 00 ....V#...A......
19 01 00 00 33 00 00 00 00 00 00 00 00 00 00 00 ....3...........

Windows has finished checking your disk.
Please wait while your computer restarts.
Triplehammer
 
Posts: 17
Joined: Sat Aug 13, 2016 4:15 pm

Re: Validate Byte-for-Byte fails under Win10 but not Win7

Postby Triplehammer » Wed Aug 31, 2016 10:36 pm

I used findlbaf as soon as I could after each failed bfb validation through several attempts. Each time it was either a different random file or files, or "Unable to determine which file uses LBA (number)". During my attempts, I had a string of four successful backups that passed bfb validation, but now it's back to failing bfb every time.

I think I'll just stop now because I'm spending way too much time on this. I was hoping there was something simple I was doing wrong in the settings, or that support could figure out what was wrong with bfb validation. I've never been able to detect any other problems being caused by this SSD, so I'll just use IFL to back it up unless that too starts failing bfb validation. The convenience of backing up from Windows was nice but I guess that's not for me for now.

TeraByte Support wrote:
> it can still have to do with a temp file created while in that copy and
> backup / restore out side wouldn't update. To check if that's the issue,
> you could try a DRAT or normal drive (restore to it, then boot from it and
> do the bfb). Otherwise if you have something hiding it's writes in
> windows,
> you can use the findlbaf.zip from the ftp site; run command prompt as
> administrator then launch that to find file files involved with changing to
>
> get an idea. Now if it's something hiding, down at the disk level, it
> could
> hide itself so nothing found.
>
> That all said, it could be the ssd drive as well, the failure of those are
> going to be different than normal drives. The difference when its
> heavy in use vs not being used. So another thing is to reset the entire
> thing (wipe it or trim the entire thing), then restore. Another drive
> will tell if it's windows environment or the drive.
Triplehammer
 
Posts: 17
Joined: Sat Aug 13, 2016 4:15 pm

Re: Validate Byte-for-Byte fails under Win10 but not Win7

Postby TeraByte Support » Wed Aug 31, 2016 11:29 pm

the best test is to install a new drive (DRAT or regular drive large
enough), restore to it, boot to it, then backup validate byte-for-byte.

What was the name of the random files. That would be consistent with
allocating space for a file without writing to it which on a non-DRAT drive
could cause byte-for-byte to fail.


"Triplehammer" wrote in message news:12428@public.image...

I used findlbaf as soon as I could after each failed bfb validation through
several attempts. Each time it was either a different random file or files,
or "Unable to determine which file uses LBA (number)". During my attempts,
I had a string of four successful backups that passed bfb validation, but
now it's back to failing bfb every time.

TeraByte Support
 
Posts: 2275
Joined: Thu May 05, 2011 3:37 pm

Re: Validate Byte-for-Byte fails under Win10 but not Win7

Postby Triplehammer » Thu Sep 01, 2016 4:34 pm

I'll admit there was two that were interesting.

#1:
C:\Windows\System32\winevt\Logs\Security.evtx
Now, when I actually go and open it, it's a logfile, and Event Viewer opens up right to it, under Saved Logs; the source is "Microsoft Windows security auditing". The IFW.log shows that the backup that failed when it attempted to use that LBA started that day at 8:10:17 PM and bfb failed at 8:31:30 PM. Security.evtx shows entries ending at 8:12:35 PM and resuming at 8:31:48 PM, just 18 seconds after IFW stopped. That raises my eyebrow.

Edit: Hey, the backup starts at 8:10:17 PM and Security.evtx has two entries at 8:12:35, during the backup. Opening those two entries show that #1, a WIndows service successfully logged on, and #2, special privileges were assigned to the new logon. The IFW.log shows that all the backup startup stuff was done by 8:10:30 PM. I don't know how to read Windows Event log entries well enough to understand what happened there, but I will post them in my next post if you want me to - I've saved them to a text file.

#2:
C:\ProgramData\Microsoft\Windows Defender\Network Inspection System\Support\NisLog.txt
When I opened this log file, it has entries on 08/31/16-21:20:35 (9:20:35 PM) and 08/31/16-21:35:33 (9:35:33 PM), while the IFW.log showed I did a backup that started that day at 9:21:24 PM for which bfb failed at 9:25:25 PM. So, not very close to the next NisLog.txt entry, which happened 10 minutes later.

Edit: Security.evtx has entries at 9:20:41 PM and 9:38:35 PM, so it did not write during this backup attempt.

#3:
Four help text files for a game that I haven't played in a long time.

All the rest were "Unable to determine which file uses" that LBA.
Triplehammer
 
Posts: 17
Joined: Sat Aug 13, 2016 4:15 pm

Re: Validate Byte-for-Byte fails under Win10 but not Win7

Postby TeraByte Support » Thu Sep 01, 2016 8:03 pm

Your best bet if you want to find out what it is, is the new drive. Those
logs could have parts preallocated in trimmed space.


"Triplehammer" wrote in message news:12443@public.image...

I'll admit there was two that were interesting.


TeraByte Support
 
Posts: 2275
Joined: Thu May 05, 2011 3:37 pm

Previous

Return to Image for DOS/Linux/Windows