Hello,
i became Errors through Image Backup on a Win 10 Client:
|Warnungen|04.05.26 17:48|Error retrieving last image backup. Doing full image backup instead.|
| --- | --- | --- |
|Fehler|04.05.26 17:48|Error creating empty image subvolume. "Unknown mode: -1"|
|Fehler|04.05.26 17:48|Error creating image backup destination.|
|Fehler|04.05.26 17:48|Backup failed|
Many Thanks!
Many Greetings
Revan335
answer from AI:
You likely encounter these error logs when using UrBackup or similar backup software. When combined with the VSS_E_PROVIDER_VETO error you just asked about, the picture becomes clear: The system is attempting to create a disk image (image backup) but is encountering both a VSS block on the Windows side and a technical issue at the backup destination.
Let’s analyze the error messages one by one:
1. “Unknown mode: -1” and Subvolume Error
This is the most notable error. It typically indicates a file system incompatibility or corruption.
Btrfs Issue: If your backup server is running Linux (such as an UrBackup Server) and the file system is Btrfs, encountering this error while creating a “subvolume” indicates that the backup disk is full, there are file system errors on the disk, or disk permissions are corrupted.
Mode Error: Mode -1 indicates that the software cannot determine how to use the target disk (write/read/create).
2. “Error retrieving last image backup”
The software attempted to locate the previous backup to perform an incremental backup but could not find it or access it. As a result, it forced a full backup by stating “Doing full image backup instead.” Since a full backup requires more space and a more robust VSS connection, the process became severely stalled.
3. “Error creating image backup destination”
This indicates that the backup software cannot create the folder or storage space where backups will be saved.
Target Disk Full: There may be no remaining space on your backup disk.
Connection Lost: If backups are being saved to a network drive (NAS), a current network outage may be causing this.
Permissions: The backup service (Service Account) may not have write permissions for the target folder.
What Should You Do to Fix It?
Check the Backup Destination:
Is there enough space on the disk where backups are being written?
Can you manually copy files to the backup folder? (Permission test).
VSS Cleanup (On the Windows Client):
Due to the previous VSS_E_PROVIDER_VETO error, there may be stuck shadow copies on the system. Open CMD as an administrator and type:
vssadmin delete shadows /all (This clears accumulated corrupted shadow copies).
Check Services:
Ensure that the backup service is running properly on the client machine and that the VSS service is set to “Manual” or “Automatic” mode.
File System Check:
If you are using a Linux-based backup server, use the `df -h` command to check disk usage and the `dmesg` command to check for disk hardware errors.
In summary: The backup software cannot open the target folder (Unknown mode: -1), and the VSS service on the Windows side is preventing the disk image from being captured (with a “Veto” error).