how are 2TB and up desktop hard drives formatted and partitioned?
Hello and Good Evening Everyone,
With the increase of very large internal hard drives like 2TB and greater, I am wondering how they are prepared with respect to formatting and partitioning. I am somewhat familiar with the FAT32 and NTFS format structure. However, I am not sure if NTFS would even support 2TB and larger internal hard disk drives. Perhaps there is a new file system which I am unfamiliar with that supports drives that large. At any rate, I am curious about the procedures or logistics of formatting and partitioning the more modern and larger hard drives.
Any shared input regarding this question will be appreciated.
Thank you
George
With the increase of very large internal hard drives like 2TB and greater, I am wondering how they are prepared with respect to formatting and partitioning. I am somewhat familiar with the FAT32 and NTFS format structure. However, I am not sure if NTFS would even support 2TB and larger internal hard disk drives. Perhaps there is a new file system which I am unfamiliar with that supports drives that large. At any rate, I am curious about the procedures or logistics of formatting and partitioning the more modern and larger hard drives.
Any shared input regarding this question will be appreciated.
Thank you
George
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
If you want a really good hard disk management tool then Hard Disk Manager 15 is a right choice: http://www.paragon-software.com/home/hdm-personal/features.html
You have in it all you would ever need for PC maintenance.
You have in it all you would ever need for PC maintenance.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hello and Good Evening Everyone
I am still reading the information contained within each submitted link. As such, I will need a little extra time or extension before closing this post just in case I might have a relevant follow up question.
Many thanks once again for all of the given information. It is really interesting reading and certainly adds to my knowledge of hard drive disk maintenance and management.
George
I am still reading the information contained within each submitted link. As such, I will need a little extra time or extension before closing this post just in case I might have a relevant follow up question.
Many thanks once again for all of the given information. It is really interesting reading and certainly adds to my knowledge of hard drive disk maintenance and management.
George
ASKER
Hello and Good Evening Everyone,
I must confess that I am very impressed with the content of each link submitted in addition to everyone's shared insights. After reviewing all of the information, I do have one more follow up question of technical interest. With respect to formatting a hard drive using 4k cluster size and formatting a hard drive using 64k cluster size, is it reasonable to conclude that more data is packed within a 64k cluster block as compared to the 4k cluster size block? In simpler terms, could it be compared to a small attic of a house that is 12x8 to a much larger attic of a different house that is 56x23? I am assuming that each block or cluster on the hard drive created from formatting is like real estate or property for building data.
Just to add, I remember several years ago terms like sectors (electro-magnetic lines created on the hard drive that make it readable/writable) and cylinders (electro-magnetic circles on the hard drive used to store data) were created through the use of formatting and partitioning tools. I am not sure if this ties into our discussion or not, but, it seems like it might have merit here. If someone could tie this in with everything discussed so far, perhaps that will paint a clearer picture.
George
I must confess that I am very impressed with the content of each link submitted in addition to everyone's shared insights. After reviewing all of the information, I do have one more follow up question of technical interest. With respect to formatting a hard drive using 4k cluster size and formatting a hard drive using 64k cluster size, is it reasonable to conclude that more data is packed within a 64k cluster block as compared to the 4k cluster size block? In simpler terms, could it be compared to a small attic of a house that is 12x8 to a much larger attic of a different house that is 56x23? I am assuming that each block or cluster on the hard drive created from formatting is like real estate or property for building data.
Just to add, I remember several years ago terms like sectors (electro-magnetic lines created on the hard drive that make it readable/writable) and cylinders (electro-magnetic circles on the hard drive used to store data) were created through the use of formatting and partitioning tools. I am not sure if this ties into our discussion or not, but, it seems like it might have merit here. If someone could tie this in with everything discussed so far, perhaps that will paint a clearer picture.
George
All depends on the data type you are going to store on this drive. If the data consists of mirriades of tiny data pieces then making a cluster size smaller is reasonable. For bigger data a bigger cluster size is good.
Look here for nice explaining: http://www.pcguide.com/ref/hdd/perf/perf/ext/fileCluster-c.html
Look here for nice explaining: http://www.pcguide.com/ref/hdd/perf/perf/ext/fileCluster-c.html
the disk buildup is the same : with heads, and platters
the platter still has tracks, divided sectors
to make things better adressable, they use a cluster based format, which comprises alot more sectors
this explains it well : http://en.wikipedia.org/wiki/Data_cluster
sectors : http://en.wikipedia.org/wiki/Disk_sector
also nicely shown here : http://ntfs.com/hard-disk-basics.htm
the platter still has tracks, divided sectors
to make things better adressable, they use a cluster based format, which comprises alot more sectors
this explains it well : http://en.wikipedia.org/wiki/Data_cluster
sectors : http://en.wikipedia.org/wiki/Disk_sector
also nicely shown here : http://ntfs.com/hard-disk-basics.htm
@GMartin - Thanks and I was happy to help.
ASKER
Hello and Good Afternoon Everyone,
Thanks so much for the shared insights and especially for the resourceful links. After reviewing all of the information given, it certainly makes more sense to use the Windows 7 and Windows 8 Disk Management tool as opposed to using a third party program. However, I did proceed with successfully creating a bootable ISO file for GParted Live CD for future references.
With respect to my confusion surrounding any potential formatting size barriers, I must conclude that stems from my lack of knowledge or insights about the differences between legacy BIOS and UEFI BIOS. Of course the more modern computers of today have what is called the UEFI BIOS which will permit formatting drives larger than 2TB. From my readings though, the UEFI BIOS does require some reconfiguration, especially disabling Secure Boot, before setting the desired boot sequence. It is not as straight forward as it has been in the past using older Legacy BIOS. Additionally, the terminology surrounding what is called a bootable drive has shifted. If I am not mistaken and drawing wrong conclusions, it is my understanding that a MBR or Master Boot Record must be created on drives at 2TB or smaller to make it bootable. Whereas, if the drive is larger than 2TB, a GPT must be created to make that partition or hard drive bootable. Perhaps I overlooked this in my readings, but, I never do remember a reference being used for the proper size of partition to use for an operating system like Windows 7 or Windows 8 on the hard drives that are 2TB or larger. To me, it would make sense to take a very large hard drive like that and divide it into several partitions. One partition (Primary, bootable one) or C: could be laid aside for the operating system, drive D; could be laid aside for applications, games, utilities, etc. drive E: could be set aside for a music archive, and so forth. However, that suggestion does bring me to a question though. Would it not be better to place all installed programs on the same partition with the operating system? It seems like it would be better that way by speeding up the time the operating system needs to open and close a program because of it being on the same partition. Just a thought though.
In closing, I sincerely thank everyone for their shared views and tips. As with many of my post, I often find answers leading to more in-depth questions which keeps my curiosity and eagerness very much alive. Each expert with EE always brings with them a special way of looking at a technical situation while exercising a willingness to work with me regardless if I have one follow up question or a dozen. At times, I feel like I give more of a critique of the responses as opposed to an analytical overview of the outcome of a troubleshooting session. For that, I am sorry. I just never want to forget to remind each and everyone of you how important your opinions and insights are to me as a continued learner of EE.
Have a great evening everyone.
George
Thanks so much for the shared insights and especially for the resourceful links. After reviewing all of the information given, it certainly makes more sense to use the Windows 7 and Windows 8 Disk Management tool as opposed to using a third party program. However, I did proceed with successfully creating a bootable ISO file for GParted Live CD for future references.
With respect to my confusion surrounding any potential formatting size barriers, I must conclude that stems from my lack of knowledge or insights about the differences between legacy BIOS and UEFI BIOS. Of course the more modern computers of today have what is called the UEFI BIOS which will permit formatting drives larger than 2TB. From my readings though, the UEFI BIOS does require some reconfiguration, especially disabling Secure Boot, before setting the desired boot sequence. It is not as straight forward as it has been in the past using older Legacy BIOS. Additionally, the terminology surrounding what is called a bootable drive has shifted. If I am not mistaken and drawing wrong conclusions, it is my understanding that a MBR or Master Boot Record must be created on drives at 2TB or smaller to make it bootable. Whereas, if the drive is larger than 2TB, a GPT must be created to make that partition or hard drive bootable. Perhaps I overlooked this in my readings, but, I never do remember a reference being used for the proper size of partition to use for an operating system like Windows 7 or Windows 8 on the hard drives that are 2TB or larger. To me, it would make sense to take a very large hard drive like that and divide it into several partitions. One partition (Primary, bootable one) or C: could be laid aside for the operating system, drive D; could be laid aside for applications, games, utilities, etc. drive E: could be set aside for a music archive, and so forth. However, that suggestion does bring me to a question though. Would it not be better to place all installed programs on the same partition with the operating system? It seems like it would be better that way by speeding up the time the operating system needs to open and close a program because of it being on the same partition. Just a thought though.
In closing, I sincerely thank everyone for their shared views and tips. As with many of my post, I often find answers leading to more in-depth questions which keeps my curiosity and eagerness very much alive. Each expert with EE always brings with them a special way of looking at a technical situation while exercising a willingness to work with me regardless if I have one follow up question or a dozen. At times, I feel like I give more of a critique of the responses as opposed to an analytical overview of the outcome of a troubleshooting session. For that, I am sorry. I just never want to forget to remind each and everyone of you how important your opinions and insights are to me as a continued learner of EE.
Have a great evening everyone.
George
It seems you have misunderstood several of the points.
1. "...the UEFI BIOS which will permit formatting drives larger than 2TB."
You don't need a UEFI BIOS to use disks larger than 2TB. In order to be able use all the data on a disk larger than 2TB, it just needs to be made a GPT disk. GPT disks are supported by both, legacy and UEFI BIOSes. But is your OS happens to be an m$ OS, you can't boot to a GPT disk if the BIOS isn't also UEFI. But there is no problem booting to an MBR disk and accessing a 2nd disk that is GPT. Other OS's hat aren't from m$ don't have that restriction. You can boo Linux from a GPT disk even if the BIOS is legacy, for example.
2 "...some reconfiguration, especially disabling Secure Boot, before setting the desired boot sequence..."
The boot sequence has nothing to do with "secureboot". Secureboot is a function in the BIOS which checks all your media for certificates that have been accepted as safe to boot from. Those certificates are stored in the BIOS database, and included on the media, but they aren't free. Manufacturers of OS's and boot media would have to buy those certs from the cert. authorities, and then they would have to be added to the BIOS database. Older boot media won't have those yet, besides, needing to buy those certs would make some free software not free anymore, so also those won't always have those certs, even if the software is more trustworthy than an m$ OS... Secureboot is an attempt to keep you booting any other OS than m$ OS under the pretext of keeping malware off.
3. "...MBR or Master Boot Record must be created on drives at 2TB or smaller to make it bootable. Whereas, if the drive is larger than 2TB, a GPT must be created to make that partition or hard drive bootable..."
MBR or GPT disks don't have anything to do with making the disk bootable. It just defines how much of the disk's size is accessible. An MBR disk limits the accessible size to 2TB, even if the disk is larger, while a GPT disk allows you to access more than 2TB space.
1. "...the UEFI BIOS which will permit formatting drives larger than 2TB."
You don't need a UEFI BIOS to use disks larger than 2TB. In order to be able use all the data on a disk larger than 2TB, it just needs to be made a GPT disk. GPT disks are supported by both, legacy and UEFI BIOSes. But is your OS happens to be an m$ OS, you can't boot to a GPT disk if the BIOS isn't also UEFI. But there is no problem booting to an MBR disk and accessing a 2nd disk that is GPT. Other OS's hat aren't from m$ don't have that restriction. You can boo Linux from a GPT disk even if the BIOS is legacy, for example.
2 "...some reconfiguration, especially disabling Secure Boot, before setting the desired boot sequence..."
The boot sequence has nothing to do with "secureboot". Secureboot is a function in the BIOS which checks all your media for certificates that have been accepted as safe to boot from. Those certificates are stored in the BIOS database, and included on the media, but they aren't free. Manufacturers of OS's and boot media would have to buy those certs from the cert. authorities, and then they would have to be added to the BIOS database. Older boot media won't have those yet, besides, needing to buy those certs would make some free software not free anymore, so also those won't always have those certs, even if the software is more trustworthy than an m$ OS... Secureboot is an attempt to keep you booting any other OS than m$ OS under the pretext of keeping malware off.
3. "...MBR or Master Boot Record must be created on drives at 2TB or smaller to make it bootable. Whereas, if the drive is larger than 2TB, a GPT must be created to make that partition or hard drive bootable..."
MBR or GPT disks don't have anything to do with making the disk bootable. It just defines how much of the disk's size is accessible. An MBR disk limits the accessible size to 2TB, even if the disk is larger, while a GPT disk allows you to access more than 2TB space.
ASKER
Hello
I always thought that the MBR is the area of the hard drive which stores system boot up files needed by the operating system to load. In other words, the hard drive is not bootable unless the system files are present. For instance, the older drives would have system files such as the config.sys , autoexec.bat, and I believe sys.com which would allow Windows 95 to load. It seems reasonable to even the more modern operating systems such as Windows 7 and Windows 8 would follow a similar premise. Now, the names of these boot up files might be different as compared to the ones used in the Windows 95 and Windows 98 days.
With respect to my comments about 2TB and larger hard disk drives, I need to clarify further what I meant by my statements. I always look at the hard drive consisting of a Primary Partition or C Drive which is the bootable sector of the HDD along with an Extended Partition which acts like a container with Logical Drives. For older computers which do not have a UEFI BIOS, the hard drive will need to be partitioned off using a utility like GParted Live CD or within the tools given by Windows for disk management to divide up the HDD into 2TB or smaller portions. With respect toe GPT, I always thought that was a new standard used in defining much larger 2TB HDD and greater and came out about the time of UEFI BIOS. In other words, if the Primary (bootable partition) is larger than 2TB, then, GPT would be used instead of MBR.
In closing, I realize that I am still learning here and certainly do not have all of the answers. I can merely reflect upon my own conclusions and come forward with them for possible correction and elaboration. At any rate, just further thoughts here.
Take care
George
I always thought that the MBR is the area of the hard drive which stores system boot up files needed by the operating system to load. In other words, the hard drive is not bootable unless the system files are present. For instance, the older drives would have system files such as the config.sys , autoexec.bat, and I believe sys.com which would allow Windows 95 to load. It seems reasonable to even the more modern operating systems such as Windows 7 and Windows 8 would follow a similar premise. Now, the names of these boot up files might be different as compared to the ones used in the Windows 95 and Windows 98 days.
With respect to my comments about 2TB and larger hard disk drives, I need to clarify further what I meant by my statements. I always look at the hard drive consisting of a Primary Partition or C Drive which is the bootable sector of the HDD along with an Extended Partition which acts like a container with Logical Drives. For older computers which do not have a UEFI BIOS, the hard drive will need to be partitioned off using a utility like GParted Live CD or within the tools given by Windows for disk management to divide up the HDD into 2TB or smaller portions. With respect toe GPT, I always thought that was a new standard used in defining much larger 2TB HDD and greater and came out about the time of UEFI BIOS. In other words, if the Primary (bootable partition) is larger than 2TB, then, GPT would be used instead of MBR.
In closing, I realize that I am still learning here and certainly do not have all of the answers. I can merely reflect upon my own conclusions and come forward with them for possible correction and elaboration. At any rate, just further thoughts here.
Take care
George
MBR or GPT doesn't make a disk bootable, for that you require additional bootcode. The first part of the bootcode though is stored in the partition table, whether it is GPT or MBR.
Any disk larger than 2 TB has to be GPT, whether it is the disk you boot from or not, provided you want to access all the space on the disk. If you make a disk that is larger than 2TB an MBR disk, you will only be able to access 2TB of it the rest of the space is lost.
Extended partitions were a way of allowing MBR disks to be divided into more than 4 partitions, as MBR disks only allow you to have a maximum of 4 primary partitions. A further limitation was that Windows OS's could only be installed to primary partitions, as most of the bootcode for those OS's needed to be started from a primary partition. This limit again is not valid for linux, you can install Linux to logical partitions within an extended partition. Only the boot loader from which you choose what OS to boot from needs to be on a primary partition.
GPT disks don't support extended partitions anymore, but it also doesn't have the 4 primary partition limit.
Any disk larger than 2 TB has to be GPT, whether it is the disk you boot from or not, provided you want to access all the space on the disk. If you make a disk that is larger than 2TB an MBR disk, you will only be able to access 2TB of it the rest of the space is lost.
Extended partitions were a way of allowing MBR disks to be divided into more than 4 partitions, as MBR disks only allow you to have a maximum of 4 primary partitions. A further limitation was that Windows OS's could only be installed to primary partitions, as most of the bootcode for those OS's needed to be started from a primary partition. This limit again is not valid for linux, you can install Linux to logical partitions within an extended partition. Only the boot loader from which you choose what OS to boot from needs to be on a primary partition.
GPT disks don't support extended partitions anymore, but it also doesn't have the 4 primary partition limit.
And it doesn't help to have your OS on a <2TB partition on a >2TB disk unless you have a BIOS that can boot from a DISK that is bigger than 2TB ie UEFI
The size of the partition is irrelevant in this situation
The size of the partition is irrelevant in this situation
That only applies to m$ OS's. Linux, BSD etc. can handle booting to GPT disks even if the BIOS isn't UEFI. So requiring UEFI to boot to GPT disk is a limit that was introduced by m$'s OS's, either due to poor programming or deliberately, maybe for marketing reasons.
The OP was about NTFS , I think we can assume that it's Windows involved
ASKER
Hello
Yes, it is about Windows. I am not versed or experienced in any of the other operating systems.
Thanks
George
Yes, it is about Windows. I am not versed or experienced in any of the other operating systems.
Thanks
George
ASKER
With respect to hard disk management tools, can someone recommend a really good one for formatting and creating/managing partitions on the larger hard disk drives?
Thank you
George