Data Recovery and Disk Utilities Forum @R-TT

We recently used 6.6005 to clone a SATA OS to an image file, to then boot off the R-Drive CD, to clone bare metal to a Intel SSD drive. Previously, we had used R-Drive Image 4.7 at another company and it was always reliable. 6.6005 simply fails to capture the boot related details, and instead restores a Primary Partitioned Active drive without a working boot sector. Boot results were "0xc000000e the boot selection failed because a required device is inaccessible" All the typical and in-depth repair efforts via the Windows 7 DVD failed.

I am not a amateur at this and had to revert to a clean install to achieve a working drive.

But the files, for some reasons, cannot be moved from the places they occupy at the moment. This is not a bug.

Alt,

Did I get it right, you really won't fix that bug?

KR,
Matthias

Hi Alt,

thanks for answering. I agree for the this possible technical reason of this bug, but do I understand it right that you won't fix it, although the product description promises partition resizing like every other partitioner /imaging program on the market?

KR,
Matthias

The developers told me and you, that the most cause for your problem is that there may be some files placed on the 250-GB disk in a way that they're outside the 80-GB size limit and they cannot be moved from their positions.

Hi Alt,
Did the developers confirm the problem? Is there a beta I can try?

@The IT Pro / @Baystack_350
Thanks to share your experience. I could imagine that fragmentation is a technical reason, but it is possible to solve it.
A defragmentation before backup could help to avoid this bug, but of course in case of desaster recovering from the last available backup there's no chance to think about that.

KR,
Matthias

I passed your problems to our developers.

I ran into a similar situation where I made a data-only image of a 250 gigabyte hdd with the data consuming 40 gigabytes of the total.

I tried to restore the 40GB data-only image to an 80GB hdd, but it failed to do so saying the destination disk needs to be larger. I was, however, able to restore the 40GB image to at 120GB hdd. One idea I have is that maybe the read-write head in the disk wrote data near a 40GB to 119GB sector on the platter, thus causing fragmentation. I'm not sure if this is the case or not.

My organization ran into the same issue with resizing. Restoring a standard MBR/NTFS disk partition. We think it has to do with disk fragmentation and unmovable system files. Try using disk defragmenter on the disk then take an image of it and see if anything changes when you restore it. I am not sure if this will solve your issue.

Hi Alt,

The partition is NTFS, the disk structure is an MBR, so resizing should work. At least the manual tells that it should work.
Do you have an idea?

KR,
Matthias