mount vhdx file

[Anatolii]

Hi
My SSD drive (have 1 parition 2TB size) started behaving strangely (reading speed was very slow in some places), so I decided to make a copy of it, and then play this copy on another drive.
I run V2V Converter -> P2V -> Disk Volume -> select volume D: (1.8TB size) -> Local file -> VHD/VHDX -> VHDX growable image - set destination file name E:\SSD_2TB.vhdx and click convert.
As result, I have file (size 1.15TB) stored on drive E:\.
When I connect this file on Windows Disk Management, I can't see my files. Only 4 partition of inexplicable size without letters, 2 of which are not marked at all.

file.JPG (22.21 KiB) Viewed 338 times

In 7-zip I can open this vhdx file and can see my folders and files. But when I extract to new drive folders and files, timestamp not correct.
I understand that if I was making a copy of a physical disk and not a partition, then this would not happen. Unfortunately, I no longer have the disk from which I made this copy, so I cannot make it again.
Maybe there is some solution, how can I restore all the data from this virtual partition to a new disk?

Thank you in advance

[yaroslav (staff)]

Welcome to StarWind Forum!
How many partitions do you have on the source disk?

[Anatolii]

Only one partition (I wrote about it above).

[yaroslav (staff)]

Anatolii,

Sorry for the delay. Can I please have the conversion logs to look into the issue in detail (you can see it here C:\Program Files\StarWind Software\StarWind V2V Converter\logs)?

[Anatolii]

Yaroslav,
I see several files there that have the name of the resulting file (E:\ssd_D_2TB.vhdx), but I'm not sure what it is.

I tried to convert my vhdx file to vhd, to vmdk file and try open this file in VM (virtualbox, vmware workstation). But in these VMs, the disk also looked divided into 4 partitions and without data.
But I still managed to mount this volume and copy the data to the new SSD drive with save datastamp. I used the utility OSFMount, and at the end I indicated that I was mounting a Logical Drive Emulation, not a Phisical Disk Emulation.

I also decided to simulate my situation again. I created a 2TB virtual disk (vhdx) using Windows tools. I created a partition on it that takes up all the space, format this disk and assign letter X:. I created several empty folders on the disk.
Then did all the things I did with the real disk V2V Converter -> P2V -> Disk Volume -> select volume X: (1.8TB size) -> Local file -> VHD/VHDX -> VHDX growable image - set destination file name D:\test_2TB.vhdx and click convert.
As a result, I have the same problem. I can't mount the newly created file, or rather it mounts, but again it shows 4 partitions with no data.
You can try to do it yourself on your own computer.

[yaroslav (staff)]

Anatolii,

I need conversion logs from your system to file a request with R&D.
Could you share those please?

[Anatolii]

Yaroslav,

Please look log file

V2V_Log-20240422-125156.zip

(923 Bytes) Downloaded 8 times

.
I now again simulate my situation.

[yaroslav (staff)]

Anatolii,

Thanks for the logs. I noticed that you are using the previous version. There was a new one released recently.
Could you please try it?

[Anatolii]

Yaroslav,

Have same problem.

pic.JPG (63 KiB) Viewed 159 times

1. Internal SSD with OS.
2. Created new virtual vhdx disk size 2TB.
3. Connected result vhdx file after convertion volume D: (2) to vhdx file.
New log file:

V2V_Log-20240423-114034.log.zip

(1013 Bytes) Downloaded 7 times

[yaroslav (staff)]

Anatolii,

Thanks for reporting. Will ask my colleagues to have a look. In a meantime could you clone the contents to a healthy drive or back it up?

[Anatolii]

Yaroslav,

I already writeln above: I convert my vhdx file to vmdk file using V2V Converter. Using OSFMount utility I mount vmdk file as a Logical Drive Emulation, not a Phisical Disk Emulation (letter for volume assigned automatic).
After I copy my all data to new disk with saving timestamp (using Far Manager).

[yaroslav (staff)]

Anatolii,

Thanks for your update. I just wanted to avoid any incident until we are looking into this incident. Thanks for your cooperation.