WD Drive not detected in BIOS after removed from Highpoint RAID - how to reset PUIS (PM2)

[shafoo]

Hi,

it seems WD thinks there is no solution to the PUIS problem caused by using staggered spin up on drives in a Highpoint controller.  I spent a day or so finding a solution.. no thanks to WD.  The other post on this forum seems to conclude there is no fix.  So see the my post below on HHDGuru (as shafoo) along with the script etc from guru in the same thread.  See http://forum.hddguru.com/wd5000aavs-pm2-puis-activated-unable-revert-t19107.html

Please spread the word and save a lot of people a lot of frustration and dead drives!!!!

And I ask the question, "When will WD and Highpoint fix this problem, it has been around for years! They could at least tell people how to fix it instead of just RMAing drives!!!"

My message is copied here so that searchs will find it.

Hi,

this post gives some clearer instructions on how to do this using the script files provided by Guru in the following discussion
http://forum.hddguru.com/wd5000aavs-pm2-puis-activated-unable-revert-t19107-20.html 
in puis.zip (also attached here for simplicity - thanks guru).
Please note, guru says
"As the weather is nice and I am in a good mood
Use the script and .bin file with MHDD.
I cannot support this and will not accept PM's )
This is a hack but it does work ( I have tested it)"

I used this successfully to reset drives that had been PUIS'd by my RocketRaid RAID controller.
My drives were WD10EACS 1TB WD Green drives but the original post worked on 500GB drives.
So, I am assuming it will work on most WD drives.

The problem I had was trying to run the script as a BATCH file, which is the impression the thread gives...
The main trick is to put the files from Guru in to the script sub-directory and then run using .puis.
Nobody seems to say that to run a script you should use type .scriptname once you have selected the device.
(So, I will say how to run a MHDD script here so that this post comes up in searches)

Pre-reqs:
 You will need to use version 4.5 of MHDD to run the script.
 A Mint Linux (or others may work) boot CD will help - to get the drive to spin up initially.
 A floppy disk drive or vfd (http://sourceforge.net/projects/vfd/) and Nero (or similar) to make a boot CD.

Please check that you don't have the PUIS/PM2 jumper set on your HD!  This will overide the software settings...

Method:
 Insert a floppy in to your drive or make a virtual floppy using vfd.
 Make a bootable floppy of MHDD - using the bootable floppy version of the MHDD download
 Extract the two files from the puis.zip file in to the script directory of the MHDD.zip file on the floppy
 If you are using a real floppy you can reboot to the floppy, otherwise you need to make a boot CD from the virtual floppy using Nero.

As the drives show up as blank in BIOS (if not spun up) then it is hard to identify the right drive for fixing.  So, I recommend shutting down, attaching the problem drive and uplugging the sata cables from other drives for extra safety.  Then boot up to your Linux Mint CD and Mint will detect the drive and using Gparted you should be able to see it as an unpartitioned drive.  No need to do anything to it now.  The trick is to now reboot (without powering off) and swap to the MHDD boot CD.  You should notice that the drive now shows up in BIOS which is good for a start

Once in MHDD you can select the drive by typing in the drive number from the list.
Then hit F2 to see the drive info if you want.
Then type in .PUIS to run the script.
Then you just need to type 1 to accept and it will spin up the drive and reset the PUIS setting

Then shutdown (full power off computer) and turn on again to check that the drive now spins up and identifies in BIOS

HINT:  To make life easier, I used an external sata caddy and once I new the drive number could power down the caddy down and change drives, then power up and select the drive number again and run the .puis on the next drive.  Worked a treat

I have spent a whole day getting to the bottom of this problem and feel quite annoyed by the lack of knowledge shown by both WD and Highpoint.  I hope my post helps save a lot of time for other people with the same problem.

NOTES:
For info on PUIS you can check the wiki at
http://en.wikipedia.org/wiki/Power-up_in_standby
It seems that the highpoint controller puts the drive in to PUIS mode but can't (or won't) take them out again.
This little script does the business.
It is interesting to see all the drives that WD simply RMA's and that WD doesn't provide a solution!  They (WD and Highpoint) don't seem to know it can be fixed!  I would have thought they could have made an automated version of this process on a bootable .iso to allow people to quickly fix the issue!!!

More keywords for searching
Drives not identified in BIOS
WD drives don't spin up after removal from Highpoint RAID 23xx 2300 2310
WD PUIS problem
WD PM2 problem
Reset WD PUIS
How to reset WD PUIS

[fzabkar]

You say that your drives were "WD10EACS 1TB WD Green drives".

Did you try disabling PUIS by means of standard ATA commands using a utility such as HDAT2 or Hitachi's Feature Tool?

The particular WD model in the HDD Guru thread was affected by a firmware bug which prevented the ATA commands from working as they should have. Normally, subcommand code 06h of the ATA Set Features command enables PUIS. Conversely, "subcommand code 07h shall cause a device that has powered-up into Standby to go to the Active state". AIUI, subcommand 06h works correctly, but 07h does not.

See sections 7.48.7 and 7.48.8 of the following document:

Working Draft AT Attachment 8 - ATA/ATAPI Command Set (ATA8-ACS):
http://www.t13.org/documents/UploadedDocuments/docs2008/D1699r6a-ATA8-ACS.pdf

The solution at HDD Guru involves the use of WD's vendor specific ATA commands. These are proprietary, and are not part of the standard.

[fzabkar]

Sorry, I goofed. I should have said that "subcommand code 86h disables the PUIS feature set". This is the command that is affected by the bug, not the spin-up command (07h).