IFL copy/validate display oddities

User discussion and information resource forum for Image products.
Post Reply
EdBrady
Posts: 15
Joined: Sat Dec 08, 2012 7:33 pm

IFL copy/validate display oddities

Post by EdBrady »

I recently used IFL (GUI) v2.77 to copy data from one drive to another. I used the validate byte-for-byte option. The operation was successful, but the progress display was way off. The bottom progesss bar moved much too fast, and reached 100% about halfway through the validate operation. From there on, the bytes and time left showed very large numbers. I did this with three separate partitions, and it was the same each time. Fortunately, the process actually worked perfectly.
TeraByte Support
Posts: 3616
Joined: Thu May 05, 2011 10:37 pm

Re: IFL copy/validate display oddities

Post by TeraByte Support »

is there a fat32 partition in there - it was probably off on the backup too.
Basically sometimes the freespace is misreported in the FAT32 structure
which causes issues with progress as the real usage is found during the
backup. chkdsk /f (scandisk) would fix it up (for the next backup).

"EdBrady" wrote in message news:4010@public.image...

I recently used IFL (GUI) v2.77 to copy data from one drive to another. I
used the validate byte-for-byte option. The operation was successful, but
the progress display was way off. The bottom progesss bar moved much too
fast, and reached 100% about halfway through the validate operation. From
there on, the bytes and time left showed very large numbers. I did this
with three separate partitions, and it was the same each time. Fortunately,
the process actually worked perfectly.

EdBrady
Posts: 15
Joined: Sat Dec 08, 2012 7:33 pm

Re: IFL copy/validate display oddities

Post by EdBrady »

TeraByte Support wrote:
> is there a fat32 partition in there - it was probably off on the backup too.
> Basically sometimes the freespace is misreported in the FAT32 structure
> which causes issues with progress as the real usage is found during the
> backup. chkdsk /f (scandisk) would fix it up (for the next backup).

No FAT32 -- all partitions are NTFS.
Post Reply