[axiak]

Hi,

I bought a larger hard drive (went from 200GB to 750GB) on a 4-year-old machine. I consider myself fairly competent when it comes to technology but this one stumps me. (I also suspect a friend's computer is having the same issue.)

Materials involved:
- New WD 750 GB, SATA 3.0
- Computer (AOpen mobo) with ample PSU and has been working with a 200GB Sata 3.0 for 4 years.

So here's the issue:
1) I installed the hard drive. Booted up, BIOS does not detect it.
2) Confused, I tried changing the hardware configuration.
3) At some point, I realized that if I boot up, quickly restart it (i.e. CTRL-ALT-Delete), the hard drive is recognized.
4) I also notice that I can hear a delay between when my computer boots and when the hard drive begins spinning up.

I am currently using the CTRL-ALT-DEL trick, but I'd like to know how to fix it. Once the hard drive boots, everything is great. I get expected speeds, no bad blocks. SMART looks good. Everything. My suspicion is that the old BIOS tries too quickly to detect hard drives, and newer BIOSs are more compatible with very large hard drives that take longer to turn on.

Do you have any theories of your own? If so, how would you go about fixing this?

Thanks!
Mike

 

[Tumbleweed36]

Have you run this drive against the manufacturer's utility? (in this case Data Lifeguard)

Hard Drive Utilities

 

[raptor_pa]

Make sure the PM2 jumper is not set, this will prevent the drive from spinning up when first powered - it will wait for the ATA spin-up command. http://www.wdc.com/en/library/eide/2579-001037.pdf What is the exact model number of the drive?

 

[axiak]

Tumbleweek36: I haven't run the hard drive utility...it apparently requires windows or dos? :-\ I haven't used either OS in 10 years... I will say that I've run badblocks, and that is a very thorough program that checks the health of your drive. Additionally, I ran smartctl (the results are in the bottom of the reply). It claims it takes 8seconds (!) to spin up the drive. ***

rapter_pa: There are currently no jumpers whatsoever on the drive. Should I call customer service? I'll do that when I'm less busy..

-Mike

ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0
3 Spin_Up_Time 0x0027 228 228 021 Pre-fail Always - 8583
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 30
5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0
7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0
9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 106
10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0
11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 28
192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 20
193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 30
194 Temperature_Celsius 0x0022 104 104 000 Old_age Always - 46
196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0