4TB GPT drive only formats to 2TB

dstarr3

Distinguished
So I've got a 4TB WD Red drive. Brand new. Shipped from WD to replace my original 4TB drive that was having problems that I attributed to the hard drive, but it might be a Windows 7 problem that suddenly developed instead.

Going into disk management, it gives me the option to initialize as MBR or GPT. I choose GPT because it's 4TB. But when going to format, I can only format for 1677.9 GB. Same results if I try to use MiniTools Partition Wizard, as well. If I want to format this for the full 4TB, I have to boot into GPartEd from a flash drive and use that to format it. Once I use GPartEd to format as 4TB, then Windows can reformat it to 4TB no problem. But it won't recognize the full size before.

The problem I was having with the previous 4TB drive that this is replacing is that it would be corrupted after every restart. I would write about 2.5TB of data to the drive, and within minutes, more and more directories would become inaccessible, and one restart later, all the data would be lost and Windows would report that the drive was unformatted. After cleaning and reinitializing the old drive, I had the same problem of needing to use GPartEd to get the full 4TB. I haven't tried filling this new drive yet to see if this has the same problem, but I'm afraid it might.

This drive is used for data backup, it only gets plugged in every few weeks to update any file changes, and then goes back in storage in a shockproof hard drive case. My PC case has a hot swap bay, but I don't use it to hot swap, I only insert or remove hard drives while the PC is off. I used my previous hard drive like this for over two years without a problem, but I went to make a backup last week and suddenly this problem started.

So what could change in a Windows installation that would suddenly break its ability to work with 4TB drives? And how do I revert that change so I can get Windows working the way it used to again?

Thanks.
 
Solution
1) The original 4TB hard drive was partitioned at 4TB back when I bought it new using the same hardware and same OS installation. Years later, once this problem occurred, I was able to reformat for the full 4TB until I cleaned the disk in diskpart. Once I did that, I was unable to partition for the full 4TB, GPT or no. I was only able to partition a full 4TB partition when using GPartEd, but Windows would give me problems about needing to be formatted at every restart after doing so. I assumed this was a hard disk failure until the replacement exhibited the same problems.

2) Yes, 64-bit W7.

Also, I managed to solve the problem today. Since my motherboard was always reporting the full 4TB capacity at post, and since GPartEd, a...
1. You indicate the new 4 TB WD HDD is a replacement for your "original" 4 TB HDD. That being the case had the original 4 TB HD been GPT-partitioned and did the system detect its 4 TB of disk-space?

2. Just a couple of other things...can we assume you're working with a Win 7 OS? If so, is it a 64-bit OS?
 

dstarr3

Distinguished
1) The original 4TB hard drive was partitioned at 4TB back when I bought it new using the same hardware and same OS installation. Years later, once this problem occurred, I was able to reformat for the full 4TB until I cleaned the disk in diskpart. Once I did that, I was unable to partition for the full 4TB, GPT or no. I was only able to partition a full 4TB partition when using GPartEd, but Windows would give me problems about needing to be formatted at every restart after doing so. I assumed this was a hard disk failure until the replacement exhibited the same problems.

2) Yes, 64-bit W7.

Also, I managed to solve the problem today. Since my motherboard was always reporting the full 4TB capacity at post, and since GPartEd, a Linux-based tool was able to partition the drive no problem, it must've been a Windows driver problem. I never changed anything, I'm an ain't-broke-don't-fix-it kind of guy, I can only assume Windows Update broke something. But I downloaded and installed the latest Intel RST drivers and suddenly everything is working again. It worked before; obviously when the drive was new two or three years ago, I was able to partition the full 4TB no problem, and continue using the drive for those years without incident. But something modified the RST drivers without my knowledge apparently, because what used to work suddenly broke.

Either way, updating Intel RST drivers fixed it and everything's back to normal.
 
Solution
That's good news. It's not totally surprising that installing the IRST was the "fix" re this issue. We've experienced that at least twice before as I recall. In both cases the OS was Win 7 and a RAID configuration had been present. Whether the latter had some sort of an impact on the problem or was just a coincidence I don't know.
 

TRENDING THREADS