Windows 10: I lost 2 Hard Disks after updated from Build 9860 to 9879

It's all good Bill I saw Linux and thought you might of been asking me *Wink
Cheers.

 

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:

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 *Biggrin)

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 HDAT2 FAQ


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.

 

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.




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





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

 

Yep Greg you might need to take pictures as you go *Smile
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.

 

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

 

Intimidate him *Confused
Cheap hdd *Confused
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 *Tongue
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 *Wink

 

Please. . .a Blood Bath, give me a break. . .really pushing it to blame Windows 10 for a HDD going bad aren't you.

 

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.

 

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.

 

Thanks Peter. I'm on this today.

Mike, this only pertains to Build 9879 from all reports linked earlier above.

Anshad, this older backup eMachine 5234 BIOS has no SATA controller setting, though it has tons of other settings which are barely recognizable to me even after parsing lots of BIOS. Any suggestions, or would you like pictures?

Daniel, it killed two of my Hitachi drives which I'd like back since I don't give up easily. *Huh This also has become a bit of an obsession and I have the luxury of free time to test and experiment while I'm home for the next month. It just means a dozen of my cases have to wait longer at 7F.

Bill, hdparm switch has been tried as related earlier. It says it was never flipped in the first place. The KB is incorporated into the latest Win10 version which I reinstalled for the purpose of curing the HD but which also did not work past the first reboot.

 

*Dinesh*Dinesh*DineshVICTORY! *Dinesh*Dinesh*Dinesh

Thanks Peter! I followed your Linux Terminal steps which finally recognized in hdparm (unlike using it in Windows) that PUIS was set, and then that it was set to Disabled (O). Drive since has rebooted many times unlike before where it would fail after each reboot.

Only hitch was that it wouldn't take sudo on each command, saying it didn't recognize it. Could it be this is because all GParted has is LX Terminal? I wouldn't know it from LAX Terminal.

Anyway, I'm stoked because I have a 500gb drive back just at the time a 320gb is dying out fast in our home backup machine here and I'm leaving for six months.

Thanks everyone for chipping in, especially for the Linux translation. Hopefully it will help others as I see in the big threads on this online that some have given up. I wonder if the commands are not working for them as they didn't for me a dozen times.

This is for you, Peter, for many years of excellent help to others. Thanks for helping me stretch my abilities.

[youtube]J16lInLZRms[/youtube]

 

Modern laptops usually won't have that SATA mode control settings anymore - except on some business class models. Do you have access to a desktop by any chance - may be a friend's machine ?.

 

It is a desktop,. I tried to change to IDE to run Hitachi Drive Fitness Test but cannot find that setting, just dozens of mostly unrecognizable ones.