Cloning hdd to ssd

B

burzek

Well-known member
Joined
Apr 2, 2022
Posts
109
Hi,

I have cloned a hdd to a new ssd via Ghost32.exe
However windows 10 is giving inaccessible boot drive error.

I have tried to use Magnum Reflect fix boot drive but it made everything worse.
Then I used Hiren x64 usb to use bootsect and bootrec, still no use.
Tried to clone 100 mb and 864 mb reserved partition again, it did not work.
Copyied boot and recovery folders from original drive to the ssd , did not help.
I can not even boot to the automatic repair message , getting blue screen with menu to press enter or F8.

Finally, wiped ssd.

Please advise a good cloning tool that can clone hdd to ssd without any setbacks.

Thanks,
Burzek
 
Also, virtually every major SSD maker includes some sort of cloning software, whether of their own making or licensed specialty copies of things like Acronis, etc.

I always recommend that if an SSD maker supplies this, that the one they supply be used. (And that's not a slam at Macrium Reflect, which is an excellent product).
 
Looking at the reported boot error, & the operation involved, might that not happen if the HDD were SATA & the SSD M.2/NVME?
Just a thought, since details of the drives weren't given.

Macrium Reflect is my tool of choice. But the manufacturer supplied utility (often a free download) is always a good choice too.
 
Hi,

I have downloaded latest Hiren Tool and used Macrium Reflect 7.3 to clone the hdd to ssd.
There are both connected via sata.
Hdd is 250gb , SSD is 120 gb gerenic Alpin brand drive.
I have resized destination disk partition with Macrium Reflect and it cloned just like Ghost.
Macrium Reflect also stated changes to registry at the end of cloning.
However, the result is still same booting and getting inaccessible boot drive error.
After 2 errors , getting to automatic repair but ends up with can not repair, can get to advanced options , troubleshooting , command prompt...
I do not want to mess with bcd since I can boot to troubleshooting menu.
When I messed with bcd after ghost cloning , I ended up with blue screen with option enter or F8 to try again.

What do you suggest?
Thanks,
Burzek
 
1) Post an image or share link of disk management:

a) widen rows disk 0, disk 1, disk 2, etc. > make sure that no characters are cut off

b) widen columns Volume and Status > make sure that no characters are cut off



2) If there was an srttrail.txt message after the attempted startup repair > post a share link into this thread using one drive, drop box, or google drive



3) See if restoring a Macrium image works instead of cloning.
 
Please find attached the screenshot of disk management and all files in c:\windows\system32\Logfiles\SRT in the srt.zip
 

Attachments

  • 1649598737010.png
    1649598737010.png
    281.5 KB · Views: 7
  • Srt.zip
    Srt.zip
    77.2 KB · Views: 3
zbook said:
See if restoring a Macrium image works instead of cloning.
Click to expand...

Yep (and whether Macrium or another imaging utility). These days I'm often finding more success with imaging and then restoring the image to a new drive than I do with cloning. Something has changed in the age of the SSD, and I'm not quite sure what.
 
The other thing I'd do is eliminate the variable of Hiren's Boot CD, I'd install Macrium (Free) & build the rescue media... which will (by default) use WinRE from the current install so should have the right drivers etc included. If your machine is UEFI & whatever rescue you're running fix boot problems from is booted in Legacy mode, then it won't work as expected.. It'll fix it for the mode it's booted in, which could be the wrong boot mode.
 
Hi Zbook,

Did you have a chance to check the files I sent?
What seems to be the problem?

Thanks,
Burzek
 
The PM is still malfunctioning.

Before making a backup image make sure scannow, restorehealth, and sfcfix are without problems:

Perform steps #2 - #5 in this link:
Windows Update Forum Posting Instructions


Open administrative command prompt and copy and paste (all at one time):

bcdedit /enum all
reagentc /info
diskpart
lis dis
lis vol
sel dis 0
det dis
lis par
sel par 1
det par
sel par 2
det par
sel par 3
det par
sel par 4
det par
sel dis 1
det dis
lis par
sel par 1
det par
sel par 2
det par
sel par 3
det par


Post images or share links displaying the commands with results.



The collected logs displayed a MBR partition without a system partition (likely incorporated into the data partition).
There were two primary partitions and one recovery partition.
A typical MBR partition has System/Primary/Recovery as per the image in this Microsoft link:
BIOS/MBR-based hard drive partitions


Compared to BIOS Legacy with MBR partition, BIOS UEFI with GPT partition provides options for improved security (secure boot), up to 128 partitions compared to only 4 with MBR, and is benchmark faster boot than MBR.

UEFI/GPT-based hard drive partitions

Windows and GPT FAQ


Does the BIOS have UEFI options?
UEFI native (without CSM)
UEFI hybrid (with CSM)

If available, consider booting UEFI without CSM > Clean install Windows 10 with GPT partition > restoring the Macrium backed up C: partition into the primary partition
 
Hi Zbook,

Thanks for replying.
Before doing your advise, I want to share this situation.

Normally when using Hiren Mini 7 or Hiren x64 Mini 10 , I can see both original and clone drive with all partitions - Attached picture devmgr-mini7.jpg
Also the ssd drive is a Toshiba Bics as you can see in attached toshiba.jpg

However, when I boot the original hdd drive with ssd attached. The windows 10 does not recognized the ssd as a drive.
Please check attached devmgr-w10.jpg , you will see that in Device Manager the ssd is listed as Other Devices , it is not seen in disk drives like ST3250318AS Seagate hdd drive, and in disk management only hdd drive is displayed.
I believe this is why I am getting an inaccesible boot drive, because the original W10 OS is not able to recognized the ssd.

I have removed the ssd from device manager by uninstalling , and rebooted still it is only displayed as other device.

I will try to do dism check/scan/restore and sfc /scannow, and will post the situation.
 

Attachments

  • devmgr-mini7.jpg
    devmgr-mini7.jpg
    94.8 KB · Views: 14
  • devmgr-w10.jpg
    devmgr-w10.jpg
    82.9 KB · Views: 14
  • toshiba.jpg
    toshiba.jpg
    30.2 KB · Views: 14
Boot to the BIOS > post images or share links of disk drives and Legacy / UEFI / CSM options

When posting images of disk management make sure that no characters are cut off (widen columns Volume and Status and widen rows disk 0, disk 1, etc.)
(the column Status had many characters that were cut off)


Run the Sysnative log collector > post a share link into this thread using one drive, drop box, or google drive
SysnativeBSODCollectionApp






Add these commands to the bottom of the group in the earlier post:
sel dis 2
det dis
lis par
sel par 1
det par
sel par 2
det par
sel par 3
det par

All commands can be copied and pasted as one group into administrative command prompt.


Open device manager > click view > click show hidden devices > manually expand all rows > look for any row displaying a yellow triangle with black exclamation mark or unknown > click properties > click details tab > scroll to hardware ID > post images or share links into this thread

How to easily find drivers for Unknown Devices in Windows
How to Find Drivers for Unknown Devices in the Device Manager
 
Hi Zbook,

I have another pc same hardware , same os , and it sees the drive , I have 2 ssd same drives both are seen in other identical pc.
Both are in legacy booting , they have uefi but drives are in legacy , I am ok with it.
However this pc I am working on , only sees the ssd drives in other devices section.
I had made repair install couple of months maybe it caused some difference , I do not know.

How about , if I plug in the same ssd to both pc and compare the SYSTEM hive?
If only you can advise some way to copy the related registry from the pc seeing the ssd drive to the pc that is not detecting the drive correctly in windows 10, then we can solve this I guess.

I also did dism restore health and sfc /Scannow , they report ok.
I will try sfcfix now.
diskpart does not see the ssd so it would not work...
The motherboard is https://www.gigabyte.com/Motherboard/GA-J1900N-D3V-rev-1x

Thanks.
 
Hi,

I have 2 pc , same specs , when I plug a new ssd , one of them sees it without any problems.
Other pc does not detect it as a hard drive, shows in other devices in device manager.

I was thinking about copying registry keys from working pc to the one that does not see the drive correctly.

Dism and Sfc and Sfcfix does not find any problems. This is probably related to registry.
Could someone advise me through the process?

Thanks,
Burzek
 
Hi,

Copying registry keys from another system is not a good idea, this can actually cause more problems.

Please give some more information about the system (hardware specs) and the SSD type's.

Follow step 6 in this guide to provide a speccy link.
 
Hi Maxstar,

When I remove sata ahci controller and storage controller from device manager and restart it goes to BSOD.
Normally w10 should scan and reinstall controllers , I believe there is a problem within the SYSTEM registry hive that is causing hardware not being recognized correctly. The detection mechanism might be broken too. The audio jack is also being shown in other devices even though it works.

Would you advise resetting some keys in SYSTEM registry to detect hardware correctly ?
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top