IFW: A hard drive error occurred while reading 128 sectors

User discussion and information resource forum for Image products.
Post Reply
bpatrice
Posts: 16
Joined: Sun Jun 30, 2019 2:38 pm

IFW: A hard drive error occurred while reading 128 sectors

Post by bpatrice »

Hello all,

Just updated to IFW 3.31 and upon verifying (validate), got this error: A hard drive error occurred while reading 128 sectors from LBA 100821936.

It's the first time since I bought your software that I get this error.

To be sure, I ran HDTune long test on the backup drive (Seagate Expansion USB3 500 gb). Also ran Seatools Long Generic, no errors.
Did a SMART check on the source (860 EVO, latest firmware, 250 gb), HDDScan and Seatools Long Generic too on it, no errors. I'm on Windows 10 Pro 1903.

What could it be? Antivirus, VSS bug, other? I also don't know which disk is responsible for the read error, not mentioned in the log...

Re-tried the backup and it completed without any errors, I'm clueless!!!

Thanks.

Complete log:
--------------------------------------------------------------------------
[06/29/2019 09:09:48 PM] Image for Windows (x64) 3.31
[06/29/2019 09:09:48 PM] Starting ...
imagew64.exe /b /d:w2 /f:"F:\Win10Pro" /v /vb
[06/29/2019 09:09:48 PM] Deleting F:\Win10Pro.TBI
[06/29/2019 09:09:49 PM] Attempting to Create VSS Snapshot...
[06/29/2019 09:09:49 PM] Added \\?\Volume{98258a00-fb1c-11e8-b6f6-f8b156c54413} to snapshot.
[06/29/2019 09:09:49 PM] Added \\?\Volume{aa717264-feb1-4ca3-b97a-6615608403ad} to snapshot.
[06/29/2019 09:09:49 PM] Added \\?\Volume{98258a03-fb1c-11e8-b6f6-f8b156c54413} (C:) to snapshot.
[06/29/2019 09:09:49 PM] Added \\?\Volume{def02c30-cf17-4ec6-bab1-7c732edae2c1} to snapshot.
[06/29/2019 09:09:52 PM] VSS Snapshot Created Successfully.
[06/29/2019 09:09:52 PM] Warning: Data excluded from files based on list in Registry.
[SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToBackup]

\ProgramData\Microsoft\Network\Downloader\* >

\WINDOWS\system32\LogFiles\WMI\RtBackup\*.*

\Users\Patrice\index.dat >

\WINDOWS\Minidump\* >

\WINDOWS\memory.dmp

\Pagefile.sys

\System Volume Information\MountPointManagerRemoteDatabase

\WINDOWS\netlogon.chg

\hiberfil.sys

\System Volume Information\Heat\*.* >

\Users\Patrice\AppData\Local\Temp\* >

\System Volume Information\*{3808876B-C176-4e48-B7AE-04046E6CC752} >

\System Volume Information\*.{7cc467ef-6865-4831-853f-2a4817fd1bca}ALT

\System Volume Information\*.{7cc467ef-6865-4831-853f-2a4817fd1bca}DB

\ProgramData\Microsoft\Windows\WER\* >

\WINDOWS\softwaredistribution\*.* >

\System Volume Information\FVE2.{e40ad34d-dae9-4bc7-95bd-b16218c10f72}.*

\System Volume Information\FVE2.{c9ca54a3-6983-46b7-8684-a7e5e23499e3}

\System Volume Information\FVE2.{24e6f0ae-6a00-4f73-984b-75ce9942852d}

\System Volume Information\FVE2.{9ef82dfa-1239-4a30-83e6-3b3e9b8fed08}

\System Volume Information\FVE2.{aff97bac-a69b-45da-aba1-2cfbce434750}.*

\System Volume Information\FVE2.{9ef82dfa-1239-4a30-83e6-3b3e9b8fed08}.*

\System Volume Information\FVE.{e40ad34d-dae9-4bc7-95bd-b16218c10f72}.*

\System Volume Information\FVE.{c9ca54a3-6983-46b7-8684-a7e5e23499e3}

\System Volume Information\FVE.{9ef82dfa-1239-4a30-83e6-3b3e9b8fed08}

\Windows\system32\MSDtc\MSDTC.LOG

\Windows\system32\MSDtc\trace\dtctrace.log

[VSS END]

[SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToSnapshot]

\Users\All Users\AppData\Local\Packages\Microsoft.Office.Desktop_8wekyb3d8bbwe\LocalCache\Local\Microsoft\Outlook\*.oab >

\Users\Default\AppData\Local\Packages\Microsoft.Office.Desktop_8wekyb3d8bbwe\LocalCache\Local\Microsoft\Outlook\*.oab >

\Users\Default User\AppData\Local\Packages\Microsoft.Office.Desktop_8wekyb3d8bbwe\LocalCache\Local\Microsoft\Outlook\*.oab >

\Users\Patrice\AppData\Local\Packages\Microsoft.Office.Desktop_8wekyb3d8bbwe\LocalCache\Local\Microsoft\Outlook\*.oab >

\Users\Public\AppData\Local\Packages\Microsoft.Office.Desktop_8wekyb3d8bbwe\LocalCache\Local\Microsoft\Outlook\*.oab >

\Users\All Users\AppData\Local\Packages\Microsoft.Office.Desktop_8wekyb3d8bbwe\LocalCache\Local\Microsoft\Outlook\*.ost >

\Users\Default\AppData\Local\Packages\Microsoft.Office.Desktop_8wekyb3d8bbwe\LocalCache\Local\Microsoft\Outlook\*.ost >

\Users\Default User\AppData\Local\Packages\Microsoft.Office.Desktop_8wekyb3d8bbwe\LocalCache\Local\Microsoft\Outlook\*.ost >

\Users\Patrice\AppData\Local\Packages\Microsoft.Office.Desktop_8wekyb3d8bbwe\LocalCache\Local\Microsoft\Outlook\*.ost >

\Users\Public\AppData\Local\Packages\Microsoft.Office.Desktop_8wekyb3d8bbwe\LocalCache\Local\Microsoft\Outlook\*.ost >

\Users\All Users\AppData\Local\Microsoft\Outlook\*.ost

\Users\Default\AppData\Local\Microsoft\Outlook\*.ost

\Users\Default User\AppData\Local\Microsoft\Outlook\*.ost

\Users\Patrice\AppData\Local\Microsoft\Outlook\*.ost

\Users\Public\AppData\Local\Microsoft\Outlook\*.ost

\System Volume Information\Heat\*.* >

\WINDOWS\softwaredistribution\*.* >

\System Volume Information\FVE.{9ef82dfa-1239-4a30-83e6-3b3e9b8fed08}

\System Volume Information\FVE2.{9ef82dfa-1239-4a30-83e6-3b3e9b8fed08}

\System Volume Information\FVE2.{9ef82dfa-1239-4a30-83e6-3b3e9b8fed08}.*

[VSS END]

[06/29/2019 09:09:55 PM] Backup: Drive 2 Basic data partition Partition (01) 455 MiB NTFS
[06/29/2019 09:09:55 PM] To: F:\Win10Pro.TBI
[06/29/2019 09:09:55 PM] INFO: Total Sectors:931848 Total Allocated:24944
[06/29/2019 09:09:55 PM] INFO: 24944 Sector(s) backed up
[06/29/2019 09:09:55 PM] Backup: Drive 2 EFI system partition Partition (02) 94 MiB FAT-32
[06/29/2019 09:09:55 PM] To: F:\Win10Pro.TBI
[06/29/2019 09:09:56 PM] INFO: Total Sectors:192520 Total Allocated:105672
[06/29/2019 09:09:56 PM] INFO: 105672 Sector(s) backed up
[06/29/2019 09:09:56 PM] Backup: Drive 2 Microsoft reserved parti Partition (03) 16 MiB GPT Entry
[06/29/2019 09:09:56 PM] To: F:\Win10Pro.TBI
[06/29/2019 09:09:56 PM] INFO: Total Sectors:32776 Total Allocated:32776
[06/29/2019 09:09:56 PM] INFO: 32776 Sector(s) backed up
[06/29/2019 09:09:56 PM] Backup: Drive 2 (C:) BOOTCAMP Partition (04) 213560 MiB NTFS
[06/29/2019 09:09:56 PM] To: F:\Win10Pro.TBI
[06/29/2019 09:14:46 PM] A hard drive error occurred while reading 128 sectors from LBA 100821936.
Do not abort if you want to ignore these errors.

Do you want to abort the operation?
[06/29/2019 10:26:31 PM] INFO: Total Sectors:437371438 Total Allocated:68022488
[06/29/2019 10:26:32 PM] Deleting incomplete or failed backup.
[06/29/2019 10:26:32 PM] Deleting F:\Win10Pro.TBI
[06/29/2019 10:26:32 PM] Time Elapsed: 0:01:16:44
[06/29/2019 10:26:32 PM] Operation Completed with Error Code 98
[06/29/2019 10:26:32 PM] Unable to read from device
[06/29/2019 10:26:33 PM] Stop
--------------------------------------------------------------------------
bpatrice
Posts: 16
Joined: Sun Jun 30, 2019 2:38 pm

Re: IFW: A hard drive error occurred while reading 128 secto

Post by bpatrice »

Ok, there are 5 partitions on the SSD:

1- Recovery
2- EFI
3- Reserved
4- Main (Bootcamp)... no, I'm not on a Mac, it's just the name I gave to my Win system!
5- Recovery

Why, two Recovery, I don't know???

Maybe related to the number of partitions?
TeraByte Support
Posts: 3598
Joined: Thu May 05, 2011 10:37 pm

Re: A hard drive error occurred while reading 128 sectors

Post by TeraByte Support »

What does the system event log say at that same time?


"bpatrice" wrote in message news:17327@public.image...

Hello all,

Just updated to IFW 3.31 and upon verifying (validate), got this error: A
hard drive error occurred while reading 128 sectors from LBA 100821936.

It's the first time since I bought your software that I get this error.

To be sure, I ran HDTune long test on the backup drive (Seagate Expansion
USB3 500 gb). Also ran Seatools Long Generic, no errors.
Did a SMART check on the source (860 EVO, latest firmware, 250 gb), HDDScan
and Seatools Long Generic too on it, no errors. I'm on Windows 10 Pro 1903.

What could it be? Antivirus, VSS bug, other? I also don't know which disk is
responsible for the read error, not mentioned in the log...

Re-tried the backup and it completed without any errors, I'm clueless!!!

Thanks.

Complete log:
--------------------------------------------------------------------------
[06/29/2019 09:09:48 PM] Image for Windows (x64) 3.31
[06/29/2019 09:09:48 PM] Starting ...
imagew64.exe /b /d:w2 /f:"F:\Win10Pro" /v /vb
[06/29/2019 09:09:48 PM] Deleting F:\Win10Pro.TBI
[06/29/2019 09:09:49 PM] Attempting to Create VSS Snapshot...
[06/29/2019 09:09:49 PM] Added
\\?\Volume{98258a00-fb1c-11e8-b6f6-f8b156c54413} to snapshot.
[06/29/2019 09:09:49 PM] Added
\\?\Volume{aa717264-feb1-4ca3-b97a-6615608403ad} to snapshot.
[06/29/2019 09:09:49 PM] Added
\\?\Volume{98258a03-fb1c-11e8-b6f6-f8b156c54413} (C:) to snapshot.
[06/29/2019 09:09:49 PM] Added
\\?\Volume{def02c30-cf17-4ec6-bab1-7c732edae2c1} to snapshot.
[06/29/2019 09:09:52 PM] VSS Snapshot Created Successfully.
[06/29/2019 09:09:52 PM] Warning: Data excluded from files based on list in
Registry.

[06/29/2019 09:09:55 PM] Backup: Drive 2 Basic data partition Partition (01)
455 MiB NTFS
[06/29/2019 09:09:55 PM] To: F:\Win10Pro.TBI
[06/29/2019 09:09:55 PM] INFO: Total Sectors:931848 Total Allocated:24944
[06/29/2019 09:09:55 PM] INFO: 24944 Sector(s) backed up
[06/29/2019 09:09:55 PM] Backup: Drive 2 EFI system partition Partition (02)
94 MiB FAT-32
[06/29/2019 09:09:55 PM] To: F:\Win10Pro.TBI
[06/29/2019 09:09:56 PM] INFO: Total Sectors:192520 Total Allocated:105672
[06/29/2019 09:09:56 PM] INFO: 105672 Sector(s) backed up
[06/29/2019 09:09:56 PM] Backup: Drive 2 Microsoft reserved parti Partition
(03) 16 MiB GPT Entry
[06/29/2019 09:09:56 PM] To: F:\Win10Pro.TBI
[06/29/2019 09:09:56 PM] INFO: Total Sectors:32776 Total Allocated:32776
[06/29/2019 09:09:56 PM] INFO: 32776 Sector(s) backed up
[06/29/2019 09:09:56 PM] Backup: Drive 2 (C:) BOOTCAMP Partition (04) 213560
MiB NTFS
[06/29/2019 09:09:56 PM] To: F:\Win10Pro.TBI
[06/29/2019 09:14:46 PM] A hard drive error occurred while reading 128
sectors from LBA 100821936.
Do not abort if you want to ignore these errors.

Do you want to abort the operation?
[06/29/2019 10:26:31 PM] INFO: Total Sectors:437371438 Total
Allocated:68022488
[06/29/2019 10:26:32 PM] Deleting incomplete or failed backup.
[06/29/2019 10:26:32 PM] Deleting F:\Win10Pro.TBI
[06/29/2019 10:26:32 PM] Time Elapsed: 0:01:16:44
[06/29/2019 10:26:32 PM] Operation Completed with Error Code 98
[06/29/2019 10:26:32 PM] Unable to read from device
[06/29/2019 10:26:33 PM] Stop
--------------------------------------------------------------------------

bpatrice
Posts: 16
Joined: Sun Jun 30, 2019 2:38 pm

Re: IFW: A hard drive error occurred while reading 128 secto

Post by bpatrice »

First, at 21:14:

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Image for Windows" />
<EventID Qualifiers="32768">258</EventID>
<Level>3</Level>
<Task>1</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2019-06-30T01:14:46.523393500Z" />
<EventRecordID>1600</EventRecordID>
<Channel>Application</Channel>
<Computer>DESKTOP-Q5VEQ2U</Computer>
<Security />
</System>
- <EventData>
<Data>A hard drive error occurred while reading 128 sectors from LBA 100821936. Do not abort if you want to ignore these errors. Do you want to abort the operation?</Data>
</EventData>
</Event>

Then, at 22:26
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Image for Windows" />
<EventID Qualifiers="49152">259</EventID>
<Level>2</Level>
<Task>1</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2019-06-30T02:26:32.627963900Z" />
<EventRecordID>1624</EventRecordID>
<Channel>Application</Channel>
<Computer>DESKTOP-Q5VEQ2U</Computer>
<Security />
</System>
- <EventData>
<Data>Unable to read from device</Data>
</EventData>
</Event>

and

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Image for Windows" />
<EventID Qualifiers="49152">259</EventID>
<Level>2</Level>
<Task>1</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2019-06-30T02:26:32.627963900Z" />
<EventRecordID>1623</EventRecordID>
<Channel>Application</Channel>
<Computer>DESKTOP-Q5VEQ2U</Computer>
<Security />
</System>
- <EventData>
<Data>Operation Completed with Error Code 98</Data>
</EventData>
</Event>

But at 21:14, there was an installation:

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Windows Error Reporting" />
<EventID Qualifiers="0">1001</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2019-06-30T01:14:13.818924400Z" />
<EventRecordID>1599</EventRecordID>
<Channel>Application</Channel>
<Computer>DESKTOP-Q5VEQ2U</Computer>
<Security />
</System>
- <EventData>
<Data>2209540145565950801</Data>
<Data>5</Data>
<Data>CbsPackageServicingFailure2</Data>
<Data>Non disponible</Data>
<Data>0</Data>
<Data>10.0.18362.200</Data>
<Data>Microsoft-Windows-LanguageFeatures-Basic-en-us-Package</Data>
<Data>10.0.18362.1</Data>
<Data>amd64</Data>
<Data>unknown</Data>
<Data>800f0825</Data>
<Data>CBS Other</Data>
<Data>Installed</Data>
<Data>Installed</Data>
<Data>FodHelper(LanguageFeaturesOnDemand)</Data>
<Data>\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE34.tmp.WERInternalMetadata.xml</Data>
<Data>\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Critical_10.0.18362.200_897445ff56d33cacb337e5e5916197ce344899_00000000_a69063e9-33b1-4466-acf4-875d706391ea</Data>
<Data />
<Data>0</Data>
<Data>a69063e9-33b1-4466-acf4-875d706391ea</Data>
<Data>268435456</Data>
<Data>2d9cfff7434e025d1ea9dd0e456c6351</Data>
<Data>0</Data>
</EventData>
</Event>

also:

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
<EventID Qualifiers="16384">7040</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2019-06-30T01:14:08.709187600Z" />
<EventRecordID>5704</EventRecordID>
<Correlation />
<Execution ProcessID="772" ThreadID="924" />
<Channel>System</Channel>
<Computer>DESKTOP-Q5VEQ2U</Computer>
<Security UserID="S-1-5-18" />
</System>
- <EventData>
<Data Name="param1">Programme d’installation pour les modules Windows</Data>
<Data Name="param2">Démarrage automatique</Data>
<Data Name="param3">Démarrage à la demande</Data>
<Data Name="param4">TrustedInstaller</Data>
</EventData>
</Event>

and

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Microsoft-Windows-WindowsUpdateClient" Guid="{945a8954-c147-4acd-923f-40c45405a658}" />
<EventID>19</EventID>
<Version>1</Version>
<Level>4</Level>
<Task>1</Task>
<Opcode>13</Opcode>
<Keywords>0x8000000000000018</Keywords>
<TimeCreated SystemTime="2019-06-30T01:14:26.586716300Z" />
<EventRecordID>5713</EventRecordID>
<Correlation />
<Execution ProcessID="996" ThreadID="12656" />
<Channel>System</Channel>
<Computer>DESKTOP-Q5VEQ2U</Computer>
<Security UserID="S-1-5-18" />
</System>
- <EventData>
<Data Name="updateTitle">9WZDNCRFJBD8-Microsoft.XboxApp</Data>
<Data Name="updateGuid">{de648363-c4e9-42e9-9d6b-2a94f2113aed}</Data>
<Data Name="updateRevisionNumber">1</Data>
<Data Name="serviceGuid">{855e8a7c-ecb4-4ca3-b045-1dfa50104289}</Data>
</EventData>
</Event>

Could it be the unnatended installation created havoc in VSS?
TeraByte Support
Posts: 3598
Joined: Thu May 05, 2011 10:37 pm

Re: A hard drive error occurred while reading 128 secto

Post by TeraByte Support »

You'd want to look in the "system" event log under "disk".

There are some things like encryption software that prevent reading the area
it's in.

It's possible the update caused vss to fail.


"bpatrice" wrote in message news:17330@public.image...

First, at 21:14:

-
-

258
3
1
0x80000000000000

1600
Application
DESKTOP-Q5VEQ2U


-
A hard drive error occurred while reading 128 sectors from LBA
100821936. Do not abort if you want to ignore these errors. Do you want to
abort the operation?



bpatrice
Posts: 16
Joined: Sun Jun 30, 2019 2:38 pm

Re: IFW: A hard drive error occurred while reading 128 secto

Post by bpatrice »

I'll look into that.

Thanks for your fast support,

Patrice
bpatrice
Posts: 16
Joined: Sun Jun 30, 2019 2:38 pm

Re: IFW: A hard drive error occurred while reading 128 secto

Post by bpatrice »

It is in french but anyway: at 21:14

Snapshot of C: has been cancelled due to user limit... or something like that.
EMC_Hirf
Posts: 1
Joined: Mon Aug 05, 2019 11:31 pm

Re: IFW: A hard drive error occurred while reading 128 secto

Post by EMC_Hirf »

Yesterday, I had the same error while trying to image my Windows 10 system solid-state drive (SSD). The specific sector number that IFW flagged was different (but close to) the sector number you mentioned.

Long story short, I spent most of yesterday puttering around running CHKDSK /r (and /f), and examining the diagnostic reports of my SSD provided by the disk mfr. and by CrystalDiskInfo, both of which reported a "healthy" drive. Running CHKDSK /r (twice, at different stages of my puttering) seemed to reveal no disk errors and/or any that were present were "repaired". Still, when I re-ran IFW, it kept reporting the unreadable sector error. I've never had this happen before.

Today, I got the idea to download and install the free version of another disk imaging program and try it. It also immediately reported a disk error (corrupt MFT). I went searching this disk imaging program's web site for some help concerning the error. I eventually found a discussion on the company's product forum. From the discussion, I got the idea to try disabling my third-party anti-malware program (Malware Bytes, free edition) and re-run the other disk imaging program. Voila! It worked - the program manage to run without error and image my system SSD. Encouraged, I then tried re-running IFW with Malware Bytes disabled (by clicking on the "Quit" command after right-mouse clicking on the Malware Bytes icon in the Windows system tray). Voila! IFW ran without error and successfully imaged the Windows 10 system SSD without any errors.

So, you might check to see if your computer has any third-party anti-malware/anti-virus software running that you can shut down or disable before you run IFW.

Cheers!
Post Reply