Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Partition Question
- Thread starter teklow
- Start date
The bios boot limit is 7.8gig and this is documented in Technet. You can get into serious problems with booting if you exceed this. It is possible, but you could suddenly find your system will not boot.
4GB is the largest you can create at installation. I normally just leave my boot partition at that size. You can use Server Magic to kick it up to the 7.8 GB limit. If you try to go larger, it will warn you about the boot limit.
Good Luck.
4GB is the largest you can create at installation. I normally just leave my boot partition at that size. You can use Server Magic to kick it up to the 7.8 GB limit. If you try to go larger, it will warn you about the boot limit.
Good Luck.
It's a better idea, anyway, to have NT and your data reside on separate partitions. There are many reasons, but if you were ever to get in a position where you have to completely reinstall NT, you could reformat the C: drive and not destroy your valuable data.
This is SOP for me.....
- Bill
"You can get anything you want out of life, if you'll just help enough other people get what they want" - Zig Ziglar
This is SOP for me.....
- Bill"You can get anything you want out of life, if you'll just help enough other people get what they want" - Zig Ziglar
NOTE: THIS POST IS LARGELY ANECDOTAL
For what it's worth (the price of admission here, perhaps)...
I like having a system root partition larger than 2 gig. In fact, my present opinion - subject to change - is that 4 gig is very nice. But then, I run my domain controller like it was a workstation (something that should make any good administrator cringe a little) and routinely have everything, including the kitchen sink, loaded.
So, for me, that would mean 4 gig for the system partition and 16 gig for data (from a 20 gig drive).
But I really don't like using partitions. (No good reason, of course; it's just one of those things that make me painfully recall that I went to my high school prom with my kid sister.) So, I popped down to a local used computer store, found a sweet deal on a pristine 4 gig drive, tested the heck out of it, and made that my system root. Thereafter, my nice new 20-gig drive was able to be one nice big partition, and - since I am using two separate drive controllers - my overall drive-to-drive bandwidth is very nice indeed. The 4 gig system drive is U2W SCSI, the 20 gig data drive is UDMA 133 IDE.
In this arrangement, I put the pagefile onto the 20 gig partition - separate from the system root - because (again) that means I have two pieces of drive controller hardware handling disk I/O - one executing system files and the other handling pagefile caching.
(BTW, the idea of using a "used" disk drive in a professional environment feels a little like eating a slice of pizza that my daughter's boyfriend had just sneezed on. Normally, I'd say, don't go there. But in this case, the server was my own - not a client's. And, as indicated, it was indeed a very sweet deal on the drive - less than 5 hours of operation in a dot-com buyout.)
I don't know if any of this helps or not. I, also, had gone through the OBFP crush (One Big Fat Partition). As indicated above, you will be happy and worry-free keeping your system root and data partitions separate.
Regards,
oldschool
For what it's worth (the price of admission here, perhaps)...
I like having a system root partition larger than 2 gig. In fact, my present opinion - subject to change - is that 4 gig is very nice. But then, I run my domain controller like it was a workstation (something that should make any good administrator cringe a little) and routinely have everything, including the kitchen sink, loaded.
So, for me, that would mean 4 gig for the system partition and 16 gig for data (from a 20 gig drive).
But I really don't like using partitions. (No good reason, of course; it's just one of those things that make me painfully recall that I went to my high school prom with my kid sister.) So, I popped down to a local used computer store, found a sweet deal on a pristine 4 gig drive, tested the heck out of it, and made that my system root. Thereafter, my nice new 20-gig drive was able to be one nice big partition, and - since I am using two separate drive controllers - my overall drive-to-drive bandwidth is very nice indeed. The 4 gig system drive is U2W SCSI, the 20 gig data drive is UDMA 133 IDE.
In this arrangement, I put the pagefile onto the 20 gig partition - separate from the system root - because (again) that means I have two pieces of drive controller hardware handling disk I/O - one executing system files and the other handling pagefile caching.
(BTW, the idea of using a "used" disk drive in a professional environment feels a little like eating a slice of pizza that my daughter's boyfriend had just sneezed on. Normally, I'd say, don't go there. But in this case, the server was my own - not a client's. And, as indicated, it was indeed a very sweet deal on the drive - less than 5 hours of operation in a dot-com buyout.)
I don't know if any of this helps or not. I, also, had gone through the OBFP crush (One Big Fat Partition). As indicated above, you will be happy and worry-free keeping your system root and data partitions separate.
Regards,
oldschool
- Status
Similar threads
- Locked
- Question