sounds like raid 0 +1 i believe if not its short stroked
3 1TB drives set up in raid 0 with only 2TB of space?
1 - 20 of 30 Posts
Quote:
Windows has a limitation in which you can only create 2TB partitions. It's a limitation of MBR disks. If you want to utilize a single partition greater than 2TB, you have to convert the physical disk (In Disk Manager) to a GPT disk.
You can reference this article as a starting point:
http://www.microsoft.com/whdc/device.../GPT_FAQ.mspx1
Originally Posted by MR_Plow  All three say they are being used in the array so i don't think they aren't connected it just says my C: is only 1.99TB (oddly although i have about 1TB on here the blue bar that shows a visible representation of the hard drive space doesn't look like it's half way...). I'm running Windows 7 64 bit 3 1TB black caviars etc. from sig I heard rumor that windows just doesn't know how to deal with more than two TB of data and thus it just says i've got 2TB when i actually have 3. any thoughts? |
You can reference this article as a starting point:
http://www.microsoft.com/whdc/device.../GPT_FAQ.mspx1
Quote:
This. If only two were being used, it would be 1.86 as previously stated. You'll have to reformat the discs if memory serves right.
Originally Posted by ComGuards Windows has a limitation in which you can only create 2TB partitions. It's a limitation of MBR disks. If you want to utilize a single partition greater than 2TB, you have to convert the physical disk (In Disk Manager) to a GPT disk. You can reference this article as a starting point: http://www.microsoft.com/whdc/device.../GPT_FAQ.mspx1 |
Quote:
your link was not working for me. here is another link that might share some info on what you were talking about
http://www.microsoft.com/whdc/device...e/GPT_FAQ.mspx
now that i pasted it. looks the same
![]()
just no 1 on the end
-->OP try partitioning your drive into a 2tb and a 1tb drive. see if it will let you do that. if so. id just use the 1tb as a system drive and keep the other 2 as a storage drive
Originally Posted by ComGuards Windows has a limitation in which you can only create 2TB partitions. It's a limitation of MBR disks. If you want to utilize a single partition greater than 2TB, you have to convert the physical disk (In Disk Manager) to a GPT disk. You can reference this article as a starting point: http://www.microsoft.com/whdc/device.../GPT_FAQ.mspx1 |
your link was not working for me. here is another link that might share some info on what you were talking about
http://www.microsoft.com/whdc/device...e/GPT_FAQ.mspx
now that i pasted it. looks the same
-->OP try partitioning your drive into a 2tb and a 1tb drive. see if it will let you do that. if so. id just use the 1tb as a system drive and keep the other 2 as a storage drive
2
Quote:
I can't wait until 2.5TB HDDs come out. Oh, the confusion that will ensue.
![]()
Originally Posted by ComGuards Reference this KB for additional information: http://support.microsoft.com/kb/946557 After you convert to a GPT disk, you *might* be able to use the Diskpart.exe command to extend the size of the C: partition. No guarantees though, I've never worked with GPT disks in that way. |
2
wow guys, that's a lot of help, really fast, thanks
![]()
ok, a few things:
definitely not RAID 0+1 or RAID 5, as i've checked the stripe size is correct for plain ole' RAID 0 (according to EVGA)
now i'm definitely taking ComGuards' warning into account here, would you say the benefits of short stroking would be great?
it appears my best options are to either short stroke or to do some hard drive shifting and take one off the RAID set up with the OS
although i'd loose some space (it is, admittedly quite a bit of space that i have to begin with...) wouldn't short stroking keep my speed up (especially for that one lone drive that would be kicked out of the array?)
ok, a few things:
definitely not RAID 0+1 or RAID 5, as i've checked the stripe size is correct for plain ole' RAID 0 (according to EVGA)
now i'm definitely taking ComGuards' warning into account here, would you say the benefits of short stroking would be great?
it appears my best options are to either short stroke or to do some hard drive shifting and take one off the RAID set up with the OS
although i'd loose some space (it is, admittedly quite a bit of space that i have to begin with...) wouldn't short stroking keep my speed up (especially for that one lone drive that would be kicked out of the array?)
Quote:
I hear ya on that one. Actually the screams have already started in the corporate world. Had a bunch of clients ask me what to do with their iSCSI disks configured with 32x 1TB drives in RAID-10 (16GB usable space), and they couldn't create partitions bigger than 2TB!
![]()
No big deal when configured as SANs and NAS anyways, since the boot drives are still usually "puny" 500GB or 1TB RAID-1 arrays usually (for redundancy).
Originally Posted by DuckieHo I can't wait until 2.5TB HDDs come out. Oh, the confusion that will ensue.
|
No big deal when configured as SANs and NAS anyways, since the boot drives are still usually "puny" 500GB or 1TB RAID-1 arrays usually (for redundancy).
3
Quote:
Check out that THG article for synthetic benchmarks. Might give you a better "objective" answer.
Honestly, if you can, get another pair of WD Blacks or Samsung Spinpoints as a separate RAID-0 for your OS and stuff... should give you more than enough speed
![]()
Otherwise.... Maybe DuckieHo might have a better suggestion...
Originally Posted by MR_Plow wow guys, that's a lot of help, really fast, thanks
ok, a few things: definitely not RAID 0+1 or RAID 5, as i've checked the stripe size is correct for plain ole' RAID 0 (according to EVGA) now i'm definitely taking ComGuards' warning into account here, would you say the benefits of short stroking would be great? it appears my best options are to either short stroke or to do some hard drive shifting and take one off the RAID set up with the OS although i'd loose some space (it is, admittedly quite a bit of space that i have to begin with...) wouldn't short stroking keep my speed up (especially for that one lone drive that would be kicked out of the array?) |
Honestly, if you can, get another pair of WD Blacks or Samsung Spinpoints as a separate RAID-0 for your OS and stuff... should give you more than enough speed
Otherwise.... Maybe DuckieHo might have a better suggestion...
3
Quote:
I got a call today about a 1.5TB only having 127GB usable... This still comes up like 7 years later.
![]()
Originally Posted by ComGuards I hear ya on that one. Actually the screams have already started in the corporate world. Had a bunch of clients ask me what to do with their iSCSI disks configured with 32x 1TB drives in RAID-10 (16GB usable space), and they couldn't create partitions bigger than 2TB!
No big deal when configured as SANs and NAS anyways, since the boot drives are still usually "puny" 500GB or 1TB RAID-1 arrays usually (for redundancy). |
3
Quote:
i feel like this has already happened? unless i'm misunderstanding things here?
Disk Manager Set Up:
(C: ) 2.04TB
Simple Drive (D: ) 1 TB (I have an extra 1 TB that's not in my array for storage)
System Reserved 100MB
granted that partition is still on my c: it seems that smaller chunk would be my "boot partition" as you say it, no?
![]()
Originally Posted by xandypx The problem is not that you can't have a partition larger than 2TB. What you can't have is a Boot Partition bigger than 2TB. Don't know what you have on your disks now, but if you can back up your data. You need to recreate your array with two partitions. install the OS on a small partition, say 80MB. Once installed, you can go into Disk management, and create a GPT disk on the remaining space. This GPT Virtual Disk can only be used for Data storage. If you later decide that you still need more space, additional HDD can be added, and extended into your 2.99 TB Virtual Disk. |
Disk Manager Set Up:
(C: ) 2.04TB
Simple Drive (D: ) 1 TB (I have an extra 1 TB that's not in my array for storage)
System Reserved 100MB
granted that partition is still on my c: it seems that smaller chunk would be my "boot partition" as you say it, no?
2
Quote:
Uhh... that won't work. The GPT conversion in Windows Disk Manager applies to the entire logical disk. If his boot partition and data partition are on the same logical disk, he's still screwed in terms of upgrading to a GPT disk. i.e. to upgrade to GPT, you select the actual "DISK" and not one of the partitions on the disk.
Originally Posted by xandypx The problem is not that you can't have a partition larger than 2TB. What you can't have is a Boot Partition bigger than 2TB. Don't know what you have on your disks now, but if you can back up your data. You need to recreate your array with two partitions. install the OS on a small partition, say 80MB. Once installed, you can go into Disk management, and create a GPT disk on the remaining space. This GPT Virtual Disk can only be used for Data storage. If you later decide that you still need more space, additional HDD can be added, and extended into your 2.99 TB Virtual Disk. |
Quote:
Have you gotten the call about the broken coffee cup holder yet? You know the one that is "so cool because it ejects out of the computer"?
![]()
Originally Posted by DuckieHo I got a call today about a 1.5TB only having 127GB usable... This still comes up like 7 years later.
|
3
1 - 20 of 30 Posts
