4TB HD showing up as 1.678

Earendil86

Reputable
Jul 15, 2016
25
0
4,540
Hello,

I have been searching the forums and found lots of cases of this happening but not a solution so far that works for my particular situation.

OS: Windows 7 Pro
Motherboard: EVGA 141-BL-E757 (Socket 423)
Harddrive in question: Seagate ST4000DM005 (4TB)

Background:

I had this drive setup and running with no issues as a secondary drive. Then I decided to use 3x 64GB SSD's that I had lying around and create a RAID 5 on those drives through the BIOS. In order to accomplish this I had to change the drive type from "IDE" to "RAID" (The other option is AHCI). In anycase, the raid 5 went smoothly and now I have the three 64 gb drives as a raid 5 and my primary boot. Then I have a 2TH WD drive as a secondary drive and this 4tb Seagate drive. Immediately after the upgrade I noticed issues with my 4tb drive and files being corrupted. After weeks of this and reformatting the drive (at 4tb) I was still getting issues. Then all of a sudden the drive unformatted itself and showed up as 1.678 tb capacity.

What I have found:

My BIOS was also registering this as 1678GB so I updated my BIOS yesterday to the latest release which was from 2011. Now the BIOS shows 3.6TB, however, the drive is still only showing up as 1678GB.

Next steps?

Would updating any of the below from the EVGA website fix this issue? Or is the MB just too old?

To get these options I selected "Intel X58/ICH10R" for family, then my MB.

There are downloads for:

Audio/AUDIO
BIOS
Chipset Driver
Intel RAID Management
Network
RAID
Software Utilities

Any ideas? I assume that the next step would be to update the Intel RAID Management or RAID?

Thank you,




 
It sounds as though your onboard chipset RAID might have accidentally included your hard drives in on the Intel MB-managed RAID....

I'd drop all of it, nuke and pave/clear/delete any/all RAID status in MB RAID setup, and start over....

WIthin control panel/admin tools/computer mngmt/storage, perhaps you can merely extend your partion out to the full capacity of the drive? Or, try deleting all partions of no OS drives from within .
 

Earendil86

Reputable
Jul 15, 2016
25
0
4,540
Sorry I should have also mentioned the following:

1) I performed the RAID setup with all other drives disconnected
2) When I boot up, the drives show as being regular drives with the 64GB drives showing as RAID.
3) I ended up returning the first drive after Seatools failed to load. This is now the replacement drive with the same issue. It has no data on it and I have performed a few formats.

As for extending the partition, it just doesn't recognize the full size of the disk in Windows. Could this be a Win 7 issue? Or is it to do with RAID drivers?

Thanks

 

Earendil86

Reputable
Jul 15, 2016
25
0
4,540
When I initialize the drive in windows it gives me the option to select GPT. I select it and then go to the format options and it only shows the 1678 as allowable space. Do I need to go through the process of formatting it first and then reboot and will it then showup as a larger drive? Then reformat again?
 

Earendil86

Reputable
Jul 15, 2016
25
0
4,540
So I just went through the process and formatted the drive and took screenshots. Don't see an option to add them so I'll just explain.

1) Drive was unallocated showing 1677.90 GB
2) Checked to ensure that it was GUID Partitial Table (GPT)
3) This spot shows the Capacity as 1718166 MB
4) Formatted as NTFS with Default Allocation unit size and did a long format.
5) Disk now shows up as a health volume of 1677 GB size.
6) During Boot sequence it shows the 3 raid disks as raid members and my 2 other drives as being non-raid members. The problem disk being one of them (but only 2 TB anyways)

Thanks,
 

Earendil86

Reputable
Jul 15, 2016
25
0
4,540
I finally got around to looking at this again and I think that I've solved the issue! Essentially I updated the rest of the drivers for my motherboard (RAID and Chipset) and now the drive is recognized in windows at the proper size. I'm in the process of formatting it now!