Urbackupsrv assemble reports partitions larger then MBR/GPT

Hi Everyone,

First up, UrBackup is an amazing kit. Thank you very much to all involved!

Regarding the issue, I seem to be having trouble with the server assemble function. I have searched multiple sections on the forum regarding assemble but can not find the answer.

The current test backup image is from a small baremetal windows 2012r2 server with a single C drive and no sysvol partition.
I am able to restore this backup to a test PC using the restore CD, but attempting to create a combined VHD on the server is producing the following error,

urbackupsrv version 2.5.26
Ubuntu 22.04.1 LTS jammy

urbackupsrv assemble -a /media/BACKUP/urbackup/win2012r2/220916-1350_Image_C/Image_C_220916-1350.vhd -o urbackupsrv-assemble-win2012r2.vhd
2022-09-18 13:37:49: Sectorsize: 512
2022-09-18 13:37:49: Clustersize: 4096
2022-09-18 13:37:49: ClustersPerMFTNode Offset: 48
2022-09-18 13:37:49: MFTStart: 786432
2022-09-18 13:37:49: Attribute Type: 16 nonresident=0 length=96
2022-09-18 13:37:49: Filename=$MFT
2022-09-18 13:37:49: Attribute Type: 48 nonresident=0 length=104
2022-09-18 13:37:49: Attribute Type: 128 nonresident=1 length=72
2022-09-18 13:37:49: Attribute Type: 16 nonresident=0 length=96
2022-09-18 13:37:49: Filename=$Bitmap
2022-09-18 13:37:49: Attribute Type: 48 nonresident=0 length=104
2022-09-18 13:37:49: Attribute Type: 128 nonresident=1 length=80
2022-09-18 13:37:49: Bitmap size=462576
2022-09-18 13:37:49: ERROR: Error reading cluster 18446744073702282962 code: 529
2022-09-18 13:37:49: WARNING: Volume OS not an NTFS volume. Copying all blocks…
2022-09-18 13:37:49: ERROR: Partitions number of input file /media/BACKUP/urbackup/win2012r2/220916-1350_Image_C/Image_C_220916-1350.vhd larger than parsed partitions from MBR/GPT

What am I doing wrong here?
I have also tried on other backups that contain both C and SYSVOL but assemble produces similar error as above.

urbackupsrv assemble -a /media/BACKUP/urbackup/WIN-UCKFST04RE4/220917-0702_Image_SYSVOL/Image_SYSVOL_220917-0702.vhd -a /media/BACKUP/urbackup/WIN-UCKFST04RE4/220917-0702_Image_C/Image_C_220917-0702.vhd -o urbackupsrv-win2019.vhd
2022-09-18 14:05:10: Sectorsize: 512
2022-09-18 14:05:10: Clustersize: 4096
2022-09-18 14:05:10: ClustersPerMFTNode Offset: 48
2022-09-18 14:05:10: MFTStart: 46848
2022-09-18 14:05:10: Attribute Type: 16 nonresident=0 length=96
2022-09-18 14:05:10: Filename=$MFT
2022-09-18 14:05:10: Attribute Type: 48 nonresident=0 length=104
2022-09-18 14:05:10: Attribute Type: 128 nonresident=1 length=72
2022-09-18 14:05:10: Attribute Type: 16 nonresident=0 length=96
2022-09-18 14:05:10: Filename=$Bitmap
2022-09-18 14:05:10: Attribute Type: 48 nonresident=0 length=104
2022-09-18 14:05:10: Attribute Type: 128 nonresident=1 length=72
2022-09-18 14:05:10: Bitmap size=17568
2022-09-18 14:05:10: Sectorsize: 512
2022-09-18 14:05:10: Clustersize: 4096
2022-09-18 14:05:10: ClustersPerMFTNode Offset: 48
2022-09-18 14:05:10: MFTStart: 786432
2022-09-18 14:05:10: Attribute Type: 16 nonresident=0 length=96
2022-09-18 14:05:10: Filename=$MFT
2022-09-18 14:05:10: Attribute Type: 48 nonresident=0 length=104
2022-09-18 14:05:10: Attribute Type: 128 nonresident=1 length=72
2022-09-18 14:05:10: Attribute Type: 16 nonresident=0 length=96
2022-09-18 14:05:10: Filename=$Bitmap
2022-09-18 14:05:10: Attribute Type: 48 nonresident=0 length=104
2022-09-18 14:05:10: Attribute Type: 128 nonresident=1 length=72
2022-09-18 14:05:10: Bitmap size=513904
2022-09-18 14:05:10: ERROR: Partitions number of input file /media/BACKUP/urbackup/WIN-UCKFST04RE4/220917-0702_Image_C/Image_C_220917-0702.vhd larger than parsed partitions from MBR/GPT

I tried the manual build process using the urbackuprestoreclient to a file based raw disk and with some manual creation of partitions I can get a bootable VHD, but I would like to know why I cant use the assemble function.

https://urbackup.atlassian.net/wiki/spaces/US/pages/2981890/How+to+restore+via+command+line
I plan to use the post_full_imagebackup script to automate conversion and deployment of VHDs and the assemble function is critical to make it work.

Any help appreciated.

Same problem here:

$ urbackupsrv assemble -a Image_C_230909-0338.vhdz -o full.vhd
2023-09-09 17:58:58: VHD-Parent: "/storage/urbackup/*****/230908-0338_Image_C/Image_C_230908-0338.vhdz"
2023-09-09 17:58:58: Sectorsize: 512
2023-09-09 17:58:58: Clustersize: 4096
2023-09-09 17:58:58: ClustersPerMFTNode Offset: 48
2023-09-09 17:58:58: MFTStart: 786432
2023-09-09 17:58:58: Attribute Type: 16 nonresident=0 length=96
2023-09-09 17:58:58: Filename=$MFT
2023-09-09 17:58:58: Attribute Type: 48 nonresident=0 length=104
2023-09-09 17:58:58: Attribute Type: 128 nonresident=1 length=96
2023-09-09 17:58:58: Attribute Type: 16 nonresident=0 length=96
2023-09-09 17:58:58: Filename=$Bitmap
2023-09-09 17:58:58: Attribute Type: 48 nonresident=0 length=104
2023-09-09 17:58:58: Attribute Type: 128 nonresident=1 length=80
2023-09-09 17:58:58: Bitmap size=7631112
2023-09-09 17:58:59: ERROR: Partitions number of input file /storage/urbackup/*****/230909-0338_Image_C/Image_C_230909-0338.vhdz larger than parsed partitions from MBR/GPT

I tried running decompress-file instead of assemble. The process worked, but the VHD does not boot under VirtualBox.