Page 7 of 9 FirstFirst ... 56789 LastLast
  1.    12 Apr 2015 #61

    I'm trying one more time to revive a 320gb Hitachi HD that I believe had flipped PUIS switch by v.9879. At least it shows all the symptoms of it, being revived to work perfectly by booting a Linux disk but then after first shutdown it disappears from BIOS except for a strange line of ------'s.

    I tried to reinstall WIndows 10 latest version per the suggestion to cure it, but it doesn't correct the problem.

    Having read all of the MS Answers threads above about this disaster, I've tried everything that Windows offers to flip the switch back, however the prescribed bootable hdparm tool doesn't even indicate that the PUIS switch has been flipped so it cannot correct it as others have done.

    I am not fluent in Linux but I wonder if others familar with the problem think that the Linux solution offered would work better, and if so I wonder if you could walk me through it. I have GParted booted and am running the Long Test. I now need to run these sudo commands given in MK's Solution given in Build 9879 hard drive disaster (read this) - Microsoft Community:

    Hi all,
    I've pinpointed the issue which is related to this function of HDDs http://en.m.wikipedia.org/wiki/Power-up_in_standby

    Your motherboard doesn't support PM2 and neither does mine.
    You should get your old HDD back as it is OK. Windows haven't broke the hardware.
    Guys in your shop are lame, sorry.

    That's the explanation of what's happening:
    HDD gets power (electric current) but stays still instead of spinning (it waits for ATA signal).
    If your BIOS doesn't support it (you probably get something like "SATA1 0MB") bootloader can't start so Windows won't work.
    On the other hand, Linux supports direct communication with SATA drives so here comes our saviour.
    SOLUTION!

    a) One time
    You can fix it for one time by booting Linux LiveCD/LiveUSB and rebooting - Linux communicates with SATA drives and spins them - after reboot BIOS will detect your WD drive and so will Windows.

    b) Permanent
    (that is until Windows 10 overwrites the setting again )

    Follow the instruction and avoid Sleep on 9879.
    After you boot your LiveUSB/CD:
    1. Open Terminal (Ctrl+Alt+T or Ctrl+Alt+F1 or just click the icon)
    2. Execute:
    sudo hdparm -iI /dev/sd?
    sudo hdparm -s0 /dev/sd?


    hdparm is a Linux tool for configuring HDDs.
    First command displays some info (look for Power-up in Standby on the list - Shift+PgUp to scroll the output).
    Second commands sends disable command to that feature.
    '?' in commands should work as a wildcard but if it doesn't use 'ls /dev/sd*' to find the letter of the HDD (it usually is either /dev/sda or /dev/sdb - but sometimes can even happen to be /dev/hda)

    Credits go to T61T9300 - I couldn't find that command


    Here comes the explanation of what happens in there from the author of HDAT2 http://www.hdat2.com/hdat2_faq.html#q19


    I'm happy to make your 'bricked' HDDs working fine again.
    I have renewed sympathy for those who come to Windows forums and think we're talking another language because I cannot parse the Linux-speak here and can use some step-by-step guidance. I have Gparted now running Full Test.

    Thanks for any help to save my two drives that will not repair with the Windows fixes given in this or either of the two MS Community/Answers threads quoted.
      My ComputerSystem Spec
  2.    12 Apr 2015 #62
    Join Date : Aug 2014
    Australia, Adelaide
    Posts : 1,569
    W7 Ultimate SP1 (64 bit), LM 18.2 MATE (64 bit), W10 Home (64 bit)

    Try this


    Quote Originally Posted by gregrocker View Post
    Thanks for any help to save my two drives that will not repair with the Windows fixes given in this or either of the two MS Community/Answers threads quoted.
    The instructions are a little confusing.

    Here's what I'd try:

    • Disconnect all other HDDs/SSDs (this should ensure that the "faulty" HDD is detected as "sda")
    • Connect the "faulty" HDD to your system
    • Boot up your Live Linux CD/DVD/USB
    • Open the Terminal
    • Type blkid to confirm that you only have "sda" listed (see picture below)
    • Type sudo hdparm -iI /dev/sda
    • Type sudo hdparm -s0 /dev/sda


    Note:
    You should be able to "Copy & Paste" the commands from this post into the Terminal.
    You can type hdparm into the Terminal to bring up a listing of the command switches.

    The first command lists detailed information about your HDD.
    The -il shown in the first command is actually lowercase i and capital i, not lowercase L.
    The "Commands/features section:" indicates if you have "Power-Up In Standby feature set" and if it is enabled. (see picture below).

    The second command sets PUIS to off.
    The -s0 in the second command is actually lowercase s and numeral 0, not capital O.

    Click image for larger version. 

Name:	blkid.png 
Views:	282 
Size:	69.9 KB 
ID:	16663

    I have 4 HDDs in my system (sda, sdb, sdc, sdd).
    3 of the HDDs have multiple partitions.

    Click image for larger version. 

Name:	hdparm.png 
Views:	285 
Size:	46.7 KB 
ID:	16664

    PUIS is not enabled on my "sda" drive.
      My ComputerSystem Spec
  3.    13 Apr 2015 #63
    Join Date : Dec 2014
    Posts : 31
    linuxmint

    Quote Originally Posted by lehnerus2000 View Post
    The instructions are a little confusing.

    Here's what I'd try:

    • Disconnect all other HDDs/SSDs (this should ensure that the "faulty" HDD is detected as "sda")
    • Connect the "faulty" HDD to your system
    • Boot up your Live Linux CD/DVD/USB
    • Open the Terminal
    • Type blkid to confirm that you only have "sda" listed (see picture below)
    • Type sudo hdparm -iI /dev/sda
    • Type sudo hdparm -s0 /dev/sda


    Note:
    You should be able to "Copy & Paste" the commands from this post into the Terminal.
    You can type hdparm into the Terminal to bring up a listing of the command switches.

    The first command lists detailed information about your HDD.
    The -il shown in the first command is actually lowercase i and capital i, not lowercase L.
    The "Commands/features section:" indicates if you have "Power-Up In Standby feature set" and if it is enabled. (see picture below).

    The second command sets PUIS to off.
    The -s0 in the second command is actually lowercase s and numeral 0, not capital O.

    Click image for larger version. 

Name:	blkid.png 
Views:	282 
Size:	69.9 KB 
ID:	16663

    I have 4 HDDs in my system (sda, sdb, sdc, sdd).
    3 of the HDDs have multiple partitions.

    Click image for larger version. 

Name:	hdparm.png 
Views:	285 
Size:	46.7 KB 
ID:	16664

    PUIS is not enabled on my "sda" drive.
    I second the simplified version. The original terminal command "sudo hdparm -iI /dev/sd? will list all the partition details which is very confusing for those unfamiliar with Linux.

    Daniel
      My ComputerSystem Spec
  4.    13 Apr 2015 #64
    Join Date : Nov 2013
    Houston
    Posts : 2,374
    3-Win-7Prox64 2-Win10Prox64

    Yep Greg you might need to take pictures as you go
    I believe this only good for retrieving data from the hdd's anyway at the time you can access it,
    Otherwise the hdd is no good anymore the feature can not be permanently turned off once activated.

    Once 10 is released to the masses as a windows update this will be a blood bath.
    Bricked hdd's ever where.

    Still no response about if ssd's are effected Microsoft has nothing more to say on the subject.
      My ComputersSystem Spec
  5.    13 Apr 2015 #65
    Join Date : Dec 2014
    Posts : 31
    linuxmint

    Quote Originally Posted by ThrashZone View Post
    Yep Greg you might need to take pictures as you go
    I believe this only good for retrieving data from the hdd's anyway at the time you can access it,
    Otherwise the hdd is no good anymore the feature can not be permanently turned off once activated.

    Once 10 is released to the masses as a windows update this will be a blood bath.
    Bricked hdd's ever where..
    Do not intimidate him as I got away by reinstalling Wind 10 (reported earlier) . Do not ask me the exact reason why I got away as I have no clue.
    Greg's harddrive is a small one and it costs little anyway.


    Daniel
      My ComputerSystem Spec
  6.    13 Apr 2015 #66
    Join Date : Nov 2013
    Houston
    Posts : 2,374
    3-Win-7Prox64 2-Win10Prox64

    Intimidate him
    Cheap hdd
    Back when this device was made it was hardly cheap probably close to 100.us
    Now they are cheap 50.us
    Hitachi hdd's were always considered bullet proof unfortunately not win-10tp proof :/

    You did it and don't know how ?
    That's why I said take pictures I guess taking notes would also apply
    Either way sounds like a good time to do both a tutorial might need making because it might come in handy in the near future
      My ComputersSystem Spec
  7.    13 Apr 2015 #67
    Join Date : Nov 2013
    Idaho USA
    Posts : 4,826
    OS X, Win 10

    Quote Originally Posted by ThrashZone View Post
    Yep Greg you might need to take pictures as you go
    I believe this only good for retrieving data from the hdd's anyway at the time you can access it,
    Otherwise the hdd is no good anymore the feature can not be permanently turned off once activated.

    Once 10 is released to the masses as a windows update this will be a blood bath.
    Bricked hdd's ever where.

    Still no response about if ssd's are effected Microsoft has nothing more to say on the subject.
    Please. . .a Blood Bath, give me a break. . .really pushing it to blame Windows 10 for a HDD going bad aren't you.
      My ComputerSystem Spec
  8.    13 Apr 2015 #68
    Join Date : Apr 2015
    Posts : 44
    Windows 7 , 8.1 and Mint

    HDAT or Linux HDPARAM tool works better with Parallel ATA mode than native SATA mode. So trying HDAT/HDPARAM after setting SATA mode to IDE emulation might have better luck in resurrecting the disks - i think.
      My ComputerSystem Spec
  9.    13 Apr 2015 #69
    Join Date : Aug 2014
    Australia, Adelaide
    Posts : 1,569
    W7 Ultimate SP1 (64 bit), LM 18.2 MATE (64 bit), W10 Home (64 bit)

    Quote Originally Posted by Lee View Post
    Please. . .a Blood Bath, give me a break. . .really pushing it to blame Windows 10 for a HDD going bad aren't you.
    It's been happening for months.
    http://www.myce.com/news/microsoft-c...rddisks-73995/
    http://www.msfn.org/2014/12/29/micro...cks-harddisks/

    I'm glad I'm using a VM.
      My ComputerSystem Spec
  10.    14 Apr 2015 #70
    Join Date : Oct 2013
    Penns Forrest
    Posts : 3,506
    Win_8.1-Pro, Win_10.1607-Pro, Mint_17.3

    Quote Originally Posted by lehnerus2000 View Post
    [URL]http://www.myce.com/news/microsoft-confirms-latest-windows-10-technical-preview-bricks-harddisks-73995/[/URL
    Following the MYCE article leads to an answer from Lee Prewitt - MSFT Senior Program Manger, Storage & File Systems

    See post# 2 on: build 9879 bricking drives!!!!

    Quote Originally Posted by Lee Prewitt
    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.

    ...more
    There is a Windows hdparm and there is also KB3021937 for the issue. Depending on the error, you would use one or the the other.
      My ComputerSystem Spec

 
Page 7 of 9 FirstFirst ... 56789 LastLast


Similar Threads
Thread Forum
Build 10158 - loses Office 2016 Preview (no data lost though)
Hi there I needed to re-install Office 2016 Preview again after updating to build 10158. - Didn't lose any data (Outlook 2016 for example uses same data files as Office 2010 which remains installed). Not a serious issue - but could flummix a...
Software and Apps
Solved Virtual hard drive made with partition wizard lost after win10 install
As per title, i have this annoying issue. Having a 3TB hard drive in win7, after partitioning normally the first 2GB of it, i opted to use partition wizard to partition the remaining 1GB of the drive. It did so, i assume, by creating a permanent...
Virtualization
Solved Lost home network in build 10074
I have a home network - not homegroup - that was working fine until build 10074. I have checked the workgroup name and have re shared some files/folders. This Win 10 refuses to appear in the network even on the win 10 pc. Any ideas? Wireless...
Network and Sharing
Build 9879 trashing hard drives!
I'm starting this thread because of the large number of HDDs I have lost since updating to Build 9879. The drives I have lost are all Seagate ST1000DM003 1 TB drives, 2 were VERY new (less than 2 Weeks old) and one was only about 2 Months old. The...
Installation and Upgrade
Solved Updated to 9860 , now missing letters in text
Just changed to 9860and noticed missing letters in plain text, the app names, settings i.e. Mouse button lef rather than left. shows on IE some missing letters while others quite readable. Previous build did not have this problem.
General Support
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 18:08.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums