WDC WD3200BPVT-22JJ5T0 - disk automatically goes to sleep?

[hdd12]

I test my new HDD with WinXP SP2 x86 and also WinXP SP x64. In both OS disk behaves in the same way. Go to sleep (parks head) after some seconds of inactivity. Because if the HDD is inactive for more than some seconds it needs to unpark its head, and that creates a very noticeable lag when launching applications or working with files because the process takes a few seconds to complete.

The systems are newly installed, SMART status GOOD.

On the internet I found similar opinions on this or similar model WD:

• AppleBlowsDonkeyBalls , November 3, 2011 3:31 PM
• New HDD causes general lockups (including mouse freezing!)

This means that it is probably a bug in the firmware.

I have also similar model WDC WD3200BEVT-22ZCT0 and this works well.

Firmware WDC WD3200BPVT-22JJ5T0 -> 01.01A01
Firmware WDC WD3200BEVT-22ZCT0 -> 11.01A11

I wonder if it would be helpful to update the firmware from version BEVT to BPVT?

[data-medics]

I doubt it has anything to do with drive firmware. Probably is a setting in your BIOS.

[fzabkar]

It could be an APM setting or the idle3 timer.

http://sourceforge.net/projects/apmtimer/
http://idle3-tools.sourceforge.net/
http://www.alexsoft.org/viewtopic.php?f=36&t=125&p=153

A possible workaround is quietHDD:
https://sites.google.com/site/quiethdd/

[data-medics]

Could be. I'd still check BIOS first.

[fzabkar]

@hdd12, you could use SeDiv to retrieve the resources (ROM and SA firmware) for your two drives.

http://sediv2008.narod.ru/Easy3.9Passwo ... 567890.rar
http://sediv2008.narod.ru/Settings.rar

We could then compare the contents of MOD 02. That's where the timer values are stored.

[hdd12]

OK, quiedHDD resolve problem

"wdidle3" detect HDD, display and set Idle Timer but this does not affect the operation of the disk.

[fzabkar]

The APMtimer project should provide a nonvolatile solution to your APM problem. You would need to execute it from a Linux platform, though.

[hdd12]

The APMtimer project should provide a nonvolatile solution to your APM problem. You would need to execute it from a Linux platform, though.

OK, but on http://sourceforge.net/projects/apmtimer/ writes that this tool is made for Western Digital 2.5 WD*PVX Hard Disks

Are you sure I can use this program with my drive BPVT?

I not understand how work this tools?

I know there is such a thing as PCI Configuration Space where various parameters are set PCI devices are on only until you cold start the computer.

AFAIK, PC BIOS e.g. AWARD can set some PCI config space of some PCI devices (e.g. write protect off for programming BIOS chip with AWDFLASH) - as a result, every time you start your computer (even cold) setting write protect off is set.

quietHDD set APM whenever boot OS WinXP

Where APMtimer store settings?

[hdd12]

I test APMtimer. I have to say that it does not solve the problem
APMtimer works like wdidle3 - read, set and disable timer but this not affect the operation of the disk and heads still parking - of course in WinXP

Code:

root@debian:~# hdparm -I /dev/sda | grep "Advanced power"
   Advanced power management level: 96
root@debian:~# ./apmtimer -g /dev/sda
APM timer is disabled

Only quietHDD initiated over 'Run' registry key in WinXP resolve problem.

Maybe tools 'wdidle3' and 'apmtimer' work only on systems for which they were created - DOS and Linux?

[beLIEve]

They patch the firmware of your hard disk and it's persistent across OSes.

It appears that your APM is still at 0x96 despite having the timer removed. I only managed to test with a limited number of hard disks when I wrote the program. I still remember there is an additional 2 bytes after the timer (Franc if you still remember, initially I said 32 bits, and then later on I changed to 16 bits) that is related to spin-down, and if they're non 0x0000, APM goes to 0x96.

I do not have any WD3200B*VT to test with. My WD3200BEKT shows 0x00000000 in the APM location. My old WD5000BEVT made in 2010 does not have this setting while a WD5000BPVT made in 2012 also show 0x00000000. First 2 bytes are timer, last 2 bytes are spin-down.

It'd be very useful if you could dump out your Mod02 (you can mask your serial number) for us. And listen to your hard disk carefully to see how long it takes after the last access on the hard disk before you hear the minor click.

[beLIEve]

The closest I could find, http://files.hddguru.com/download/Non-P ... 4K%20ROYL/ shows only the timer present @ 0353h, 0xC8 == 200 ms

[hdd12]

I dump (ModuleByID 0002.bin) of my disk. In offset 353 is BA value (186 DEC)

Attachments

0002.zip

(1002 Bytes) Downloaded 857 times

[beLIEve]

No, you shouldn't compare your offset with the one from a different hard disk. The one I gave is only applicable for that hard disk. From what I've learned, even hard disks with the exact same model could have different Mod contents and size.

Anyway, for your Mod 02, I can see that there is no APM timer nor spin down (03A8h-03ABh). Do you remember if there was any value before you patched it?

Your Idle3 has a value of 0x50 (offset 0388h) == 80 == 8.0 seconds. You might want to consider patching it with wdidle3.exe or idle3-tools and see if the intellipark feature gets disabled. And of course share with us if the APM goes to 0x80 after that.

Some corrections to my earlier comments :
1. 0x96 should be stated as 0x60 (96 decimal, not 96 hex). If you get 0x80 (== 128 decimal) then the intellipark feature should be disabled.
2. 200 ms should be stated as 20.0 seconds

[hdd12]

Do you remember if there was any value before you patched it?

When purchase the hard drive I changed the value of Idle Timer several times with wdidle3. The default value of Idle Timer was 3.000 s. I changed to 60s, disable and now set to 8s because this is the minimum that can be set using wdidle3:

Code:

wdidle3 /s8

Next i use APMtimer to disable APM timer:

Code:

root@debian:~# ./apmtimer -d /dev/sda

[beLIEve]

Yours seems pretty unique to have 3 seconds for idle3.

Can you help to observe how long it takes before the hard disk goes to sleep? Access the hard disk, listen and start counting (check your computer's clock) until it goes to sleep.

[hdd12]

OK, but I have to turn off the first quietHDD. I use hdparm for Windows:

Code:

hdparm -i /dev/hda

• while quietHDD working in tray, heads no parking:
  

  Code:

  AdvancedPM=yes: disabled (255) WriteCache=enabled

• exit quietHDD and restart Windows, heads still no parking:
  

  Code:

  AdvancedPM=yes: disabled (255) WriteCache=enabled

• power OFF PC and power ON after few minutes, heads parking after 8 or 20 sec. and APM is unknown:
  

  Code:

  AdvancedPM=yes: unknown setting WriteCache=enabled

Last edited by hdd12 on October 16th, 2014, 22:04, edited 1 time in total.

[beLIEve]

8 seconds should be due to idle3. So you need to disable it first and then repeat the test again. You need a power-cycle the hard disk (or computer) before these settings take effect.

Can you check the APM again after that, and if it's still unknown, try with Unix.

[hdd12]

After disable Idle Timer with wdidle3, power OFF and power ON PC hdparm still display unknown APM:

Code:

AdvancedPM=yes: unknown setting WriteCache=enabled

Exactly the same shows hdparm in Windows and Debian - unknown setting

Heads parking about 20 sec. after idle time.

[beLIEve]

Thanks. I'll have to inspect your Mod 02 further to see what else can we do.

Do you recall the value of "apmtimer -g" before you made any changes? If we can undo that change, you should get back your APM value.

[hdd12]

I do not remember, unfortunately, probably 127 or 128, I'm not sure. hdparm -i /dev/hda display the same value APM that set quietHDD but APMtimer set other APM value - right?