TeraByte Unlimited

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
--
Cheers,

DrT

** Stress - the condition brought about by having to
** resist the temptation to beat the living daylights
** out of someone who richly deserves it.

Sorry to post so soon after the OP. But my first backup today worked
okay, so I tried another which has just failed.

The first one was an incremental based on the last backup file. The
one that failed was a differential/incremental based on the first
(full) backup.

Just running a full backup now. I will only post the results if
somebody requests it to avoid clagging up this thread.
--
Cheers,

DrT

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

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
--
Cheers,

DrT

** Stress - the condition brought about by having to
** resist the temptation to beat the living daylights
** out of someone who richly deserves it.

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

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

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

I noticed in the previous posts several people mentioned running chkdsk on their drives. I have no idea how large those drives are, but be aware that chkdsk doesn't properly recognize partitions larger than 2.2TB.

If you run chkdsk with an option that writes to your drive (i.e. chkdsk/f) it can REALLY screw up those partitions. Chkdsk without parameters SHOULD be okay (since without parameters it's supposed to be read-only), but try it AT YOUR OWN RISK. Before I knew about this problem, I tried chkdsk without parameters on a newly formatted 4TB drive and saw weird summary stats, which got me investigating the issue.

As an example, I found one tale of doom about a defragging program that seemed to work fine on a large HDD, but when it finished, the user rebooted the computer and (the defrag program then automatically?) ran chkdsk (I assume in some write-mode) and it looks like that chkdsk run caused the user to lose nearly 2TB of files. Here's the link for that post: sevenforums dot com slash hardware-devices slash 337459-chkdsk-deleted-2tb-stuff dot html

If you do a web search for chkdsk 2.2TB you can find other warnings about this issue.

Anyway, since a lot of us here are long-term computer users from the DOS days, we often trust our old utilities more than the newer ones. Here is one instance were the old is now dangerous to use!

Maybe a warning about this problem should be posted in the announcement section of the forum?

if your OS doesn't support it (driver update needed) or running an old
version, perhaps, but chkdsk as part of windows that supports large drives
I've used with an 8 TiB file systems without issue.

I know some 3rd party defrag utilities corrupt files > 2G on FAT32 file
systems, but that was years ago.

"Muad'Dib" wrote in message news:[email protected]...

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

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