TeraByte Unlimited

Hi!

I'm running IfW from a script to make backup images, and it sends me a log. Recently, it sent me a log which looks like this:

[5/10/2020 9:24:04 AM] /b /uy /um /d:w0@0x45C /f:I:\Backups\Images\BackupF10 /comp:10
[5/10/2020 9:24:10 AM] Image for Windows 2.87 (GUI)
[5/10/2020 9:24:10 AM] Starting ...
imagew64.exe /b /uy /um /d:w0@0x45C /f:"I:\Backups\Images\BackupF10" /comp:10
[5/10/2020 9:24:10 AM] Deleting I:\Backups\Images\BackupF10.TBI
[5/10/2020 9:24:12 AM] PHYLock is waiting for drive writing to stop ...
[5/10/2020 9:24:17 AM] PHYLock using drive F:
[5/10/2020 9:24:17 AM] PHYLock Started
[5/10/2020 9:24:17 AM] PHYLock Using Disk
[5/10/2020 9:24:17 AM] PHYLock version 11
[5/10/2020 9:24:18 AM] Backup: Drive 0 (F:) Data Volume (45C) 112243 MiB HPFS/NTFS
[5/10/2020 9:24:18 AM] To: I:\Backups\Images\BackupF10.TBI
[5/10/2020 9:25:14 AM] A hard drive error occurred while reading 128 sectors from LBA 518175358.
Ignore all errors and continue?
[5/10/2020 10:26:40 AM] INFO: Total Sectors:229874085 Total Allocated:124364568
[5/10/2020 10:26:40 AM] INFO: 124364568 Sector(s) backed up
[5/10/2020 10:26:52 AM] Bad Sectors - Reading:3 Writing:0 (1)
[5/10/2020 10:26:53 AM] Operation Completed with Error Code 0
[5/10/2020 10:26:53 AM] Stop

As you guys can see, there's an error at 9:25:14 AM. I understand from the knowledge base that this error means that IfW found a defective sector or sectors.

1. Can I just ignore this, as long as there's plenty of space on my drive?
2. Is this a sign that my drive is dying of old age, and I'll shortly have a lot of problems with it?

Thanks.
M.

You can run the drive manufactures utility or something like spinrite to
check the drive and remap bad sectors (if not being done automatically)
or if relocation table full, I wouldn't mess with it, especially if
older drive, I'd just get a new one to prevent all the programs that can
happen when starts going bad vs just dying.

On 5/13/2020 3:27 AM, Marshmallow wrote:
> [5/10/2020 10:26:52 AM] Bad Sectors - Reading:3 Writing:0 (1)
>
> As you guys can see, there's an error at 9:25:14 AM. I understand from the knowledge base that this error means that IfW found a defective sector or sectors.
>
> 1. Can I just ignore this, as long as there's plenty of space on my drive?
> 2. Is this a sign that my drive is dying of old age, and I'll shortly have a lot of problems with it?
>
> Thanks.
> M.
>
>

Does it mean that the error are on the drive that was being copied FROM?

Thanks again.
M.

Marshmallow wrote:
> Does it mean that the error are on the drive that was being copied FROM?
>
> Thanks again.
> M.

I don't know that I have the definitive answer here, but since it says:

Bad Sectors -
READIMG:3
WRITING:0

I would certainly think so (reformatting is mine).