BIOS Update Caused HDD to no longer be recognized

Jun 3, 2018
3
0
10
Hello,

I have used these forums a lot to help myself with computer issues that I have ran into, but it seems my current situation is unique. I recently had an issue with my computer booting windows 10. I had just upgraded to new Mobo, Memory, and CPU so I figured maybe I needed a fresh install of WIndows 10, and in the process, update my bios.
(Note: My computer ran fine after the upgrade for weeks, with everything working flawlessly)

After doing the fresh install my problem persisted. After running some diagnostics, and running memtest+, I discovered I had some faulty ram. I took out the problem card and the computer ran flawlessly. After getting everything set back up after the wipe, I noticed that my 4 TB HDD no longer showed up. I have had HDDs fail in the past so I just assumed this was the case.

Replaced SATA cable, replaced power cable, and still nothing. Used the SATA cable and power cable from the working SSD and still nothing. I went off to the store and bought a new 4 TB HDD to replace it. After installing that in the PC, that wouldnt come up either. Went out and purchased an SSD and installed that. That came up without issue. Checked all my SATA ports, even swapped the working SSDs with both HDDs and still nothing. Tried different SATA power cords for PSU and even used different ports on the PSU.

What I am thinking has happened is when I updated my BIOS, it changed some type of setting that doesn't allow my HDDs to be recognized, but shows my SSDs. I checked my bios and SATA is enabled, AHCI is also selected, and in the list of SATA ports, my disk drive, and both of my SSDs and there, but no HDDs.

I read a lot about needing to run some type of DOS Diagnostics for Western Digital and changing the speed of the HDD but I am not sure why that would be required when the HDDs showed up before the BIOS upgrade

Any input would be appreciated

Build:
PSU: EVGA 1600w Full Modular Titanium
MoBo: Asus Prime Z370-A ATX
Memory: 64gb Corsair Dominator Platinum DDR4 3200MHz (now 32gb after issue discovered)
CPU: Intel i7-8700k 6-core @ 4.2GHz Liquid Cooled
GPU: MSI SeaHawk Hybrid Cooling GTX 1080ti (x2)
Storage: ADATA XPG SX900 2.5" 256GB SSD (OS), Crucial MX500 500GB SSD (Gaming), WesternDigital Blue 4 TB HDD (Storage), WesternDigital Black 4TB HDD (Storage)

 
Jun 3, 2018
3
0
10


I have not used bit locker on this computer. That would make sense but unfortunately the new drive I bought never showed up to even be able to do anything with it. However, I'm going to go and get an external docking station through USB and see if both hard drives show up to eliminate a mechanical failure
 

CaptainCretin

Respectable
Jul 18, 2016
625
0
2,160
I had a similar issue after a Win7 update, the drive wasnt recognised on any SATA port, and no SSD/HDD would work on the port. I used some tools supplied with "Aomei Partition Assistant" (which is free), to reset the HDD drive and get it working again - this after throwing away the first mobo it happened on.

The update buggered up the mobo's port settings, so it couldnt talk to the SATA interface on the drive, and also buggered up the HDD's interface, so it couldnt be formatted or read.
I cannot remember exactly what I did to get the port working again, I tried several options, and eventually one of them took, and the SATA port started working again; it might have been some setting under "Computer Management/Storage Devices" that finally fixed it.
 
Jun 3, 2018
17
0
10


Okay. Please do note that there are almost a dozen threads in this forum which seem to cover a very similar observation as you've had. I've not had time to look into them, but I hope that you've looked at those before going and buying anything new.
 
Jun 3, 2018
3
0
10


I have looked through a lot of things and I can't seem to find anything out of the ordinary. I did go purchase a HDD dock and neither one of the hard drives will read in that either. Which leads me to believe that the hard drive I bought was a lemon, and the original hard drive I have was in fact dead. I think I have another working hard drive laying around that I can try and this will prove my theory out.

Thanks