"File system error is found. Consider checking the disk using Check Disk Utility"
Using Acronis TI 2021 with Windows 10, I was doing partition backups on disks in a Dell desktop with 2 hard drives. Backups of C: partition on Disk 0 and the Data G: partition on Disk 1 completed normally. When I tried to backup Programs H: on Disk 1 I got the error message, and Acronis paused and tried again several times before if showed that the backup had failed. I have run chkdsk /f /r on H: several times, both from the cmd prompt and at bootup, but I still get the error and backup failure. The Western Digital Dashboard utility shows normal health for the drive. How can I get a backup of H: ?
Sorry for the cross post, but I had inadvertently posted this on the 2020 forum.
The attached log is from the latest backup attempt
Cecil, thanks for the backup worker log, this is showing a VSS snapshot error at the end of the backup process:
08/05/2021 09:36:32:504 AM Pid: 23048 type=log; level=inf; message=ar#1: archive close (commit=12/12, file_size=1952841728, uuid=09b7b62ad24dfa6f84e4d9a05a169c98, user read=0MB write=3245MB) rc=0 (Success);
08/05/2021 09:36:32:520 AM Pid: 23048 type=commonerror;
value= Read error.
$func: PartitionBackuper::ReadDrive
$line Failed to read the snapshot. See VSS logs for details.
$func win_snapshot_volume::IoOp
$line CRC error.
08/05/2021 09:36:32:520 AM Pid: 23048 type=retcode; value=4095; id=1;
08/05/2021 09:36:32:520 AM Pid: 23048 >>> exit
Please download and run the Acronis VSS Doctor tool (link below) to check for issues in this area, and let the tool fix any issues it offers to do so for.
I ran VSS Doctor and have attached its report. I clicked fix issues in the Access Control section. It ran a few minutes but didn't appear to have changed anything. I did note Access Control for G:, which backed up normally, was the same as for H:, which failed. I didn't recognize a few of the devices listed as having below minimum free space, but that wasn't an issue for my actual partitions. The events section showed some block errors. Is there some other way I should run chkdsk or another utility to correct that issue? As I mentioned I did run chkdsk /f /r several times.
Cecil, the VSS Doctor report is showing several potential issues...
Free space warning:
Name: \\?\Volume{1337c60a-f167-48d3-ba5e-9b3ac66d0466}\
DeviceId: \\?\Volume{1337c60a-f167-48d3-ba5e-9b3ac66d0466}\
Size: 551 MB
Available: 76 MB
Minimum: 320 MB
IsOk: False
Description: Free space is below required minimum
IsMounted: FalseGiven the size of 551 MB this is probably a Windows Recovery partition.
Access control warnings:
Name: G:\ SystemHasAccess: False SystemSid: S-1-5-18 IsOk: False Description: "SYSTEM" account has no "Full Control" access Name: H:\ SystemHasAccess: False SystemSid: S-1-5-18 IsOk: False Description: "SYSTEM" account has no "Full Control" access Name: I:\ SystemHasAccess: False SystemSid: S-1-5-18 IsOk: False Description: "SYSTEM" account has no "Full Control" access Name: J:\ SystemHasAccess: False SystemSid: S-1-5-18 IsOk: False Description: "SYSTEM" account has no "Full Control" access
All the above refer to the same disk:
Name: 1 F: G: H: I: J:
Event log error entries:
Timestamp: 5/8/2021 9:36:32 AM Type: Error Source: disk Message: The device, \Device\Harddisk1\DR1, has a bad block. InstanceId: -1073479673 SearchLink: https://www.google.com/#newwindow=1&q=disk+event+id+3221487623 Timestamp: 5/8/2021 9:35:31 AM Type: Warning Source: disk Message: The IO operation at logical block address 0x5d7a4af1 for Disk 1 (PDO name: \Device\00000038) was retried. InstanceId: -2147221351 SearchLink: https://www.google.com/#newwindow=1&q=disk+event+id+2147745945
The above also refer to the same disk 1 for the previous error messages.
CHKDSK /F needs to be run for the whole of disk 1, all partitions or else a full disk scan by diagnostic tools provided by the disk manufacturer.
Dedicated diagnostic utilities from the disk manufacturers take the longest time to complete the checks, but provide the most accurate methods of checking whether the disk is good or needs replacement:
- Western Digital drives: Data Lifeguard Diagnostic for Windows
- Seagate disks: SeaTools for Windows
- HGST disks: HGST Windows Drive Fitness Test (WinDFT)
- Intel SSDs: Intel Memory and Storage Tool (GUI)
- Samsung drives: Samsung Magician
- ADATA drives: ADATA SSD ToolBox
- Kingston SSDs: Kingston SSD Toolbox, Kingston SSD Manager
- Transcend SSDs: Transcend SSD Scope
- Silicon Power disks: SP ToolBox
- Toshiba disks: Toshiba PC Diagnostic Tool Utility
- Crucial disks: Crucial Storage Executive
- SanDisk disks: SanDisk SSD Dashboard tool / SanDisk SSD Dashboard user guide
Thanks again. The disk is Western Digital, which has replaced the utility in your sig:
Data Lifeguard Diagnostic for Windows has been DEPRECATED and replaced with the Western Digital Dashboard utility. Data Lifeguard Diagnostic for Windows is no longer supported. Please use the Western Digital Dashboard utility available at https://support.wdc.com/downloads.aspx?lang=en&p=279
This is a Windows version of the Data LifeGuard Diagnostics. It will test WD internal and external drives. In additional, it can provide you with the model and serial of WD drives attached to the system.
I did run that utility in quick mode, which showed normal drive health. I will try again with the extended test.
So far every test I have run from Windows has shown no errors. Properties for H: shows full System access.
As I mentioned, most of the installed programs are on the partition I can't backup with the Disks and Partitions option. If a Files and Folders backup for that partition succeeds, would I be able to use that along with the backups of the other partitions (System C: & Data G:) to make a functioning restoration to a new HD?
The extended test with the Dashboard utility failed with an Error 7.
Cecil, I'm just coming into this issue.
My understanding is the following facts:
- H: is just another partition on the same physical drive as G: and others
- ATI is failing in what appears to be when dealing with VSS
- There are a number of bad block error reports in the Windows log
- Your VSS Shadow Storage Status only references drives C: and H: with H: showing 0 B used and allocated
- H: is 140 GB with 111 GB available
I am wondering if there is a hard disk problem that is manifesting itself in the VSS arena.
Have you looked at the S.M.A.R.T. data for the drive? CrystalDiskInfo is a good program to see that.
You say that programs are installed on H: How is that done? Are you using links? Do you just install some programs to a folder on H:? Is it just a subset of programs installed there?
Do you have Protection on for drive H:?
Do you have File History on?
Do you have anything Excluded in the backup of H:?
Have you tried running a backup of H: with the Ignore bad sectors box checked in the Advanced/Error handling options?
Have you tried running a backup of H: with the Snapshot for backup set to something other than VSS (Advanced/Performance options)?
It appears that H: has only about 29 GB allocated. C: has about 600 GB available, so for now could you just create a folder on C: in which you just copy everything on H: so at least it gets backed up with C:. If doing this, be sure to view all hidden and system files to be sure everything gets copied over.
Do you have any plans to replace that drive?
Cecil Bankston wrote:As I mentioned, most of the installed programs are on the partition I can't backup with the Disks and Partitions option. If a Files and Folders backup for that partition succeeds, would I be able to use that along with the backups of the other partitions (System C: & Data G:) to make a functioning restoration to a new HD?
The extended test with the Dashboard utility failed with an Error 7.
Cyril, if your installed programs live on the problem partition but the OS and thus Windows Registry etc, including AppData folders are all on the good C: partition, then you may well be able to get away with using a Files & Folders backup of H: ?
The downside here is that to ensure that you don't encounter any locked programs files, you should really make the backup after booting from the Acronis Rescue Media, not try this from within Windows!
If you haven't already ordered a replacement drive, then would recommend doing so!
BrunoC wrote:My understanding is the following facts:
- H: is just another partition on the same physical drive as G: and others
There are 2 physical disks, C: on Disk 0 and all other named partitions, including G:, on Disk 1.
- ATI is failing in what appears to be when dealing with VSS
- There are a number of bad block error reports in the Windows log
- Your VSS Shadow Storage Status only references drives C: and H: with H: showing 0 B used and allocated
- H: is 140 GB with 111 GB availableI am wondering if there is a hard disk problem that is manifesting itself in the VSS arena.
Have you looked at the S.M.A.R.T. data for the drive? CrystalDiskInfo is a good program to see that.
The Western Digital Dashboard utility shows that information. The Status tab shows Normal health for the entire disk. It provides a quick test, which showed no errors, and an extended test, which failed with error 7.
You say that programs are installed on H: How is that done? Are you using links? Do you just install some programs to a folder on H:? Is it just a subset of programs installed there?
The installer for most programs allows choosing a destination, so I generally choose G: or one of its sub-folders. Some programs install on C: without giving a choice.
Do you have Protection on for drive H:?
No
Do you have File History on?
No
Do you have anything Excluded in the backup of H:?
No
Have you tried running a backup of H: with the Ignore bad sectors box checked in the Advanced/Error handling options?
I will try that.
Have you tried running a backup of H: with the Snapshot for backup set to something other than VSS (Advanced/Performance options)?
I had not noticed there was such an option.
It appears that H: has only about 29 GB allocated. C: has about 600 GB available, so for now could you just create a folder on C: in which you just copy everything on H: so at least it gets backed up with C:. If doing this, be sure to view all hidden and system files to be sure everything gets copied over.
I could copy to the external HD I use for the backups. The objective is to avoid having to reinstall all the programs.
Do you have any plans to replace that drive?
I might end up having to do that.
Thanks again to both MVPs who have replied.
Cecil,
Just joining this thread I read that the WD tools report an error code 7 for this disk. The only way to correct that error is by using chkdsk /f /r option on all partitions on the disk in the following format:
chkdsk X: /f /r where X: is the partition letter on Disk 1
So you will run the above command from either a Admin PowerShell prompt or an Admin Command prompt replacing X: with drive letters F:, G:, H:, I:, and finally J:. So all total you will need to run the command 5 times on Disk 1.
True Image will not backup a disk with errors as the application looks for disk corruption during the first stages of the backup process. If corruption is found on disk then the app errors out. The reasoning here is that creating such a backup of a disk will carry the corruption of the disk to a new disk which of course is undesirable and defies logic.
Once you have completed all the chkdsk runs and the errors are corrected then you can successfully backup Disk 1. I would encourage you to perform a file and folder copy of all data on Disk 1 to another disk such as an external one as a safety net in case things go wrong while attempting to fix Disk 1.
I ran chkdsk /f /r on all partitions and found no errors.
I successfully backed up H: with the ignore bad sectors option.
Cecil,
Given that is the case I would seriously consider replacing the disk with a new one. Since you now have a backup of the disk recovering that backup image to a new disk should get you back to an error free setup.
Two mysteries remain.
Why was Acronis finding errors when chkdsk showed none.
I backed up the 3 partitions to the same external WD Passport HD, attached to the same USB port. The Acronis backup list shows the C: and G: backups as being on device N: . The H: backup, done on a different day is listed as being on device O: . No other external devices were attached on either backup day.
Cecil,
Windows assigns drive letters in order of device attachment. External drives will have letters assigned as they are attached so letter designation is prone to change. When using an external disk to store backups it is recommended that a drive letter be manually assigned to such devices and that letter needs to be high in letter chain (V:) for example. Doing this does not guarantee that Windows might not assign something different to the disk but does help to prevent that.
Cecil, I've been doing some reading about chkdsk and believe (if you can believe anything you read these days) that using the /r option will not check sectors that have already been marked as bad. In other words, once the bad sector is marked as bad and will not be allocated again it is not an error condition. That's why you are not seeing it.
Using the /b option I think will recheck the sectors marked bad and may actually unmark them if all looks good.
Finally, there is a question in my mind about whether cloning a drive with sectors marked as bad may in fact mark those sectors as bad on the new drive as well, leading to the question about whether chkdsk /b should be used on a new HDD that was cloned to.
If I assign a device letter to my external HD, will there be any problem with ATI finding and listing the backups that already are there?
You will have to re-select the destination drive in the ATI GUI for each task.
BrunoC wrote:Cecil, I've been doing some reading about chkdsk and believe (if you can believe anything you read these days) that using the /r option will not check sectors that have already been marked as bad. In other words, once the bad sector is marked as bad and will not be allocated again it is not an error condition. That's why you are not seeing it.
Using the /b option I think will recheck the sectors marked bad and may actually unmark them if all looks good.
Finally, there is a question in my mind about whether cloning a drive with sectors marked as bad may in fact mark those sectors as bad on the new drive as well, leading to the question about whether chkdsk /b should be used on a new HDD that was cloned to.
Chkdsk /b option does in fact clear sectors marked as bad and retests them, if the sector is still bad it is marked as bad again. It the sector tests good then it is marked good meaning repairs are made. Are these changes permanent? That depends on a number of factors.
SMART data is the best indicator of disk health. Basically a Raw value over 0 in the categories SMART 5 and SMART 197 indicates a drive is failing:
- SMART 5
- SMART 187
- SMART 188
- SMART 197
- SMART 198
The remaining categories above with values above 0 are reason to investigate and using drive diagnostic tools such as those produced by manufacturers or chkdsk are advisable.
With respect cloning and/or restore using sector by sector, running chkdsk should be done on the source disk and the target disk prior to backup. Running chkdsk /b can be run again after the cloning process on the target drive however, watching SMART data for awhile is better advised because Windows will often correct bad sectors itself and if it does SMART data will be updated.
Final follow-up.
I did assign a device letter to the external USB HD, but it still shows up with whatever letter Windows assigns to it.
I ran chkdsk /b on all partitions, showing some errors that couldn't be corrected on H: . Testing with Crystal Disk Info showed Caution for the problem 1 Tb HD, so I did final backups with ATI and replaced it with a new 2 Tb WD HD.
The backup files, done with the Disks and Partitions option, were a bit strange. My intention was to make one backup of the entire disk and, just to play it safe, a separate backup of only the data partition (G:). The G: backup had only that partition checked, but the backup file included the whole disk. Since that backup was the most recent, it was the one I successfully recovered to the new HD. The programs that were installed on H: work normally on the new HD.
I really appreciate all the input from the MVPs.
Cecil,
Glad to hear that you have this sorted. Your feedback is appreciated, thanks.