GPT - Revision history

Mcefan at 22:43, 19 October 2012

2012-10-19T22:43:47Z

←Older revision		Revision as of 22:43, 19 October 2012
Line 3:		Line 3:
	\|}		\|}
	[[Category:Installation Tutorials]]		[[Category:Installation Tutorials]]
			[[Category:Hardware\| ]]


	If you want to create partitions larger than 2TB you'll have to use GTP partitioning system instead of classical MBR. Note that you BIOS knows only MBR partitioning schema and will not likely boot from a GTP partition. You cannot mix GTP and MBR partitions on a single drive so drives larger than 2TB will need to be completely GTP and will be non-bootable; you will need a separate hard drive that contains the system.		If you want to create partitions larger than 2TB you'll have to use GTP partitioning system instead of classical MBR. Note that you BIOS knows only MBR partitioning schema and will not likely boot from a GTP partition. You cannot mix GTP and MBR partitions on a single drive so drives larger than 2TB will need to be completely GTP and will be non-bootable; you will need a separate hard drive that contains the system.

Mcefan at 22:42, 19 October 2012

2012-10-19T22:42:17Z

←Older revision		Revision as of 22:42, 19 October 2012
Line 2:		Line 2:
	\| __TOC__		\| __TOC__
	\|}		\|}
	[[Category:Tutorials]]		[[Category:Installation Tutorials]]

	If you want to create partitions larger than 2TB you'll have to use GTP partitioning system instead of classical MBR. Note that you BIOS knows only MBR partitioning schema and will not likely boot from a GTP partition. You cannot mix GTP and MBR partitions on a single drive so drives larger than 2TB will need to be completely GTP and will be non-bootable; you will need a separate hard drive that contains the system.		If you want to create partitions larger than 2TB you'll have to use GTP partitioning system instead of classical MBR. Note that you BIOS knows only MBR partitioning schema and will not likely boot from a GTP partition. You cannot mix GTP and MBR partitions on a single drive so drives larger than 2TB will need to be completely GTP and will be non-bootable; you will need a separate hard drive that contains the system.

Tekoholic at 01:09, 5 November 2011

2011-11-05T01:09:06Z

←Older revision		Revision as of 01:09, 5 November 2011
Line 4:		Line 4:
	[[Category:Tutorials]]		[[Category:Tutorials]]
	If you want to create partitions larger than 2TB you'll have to use GTP partitioning system instead of classical MBR. Note that you BIOS knows only MBR partitioning schema and will not likely boot from a GTP partition. You cannot mix GTP and MBR partitions on a single drive so drives larger than 2TB will need to be completely GTP and will be non-bootable; you will need a separate hard drive that contains the system.		If you want to create partitions larger than 2TB you'll have to use GTP partitioning system instead of classical MBR. Note that you BIOS knows only MBR partitioning schema and will not likely boot from a GTP partition. You cannot mix GTP and MBR partitions on a single drive so drives larger than 2TB will need to be completely GTP and will be non-bootable; you will need a separate hard drive that contains the system.

			--forgive me, but this is no longer accurate. I've got some pretty old gear around here, and NOT ONE of my systems has any trouble booting to GPT (as opposed to "GTP") mbr... --tekoholic


	== Creating Partitions ==		== Creating Partitions ==
	You'll need to use parted to create the partitions since fdisk only know to work with MBR. The next command will open a parted shell, you'll need to replace /dev/sda with the drive that you want to partition.		You'll need to use parted to create the partitions since fdisk only know to work with MBR. The next command will open a parted shell, you'll need to replace /dev/sda with the drive that you want to partition.

Rwilson131 at 04:23, 6 December 2008

2008-12-06T04:23:42Z

←Older revision		Revision as of 04:23, 6 December 2008
Line 2:		Line 2:
	\| __TOC__		\| __TOC__
	\|}		\|}
			[[Category:Tutorials]]
	If you want to create partitions larger than 2TB you'll have to use GTP partitioning system instead of classical MBR. Note that you BIOS knows only MBR partitioning schema and will not likely boot from a GTP partition. You cannot mix GTP and MBR partitions on a single drive so drives larger than 2TB will need to be completely GTP and will be non-bootable; you will need a separate hard drive that contains the system.		If you want to create partitions larger than 2TB you'll have to use GTP partitioning system instead of classical MBR. Note that you BIOS knows only MBR partitioning schema and will not likely boot from a GTP partition. You cannot mix GTP and MBR partitions on a single drive so drives larger than 2TB will need to be completely GTP and will be non-bootable; you will need a separate hard drive that contains the system.
	== Creating Partitions ==		== Creating Partitions ==

Rwilson131 at 04:23, 6 December 2008

2008-12-06T04:23:21Z

←Older revision		Revision as of 04:23, 6 December 2008
Line 1:		Line 1:
			{\| align="right"
			\| __TOC__
			\|}
	If you want to create partitions larger than 2TB you'll have to use GTP partitioning system instead of classical MBR. Note that you BIOS knows only MBR partitioning schema and will not likely boot from a GTP partition. You cannot mix GTP and MBR partitions on a single drive so drives larger than 2TB will need to be completely GTP and will be non-bootable; you will need a separate hard drive that contains the system.		If you want to create partitions larger than 2TB you'll have to use GTP partitioning system instead of classical MBR. Note that you BIOS knows only MBR partitioning schema and will not likely boot from a GTP partition. You cannot mix GTP and MBR partitions on a single drive so drives larger than 2TB will need to be completely GTP and will be non-bootable; you will need a separate hard drive that contains the system.

	== Creating Partitions ==		== Creating Partitions ==
	You'll need to use parted to create the partitions since fdisk only know to work with MBR. The next command will open a parted shell, you'll need to replace /dev/sda with the drive that you want to partition.		You'll need to use parted to create the partitions since fdisk only know to work with MBR. The next command will open a parted shell, you'll need to replace /dev/sda with the drive that you want to partition.
Line 19:		Line 21:
	After doing the previous command, you should have created two partitions, a 3TB and a 2TB one. In order for udev to create /dev/sda1 and /dev/sda2 devices associated with the partitions, you need to run the next command or reboot your computer:		After doing the previous command, you should have created two partitions, a 3TB and a 2TB one. In order for udev to create /dev/sda1 and /dev/sda2 devices associated with the partitions, you need to run the next command or reboot your computer:
	partprobe /dev/sda		partprobe /dev/sda

	== Formating the Partitions ==		== Formating the Partitions ==

	Except of partition creation you won't see any difference between GPT and MBR in linux. So for formatting you can do it the same way as you would format any other discs. For example:		Except of partition creation you won't see any difference between GPT and MBR in linux. So for formatting you can do it the same way as you would format any other discs. For example:

	mkfs.ext3 /dev/sda1		mkfs.ext3 /dev/sda1


	== Resize Partition Table ==		== Resize Partition Table ==
	If you partitioned a raid array with GPT and you later increased the size by adding more disks you must run parted again on that drive and tell it to use all available space. A simple 'print' command in parted will use the warning message to which you you need to answe 'F'.		If you partitioned a raid array with GPT and you later increased the size by adding more disks you must run parted again on that drive and tell it to use all available space. A simple 'print' command in parted will use the warning message to which you you need to answe 'F'.

	# parted /dev/sda		# parted /dev/sda

Line 36:		Line 32:
	of the space (an extra 1953103872 blocks) or continue with the current setting?		of the space (an extra 1953103872 blocks) or continue with the current setting?
	Fix/Ignore? F		Fix/Ignore? F


	== Resize Existing Partitions ==		== Resize Existing Partitions ==

	'''Warning:''' <span style="color: #700">Parted has some known bugs in both Ubuntu 0710 and LinuxMCE that will prevent resizing of a ext3 partition. Until this bugs get fixed the next instruction are here just for information purpose.</span>		'''Warning:''' <span style="color: #700">Parted has some known bugs in both Ubuntu 0710 and LinuxMCE that will prevent resizing of a ext3 partition. Until this bugs get fixed the next instruction are here just for information purpose.</span>

	Parted can also resize an existing partition to fill some unused space that you added. Before trying doing the partition resize check first that you partition is umounted and that it the filesystem on it is fine. Parted will complain about mounted partitions or inconsistent filesystem anyway.		Parted can also resize an existing partition to fill some unused space that you added. Before trying doing the partition resize check first that you partition is umounted and that it the filesystem on it is fine. Parted will complain about mounted partitions or inconsistent filesystem anyway.

Razvang: /* Resize Existing Partitions */

2008-03-31T07:18:38Z

Resize Existing Partitions

←Older revision		Revision as of 07:18, 31 March 2008
Line 40:		Line 40:
	== Resize Existing Partitions ==		== Resize Existing Partitions ==

	'''Warning:''' <span style="color: #700">Parted has some known bugs in both Ubuntu 0710 and LinuxMCE that will prevent resizing of a ext3 partition. ~~Utils~~ this bugs get fixed the next instruction are here just for information purpose.</span>		'''Warning:''' <span style="color: #700">Parted has some known bugs in both Ubuntu 0710 and LinuxMCE that will prevent resizing of a ext3 partition. Until this bugs get fixed the next instruction are here just for information purpose.</span>

	Parted can also resize an existing partition to fill some unused space that you added. Before trying doing the partition resize check first that you partition is umounted and that it the filesystem on it is fine. Parted will complain about mounted partitions or inconsistent filesystem anyway.		Parted can also resize an existing partition to fill some unused space that you added. Before trying doing the partition resize check first that you partition is umounted and that it the filesystem on it is fine. Parted will complain about mounted partitions or inconsistent filesystem anyway.

Razvang: /* Resize Partition Table */

2008-03-31T07:18:07Z

Resize Partition Table

←Older revision		Revision as of 07:18, 31 March 2008
Line 36:		Line 36:
	of the space (an extra 1953103872 blocks) or continue with the current setting?		of the space (an extra 1953103872 blocks) or continue with the current setting?
	Fix/Ignore? F		Fix/Ignore? F


			== Resize Existing Partitions ==

			'''Warning:''' <span style="color: #700">Parted has some known bugs in both Ubuntu 0710 and LinuxMCE that will prevent resizing of a ext3 partition. Utils this bugs get fixed the next instruction are here just for information purpose.</span>

	Parted can also resize an existing partition to fill some unused space that you added. Before trying doing the partition resize check first that you partition is umounted and that it the filesystem on it is fine. Parted will complain about mounted partitions or inconsistent filesystem anyway.		Parted can also resize an existing partition to fill some unused space that you added. Before trying doing the partition resize check first that you partition is umounted and that it the filesystem on it is fine. Parted will complain about mounted partitions or inconsistent filesystem anyway.

Razvang: /* Formating the Partitions */

2008-03-11T13:52:10Z

Formating the Partitions

←Older revision		Revision as of 13:52, 11 March 2008
Line 25:		Line 25:

	mkfs.ext3 /dev/sda1		mkfs.ext3 /dev/sda1


			== Resize Partition Table ==
			If you partitioned a raid array with GPT and you later increased the size by adding more disks you must run parted again on that drive and tell it to use all available space. A simple 'print' command in parted will use the warning message to which you you need to answe 'F'.

			# parted /dev/sda

			(parted) print
			Warning: Not all of the space available to /dev/sda appears to be used, you can fix the GPT to use all
			of the space (an extra 1953103872 blocks) or continue with the current setting?
			Fix/Ignore? F

			Parted can also resize an existing partition to fill some unused space that you added. Before trying doing the partition resize check first that you partition is umounted and that it the filesystem on it is fine. Parted will complain about mounted partitions or inconsistent filesystem anyway.

			For example, let's take a 5000GB drive that has a 4000GB ext3 partition on it.
			(parted) print
			Model: AMCC 9650SE-16M DISK (scsi)
			Disk /dev/sda: 5000GB
			Sector size (logical/physical): 512B/512B
			Partition Table: gpt

			Number Start End Size File system Name Flags
			1 17.4kB 4000GB 4000GB ext3 primary

			To resize that partition, you need to use the ''resize'' parted command which has the fallowing syntax :
			resize <partition_no> <new_start> <new_end>

			To transform the partition from our example from 4000GB to 5000GB :
			(parted) resize 1 0GB 5000GB

Aaron.b at 16:16, 29 February 2008

2008-02-29T16:16:16Z

←Older revision		Revision as of 16:16, 29 February 2008
Line 1:		Line 1:
	If you want to create partitions larger than 2TB you'll have to use GTP partitioning system instead of classical MBR. Note that you BIOS knows only MBR partitioning schema and will not likely boot from a GTP partition.		If you want to create partitions larger than 2TB you'll have to use GTP partitioning system instead of classical MBR. Note that you BIOS knows only MBR partitioning schema and will not likely boot from a GTP partition. You cannot mix GTP and MBR partitions on a single drive so drives larger than 2TB will need to be completely GTP and will be non-bootable; you will need a separate hard drive that contains the system.

	== Creating Partitions ==		== Creating Partitions ==

Razvang: /* Formating the partitions */

2008-02-29T15:44:51Z

Formating the partitions

←Older revision		Revision as of 15:44, 29 February 2008
Line 20:		Line 20:
	partprobe /dev/sda		partprobe /dev/sda

	== Formating the ~~partitions~~ ==		== Formating the Partitions ==

	Except of partition creation you won't see any difference between GPT and MBR in linux. So for formatting you can do it the same way as you would format any other discs. For example:		Except of partition creation you won't see any difference between GPT and MBR in linux. So for formatting you can do it the same way as you would format any other discs. For example:

	mkfs.ext3 /dev/sda1		mkfs.ext3 /dev/sda1