True Image 2018 fails to read VSS and VSS Doctor reports problems
For 2 to 3 weeks I have had a problem running a successful Acronis True Image 2018 backup. I repeatedly get the same error message and most of the time it occurs at the same sector. An image of that error message is below:
I have noticed that if I attempt a backup of a smaller size, the backup runs successfully and validates successfully. Maybe this means there’s something about the size of the backup that is a problem or the files that I did not include in the backup are causing the problem?
I have already taken several actions that I had hoped would resolve the problem but did not:
- Updated my SSD driver with the manufacturer’s latest (Samsung).
- Ensured I have the latest firmware for my SSD.
- Run CHKDSK on all of my discs and all of my unlettered partitions on Disk 1.
In doing research on the web I found the Acronis VSS Doctor program. I ran the program and it showed me two errors highlighted with the “red dot”. Unfortunately I do not know how to resolve the problems found nor are there any “Fix Issues” boxes associated with the problems.
I have included images of the two problems reported by VSS Doctor.
The first issue identified above by VSS Doctor is something about my C drive. Unfortunately, I cannot quite understand the technical language used in the description of the problem on my C drive. Since I have over 300GB of free space, I’m not sure what “Clean up some space” means(?). If you know what this message means, I would appreciate any help or insight you could provide as to whether it is a valid problem and if so, how I can correct it.
On the second issue identified by VSS Doctor, I can see that there is something about the 13 GB partition on Disc 1 that may be of insufficient size. Unfortunately I do not know how to extend the size of that partition, since the normal partition actions are grayed out when I select that partition in Disk Management. Maybe the problem with my failing backups is due to this partition being too small? I hope you can help me make this partition larger so that at least I could eliminate that as a cause of my failing backups.
Below I have included an image from Disk Management showing my C drive. (I am not sure why my C drive appears as Disc 1 instead of Disc 0, but I assume it has always been that way and it is not part of this current problem).
Thanks in advance, very much, for your help.
Thanks very much Steve for your quick reply.
I used the Samsung Magician software and could find no errors on the SSD. I obtained a commercial hard disk analysis tool called Hard Disk Sentinel and did a block by block check on the SSD. It did show 2 bad blocks. The sectors in one of the blocks included the sector identified in the Acronis error message. I assume this is the cause of the VSS read error.
Now that I know (think) there is a problem on the SSD containing my C: drive (Windows Disk 1 in the image below), I believe the only option I have is to perform a full (not Quick) format on the SSD so that the bad blocks can be identified and removed from use (or I could replace the SSD). I think that means I will have to use the bootable Acronis Recovery tool to reload my system from an external drive after the formatting.
My question is that when I look at the SSD containing C: (which is Disk 1 in Windows and Disk 2 in Acronis), I see 4 other partitions in addition to C: (see image above). I assume during formatting they will NOT be deleted(?). When I restore from a previous backup of C:, what will happen to these other 4 partitions? I hope Acronis True Image 2018 will only restore C: and not change the other 4 partitions. Is that correct?
One other option is that I could clone C: to D: (Disk 1 to Disk 0 in Windows). Then I could boot with D: and use D: to format C:. After full format of C:, then clone D: back to C:. During this process I would still have a backup of C: on an external drive. Do you see any problem with that and would you recommend that? I assume I would have to enter the BIOS to change the boot order after cloning C: to D:. Then re-enter BIOS and change boot sequence back after cloning D: back to C:. Sound right?
Thanks again Steve for your advice.
Bob, thanks for the further information here even though this includes finding bad blocks on your OS SSD.
The first recommendation here is to ensure that you have a good Disk Backup image of the SSD before taking any other steps to try to fix the bad block issue!
If you have issues with creating that Disk backup within Windows due to hitting VSS snapshot errors, then the way around this is to boot from the Acronis Rescue Media and create the backup outside of Windows.
Note: you may need to try using both the ATI 2018 'Simple' Windows PE and the Linux versions of the rescue media in case the WinPE media also gives you any snapshot errors.
The backup should be stored on an external backup drive.
Next, what do you have stored on your Disk 0 drive (if you are considering cloning to it)? If there is any important data present, then you should also make a backup of that drive too separately.
Personally, I would not recommend cloning from C: to D: for several reasons!
First, the same bad block is likely to cause the clone to fail.
Second, looking at your disk management image, it looks like Windows has decided to use Disk 0 to store the Recovery partition and probably also the System partition used for booting into the OS, which is one of the downsides of not having the OS installed on Disk 0.
You can test the second point above fairly easily by shutting down the PC then disconnecting or removing the Disk 0 SSD then attempt to boot into Windows without it. If this fails then it confirms that the Boot Configuration Data (BCD) is stored on Disk 0 and you would need to use the Windows 10 Install media to boot into the Recovery Environment and perform a Startup Repair to get Disk 1 to be bootable without Disk 0 present. If attempting this last action, then I would suggest moving Disk 1 to the Disk 0 placement so that it is in the correct place going forward!
The other partitions on the current OS Disk 1 look to include a 13GB factory recovery partition that probably came with the PC when received from the maker and as such would put it back to the OS that it had at that time if ever used!
With regard to formatting Disk 1 for the bad block, then expect for the whole disk to be formatted, not just the C: partition. You mentioned Samsung Magician finding 2 bad blocks so the other one may be in one of those other partitions on the drive!
Steve, I had a little trouble with the terminology. I thought “Rescue Media” was the same as the MVP Bootable Acronis. I tried the MVP Bootable 3 times but always got an error about Snapshot. I finally created a “Rescue Media” in Linux and was able to use that to successfully create a backup image of C: to an external drive.
I then used the MVP Bootable to format the C: drive on the Samsung 970. I think that formatting should identify the bad sectors/blocks and mark them for non-use. After formatting, I used Hard Disk Sentinel to verify that all sectors/blocks were good. Then I restored the backup image…. and it worked!
I have contacted Samsung about possibly returning the 970 drive for warranty if I have further bad sectors.
Thanks for your help with this problem. It was all good advice!