Cannot Detect SSD After Installing HD as Slave

Hey Toms, long time reader/lurker but finally compelled to sign up. I'm having an odd problem and I'm not sure where to start.

Situation: After installing a WD 500gb HD (it'd been laying around for a few years, but I verified it was working & formatted it on my other computer) without jumpers into the machine [ASRock B250M Pro4 mobo], the PC apparently attempted to boot from the HD (with no OS). No luck.

Around the same time, the PC started not recognizing that the monitor was plugged in, saying 'cable not connected'. I tried to troubleshoot that issue by unplugging HD (the only thing that changed) but no change. After a couple (attempted) boots, I opted to switch HDMI cables. With HD unplugged (IIRC, it was late) I booted, the OS started as normal and the monitor was receiving signal. No issue.

I then powered off, hooked the HD up again, and tried to boot. It wouldn't boot again, and I couldn't get the BIOS open to check. It just hung there, unresponsive. I unhooked HD yet again and attempted to boot. This time, it returned the standard 'insert boot media' error. Rebooted, opened BIOS, and the BIOS sees no possible boot device aside from the optical drive.

I really don't know where to start looking for what is causing all this. My current plan is to hook SSD to other computer and see if it'll boot. If not, I'm thinking of putting the SSD back in the other PC and trying to boot from Windows 10 disc or USB, and using the repair options.

Do any of you guys have other ideas? Should I be worried about less common issues like having shorted/damaged the mobo? Any advice is greatly appreciated, as I've got data that I need to access today. Thanks in advance.

UPDATE: I hooked up the SSD to my other (working) PC using cables from a working SSD, and neither BIOS nor Windows can recognize or even detect the drive. For a moment, Device Manager had something labeled "ST200..." but it disappeared after a few seconds. Also, no further issues with the other PC's monitor or BIOS while no SSD or HD present.
Reply to krm6886
2 answers Last reply
More about detect ssd installing slave
  1. 1. Forget about the WD HDD at this time. That's not your basic problem.

    2. Your basic problem is that you have a boot drive, i.e., the SSD of which we know NOTHING about; only that is not functioning. Whether it's defective or not is impossible to even guess from the information you provided.

    3. What's the background of this SSD? Make/model? It apparently served as the boot drive in one of your PCs. Had it performed for any length of time as a bootable, functional drive?

    4. You indicate you PROPERLY connected the SSD as a SECONDARY drive in one of your other PCs, but the SSD was not detected in the system - either in the BIOS or Device Manager? Is that right?

    5. Have you tried installing the SSD as a USB external drive and connected it to a working PC? Still the same problem?

    6. Does it occur to you that SSD may be defective? Or have you ruled that out for some reason?
    Reply to ArtPog
  2. ArtPog said:
    1. Forget about the WD HDD at this time. That's not your basic problem.

    2. Your basic problem is that you have a boot drive, i.e., the SSD of which we know NOTHING about; only that is not functioning. Whether it's defective or not is impossible to even guess from the information you provided.

    3. What's the background of this SSD? Make/model? It apparently served as the boot drive in one of your PCs. Had it performed for any length of time as a bootable, functional drive?

    4. You indicate you PROPERLY connected the SSD as a SECONDARY drive in one of your other PCs, but the SSD was not detected in the system - either in the BIOS or Device Manager? Is that right?

    5. Have you tried installing the SSD as a USB external drive and connected it to a working PC? Still the same problem?

    6. Does it occur to you that SSD may be defective? Or have you ruled that out for some reason?


    1. Understood, I just focused on it because that was the only thing changed when everything started going wrong.

    3. Sandisk 90gb, it's currently in wife's car so I don't have exact model. It was serving as main/boot/only drive in wife's PC for approx. 2 months, with no issues. Prior to that, though, it'd been sitting in a box for maybe a year, after having worked in a discarded PC.

    4. That is correct. My PC cannot detect it in either BIOS or inside Windows tools.

    5. I'm not exactly sure how to do that. I'll look up some info and try that tomorrow.

    6. It hadn't, because it'd worked fine until plugging the other drive in. But I read your reply earlier and took the drive to Microcenter and had them hook it up to one of their machines, and it couldn't detect it... the guy says it looks bricked.

    While there I grabbed a 120gb drive for $60 and reinstalled Win10 onto it, just so she has a working machine while I try and recover the data she had on the 90gb drive. So that's where we are currently. I'm tempted to try the 500gb drive again as a slave to this drive, but have a nagging feeling I'd just replay what happened before. I'm more inclined to wait for a sale and pick up a new slave drive.
    Reply to krm6886
Ask a new question Answer

Read More

ASrock Slave Drive BIOS Boot Failure Motherboards SSD Western Digital HD