HDD won't show up

[Rubnik]

So I've got an SSD drive for OS and storage, and a Toshiba DT01ACA200 2TB HDD for storage. I've been using these two on my system for over a year now without any problems.

A few months now, my HDD does not appear after booting with Fast Boot or MSI Fast Boot. With normal boot it does appear on Windows Explorer and works fine, but if my pc goes to sleep, on wake, my HDD disappears again.
When the HDD does not show up, in Device Manager it's listed as Unknown Device under the Disk Drive section. In Disk Management it shows up as Disk 1 (Unknown, Not Initialized), asking me to initialize it in MBR\GPT resulting in an error afterwards.

Using my trusty stethoscope, with fast boot on, the HDD does not spin, resulting in a long boot screen and then logging into Windows with the HDD disabled.

I've tried using different SATA cable and sata power cable but did not help. I tried installing an OS on the HDD and worked fine every time,plus, when using it as a storage drive, when it does appear, it seems to work fine.
Any thoughts?

I'm using
Win 8.1x64
MSI Z87 G45
i5 4670k
8 Gb Corsair Vengeance RAM
MSI GTX 770
EVGA G2 750W

 

[Kursah]

Have you checked the SMART data for the HDD? Use Crystal Disk Info or Speccy or similar to check that out.

You say the drive doesn't spin up at times...it should always spin up on initial power on, at least that's been my experience with mechanical drives. But the fact you have no issues when using it as an OS drive makes me question that logic...

I would say disable fast boot if that is causing issues. Fast boot, at it's fastest settings is supposed to skip non-bootable drives until the OS loads so there could be an issue with the firmware or chipset there that's causing part of this issue.

That still goes back to the drive not spinning up though...with or without a data cable connected, upon initial power on, the drive should spin and perform it's own POST before idling back down if no requests are populating its queue.

Can you verify the drive is seen in UEFI when it's not being seen as a formatted and populated drive in Windows?

I would check the drive's SMART status list, if good, update chipset drivers and UEFI if possible. I am questioning the drive or chipset on this issue.

What port are you using for the data drive? Is it using the same chipset driver as the OS drive. I know many boards come with an extra chip for extra internal SATA ports, and most of those extra chips suck and cause issues/headaches.

 

[Ferrum Master]

Did you try WIN10? Sounds like PUIS enabled.

 

[Rubnik]

I will check SMART data later today and let you know.
I had fast boot disabled, so that i wouldnt encounter that problem, but even with fast boot disabled, the HDD disappears after sleep, which is bothering me.
Whenever I enter UEFI, the drive is detected.
I'm using the second SATA port, which i guess is on the chipset and not on another controller.

I forgot to mention this problem might have started shortly after installing Win 10 on another SSD and importing the HDD onto Win 10. So i had my regular Win 8 OS and switched to Win 10 to try them out. I removed the Win10 SSD after a day though, didn't try them out much.

One more question, is it normal for the boot order to be like : 1) UEFI Hard Drive and then in drive priorities only Windows Boot Manager listed instead of like Samsung EVO SSD, in the UEFI?

 

[Ferrum Master]

then it is PUIS switched on, a common problem.

KB3021937

Your options.

1. Linux.

sudo hdparm -iI /dev/sdx
sudo hdparm -s0 /dev/sdx

where x stands for your disk letter.

2. HDAT2 burn an CD boot it and disable it in features.

3. On windows download hdparm exe

To use hdparm:

1. Download the hdparm installer for your architecture (32-bit or 64-bit) from http://disablehddapm.blogspot.com/
   
   
2. Install hdparm with the installer you downloaded above.
   
   
3. Start Disk Management (WIN+X, then K).
   
   
4. Determine which disk # maps to the disk that needs PUIS disabled.
   
   
5. Run an elevated command prompt (WIN+X, then A).
   
   
6. In the command prompt, run the following in order:
   1. cd %systemdrive%"\Program Files (x86)\hdparm"
      
      
   2. hdparm.exe -s 0 hd[a-z]
      1. [a-z] is a single letter that maps to the disk number. E.g. if your disk # is 0 then you would use “hda”, if your disk # is 1 then you would use “hdb”, etc.

 

[Rubnik]

I believe your suggestion fixed it.Gonna try a few more boot ups just to be sure
Sorry for not mentioning Win10 earlier.Asked a few weeks back on another forum and was led to believe that it probably was irrelevant.

 

[Ferrum Master]

Asked a few weeks back on another forum and was led to believe that it probably was irrelevant.

If you use the beta branch be ready for everything. And MDL forum is one the best sites for windows beta knowhow build up. I learned it the hardway, as I got the problem pretty fast when no info was available yet.

I got the same with my DM crapcuda at work, not that I did wonder that it could simply die as it is DM001, I just was too bonkers, swapped the logic boards and resoldered eeprom and the same problem, then and threw it up the COM port for debug at putty terminal and it spun up and worked, then I understood - it was something else.

A combination of lousy bios and beta OS and some peps at MDL reported soon it too, booted up Linux and solved everything.