build 9879 bricking drives!!!!

from the beginning of the win 10 tp program:

thinkpad T61 with hgst 7k1000. build 9841 worked. build 9860 worked with a couple of problems which were reported/resolved.

installed build 9879.

all updates to builds have been installed.

at the first wake from sleep event, BIOS could not find the HDD, specifically error 2100. tried to get drive back to life in several computers, using several differnt techniques; its bricked, does not spin up does not respond to commands, nothing can see it.

found another drive same hgst 7k1000 model. repeated above. HDD number 2 is now bricked too.

switched to a thinkpad T400 and yet another hgst 7k1000. repeated install as above. HDD number 3 is now bricked too.

have NEVER before in  many many years experienced a travelstar failure.

this is a $erious issue that needs attention ASAP. microsoft please respond!!

 

Question Info


Last updated April 19, 2019 Views 25,484 Applies to:
Answer
Answer

We are sorry to hear that you are having issues with build 9879 of Windows Technical Preview.  As part of our expansion of the Instant Go feature to devices with Hybrid Hard Drives (drives that have both SSD FLASH and spinning media) we added a command that turns on the drive’s Power-Up in Standby (PUIS) feature.  This gives more power savings.  In this mode, the drive does not spin-up when power is applied, but only once it receives a spin-up command.  This command is sent by the system’s BIOS during startup or on resume from Sleep/Hibernate.  

 

It turns out that there are a few BIOS implementations that do not send the needed PUIS spin-up command and we had a bug in which we enabled PUIS not only on Hybrid Hard Drives, but on all Hard Disk Drives (HDD).  Because those BIOS implementations do not send the spin-up command, they either are unable to identify the drive during boot and ultimately fail to start Windows or are unable to find the drive during resume from Sleep/Hibernate and the machine freezes.

 

The system must have the following configuration to hit this issue:

  1. The drive must be a SATA HDD.

  2. The drive must support Power-Up in Standby (PUIS) where the HDD keeps its platter spun down when the disk gets powered up.

  3. The system must be running the in-box SATA driver, StorAHCI.

  4. The system is running the Windows Technical Preview build 9879.

  5. The system BIOS does not send a spin-up command after power on and/or after resume.

 

There are two possible symptoms, each of which is dependent upon the BIOS:

  1. On powering up your system, depending on your BIOS, you see a message saying; “No boot device…” or something similar.

    1. This occurs when on boot the BIOS does not issue a PUIS spin-up command to the HDD before querying for Identify Data.  Thus, the HDD does not return enough data for the BIOS to properly identify, initialize, and ultimately boot from the HDD.

  2. The system boots without issue but hangs (spinning dots) upon resuming from sleep or crashes with a d1, 7a, or 7b error code.

    1. In this case the BIOS *does* send the PUIS spin-up command on boot.  This distinguishes it from symptom #1.

    2. This issue with resume from sleep occurs because the BIOS doesn’t issue a PUIS spin-up command upon resume, either because it can’t or it simply doesn’t.  The Microsoft inbox SATA driver fails to start the drive’s port because the disk is spun-down.

 

We have a fix ready and it is a part of KB3021937.  If you are experiencing symptom #2, then you will need to download and install the KB, keeping the computer awake through the whole process.  If you are experiencing symptom #1, you will first need to get PUIS disabled on the HDD to allow it to boot.

 

The best way to do this is to use a 3rd party tool that can turn PUIS on and off such as the hdparm Tool for Windows.

 

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.

 

Note: if you can’t get your system to boot, then you will need to remove the disk from the current system and install it into a separate system and run the tool on the drive there.

 

Sincerely,

The Windows Storage Team

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Answer
Answer

fired up 9879 again with the the temporary HDAT2 puis fix.

downloaded hdparm for windows from this link:

http://disablehddapm.blogspot.com/

installed hdparm package per instructions.

run command prompt as administrator.

CD'd to the installed hdparm.exe location.

entered command 'hdparm -I /dev/hda'. sure enough PUIS is enabled.

entered 'hdparm -s0 /dev/hda' to disable PUIS.

reentered 'hdparm -I /dev/hda' several times over next hour. PUIS remained disabled.

shutdown system. powered up system.

bios found HDD and 9879 booted back to desktop.

but of course somewhere in the process of starting up PUIS was reenabled.

system has been running for over an hour and PUIS still disabled.

perhaps one or more CMD scripts to automate the process of disabling PUIS at boot, etc.

machine is thinkpad t61 T9300 cpu hgst 7k1000.

system currently set to never sleep. HDD set to never spin done.

more testing needed to explore outcome using other power configuration settings.

2 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.