Can't boot SSD without HDD connected

Page 1 of 3 123 LastLast
  1. Joro's Avatar
    Posts : 29
    10 (20H2)
       #1

    Can't boot SSD without HDD connected


    In my desktop i7 machine, Windows 10 1909:

    I just bought an SSD and then cloned my C: hard drive to the SSD.

    The SSD boots (very fast) and functions perfectly - only if I have the HDD also connected. It won't boot on the SSD alone, I get a 'PC needs repair' message.

    (If I disconnect the HDD while it's running, the system fails. But while the HHD was running the system, I was able to hot-add the SSD with no problem.)

    What's up?
      My Computer


  2. Posts : 38,421
    windows 10 professional version 1607 build 14393.969 64 bit
       #2

    1) Open disk management > by default some columns are compressed > widen each Status and Volume > make sure the contents within the parenthesis are in full view and that none of the characters are cutoff > view disk 0 > widen this row as needed so that all of the characters are in full view > post an image into the thread
    Disk Management - How to Post a Screenshot of

    2) Download and install Minitool Partition Wizard > post an image of the results into this thread
    MiniTool Partition Wizard Free Edition - Free download and software reviews - CNET Download.com

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

    Code:
    bcdedit /enum all
    bcdedit | find "osdevice"
    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 par 5
    det par
    sel par 6
    det par
    sel dis 1
    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 par 5
    det par
    sel par 6
    det par

    4) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread


    5) Post an image of the BIOS boot order
      My Computer

  3. Steve C's Avatar
    Posts : 6,290
    Windows 10 Pro 64 bit
       #3

    Cloning has probably resulted in both drives having the same disk ID which can cause problems and the PC may be booting from the active boot partition still on the HDD. You need to change the disk ID of the SSD, configure the boot configuration using bcdedit to boot from the SSD and change the status of all partitions on the HDD to inactive (e.g. using Partition Magic). I use imaging rather than cloning to move an installation to avoid the disk ID conflict.
      My Computers


  4. Posts : 38,421
    windows 10 professional version 1607 build 14393.969 64 bit
       #4

    For possible disk signature collision see this link:

    https://docs.microsoft.com/en-us/arc...ure-collisions
      My Computer

  5. Joro's Avatar
    Posts : 29
    10 (20H2)
    Thread Starter
       #5

    Thanks Zbook and Steve C. The explanations given and the link most likely explain the problem. The fix suggested looks complex; so I 'd prefer to find a way to avoid the conflict and reclone the disk if that's possible.

    I periodically clone my HDD to another HDD and have never had this issue before. I wonder if this happened because of cloning to an SSD.

    Is there a switch or other way to prevent this conflict when cloning?
      My Computer

  6. Steve C's Avatar
    Posts : 6,290
    Windows 10 Pro 64 bit
       #6

    Joro said:
    Thanks Zbook and Steve C. The explanations given and the link most likely explain the problem. The fix suggested looks complex; so I 'd prefer to find a way to avoid the conflict and reclone the disk if that's possible.

    I periodically clone my HDD to another HDD and have never had this issue before. I wonder if this happened because of cloning to an SSD.

    Is there a switch or other way to prevent this conflict when cloning?
    Use Macrium Reflect. Don't clone the disk. Image the installation to an external drive, boot the Reflect USB recovery drive then recover the image file to the new disk.
      My Computers


  7. Posts : 38,421
    windows 10 professional version 1607 build 14393.969 64 bit
       #7

    When available please update the thread with the results from post #2.

    Imaging as compared to cloning should be free from signature collisions.


    If the results indicate a cloning problem it may be able to be fixed using command line.
    Last edited by zbook; 01 Mar 2020 at 03:37.
      My Computer

  8. Joro's Avatar
    Posts : 29
    10 (20H2)
    Thread Starter
       #8

    My objective was and is to clone the HDD to the SSD and then use the SSD as the working drive.
    I need the SSD to boot independently for that.
    I periodically clone the working drive (I've had problems with restoring images) and the cloned drive has always booted independently.
    But this time, my first attempt to clone to an SSD - and with this conflict.
    Is this an issue with SSDs?
      My Computer

  9. bobkn's Avatar
    Posts : 3,609
    Win 10 X64 Pro 21H1 19043.928
       #9

    Joro said:
    (snip)
    But this time, my first attempt to clone to an SSD - and with this conflict.
    Is this an issue with SSDs?
    Nope.

    I've been using SSDs as boot drives for a few years. Cloning onto an SSD is no different than with an HDD.
      My Computers


  10. Posts : 38,421
    windows 10 professional version 1607 build 14393.969 64 bit
       #10

    When available please post results from administrative command prompt.
      My Computer


 
Page 1 of 3 123 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 23:18.
Find Us




Windows 10 Forums