[SOLVED] mounting 'drive-scsiXX.img.fidx/part/1' failed: all mounts failed or no supported file system (400)
- Thread starter MisterDeeds
- Start date
Hm, a simple Windows installation with a special software for business - nothing really weird. Is there a log i can give you to check the important differences (or none differences)?
Hello,
I've a clean Windows 11 Installation without any additional software on it just the Virtio Drivers and have the same Problem mentioned when trying to explore the partition in the PVE-GUI from the PBS-Store:
part/3 is the main partition of that Windows machine.
Chkdsk in the VM returns no errors.
All backups were done in Stop-Mode.
I have 13 backups of this vm stored in my pbs datastore. All give me the same error.
While I am writing and checking in the Windows Disk Manger inside the VM, I've found that Bitlocker was "partially" active:
The Disk Manger shows that the partition is encrypted:
But inside Bitlocker Settings itself, it shows that it is awaiting activation (german):
One can deactivate Bitlocker completly with the cmd:
and check if the decryption is done with:
After the decryption is done, I restartet the backup job and the backup files are now browseble and restoreable again.
This Bitlocker state not fully encrypted, not fully decrypted — just something in between, seems to be the problem, at least in my case.
By the way, this is the standard Bitlocker state with recent Builds of Windows 11, if the user on the machine is not signed in with a Microsoft or an Azure AD account.
What bothers me: the verification Jobs were all ok on these backups. Could such a backup be restored if it was not browsable in the first place?
I am wondering if the drive would be browsable in the GUI if Bitlocker was fully active/armed?
Hope it helps.
I've a clean Windows 11 Installation without any additional software on it just the Virtio Drivers and have the same Problem mentioned when trying to explore the partition in the PVE-GUI from the PBS-Store:
Code:
mounting 'drive-scsi0.img.fidx/part/3' failed: all mounts failed or no supported file system (400)part/3 is the main partition of that Windows machine.
Chkdsk in the VM returns no errors.
All backups were done in Stop-Mode.
I have 13 backups of this vm stored in my pbs datastore. All give me the same error.
While I am writing and checking in the Windows Disk Manger inside the VM, I've found that Bitlocker was "partially" active:
The Disk Manger shows that the partition is encrypted:
But inside Bitlocker Settings itself, it shows that it is awaiting activation (german):
One can deactivate Bitlocker completly with the cmd:
Code:
manage-bde C: -offand check if the decryption is done with:
Code:
manage-bde -statusAfter the decryption is done, I restartet the backup job and the backup files are now browseble and restoreable again.
This Bitlocker state not fully encrypted, not fully decrypted — just something in between, seems to be the problem, at least in my case.
By the way, this is the standard Bitlocker state with recent Builds of Windows 11, if the user on the machine is not signed in with a Microsoft or an Azure AD account.
What bothers me: the verification Jobs were all ok on these backups. Could such a backup be restored if it was not browsable in the first place?
I am wondering if the drive would be browsable in the GUI if Bitlocker was fully active/armed?
Hope it helps.
Last edited:
backing up and full restore (and verification) happen on the block level - the whole process doesn't know what's inside, and doesn't care either. file-level restore requires that the special restore VM that is used can handle the contained data, that's why it has limitations like this. so yes, the backup is fine, it just is not accessible for file-level restore operations by PBS/PVE, a normal restore should work fine.