Hard Drive Not Working/Not Detected By Your BIOS Anymore?

I was starting to panic because suddenly my 1TB Seagate SATA drive wasn't working, I thought it was a BIOS issue because it seemed to have happened after I tried overclocking my Desktop too much.

I tried powering down and waiting, but I still couldn't hear the drive spin up at all.  I tried a second 1TB hard drive and it wouldn't work either.  I checked all power connections again and again until one of the pins in the MOLEX connector popped completely loose.

This was a small problem but who knows how long one could troubleshoot not knowing it is the connector ? It looked fine until I moved it by accident and the pin moved completely out of the socket.

I guess if a drive is not being detected I always remember this and to ensure the pins in any MOLEX are good.  It's a relief and a big embarassment that the problem with my 1TB Seagate SATA drive was just because of 1 loose pin on the MOLEX power connector.

Latest Articles

  • AMD Set Fan Speed and Other Powerplay Memory/CPU Timings with a Linux script
  • Ethereum Mining Claymore Nanopool Error
  • genisoimage errors with long filenames and deep directory structures
  • Linux Kernel USB Export Errors
  • How to download gajim 0.16.9 XMPP/Jabber client so you can use OMEMO encryption
  • HP DL385 G7 Linux BIOS Update Flash
  • hwloc-nox set CPU affinity in Linux
  • Firefox An error occurred during a connection to some-ip-or-domain. SSL peer reports incorrect Message Authentication Code. Error code: SSL_ERROR_BAD_MAC_ALERT Solution
  • Proxmox understanding the directory structure and why an NFS datastore appears to be missing files/isos
  • pandoc convert markdown to html
  • Proxmox error uploading an iso solution
  • Cannot install moodle
  • MySQL change for Antelope format to Barracuda error solution
  • vmkping -I vmk1 10.0.2.69 PING 10.0.2.69 (10.0.2.69): 56 data bytes sendto() failed (Host is down)
  • gvfs mount in /run/user cannot be accessed or displayed wrong permissions
  • VMWare vSphere 6.7 Errors Solution 503 Service Unavailable (Failed to connect to endpoint:
  • How To Enable Nested KVM so guests can virtualize with hardware extensions
  • vi error solution E166: Can't open linked file for writing
  • Supermicro IPMI / KVM / BMC Remote Console Screen Resizing Issue - Window Cut Off Solution
  • Linux bash shell doesn't show username, hostname or current path fix solution