Re: Creating a GPT tab

[John Nemeth <jnemeth%cue.bc.ca@localhost>]

On Jan 24, 11:49, Brook Milligan wrote:
}
} I am trying to create GPT partitions that are the same as the following:
} 
} # fdisk sd0
} fdisk: Cannot determine the number of heads
} Disk: /dev/rsd0
} NetBSD disklabel disk geometry:
} cylinders: 118152, heads: 64, sectors/track: 32 (2048 sectors/cylinder)
} total sectors: 241975296, bytes/sector: 512
} 
} BIOS disk geometry:
} cylinders: 1023, heads: 255, sectors/track: 63 (16065 sectors/cylinder)
} total sectors: 241975296
} 
} Partitions aligned to 2048 sector boundaries, offset 63
} 
} Partition table:
} 0: Primary DOS with 32 bit FAT - LBA (sysid 12)
}     start 32768, size 163840 (80 MB, Cyls 2/10/9-12/60/48), Active
} 1: <UNUSED>
} 2: <UNUSED>
} 3: GPT Protective MBR (sysid 238)
}     start 1, size 32767 (16 MB, Cyls 0/0/2-2/10/8)
}         PBR is not bootable: Bad magic number (0x0000)
} First active partition: 0
} Drive serial number: 0 (0x00000000)

     This is a bit of a mess, as you should NEVER EVER have anything
other than a "GPT Protective MBR" in the MBR on a disk that has a
GPT.  This is basically mixing two very different partitioning
schemes on the same disk (that can only lead to sadness).

} # gpt show sd0
}       start       size  index  contents
}           0          1         MBR
}           1          1         Pri GPT header
}           2         32         Pri GPT table
}          34      32734         Unused
}       32768     163840      1  GPT part - Windows basic data
}      196608   33554432      2  GPT part - NetBSD FFSv1/FFSv2
}    33751040  207618048      3  GPT part - NetBSD FFSv1/FFSv2
}   241369088     606175         Unused
}   241975263         32         Sec GPT table
}   241975295          1         Sec GPT header
} 
} The complicating factor is that there is an MBR in sector 0 and
} the primary GPT begins at sector 1.
} 
} I cannot figure out how to make the tools replicate this and
} would appreciate help.

     The tools won't replicate this, nor should they, as it is a
seriously broken setup.  To fix this setup, delete MBR parition 0.

}-- End of excerpt from Brook Milligan