TeraByte Unlimited

I've been using IFW x64 2.99-00 with a removable drive.
I recently encrypted the removable drive with Bitlocker.
Now IFW gets 3% into writing the image, and fails with "Unable to write data to file!"
Nothing has changed except for Bitlocker on the image storage drive.

I tried IFW with both VSS and PHYlock, and get the same failure.

timg11,

Was BitLocker on the removable drive unlocked before you started IFW?

Yes it was unlocked when I started IFW, and it was still unlocked after IFW gave the error.

Is this a USB drive? NTFS/FAT32?

Is it always failing at the same point? Is it any backup or just a specific drive/partition?

Are any other images on the drive already? Do they validate successfully?

What version of Windows? Is it the newer/current version of BitLocker (Windows 10, 1511 update)?

TeraByte Support(PP) wrote:
> Is this a USB drive? Yes - Transcend Storejet : http://www.newegg.com/Product/Product.a ... 4RE4670749

NTFS/FAT32? NTFS
>
> Is it always failing at the same point? Is it any backup or just a specific
> drive/partition?

I ran the backup 3 times. It failed on the initial backup (not verify) at the 3% mark each time.
>
> Are any other images on the drive already? Do they validate successfully?

I used the same physical drive with IFW before applying Bitlocker, and the backups completed and validated successfully

>
> What version of Windows? Is it the newer/current version of BitLocker
> (Windows 10, 1511 update)?

Windows 10, x64, 1511 (build 10586.0)

Regarding validating images already on the drive, with the drive unlocked will IFW successfully validate them? This would just be a test to know if it's able to read correctly from the unlocked drive.

Also, when you encrypted the drive did you use the older BitLocker encryption or the newer version? The newer version won't be able to be used when the drive is connected to previous versions of Windows.

Maybe I'm just adding confusion here, but it says above: "Windows 10, x64, 1511 (build 10586.0)".

I'm at "Version 1511 (OS Build 10586.494)".

How does one manage to stay at Build 10586.0, I wonder.

TeraByte Support(PP) wrote:
> Regarding validating images already on the drive, with the drive unlocked
> will IFW successfully validate them? This would just be a test to know if
> it's able to read correctly from the unlocked drive.
>
Mixed results on this one. I validated an image I made 2 weeks ago. First time, the validation failed at 60% with "unable to read from drive". I immediately repeated the validation, and it succeeded. Maybe the drive is starting to fail, and it is just coincidence that I applied Bitlocker?

> Also, when you encrypted the drive did you use the older BitLocker
> encryption or the newer version? The newer version won't be able to be used
> when the drive is connected to previous versions of Windows.

Windows 10 did not offer any options for version, or if it did, they were not apparent and I missed it. I'm not concerned about compatibility with previous version of Windows, though.


Bob Coleman wrote:
> How does one manage to stay at Build 10586.0, I wonder.

I searched for how to determine the build number. I used "WINVER" from the command line. It pops up a dialog that says 10586.0.

Download and run Defraggler. It will show if the drive has bad sectors
w/o needing to actually defrag. Just check Health.

Mary

On 7/18/2016 9:52 AM, timg11 wrote:
> TeraByte Support(PP) wrote:
>> Regarding validating images already on the drive, with the drive unlocked
>> will IFW successfully validate them? This would just be a test to know if
>> it's able to read correctly from the unlocked drive.
>>
> Mixed results on this one. I validated an image I made 2 weeks ago. First time, the validation failed at 60% with "unable to read from drive". I immediately repeated the validation, and it succeeded. Maybe the drive is starting to fail, and it is just coincidence that I applied Bitlocker?
>
>> Also, when you encrypted the drive did you use the older BitLocker
>> encryption or the newer version? The newer version won't be able to be used
>> when the drive is connected to previous versions of Windows.
>
> Windows 10 did not offer any options for version, or if it did, they were not apparent and I missed it. I'm not concerned about compatibility with previous version of Windows, though.
>
>
> Bob Coleman wrote:
>> How does one manage to stay at Build 10586.0, I wonder.
>
> I searched for how to determine the build number. I used "WINVER" from the command line. It pops up a dialog that says 10586.0.
>
>

Also to see version in Windows 10 you can go to:
Start
Settings
System
on left click on About.

Ed.

"timg11" wrote in message news:11810@public.image...

TeraByte Support(PP) wrote:
> Regarding validating images already on the drive, with the drive unlocked
> will IFW successfully validate them? This would just be a test to know if
> it's able to read correctly from the unlocked drive.
>
Mixed results on this one. I validated an image I made 2 weeks ago. First
time, the validation failed at 60% with "unable to read from drive". I
immediately repeated the validation, and it succeeded. Maybe the drive is
starting to fail, and it is just coincidence that I applied Bitlocker?

> Also, when you encrypted the drive did you use the older BitLocker
> encryption or the newer version? The newer version won't be able to be
> used
> when the drive is connected to previous versions of Windows.

Windows 10 did not offer any options for version, or if it did, they were
not apparent and I missed it. I'm not concerned about compatibility with
previous version of Windows, though.


Bob Coleman wrote:
> How does one manage to stay at Build 10586.0, I wonder.

I searched for how to determine the build number. I used "WINVER" from the
command line. It pops up a dialog that says 10586.0.