Windows 7 hangs at start after adding new drives to new build.

CWR63

Honorable
Mar 18, 2014
38
0
10,530
These are my specs:

Trophy Wife

Following the Newegg first PC build videos I assembled my rig as shown, pre installing the SATA data and power cables so I can later install the HDD from my old machine. Decided later to use my Seagate backup drive to transfer my old data instead, but those cables are still attached to the PSU and mobo respectively - in case that has any bearing on my problem.

All three drives are hooked up by SATA power and data cables, I then disconnect the data cables from the Crucial 1 TB SSD & WD 3 TB HDD (cache and archive drives) leaving the Samsung connected so the OS (Windows 7 Pro 64bit) will only be loaded on the fastest boot drive.

After installing OS, updates, drivers and the like everything's fine, so it's time to reconnect the data to the other 2 drives so I can make a backup image of my system to store on the archive disc like the video says to do. Power off, allow everything to fully power down, turn off PSU, let all residual power die down, wait some more for good measure, put on static discharge leash clipped to PSU riser - push clips into drives, then carefully reverse the steps to power on. I'm taking no chances.

Starting Windows animates in slow motion to a blank dark screen and hangs there. Let it run for a half hour to see if it comes out on its own, then reboot and go into BIOS, sometimes it shows the just the boot and optical drives in the drive list and the bootable drive list, but not the other 2 drives; other times it shows the 3 SATA drives in the drive list, nothing in the bootable list, and the optical drive is not shown at all (it is an external USB 3.0 drive which the BIOS may only detect when it's in a USB 2.0 slot).

Whenever I disconnect the 2 drives data cables again, everything's fine again. I think they were disconnected during power up tests, but if they weren't maybe one of them has a boot quadrant?

Do I dare try a hot plug?
 
Solution

Options depend on actual problem.
1. Drive may be faulty. Then get a replacement.
2. Motherboard has problem supporting drives larger than 2TB. Then try updating BIOS to latest version. If that still doesn't resolve the issue, then get a pci/pcie sata controller card, that would support your 3TB drive.

And yes, you will need to set your 3TB drive to GPT format, create partition and format it.
Hey there CWR63.

Go ahead and follow @SkyNetRising's advice. You could also try them out with a different computer if you have that options. Also try different cables and ports as well (there might be a faulty port on the mobo or a cable which could cause similar issues). It would be even better if you could connect them externally via a SATA to USB adapter, external enclosure, or a docking station, to see if all secondary drives are recognized and then use their respective manufacturers' diagnostic tools to test them for errors, just to see if anything weird pops-up. Here's a link on how to run the Quick and Extended tests with DLG on the WD drives: How to test a drive for problems using Data Lifeguard Diagnostics for Windows.

Hope that helps. Please keep us posted on your progress.
Boogieman_WD
 

CWR63

Honorable
Mar 18, 2014
38
0
10,530


I will, and I'm assuming that I shouldn't try to hot swap 'em?
 

CWR63

Honorable
Mar 18, 2014
38
0
10,530
I've had a chance to power off and plug in the other SSD, 1TB Crucial that I hope to use as a cache drive, and after a slow power up it was successful. I immediately checked disk management and found it listed as Disk 0 - it was named drive D: but labeled with something like master boot potential? I sort of panicked and R clicked - changed it into unallocated.

So now it has no drive designation, just labeled

Disk 0
Basic
931.39 GB
Online

R-click here gives options
Convert to dynamic disk...
Convert to MBR disk
Offline

with the shaded area to the right labeled: 931.39 GB Unallocated

R-click on shaded area gives option
New Simple Volume...

Should I be doing this under disk management? Why am I still having to make a text approximation of a GUI 16 years into the 21st century?
 

CWR63

Honorable
Mar 18, 2014
38
0
10,530


Sorry, just my designation - I do a lot of 2D graphics work and plan to use this as a cache drive for big poster size projects.

500GB SSD "boot drive" for fast loading OS, programs and games; 1TB SSD "cache drive" for workspace and perhaps some of the larger 3D programs; 3TB HDD "archive drive" for storage.

This may seem overkill, but this is what I worked with for 18 years prior:

Starter Wife
 

CWR63

Honorable
Mar 18, 2014
38
0
10,530


Is it a problem that it is showing up as Disk 0? I can just swap the plugs at the mobo to fix that, right? Unless it doesn't actually matter.
 

CWR63

Honorable
Mar 18, 2014
38
0
10,530


And that can only be accessed during the boot process? So I'll reset, spam delete or F2 during boot and confirm that everything is in the correct order in BIOS. Then save and exit, shut down safely, connect the data cable for the 3TB HDD and do this again.

If it hangs on start with the WD 3TB HDD connected, what are my options?

If it starts up okay like this SSD did, do I have to partition it since it's over a TB, or is that no longer necessary? These procedures sometimes go out of date without warning, the hazard of YouTube not offering a simple newness sorting when following these type of tutorials.
 

Options depend on actual problem.
1. Drive may be faulty. Then get a replacement.
2. Motherboard has problem supporting drives larger than 2TB. Then try updating BIOS to latest version. If that still doesn't resolve the issue, then get a pci/pcie sata controller card, that would support your 3TB drive.

And yes, you will need to set your 3TB drive to GPT format, create partition and format it.
 
Solution

CWR63

Honorable
Mar 18, 2014
38
0
10,530


Sorry, wording was imprecise, I was asking if I would need to make 3 X 1TB partitions, as that used to be advised. The Sabertooth X99 can handle 3TB drives, apparently (just checked their forums), so if it fails it's most likely that the drive's bad.

Okay, off to storm the castle!

 

CWR63

Honorable
Mar 18, 2014
38
0
10,530


Well, after extensive tests I could not get the system to start with the WD Re 3.0TB plugged in. With and without the 1TB SSD, using a different data cable, plugged into a different port, nothing doing. The odd thing is that the BIOS always identified the drive and it's location accurately. I just don't understand how a faulty storage drive can hang an OS - is it trying to be the boot drive? But then why would Windows even start - plus, every time I checked the BIOS it had the 500GB SSD correctly listed as the boot.

Because it's an Re drive?

I'll contact the retailer and see what's up. I don't have another PC that's new enough or powerful enough to hook this drive into for testing. Are there any other options?
 
Sorry to hear about everything you've been through with that HDD.

It's not uncommon for a faulty drive to mess things up for the system in general, even though there's no OS on it. So if the HDD is at fault, this is somewhat "normal" if you can call it that. It's not because of its model. The WD Re drive should work just as fine as any other drive with that setup, so there might be a problem with it.

Since you can't try it out with a different computer, you should contact the customer support of the vendor you got it from and try to RMA it. Another option would be to do that via our support portal: WD Support Portal.

Please keep me posted.
 

CWR63

Honorable
Mar 18, 2014
38
0
10,530
I'll start the RMA process and keep you posted. You were both very helpful, but SkyNetRising was the first response and so received the "best answer".
 

CWR63

Honorable
Mar 18, 2014
38
0
10,530
I'm sending it back to WD tomorrow - as it was purchased a week more than 30 days ago, the Amazon sponsored retailer said "Nyah, nyah, to the manufacturer with you!" so that's another $5 to ship it back, added to the $20 less that it is selling for on Amazon currently, leading to slight buyers remorse, i.e. 'This means I'm paying $25 more than someone buying it today' but I realize that's not how it actually works.

At least it was the storage drive and not the boot drive. I'll update again when I (hopefully) receive a replacement. Thanks again to you both for the help.
 

CWR63

Honorable
Mar 18, 2014
38
0
10,530
Got it back today. Installed it and initialized a moment later - 5 minutes tops. Thanks to your helps I finally have a fully functional 21st century machine. I'll post a link when I publish it as a finished build at pcpartpicker.com - still have some finishing touches to attend to.