Qs Laptop
Thinks s/he gets paid by the post
- Joined
- Mar 11, 2018
- Messages
- 4,427
This is very weird. For the second time in the same week I've had trouble booting up a computer because the SSD containing the OS is missing from the boot sequence in BIOS.
This is on my old Win 7 machine. I sometimes need to access old files on it and it has always booted up before. This time I got an error message so I restarted the computer, entered BIOS, checked the boot sequence and noticed the SSD was missing. The boot sequence was CD/DVD then data HDD.
I went through the same steps as I had before with my Win 10 machine (see other thread for details) culminating in clearing CMOS which allowed the computer to see the SSD, setting the SSD to be first in boot sequence. A restart gave a different error message about not being able to access the HDD. I unplugged and reseated all SATA cables at both ends. Same error message. After much troubleshooting I determined if I disconnected the SATA cable from HDD I could make the setting of the SSD as primary boot device "stick" and get into Windows as a one time event but subsequent restarts failed as the SSD had vanished from the boot sequence, leaving the CD/DVD as the only boot device.
I now suspected the SATA cable connecting the SSD drive to the motherboard as the culprit but I didn't have any spare SATA cables. Then I saw the dangling SATA cable from my disconnected HDD and used it to connect my SSD. Now I can get into Windows every time but I don't have access to my HDD, so can't get at the data I want. I ordered three new SATA cables from Amazon. I'll update this thread as to my progress.
I never would have believed a cable can go bad unless I had experienced it for myself. I still don't believe it. How can a securely connected cable that doesn't get touched inside a case that never gets moved, spontaneously go bad?
I suppose it is possible the SATA connector on the motherboard could be bad and not the cable. I don't feel like testing that theory right now. I guess I'll find out when I try the new SATA cable.
This is on my old Win 7 machine. I sometimes need to access old files on it and it has always booted up before. This time I got an error message so I restarted the computer, entered BIOS, checked the boot sequence and noticed the SSD was missing. The boot sequence was CD/DVD then data HDD.
I went through the same steps as I had before with my Win 10 machine (see other thread for details) culminating in clearing CMOS which allowed the computer to see the SSD, setting the SSD to be first in boot sequence. A restart gave a different error message about not being able to access the HDD. I unplugged and reseated all SATA cables at both ends. Same error message. After much troubleshooting I determined if I disconnected the SATA cable from HDD I could make the setting of the SSD as primary boot device "stick" and get into Windows as a one time event but subsequent restarts failed as the SSD had vanished from the boot sequence, leaving the CD/DVD as the only boot device.
I now suspected the SATA cable connecting the SSD drive to the motherboard as the culprit but I didn't have any spare SATA cables. Then I saw the dangling SATA cable from my disconnected HDD and used it to connect my SSD. Now I can get into Windows every time but I don't have access to my HDD, so can't get at the data I want. I ordered three new SATA cables from Amazon. I'll update this thread as to my progress.
I never would have believed a cable can go bad unless I had experienced it for myself. I still don't believe it. How can a securely connected cable that doesn't get touched inside a case that never gets moved, spontaneously go bad?
I suppose it is possible the SATA connector on the motherboard could be bad and not the cable. I don't feel like testing that theory right now. I guess I'll find out when I try the new SATA cable.