Failed to decompress LZ4 block: bad CRC

[robnicholsonmalt]

This is more of a "FYI" as it's for the free Windows agent version. I use Veeam to image my OS partitions each night. The image is written to the E: drive on the same PC. A script also copies the backup to my server and, if it's plugged in, an external USB-C drive.

Whenever I try to restore the image from the E: drive, it fails with the error below. Every time. However, if I restore it from the network OR that cheap USB-C drive, it works fine (so the backup files aren't corrupt).

So why is the E: drive different? Well, I think because it's a Windows Storage Spaces drive. It's a dual-4TB drive effectively in RAID-0 for speed. Yes, I know RAID-0 is dangerous but everything is backed up and this is "just" my PC so if it blew up, it would just be annoying.

I've not bothered to raise a ticket because, as a free user, it's a waste of my time. The ticket is always closed as "too busy".

[HannesK]

Hello,
just for clarification: that restore is "bare metal restore", right?

First I thought, that it is because we cannot read from Storage Spaces RAID0 at all, but it looks like the first partition (EFI) is restored successfully. Which Windows version do you use?

Best regards,
Hannes

[robnicholsonmalt]

It's whatever the top option is on the Veeam recovery environment. Can't recall what it's called. Windows 11. Yeah I know, see other hot topic But I've had a ticket open for a while on this so I think it also occurred on Windows 10. Basically, I could never restore using Veeam recovery USB stick. I had the backup mainly for file restore.

[HannesK]

the Veeam recovery environment

thanks! yes, that's bare metal restore.