TeraByte Unlimited

I have changed USB port. The cable is one of the old type with the
square input to the device. I'm still looking for one. Haven't run the
WD scan utility yet. I'll need some time: it's a 2TB drive.

On 8/24/2016 10:10 AM, Walter Blanchard wrote:
> Thanks. I'll give it a try. It's a WD My Disk (old) Will change cabling
> first as well as USB port on box.
>
> On 8/23/2016 11:47 AM, TeraByte Support wrote:
>> unable to read and freeze is the hard drive error and won't continue until
>> the drive recovers which can take an extended period of time. It will tell
>> you the number of bad sectors found at the end. You need to run the drive
>> manufactures scan utility on the drive (not chkdsk), but could be in the
>> electronics or cable as well.
>>
>>
>> "Walter Blanchard" wrote in message news:[email protected]...
>>
>> I have gotten the same error several times during the Validation
>> process. It varies only in the LBA number (last time 99408112). I have
>> tried both Ignore and cancel. Each choice freezes the computer. One
>> time, so badly that I had to restore an image. I usually have two
>> images of the same OS, each on a separate external MBA drive which is
>> off unless I'm making images.
>> Computer: ASUS Crosshair V Formula Z. BIOS is Windows UEFI. The internal
>> drives are all GPT. This problem only started with IFW v. 3.01.
>>
>> I have also run CHKDSK which shows no errors.
>>
>

--
Walter B

Gave it a run, Mary. Showed OK, just some fragmentation, but on a 2TB
drive, I ran a Quick Defrag. Haven't tried putting an image on it yet.

On 8/24/2016 10:11 AM, Walter Blanchard wrote:
> Thanks, Mary. I'll take a look.
>
> On 8/23/2016 10:56 AM, MJNelson wrote:
>> Try downloading & installing Defraggler.
>>
>> Then have it look at the drive. It identified a USB hard drive that was
>> ready to fail and may spot something on yours.
>> Mary
>>
>> On 8/23/2016 7:54 AM, Walter Blanchard wrote:
>>> On 8/22/2016 11:29 PM, TeraByte Support wrote:
>>>> A hard drive error occurred while reading 128 sectors from LBA 1194541760.
>>>> Ignore all errors and continue?
>>>>
>>>> You canceled so now you get:
>>>>
>>>>
>>>> Operation Completed with Error Code 98
>>>> Which is:
>>>> Unable to read from device
>>>>
>>>>
>>>>
>>>> "DrTeeth" wrote in message news:[email protected]...
>>>>
>>>> Hi,
>>>>
>>>> Below is attached an entry from IfW.log. What does the error code
>>>> signify?
>>>> ------------------------------------excerpt begins-------------------
>>>> [21/08/2016 21:54:29] Image for Windows 2.99-00
>>>> [21/08/2016 21:54:29] Starting ...
>>>> imagew.exe /b /d:w0@0x4 /f:"E:\Win 7 -
>>>> Kim's\Backup-w0-0x4-$~YYYY$-$~MM$-$~DD$-$~HHMM$" /v /hash
>>>> [21/08/2016 21:54:30] PHYLock is waiting for drive writing to stop ...
>>>> [21/08/2016 21:54:35] PHYLock using drive C:
>>>> [21/08/2016 21:54:35] PHYLock Started
>>>> [21/08/2016 21:54:35] PHYLock Using Disk
>>>> [21/08/2016 21:54:35] PHYLock version 12
>>>> [21/08/2016 21:54:35] Backup: Drive 0 (C:) Win7 - Kim's Partition (04)
>>>> 700861 MiB NTFS
>>>> [21/08/2016 21:54:35] To: E:\Win 7 -
>>>> Kim's\Backup-w0-0x4-2016-08-21-2154.TBI
>>>> [21/08/2016 22:17:12] A hard drive error occurred while reading 128
>>>> sectors from LBA 1194541760.
>>>> Ignore all errors and continue?
>>>> [21/08/2016 22:36:18] INFO: Total Sectors:1435363328 Total
>>>> Allocated:231536944
>>>> [21/08/2016 22:36:18] Deleting incomplete or failed backup.
>>>> [21/08/2016 22:36:18] Deleting E:\Win 7 -
>>>> Kim's\Backup-w0-0x4-2016-08-21-2154.#0
>>>> [21/08/2016 22:36:18] Deleting E:\Win 7 -
>>>> Kim's\Backup-w0-0x4-2016-08-21-2154.TBI
>>>> [21/08/2016 22:36:19] Operation Completed with Error Code 98
>>>> [21/08/2016 22:36:19] Unable to read from device
>>>> [21/08/2016 22:36:20] Stop
>>>> -----------------------------------ends-------------------------
>>>>
>>>> I ran chkdsk /f which did not fix things. I then ran chkdsk /r on both
>>>> the partition to be backed up and the disk to which the backup was to
>>>> be written and all seems well.
>>>>
>>>> Thanks
>>>>
>>> I have gotten the same error several times during the Validation
>>> process. It varies only in the LBA number (last time 99408112). I have
>>> tried both Ignore and cancel. Each choice freezes the computer. One
>>> time, so badly that I had to restore an image. I usually have two
>>> images of the same OS, each on a separate external MBA drive which is
>>> off unless I'm making images.
>>> Computer: ASUS Crosshair V Formula Z. BIOS is Windows UEFI. The internal
>>> drives are all GPT. This problem only started with IFW v. 3.01.
>>>
>>> I have also run CHKDSK which shows no errors.
>>>
>>
>>
>

--
Walter B

This is the fix.

The standard chkdsk /f did not fix the error. I mistakenly wrote in my
OP that I ran chkdsk /r on the disk/partition to be backed up.

I had NOT and running that command fixed the error and that was
confirmed by checking the chkdsk log.

The BIBM error check did not find anything wrong but a resize
operation failed.

Since running chkdsk /r all is well.
--
Cheers,

DrT

"If you want to find out what is wrong
with democracy, spend five minutes with
the average voter." - Winston Churchill

Do you wonder sometimes how to stay sane (relatively) using a computer?
Mary

On 8/25/2016 10:45 AM, DrTeeth wrote:
> This is the fix.
>
> The standard chkdsk /f did not fix the error. I mistakenly wrote in my
> OP that I ran chkdsk /r on the disk/partition to be backed up.
>
> I had NOT and running that command fixed the error and that was
> confirmed by checking the chkdsk log.
>
> The BIBM error check did not find anything wrong but a resize
> operation failed.
>
> Since running chkdsk /r all is well.
>