Disk not detected on first boot, but detected on reboot

Bikonja

Reputable
Jun 16, 2014
20
0
4,510
Hi, I installed a new motherboard (ASUS M5A97 R2.0) and a new SSD. I have a few hard disks, one of them being a Samsung Spinpoint F1 1TB.
I discovered that my computer now consistently behaves this way:
When I boot the computer from powered off state, the Samsung disk doesn't get detected (neither if I go to BIOS and look for it or if I let Windows boot), however, if I restart my computer (even if I enter BIOS or just plain restart it before it even boots) the Samsung gets detected in both BIOS and Windows and works normally.
Thinking maybe it took it's time to power up I tried setting my BIOS to have the maximum POST delay time (10 seconds) and disabled fast-boot, but that didn't help.
I still suspect that for some reason the Samsung doesn't get a signal to turn on on first boot, but I have no idea what to do about it or whether I'm right. My other disks are all WD (other than the SSD which is a Kingston) so it might be a Samsung thing. They're all SATA disks and my optical drive is also on SATA since the mobo doesn't have IDE.
Has anyone seen this problem? Anyone know a solution or has any ideas what to try?
 
Solution
I would begin by updating the motherbds bios
http://www.asus.com/Motherboards/M5A97_R20/HelpDesk_Download/
Followed by checking for a firmware update for your SSD.

I know the f1's had a firmware update back in late '09(I still have 3 running just fine) but didnt find it on seagates newer samsung site :-(
Hi,

Have you tried using another sata port ?

The last time I had this problem is that my drive was failing. Not much to do except when it fails
although Samsung SSD are really good usually.
Check to be sure that the power cable and sata cables are in good condition.
 

popatim

Titan
Moderator
I would begin by updating the motherbds bios
http://www.asus.com/Motherboards/M5A97_R20/HelpDesk_Download/
Followed by checking for a firmware update for your SSD.

I know the f1's had a firmware update back in late '09(I still have 3 running just fine) but didnt find it on seagates newer samsung site :-(
 
Solution

Bikonja

Reputable
Jun 16, 2014
20
0
4,510
First of all, thank you for your replies!

@dextermat
I haven't tried another port since all my SATA ports are in use and every other connected device runs perfectly.

Keep in mind that I've been runing this drive fine for about 2 years as my system drive, than changed my motherboard and all of a sudden now it behaves this way.

The SATA cable is brand new and the power cable is the same power cable that powered the drive for those 2 or so years. I've triple checked the connections to make sure none of them are loose.

Also, the SSD is Kingston, the "problematic" drive is Samsung.

@popatim
Motherboard BIOS is up-to-date (actually came up-to-date which was a shock :)), but didn't think to look for an update to the F1, will try to look for it and post back with results.

EDIT: New Samsung HDD firmware fixed the problem! Thank you so much!
This is where I downloaded it from:
http://knowledge.seagate.com/articles/en_US/FAQ/223631en