HDD hard drive not recognized with boot system of SSD Win 10, what is then also no longer recognized, what to do?

My problem, as written above, is that when I want to swap a 2TB for a 1TB hard drive (Sata connection) and start the laptop, it shows me * Boot Device failed *. My SSD is recognized in the BIOS and is at the top with Win 10 as the boot.

If I don't plug in an HDD and boot up, same problem.

If I plug my old SSHD back in, it boots over the SSD and everything works.

Both Sata plates are empty.

I noticed that a boot manager appears in the BIOS via my SSHD, which simply overflows my SSD and stands up, could it be together with it? Or is it possibly the connector? I read a similar report, the requirements were about the same and the connector was the problem!

But before I buy a cable for 26 hours that looks identical to what is inside, I would like to add other knowledge, maybe there's another solution!

Components that are:

Samsung SSD 970 Evo Plus 500GB (Win 10) additionally extended NVMe M.2

Toshiba SSHD MQ02ABD100H 1Tb (NTFS) was installed as standard

Seagate Barracuda ST2000LM015 2TB (NTFS) is to be installed

System was stable before!

Thank you for any help, just write if you have any further questions.

Yes, of course you can check the bios before every start and see if it is number one, have you ever been able to check the battery? So is the time current in windows? This is saved by the bios battery so you could recognize it at the minute.

Otherwise there may be an error on the disk itself, and remember that it must also have an operating system, because if the disks are completely empty there would be no win 10 on it.

As I said, my win 10 runs on SSD NVMe M.2. And both satas are formatted.

Time and everything is right so far, the battery will not be the trigger that two hard drives disappear…

You mean that they are recognized in the PC? Formatting would be a kind of reset to the original state and then you would no longer have win 10. You shouldn't be able to format your disk under win so the one with win because windoof refuses.

Now the battery saves the bios settings, so it can be that there are conflicts if he can't save it. So close both disks again to win 10 on place one, another on place two and start and go to the bios again to check if everything is correct, open windows and start disk management. And then format disk two on ntfs.

I think you are confusing something! My SSD is the operating system! Windows is on there! The two Sata disks are empty and are also recognized in the BIOS as soon as they are connected, only as I said, as soon as it boots up, it does not want to boot from the SSD, and apparently does not recognize it as a hard disk.

And that's exactly why you should check the bios with the setting. You don't understand what I'm trying to tell you. If your bios has an error then there's a defect, otherwise it is the cable THEREFORE and also a disk can be erased in such a way that it has no formatting.

Okay, then we're on the right track after all… Maybe!

I'll take pictures for understanding and I'll get back to you right away.

He recognizes everything, only not when booting: /

So then there's only one thing left to do with your boot medium or plug it in and try whether you can possibly get into system repair with it. Data is not lost there.

He tells me that there's no bootable medium that can be repaired: / I now set win 10 to the 2Tb and boot from there if that works, then I check whether the SSD is accessible from the medium and change the boot order again, let's see if that's working.

Thank you for your time and help.

If there's something new, I'll get in touch.

Yes otherwise nothing would have occurred to me except a disk use disk management or set up again, hope it brings something.

I still know a very unlikely possibility if you know what a jumper is, have you ever changed? Or does the second disk have a jumper on it?

Yes, I know what you mean, both hard drives didn't have a jumper, so none was favored.

It is strange that he asks me when I set up whether I want to move my data: / So there's something wrong in front and behind… Windows can't be repaired because there's none, but transferring data from NVMe to Sata, xD works

That thing is really beating me up right now.

Update: Unfortunately it doesn't work. A shame, would have been nice… The SSD is recognized, but not the windows on it. The next step is then to format the SSD, reinstall the windows and see if it then accepts it!

So it can also be that some technology is broken, but both disks have worked?

I rule out a defect because the 2TB runs with windows, the access is louder and annoying, but not the reason: / I bought this new.

The laptop itself has survived my * RAM and NVMe * conversion work well and there has been no hardware damage until now.

What is noticeable, however, is that my roccat kone aimo gaming mouse also does not boot when the laptop is booted and the USB is plugged in, it then freezes at the logo.

There's some defective cable check everything on hardware and check dust… If he messes around like that he definitely has a problem. That with the usb is more common but mostly only with real usb sticks not with mice. The boot menu itself may have been damaged somehow or the boot process itself.

SSD new, HDD new. And both work, just not together.

With the mouse, it is probably due to the internal memory that it accesses when booting, so I would have to adjust the USB ports in the BIOS, but that was too much for my layperson to know.

Yes the hard disks may be okay but technology so the pc the motherboard can have some problem and if it is only the pcie slot. But I don't have any more idea than that, if all of this doesn't work, I would ask again in special forums or with the repair service.

Update: Problem solved, albeit cumbersome!

2TB connected, with my SSD.

Delete all partitions (without exception) and then play the OS on the SSD. Later, when windows is running, mark the HDD as a simple volume and you're done.

Apparently it does not recognize the boot process, which puzzled me, since all SATA disks have a boot manager, except the SSD. Since my SSD probably doesn't have one, it must have accessed the others… Only there was nothing on it, at least explains the * Boot Device failed *. I have no idea whether this is due to the interface or whether it was simply overlooked or I should have downloaded a tool beforehand. In any case, he now recognizes the 2TB, and SSD is the system disk.

Um the ssd is booted it has no boot system… Um well no plan but yes i said format and by that i meant everything.

Okay, yes well, but he always wanted to boot from the Satas. Even with my old one, he first had to receive the information via the HDD that the SSD is in front, that is, he gets the boot information from the HDDs. Which is not exactly bad if the SSD should have a hardware damage and you also have a bs on the storage disk, but I didn't want that. Well, Wayne is now too.

I had a hard time formatting my SSD because my data was there, and the constant pushing around on my sack was because of the complete flattening of the HDD. Unfortunately I only have an external 300Gb that can't process 5GB packages, so I had to test everything else before I was confronted with pushing everything back and forth 5 times, which I still had to do now, haha.

Oh, life could be so beautiful… If you didn't always make things complicated yourself.

Nevertheless, thank you again for your support.

The 300gb disk can do that but not under the fat 32 format and booting itself is not in its hard disk which has its own small start system, yes, but also not.