DISK recovery only recovering SYSTEM RESERVED partition


- Log in to post comments

I'm doing the recovery from within Windows 7 64bit with latest updates.
I've also tried using the PARTITIONS option to restore both partitions but the same issue occurs.
What's strange is it definitely writes the data to the disk, but then when it finishes successfully and I check DISK MANAGEMENT, it shows that only the SYSTEM RESERVED partition exists, and the rest of the disk is unallocated. And I am unable to boot from the disk.
- Log in to post comments

Also, I'm using a USB 3.0 to SATA III hard drive adapter cable to connect the SAMSUNG SSD to the PC.
When I connect it directly to the motherboard USB 3.0 port, the disk recovery completes successfully but I get the issue.
When I connect it to a USB 3.0 hub that is connected to the motherboard USB 3.0 port. I get the following message:
When I connect it directly to the motherboard USB 3.0 port, and run the disk recovery from the recovery media (boot from the recovery media), the disk recovery is successful and I can boot from the SAMSUNG SSD into Windows.
- Log in to post comments

What type of SSD is it? Do you have the model #.? Just want to make sure this is not a PCIe NVME drive because windows 7 does not play nice with them unless manual hot fixes are in place and you also may have to deal with converting MBR to GPT to be usable and bootable.
Also, in your backup task, under source, re-pick the source and expand the disk to show all partitions to be sure all are selected.
- Log in to post comments

Just saw your update... Please validate the backup first.
If that goes well, then run chkdsk /f /r on the source and destination disk
- Log in to post comments

Backups are validated, and no issues were found when running chkdsk /f /r on the source and destination disks.
Since my last comment, I've tested restoring a number of different disk backups in the Windows environment and with the Rescue Media. I have two separate external HDDs that I do disk backups to.
Here are the results. I've tested with two different target SSDs connected using both a USB 3.0 to SATA III hard drive adapter cable, and a USB 3.0 Dock Station - connected to USB 3.0 ports on the motherboard.
Backup I
3rd Jul – Fails
2nd May – Works
Backup II
19th Jun – Works
16th May – Fails
19th April – Fails
For one of the ones that failed in the Windows environment, I got the FAILED TO WRITE DATA TO THE DISK message pictured in my previous message. And for the others that failed in the Windows environment, the restore operation indicated that it was successful, even though the target only had the SYSTEM RESERVED partition, with the rest of the disk unallocated. It's definitely writing the data to the disk, but when I try boot from it I get this message:
For one of the ones that failed using the Rescue Media, I got the following message. And for the others that failed, the results were the same as the results in the Windows environment.
BUT I was able to get ALL the disk backups listed above to restore successfully when the target SSD was connected to the internal SATA 3 port on the motherboard (I removed the C drive SSD and swapped it for the target SSD). This is the only way I was able to restore all the listed disk backups successfully with no missing partitions.
I'd like to know what's causing some of the restore operations to fail when using a USB 3.0 to SATA III hard drive adapter cable, and a USB 3.0 Dock Station, and why all restore operations work when using the internal SATA 3 port on the motherboard.
- Log in to post comments

My guess now, since it works on the internal connection and not the external is you either have a faulty usb connector (PC side or whatever adapter you're using) or a faulty usb cable. If the USB drive is losing connectivity (lack of enough power, bad connection via cable, pc port or adapter port, or something like that), the drive may be spinning down - even if just momentarily, and causing an issue.
I know you said you tried with an adapter and a different dock, but are we using the same cable or the same USB port with both of these tests? Even if there is another USB port, does it share power with the other one at the same time which would give it similar behavior?
If possible, try a different USB port... preferably a USB port on the back of the PC if using a desktop. My desktop PC front USB often lose USB connectivity (momentarily), but the back ones are rock solid. This may not be possible on a laptop, but if you have USB ports on both sides, switch to one on the other side.
And if it's not a lack of sufficient USB power, the next option would be to swap the USB cable, and if it is still happening, the USB adapter and cable.
There really isn't a diagnostic for this (or log that will identify this in the rescue media). You'll have to do some physical trial and error here.
- Log in to post comments

USB ports other than those on the rear of the motherboard can be problematic. I had that issue with USB 3 ports on the front of one of my PCs. Replaced the motherboard and it now works correctly.
These days motherboards have multiple USB controllers - some are on the CPU, some on the chipset and other have dedicated controller. The user guide for the motherboard would help identify which are which.
Ian
- Log in to post comments

Yes, I've tested using different USB 3.0 ports on motherboard; different USB 3.0 cables; different dock stations, and different SSDs. But those things can't be the issue because, for example, Backup I, 3rd Jul, consistently fails every time I restore it; and Backup I, 2nd May, consistently works every time I restore it. All the backups are consistent in their results.
- Log in to post comments

Keylonta,
I'm not sure then. Have you tried using rescue media to restore the backups from the same computer to see if the results are the same?
If the results are the same, I would also attempt the restore from rescue media using a different computer to see if they are also the same or not. That would help identify if the USB is really the problem or not.
Beyond that, I have no idea. If it works from the internal SATA and not from USB, logic says it's the USB that is the issue, but it would be hard to pinpoint. When using the internal SATA, the drive sectors will be truly and accurately reflected. When using USB, the drive sectors will be emulated based upon however the dock or adapter is programmed and the emulation may be throwing something off. Can't say I've seen this from anyone else in the forums before though with this specific behavior where they could always restore from the internal sata, but always fail to restore certain backups from the same drive when connected to USB.
One last thought, what is the original and the new drive? Are either of them a true 4K drive and not an emulated 4K drive?
- Log in to post comments

The results are the same whether in the Windows environment or using the Rescue Media.
The original C drive is a Kingston 240GB HyperX SSD (SH100S3240G). The target drives I've tested are the 1TB Samsung 850 PRO SSD, and the 860 PRO SSD.
- Log in to post comments

Other than testing the same on a different PC as well, I got nothing.If you're able to let the restore run it's course in the rescue media (to failure, or completion but where it won't boot), you should be able to save the system report / log to your USB drive or another writeable media and provide it with an open technical support case.
- Log in to post comments