Salta al contenuto principale

Win 10 M.2 SSD full backup detecting drive errors but all seems well

Thread needs solution

Some background. I have been having issues with Acronis backups on and off for a while. After the Windows 10 anniversary edition I could no longer do full backups because the computer would black screen. Windows recently did an automatic update to the Creator edition and that dealt a death blow to a PC I was sure was on it's way out anyway. I now believe all my issues with my old PC may have been due to the PC itself.

About a week ago I completed a build of a new PC and Acronis backups seemed to work fine for a couple of days. The new build is listed below. It has not been altered for performance yet and the new video card is on back order. As you can see the boot drive is an M.2 1TB drive. This is my first experience with this type of drive and there have been no issues with the machine since it's completion except for Acronis full backups.

When I do an Acronis full backup I get several reports of CRC errors in the shadow copy. Retry does not correct the problem and I am forced to ignore the errors for the backup to complete. Since I am ignoring these errors I am uncertain of the integrity of the backup. I am working with Samsung to get to some insight into the errors but nothing yet. Samsung Magician reports no problems. CrystalDisk shows no errors. I can perform a Windows image backup with no errors.

I have no idea what's happening and why I can not do an Acronis full backup without the CRC errors showing up. I assume since the first backup was performed immidiately after the build the size of the backup was quite small and that may be a reason it succeeded. To make things more interesting the system event logs show bad block errors for the blocks the Acronis shadow copy is trying to access.

Could this just be an SSD issue? There is nothing else software or test wise that detects any errors.

Operating System
    Windows 10 Pro 64-bit
CPU
    Intel Core i7 @ 4.20GHz    26 °C
    Kaby Lake 14nm Technology
RAM
    32.0GB Dual-Channel Unknown @ 1069MHz (15-15-15-36)
Motherboard
    ASUSTeK COMPUTER INC. STRIX Z270E GAMING (LGA1151)    25 °C
Graphics
    DELL U2412M (1920x1200@59Hz)
    1535MB NVIDIA GeForce GTX 580 (EVGA)    38 °C
Storage
    931GB Samsung SSD 960 EVO 1TB (Unknown)
    2794GB Seagate ST3000DM001-9YN166 (SATA)    34 °C
    4657GB Seagate Expansion Desk SCSI Disk Device (USB (SATA))    37 °C
    2794GB Western Digital WD My Book 1230 USB Device (USB (SATA))    34 °C
    1397GB Western Digital WD My Book 1140 USB Device (USB (SATA))    32 °C
Optical Drives
    ATAPI iHBS112 2
Audio
    Realtek High Definition Audio

0 Users found this helpful

Darkkhelmet, if the CRC error is related to VSS and shadow copy, then this could be on a different partition than your main OS, assuming that you also have an EFI partition on this M.2 SSD drive.

I would suggest creating the WinPE version of the ATIH Rescue Media if you don't have it already, then booting from this should result in the EFI Partition being given a drive letter, then you can try running a CHKDSK against that partition.

An alternative would be to choose a different Snapshot method as described in KB 59440: Acronis True Image 2017: 'Snapshot for backup' option overview

You should also use the MVP Log Viewer to provide more details on any error messages reported in the backup task log files - link below if needed.

When you say Full Backup do mean you are selecting the Entire PC method for the backup task or are you selecting a Full disk using the Disk and partitions method?

I would agree with Steve here to attempt backup using bootable media.  Since you have an M.2 drive in play here you might have the drive setup so that it is using the SATA controller in RAID mode.  If this is so you will need to create WinPE media using the MVP WinPE builder tool which you will find link to in the signature section of Steve's post above.  Make sure you read the instructions on how to inject custom drivers using the tool so that you can work with your drive.