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

That's normally correct but I've got a Seagate HDD right now which can be seen in the BIOS, yet when I boot up on Seatools it won't finish booting because it says I haven't got a Seagate HDD, go figure.

 

Thankyou BillyBob and gregrocker for you comments.
I tried all that with the Hitachi on USB and separate power on my other PC to no avail. I will not try 9879 and wait for the next release and install when it is considerate to be stable.
As a Win 8.1 user, Windows 10 looks great - just needs the bugs sorting.

 

I had the same issue, however, I lost 2 drives on two different machines.
I have 2 machines that I use for "play with/experiment", a Gigabyte GA-Z68MA-D2H-B3 w i7-2600 cpu & 16 GB memory, and a Gigabyte GA-X58A-UD3R with i7-930 cpu & 12 GB of memory. Both machines have Kingwin 3.5 Internal Tray-less Hot Swap Racks.
Both machines had (for C:\ drive) brand new Seagate ST1000DM003 1 TB hard drives.
Everything was fine for some days, however, after updating to Build 9879, I lost both C: Drives.
Neither would boot after shutting down overnight and nothing I could do helped:
Boot the machine up with Win 8.1 Pro or Win 7 Pro and the drive(s) would not be recognized until after an excessive amount of time.
I tested both drives on my main computer (Win 7 Pro) that I don't experiment with and I finally got SeaTools for DOS V2.23 to recognize one of the drives, however, ALL tests would fail.
One drive was only 2 Weeks old and I took it back to the store and exchanged it.
The other was 2 Months old, so I got a RMA from Seagate to replace the drive.
Has anybody else seen this?
Anybody have any ideas what is causing this and what the fix might be??

 

Yes faced same issue and finally after much of R&D and wasting 2 days came up with solution : -

1) DL hiren CD.
2) Boot up mini XP.
3) Disk manager > Format it (For me primary didn't work so i formatted it to extended NTFS).
4) Get WINXP CD and install it.

And all done.. After installation u can reinstall any OS u want ...

Though i tried installing 9879 build again and faced same issue now will again format HDD once i reach home..

 

Guy I need help, My HDD (Main one) disappeared after that stupid auto update of new TP build at night. TP is on separate SSD and other HDD is my main HDD with windows 8.1 on partition 1 and my data on partition 2. How do i get back my HDD.

It is a laptop i bought recently, i dont even know what brand HDD it was. Now I am pissed and don't know what to do, the HDD don't appear in Disk management.

Please help *Sad

 

Thanks for the info o0k00l and I will download and inspect those files, however, since none of the Seagate tools (SeaTools for Windows or SeaTools for DOS) was able to handle the issue, I've already exchanged one at the store and the replacement from Seagate will arrive today.
Note that Seatools for Windows (latest version) would not recognize either of the drives. Seatools for DOS (V2.23) did recognize one drive, however, all repair/reformat operations failed with seagate failure codes.
If I have the same issue happen in the future, I'll give these utilities a try, however, if I do lose another drive(s), that will be it the last time for the Tech Preview until it becomes more stable and no more of these issues show up.
Also note that when I experiment with new systems, I do so with a dedicated hard drive(s) and NEVER attempt to install as dual boot with my daily machine!

 

Check again scrolling down in Disk Mgmt to see if it is there but needing a drive letter assigned. Drive Letter - Add, Change, or Remove

BOot into BIOS setup to see if the HD is detected there. most often by Serial you can google to find make/model, and if not reseat it in its compartment to try to get it detected.

If it's detected in BIOS and still not seen by Windows then boot the maker's Hard Drive Diagnostic Procedure extended CD scan to see if it detects the HD

 

Might be wroth looking into this thread,
https://www.tenforums.com/general-dis...lder-hdds.html

 

Does this mean that failures have been due to Power-up in standby (PUIS) on motherboards that don't support this feature.

For those of us that have been fortunate enough not to have experienced this, does it mean that we likely won't or is it just a matter of time.

Is this another Microsoft 'trick' like Hybrid Boot used in Windows 8/10 to provide faster shut down/reopen where the system left in an hibernated state, with the drives mounted, open and ready to take off as soon as Windows 8/10 restarts.

 

Hi guys, I have had the same problem since I updated to 9879. I have a Samsung 120 GB SSD as Disk 0 and a Seagate 1 TB as Disk 1 with D: and E:
After updating to 9879 Disk 1 disappeared.
Disk Manager shows Disk 1 as not active, when I tried activate I got a 0/1 error.

Downloaded Sea Tools for Windows to try and repair the disk but the program could not find the disk ...
Started the Samsung Magician who could see the disk but do not read it ... more shit.

Today I downloaded Xubuntu 14.10 to see if I could see the disk in Gparted, when I had prepared the USB stick and was restarting, Windows wanted to do an update, ok let go I thought, and started again from the hard drive, and believe or not but there were Disk 1 D: and E: as usual.

Im not sure if the update fix the problem or what but my Disk 1 is back with all my music and movies.

 

And just lost a 3rd Seagate hard drive! :-(
2 things in common with the failures, Seagate ST1000DM003 and Win 10 Tech Preview Build 9879.
While I have been able to get the drives replaced rather quickly (2 exchanged at the store and one from Seagate), That is ENOUGH for me. I am quitting participation in the Tech Preview program until such time as it gets less destructive to hard drives and these posts start slowing down.
I have found (on the internet) references to that family of Seagate drives failing with firmware below a certain level (CC4G) and the drives that I have are all below that level, I am going to update all of those drives to the recommended F/W level (CC4H), however, I will no longer be placing any drives in jeopardy by continuing with the Tech Preview program.
If anybody actually figures out what is causing these failures, I would appreciate the solution being posted prominently In this forum (Installation & Setup).
Thanks all & I'll keep a watch out!

 

After posting that last, I had ANOTHER ST1000DM003 1 TB Seagate fail!
o0k00l had a suggestion about downloading hiren CD, booting mini XP and using its Disk manager to try and fix the drive, well, it WORKED!
I'm going to start another thread specifically warning about Build 9879 and the LARGE number of hard drives that are failing/being trashed by this build.
In the meantime, I modified my Win 10 setup to use older WDC drives and only stick with one install.

 

There must be some fundamental flaw in filesystem management in Win10 TP. I've been getting boot failures and forced CHKDSKs for some time, now. I have Win10TP installed on a Crucial SSD -- which worked without any incidents when I was running Windows 8 on it. When I upgraded to Win8.1, I also migrated it to a new Kingston SSD, and put the Crucial on a shelf.

When Win10TP came out, I took out the Crucial, reconnected it, reformatted it -- and installed Win10 TP on it.

While it worked OK for a while, I started getting error messages booting Win8.1 about needing to check the filesystem in use on Win10 TP. Since upgrading to the current build, I get these errors now nearly every boot, so much so that I routinely run CHKDSK on it from Win8.1 before I reboot into Win10.

I should also mention that I ran some Linux distros on the same SSD for a few months -- and had absolutely no filesystem problems with them, either.

I find it hard to accept this is strictly a hardware problem with Crucial SSDs when, out of four different installs on this same SSD, the ONLY ONE that has problems is Win10TP.

 

I also find it hard to accept these problems.
The two systems I am using for testing are:
1. Gigabyte GA-X58A-UD3R MB, i7-930 CPU, 12 GB Memory
2. Gigabyte GA-Z68MA-D2H-B3 MB, i7-2600 CPU, 16 GB Memory
Both systems use KingWin KF-1000-BK 3.5" Internal Tray-less Hot Swap Racks, 1. has 3, 2. has 4
OSs used include:
- Win 8.1 Pro
- Win 7.0 Pro
- Linux Distros
-- CentOS 6.6 & 7.0 (Red Hat Enterprise Linux clone)
-- Scientific Linux 7.0 (Red Hat Enterprise Linux clone)
-- Fedora 20 & 21 Beta (RHEL bleeding edge development)
To change the OS, simply shut down the existing system, remove the HD, insert other HD and boot up - New system!
While I have lost a hard drive "occasionally" (probably 1 every 3-4 years!) I have been simply astounded by number of issues that Windows 10 Tech Preview have unleashed on the community!
As far as I'm concerned, this is entirely due to the attempt to use the "Power-Up In Standby" (PUIS) feature that apparently requires the MB support, Drive Support as well as OS support.
A Drive with that feature "enabled" and plugged into an external docking port simply "DOES NOT SPIN UP". It takes inserting that drive into a linux machine and disabling as shown in previous posts, then, it either works fine or "requests Scan & fix" and is OK after!
Another thing that can't be stressed strongly enough to anybody contemplating testing this system - DO NOT USE ON CRITICAL DATA". In other words, if you can't afford to lose it, DON'T DO IT!
I'm going to post this here (I lost 2 Hard Disks after updating from Build 9860 to 9879) and (Build 9879 trashing hard drives!) to get the most exposure.

 

I also think this is related to fast startup as I get Disk Checks on irregular startups. I also notice this can be turned off in Settings and wonder why it's even needed as opposed to using Sleep and Hibernate. I realize it's a Windows 8 thing so am not that familiar with it yet. *Huh