Question New 4TB HDD causes any OS and any installation media to boot up indefinitely ?

[rzwk]

As the title says bought a new HDD @ 4tb (sata) and upon plugging it in it causes win10 & Win7 to load indefinitely, as well as their install medias but the drive detects in BIOS just fine. I've tried tinkering with BIOS settings, (turned off secure and fast boots, quadrochecked the boot order of drives, turned compatibility boot on and off and more I can't remember), did BIOS reset to 'recommended' defaults, pulled the CMOS battery JIC, used different SATA cables & mobo slots, unplugged all drives except the new one, but it' s just all the same no matter what I do. I already have 2 other HDD's and there are no problems with them.

What's funnier is when I connected the drive to another PC (much older build tho) it recognized it just fine, no issues, I've allocated and formatted the drive for GPT on that other PC, plugged back in - no results, still trying to boot forever. Also tried hot plugging it when the OS booted up, but it just didn't appear nor in the device manager,, Is there a BIOS setting I might be missing? I'm at a total loss as to what to do now.

Specs

Mobo: Asus prime H510M-K R2.0

The drive in question : Seagate Skyhawk ST4000VX007

Please help, thanks!

 

[SkyNetRising]

Also tried hot plugging it when the OS booted up, but it just didn't appear nor in the device manager.
Is there a BIOS setting I might be missing? I'm at a total loss as to what to do now.

Hot Plug for specific SATA port in BIOS has to be enabled for this to work.

Anyway - I'd suspect file system corruption.
Clean the drive - no partitions/no data.
Check drive health.

 

[rzwk]

Hot Plug for specific SATA port in BIOS has to be enabled for this to work.

yup accounted for that

Clean the drive - no partitions/no data.

when it was clean/unallocated it wouldn't boot either that's why I stuck it in the other PC to see if it will work and then allocate and format it i suspect something is up with the mobo or bios settings because why would it ever work in the other PC if the drive itself was faulty? thanks

 

[TerryLaze]

Disks above 2.2Tb need to be supported by the bios, that's my only guess at the moment, look if your newer system has any bios update or utility tool that mentions anything about 3+Tb disks.

 

[SkyNetRising]

Disks above 2.2Tb need to be supported by the bios,
that's my only guess at the moment, look if your newer system has any bios update or utility tool that mentions anything about 3+Tb disks.

It's H510 board.
It would not have any such problems.

 

[shaester_123]

Moisture? Has the drive come into contact with Moisture? I have had drives do similar from being damaged by Moisture in the air over time . These days I store mine in cases with color changing Moisture absorbing gell .

 

[rzwk]

Moisture? Has the drive come into contact with Moisture? I have had drives do similar from being damaged by Moisture in the air over time . These days I store mine in cases with color changing Moisture absorbing gell .

Doubt that as the drive is fresh new from the store. Plus it's working fine on the other PC for some unknown reason without even getting into BIOS and changing anything there (as it should be).

 

[rzwk]

Disks above 2.2Tb need to be supported by the bios, that's my only guess at the moment, look if your newer system has any bios update or utility tool that mentions anything about 3+Tb disks.

I'll see what BIOS version i have but they don't have any hard drive tools (apart from Intel Rapid Storage Technology driver I'll also install it but I'm kinda doubtful it'll solve the issue) i'll update bios firmware if I'm behind

 

[Misgar]

bought a new HDD @ 4tb (sata) and upon plugging it in it causes win10 & Win7 to load indefinitely,

You haven't mentioned how your Windows 10 and Windows 7 drives are configured, but is it possible their respective boot partitions are not on the correct drives?

This can happen (hidden partition, UEFI partition and C: drive partition not on the same physical disk) when cloning OS drives, but failing to disconnect the original drive when booting up the new clone for the first time. The boot partition sometimes remains on the old drive, but the C: drive is now on the new drive. The new drive will boot fine, but fail when you add/remove drives.

A new formatted hard disk with a valid drive letter, might stop Windows from booting if the new drive letter moves an existing drive letter to something new. If the boot sector is loaded by the BIOS, but the associated C: drive may have "vanished", because the new 4TB drive has taken its place.

Do you have two separate drives, one for Windows 10, the other for Windows 7, or do you have both versions of Windows on one physical (dual boot) drive?

If you can unplug the Windows 7 drive, see if you can boot into Windows 10 with no other drives connected. Plug in the new 4TB drive and see if you can still boot into Windows 10. Repeat the test with the Windows 7 drive.

 

[rzwk]

You haven't mentioned how your Windows 10 and Windows 7 drives are configured, but is it possible their respective boot partitions are not on the correct drives?

This can happen (hidden partition, UEFI partition and C: drive partition not on the same physical disk) when cloning OS drives, but failing to disconnect the original drive when booting up the new clone for the first time. The boot partition sometimes remains on the old drive, but the C: drive is now on the new drive. The new drive will boot fine, but fail when you add/remove drives.

A new formatted hard disk with a valid drive letter, might stop Windows from booting if the new drive letter moves an existing drive letter to something new. If the boot sector is loaded by the BIOS, but the associated C: drive may have "vanished", because the new 4TB drive has taken its place.

Do you have two separate drives, one for Windows 10, the other for Windows 7, or do you have both versions of Windows on one physical (dual boot) drive?

If you can unplug the Windows 7 drive, see if you can boot into Windows 10 with no other drives connected. Plug in the new 4TB drive and see if you can still boot into Windows 10. Repeat the test with the Windows 7 drive.

Hi! Yeah see, the thing with that is I only have Windows 10 at the moment. Here's how it went:

I had Windows 10 before, the drive didn't work so I decided to re-install it, but to my surprise the installation media didn't boot as well as the OS, i then unplugged the drive, installed win7 (cuz at that point i'd done all my previous attempts at fixing the issue in bios and tested it on the other PC which has win7 only, so I thought maybe somehow win10 was the issue, or even if it wasn't and I just needed a clean install I decided i'd go for 7 since that's what worked on the other PC that I plugged the drive in)

After installing win7 with the drive unplugged I plugged the drive in again and attempted booting up - didnt work, so I went ahead and installed back WIndows 10 (with the drive unplugged of course). Then attempted booting to win10 install after that (with the drive plugged in) -still doesn't boot up, also attempted using MS DART - guess what it doesn't boot either. So pretty much nothing boots as long as the 4tb drive is plugged in. Not a single bootable media even OS installs can boot.

So right now I have one system drive with windows10 on it and one extra drive for back ups, apps and misc files that I don't want to lose if I need to format the system drive. Thanks!

PS The second drive (not the system one) it's impossible for it to have any boot partitions because I've never installed any OS on it ever since I got that drive I only used it as a file storage. Still though as I said I tried disconnecting the drives one by one till all of em were out, also left only one drive in if we don't coun the 4TB drive (first files drive, then the system drive) none of it yielded anything even if there are no drives but the new 4tb plugged in-- installation media never boot up, it is pretty much stuck at the loading screen with the animations and everything going, max I waited was about 5-10 minutes, given that it boots up in the matter of seconds usually ,I doubt that waiting for 5+ minutes is something that I might have to do to be able to boot into a system after installing a new drive.

 

[rzwk]

Also if that's valuable information: the letters of active drives are C (for system) and D for the files drive

 

[rzwk]

Turns out I have BIOS v1001 which is the latest version so it probably isn''t the firmware I'm gonna fiddle more with the drive and BIOS this weekend, maybe a miracle will happen.