The closest document I could find, and this is the one referred to in the Windows Host Connectivity Guide is "Using diskpar and diskpart to Align Partitions on Windows Basic and Dynamic Disks"
@space: Thanks. I have seen that document. Unfortunately, there's no mention of aligning GPT disks. The only reference to GPT is in the partition table contents (the hex value listing partition table type).
@AranH: Good catch on the 17K offset. I would bet that this *does* affect the overall disk alignment.
I'm searching now to see if there are any tools for manually messing with GPT partitions...
Well I used to think that GPT disks required the alignment offset, but now after reading up on them a bit more I am not so sure.
The knowledge base article emc104675 states that GPT disks do require alignment and refers to the white paper you mentioned, but I cannot find that white paper either. There is a white paper titled " Using diskpar and diskpart to align partitions on Windows Basic and Dynamic Disks" but there is no mention of GPT disk in he document.
If I look at the partitions on a GPT disk on a host , this is what I see: DISKPART> list partition
So the reserved partition on a GPT disk is, as referenced in the GPT literature from MS, 128 MB. But the offset is 17KB which is not ideal for the stripe alignment right? This is assuming that the reserved partition affects the data partition. This reserved partition is created automatically when the disk is converted from basic to GPT so I don't know if there is a way to set that offset value.
With some poking around, I did find that you can, in fact, change the offset for the hidden GPT partition. If our assumption is correct that the 17KB offset *does* impact GPT disk alignment, then the process below would correct that.
I'd still like EMC to say, "Yes, GPT partitions need to be aligned and here's the approved/recommended way to do it.". I'll see if anyone replies within the next couple of days. If not, I'll put in a phone call
A couple of notes on what's below: 1. The default unit for diskpart on GPT disks is MB and there doesn't appear to be a way to change this. As a result the smallest offset is 1 MB which is fine since it's evenly divisible by 64. Shops using a different element size would need to do the math to find out where this lines up for them. On an MBR disk, the unit is KB for offset values so this is less of an issue. 2. I know the disk is only 1.5TB, but it's likely to be expanded beyond 2TB in the future, hence the need for GPT in the first place
The process (as I see it): DISKPART> list disk
Disk ### Status Size Free Dyn Gpt -------- ---------- ------- ------- --- --- Disk 0 Online 136 GB 0 B Disk 1 Online 136 GB 0 B * Disk 4 Online 1500 GB 1500 GB
DISKPART> convert gpt
DiskPart successfully converted the selected disk to GPT format.
I didn't realize you could delete the MSR without impacting the disk. Very cool. That looks good to me. Now let's get some EMC gurus in here to chime in and see if we are crazy or not
Home > Support > Technical Documentation and Advisories > Hardware/Platforms Documentation > CLARiiON CX3 UltraScale Series Systems > CLARiiON CX3-20 > Technical Notes/Troubleshooting
kelleg
4 Operator
•
4.5K Posts
0
January 7th, 2009 14:00
http://powerlink.emc.com/km/live1/en_US/Offering_Technical/Technical_Documentation/300-004-075_a01_elccnt_0.pdf
glen
StorageDC
10 Posts
0
January 7th, 2009 12:00
jmery
9 Posts
0
January 7th, 2009 12:00
@AranH: Good catch on the 17K offset. I would bet that this *does* affect the overall disk alignment.
I'm searching now to see if there are any tools for manually messing with GPT partitions...
AranH1
2.2K Posts
0
January 7th, 2009 12:00
The knowledge base article emc104675 states that GPT disks do require alignment and refers to the white paper you mentioned, but I cannot find that white paper either. There is a white paper titled " Using diskpar and diskpart to align partitions on Windows Basic and Dynamic Disks" but there is no mention of GPT disk in he document.
If I look at the partitions on a GPT disk on a host , this is what I see:
DISKPART> list partition
Partition ### Type Size Offset
------------- ---------------- ------- -------
Partition 1 Reserved 128 MB 17 KB
Partition 2 Primary 2248 GB 128 MB
So the reserved partition on a GPT disk is, as referenced in the GPT literature from MS, 128 MB. But the offset is 17KB which is not ideal for the stripe alignment right? This is assuming that the reserved partition affects the data partition. This reserved partition is created automatically when the disk is converted from basic to GPT so I don't know if there is a way to set that offset value.
Hmm... Good Question
jmery
9 Posts
0
January 7th, 2009 13:00
With some poking around, I did find that you can, in fact, change the offset for the hidden GPT partition. If our assumption is correct that the 17KB offset *does* impact GPT disk alignment, then the process below would correct that.
I'd still like EMC to say, "Yes, GPT partitions need to be aligned and here's the approved/recommended way to do it.". I'll see if anyone replies within the next couple of days. If not, I'll put in a phone call
A couple of notes on what's below:
1. The default unit for diskpart on GPT disks is MB and there doesn't appear to be a way to change this. As a result the smallest offset is 1 MB which is fine since it's evenly divisible by 64. Shops using a different element size would need to do the math to find out where this lines up for them. On an MBR disk, the unit is KB for offset values so this is less of an issue.
2. I know the disk is only 1.5TB, but it's likely to be expanded beyond 2TB in the future, hence the need for GPT in the first place
The process (as I see it):
DISKPART> list disk
Disk ### Status Size Free Dyn Gpt
-------- ---------- ------- ------- --- ---
Disk 0 Online 136 GB 0 B
Disk 1 Online 136 GB 0 B
* Disk 4 Online 1500 GB 1500 GB
DISKPART> convert gpt
DiskPart successfully converted the selected disk to GPT format.
DISKPART> list partition
Partition ### Type Size Offset
------------- ---------------- ------- -------
Partition 1 Reserved 128 MB 17 KB
DISKPART> select partition 1
Partition 1 is now the selected partition.
DISKPART> delete partition override
DiskPart successfully deleted the selected partition.
DISKPART> list partition
There are no partitions on this disk to show.
DISKPART> create partition msr size=128 offset=1
DiskPart succeeded in creating the specified partition.
DISKPART> list partition
Partition ### Type Size Offset
------------- ---------------- ------- -------
* Partition 1 Reserved 128 MB 1024 KB
Message was edited by:
jmery
AranH1
2.2K Posts
0
January 7th, 2009 13:00
I didn't realize you could delete the MSR without impacting the disk. Very cool. That looks good to me. Now let's get some EMC gurus in here to chime in and see if we are crazy or not
jmery
9 Posts
0
January 7th, 2009 14:00
I'm in the same boat as AranH - how did you find this document? I too searched everything I could think of and wasn't able to locate it.
Also looking forward to the answer to AranH's question on aligning the MSR as well
AranH1
2.2K Posts
0
January 7th, 2009 14:00
No matter how I searched on Powerlink, the search results never came back with this document.
What about the MSR partition? The document does not talk about the need to align the MSR partition.
kelleg
4 Operator
•
4.5K Posts
0
January 7th, 2009 14:00
Home > Support > Technical Documentation and Advisories > Hardware/Platforms Documentation > CLARiiON CX3 UltraScale Series Systems > CLARiiON CX3-20 > Technical Notes/Troubleshooting
kelleg
4 Operator
•
4.5K Posts
0
January 7th, 2009 15:00
Aligning GPT Basic and Dynamic Disks for Microsoft Windows