When you connect a hard drive, you cannot boot from other drives, what is the reason?

Question

Hard disks

Good afternoon!
The laptop had a Toshiba MQ04ABF100 HDD, it stopped loading. I tried to put it in the computer to copy the data.
But the problem is that if I connect this screw, then I cannot boot from any other disk. I select them in boot order, but the error keeps popping up saying it can't be loaded. Checked on two different machines. If you connect a faulty HDD, booting from the system disk becomes impossible.
I tried to connect it through a remote docking station. When turned on, a faulty hard drive periodically appears in the list of disks and disappears, sometimes for a second, sometimes for a minute, but I don’t have time to do anything with it, it disappears again.
The R.tester program sees it when it appears and does not see it when it disappears.
What could it be? Controller cover, or can be repaired?

Answer 1

The R.tester program sees it when it appears and does not see it when it disappears

If the R.tester sees and does not see the hard drive in this way, then it disappears as a device.
Stop trying to turn on the disk in any way, it is now clear that the likelihood that he will "come to his senses" is, in fact, zero.
Try to see SMART in the same R.tester when the disk appears and take a screenshot. But don't get too carried away here. If this cannot be achieved in one, maximum, a couple of times, stop any actions at all, incl. on, and set the disc aside.

Controller cover, or can be repaired?

The probability of problems with the controller according to the description looks low. Rather, some internal problems, for the diagnosis of which there is not enough information yet.
You should not follow the advice from Youtube on replacing the board either. In your case, you need at least either a transfer of the ROM or its contents.
There may be, for example, bugs due to G-list overflow. Heads could degenerate, as a result of which they can read, but cannot write, etc.
In general, there are 4 options:

1. The drive has been overloaded while running and is still writing tiled recording ( SMR ) tapes. In this case, you can try to wait, although it is unlikely;
   
2. Defects in the magnetic surface of the plates;
   
3. Failure of one or more heads;
   
4. Drank (a scratch on the pancake).
   

The probability of the first scenario is low in itself. In your case with multiple inclusions, it is even lower. In this regard, just turn on, wait, and hope is not worth it. If the information on the screw is important, this is a risk, he can finish himself off.

to copy data

If you need to recover data from a hard drive, then by writing here, you acted reasonably.
Now you have a good chance to get off with "little blood" - as long as the disk is not completely shattered, the probability of subtracting it as is, without interfering with the HDA, is noticeably higher. Thanks to this, the price will be acceptable.
In order not to lose this chance, contact companies that deal only with restoration, no "PC repair". For those who work honestly, diagnostics are free.
Here is a brief universal data recovery guide: https://xn----7sbbfbnfa0a2audfacc2cat8e9f.xn--p1ai/
If you are in Moscow, we will be happy to help. On holidays we work all day *sighs*

Answer 2

it is obvious that the order of the disks in the OS loader does not correspond to what happened with the connection of a new disk ; the
solution is to swap the disks in the slots in the motherboard or correct the settings of the OS loader

Answer 3

I had the same problem so I'm sharing my experience.

I select them in load order, but the error keeps popping up saying it can't be loaded.

I just had a black screen. At what, when Secure Boot was turned on, the boot stopped even from this disk.
For a while, I put up with it. But then artifacts appear during the operation of the system itself. I tried many ways, up to BIOS flashing. There are more than 5 questions on my disk subsystem on this resource.
What finally helped:
I switched the SATA connector to Hot Plug mode. Then I booted into WinPE and from there, having connected it to a hot one, I restored it to Victoria HDD 5.17. Launched Refresh and Remap modes. After 4 hours of disk repair, the system began to work perfectly. Artifacts disappeared during the operation of virtual machines and all BIOS functions began to work normally.
Here is a solution.
PS: If you have any questions, write to me, I will write my story in detail.