M
Michael Kantor
Guest
Hello,
I am in the process of building a file server with 8 750GB drives running in
RAID5 for a volume of 5.25TB. It got the computer up and running with XP Pro
32-bit, but once the array was built, I realized that it will not go past 2TB.
This is a huge problem, and I did not anticipate it because I read that NTFS
supports far over 2TB, but had not encountered information about the
distinction of MBR and GUID prior to seeing this problem.
Please answer these questions for me if you can:
1. I read that XP Pro 64-bit would support the GUID partition. Does it also
need an Itanium chip to do this, or will it work on Core2 Duo? I read some
notes on Itanium, but perhaps they were outdated.
2. If #1 is resolved, and then I format the array to its full size, will a
computer on the network (32-bit XP or OSX) be able to read/write into the
full 5.25TB of this shared drive? I would assume so, since network computers
just talk to the OS, and not the storage drivers, but I havent been able to
confirm this.
Thank you,
Michael
I am in the process of building a file server with 8 750GB drives running in
RAID5 for a volume of 5.25TB. It got the computer up and running with XP Pro
32-bit, but once the array was built, I realized that it will not go past 2TB.
This is a huge problem, and I did not anticipate it because I read that NTFS
supports far over 2TB, but had not encountered information about the
distinction of MBR and GUID prior to seeing this problem.
Please answer these questions for me if you can:
1. I read that XP Pro 64-bit would support the GUID partition. Does it also
need an Itanium chip to do this, or will it work on Core2 Duo? I read some
notes on Itanium, but perhaps they were outdated.
2. If #1 is resolved, and then I format the array to its full size, will a
computer on the network (32-bit XP or OSX) be able to read/write into the
full 5.25TB of this shared drive? I would assume so, since network computers
just talk to the OS, and not the storage drivers, but I havent been able to
confirm this.
Thank you,
Michael