Hitchhiker's Guide to Openbsd

Partition id ('0' to disable) [0 - FF]: [0] (? for help) a6
Do you wish to edit in CHS mode? [n] Enter
offset: [0]
uh-oh! What's our offset? Simple -- the offset of the previous partition plus the size of the partition, in this case, 63
[phone] = 10490445. 
http://www.openbsd.org/faq/faq4.html (21 of 43)9/4/2011 10:01:58 AM

---

4 - OpenBSD 4.9 Installation Guide
offset: [0] 10490445
size: [0] *
fdisk:*1>
Note that here, we entered "*" as the size, meaning "rest of the disk". Again, we could have entered the size in sectors, 
"m" or "g" if we wanted to leave space for something else. 
Now we look at our partition table: 
fdisk:*1> p
Disk: wd0 geometry: 4998/255/63 [80293248 Sectors]
Offset: 0 Signature: 0x0
Starting Ending LBA Info:
#: id C H S - C H S [ start: size ]
-------------------------------------------------------------------------------
0: 07 0 1 1 - 652 254 63 [ 63: 10490382 ] NTFS
1: A6 653 0 1 - 4998 5 63 [ 10490445: 69802803 ] OpenBSD
2: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused
3: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused
fdisk:*1>
WE AREN'T DONE YET!
This disk is not yet bootable! As it was a brand new disk, the disk's 
MBR
 was completely blank. The "Signature: 0x0" 
message there shows there is not a valid signature (0xAA55), which indicates there definitely is not a valid boot code. Of 
course, you could have a valid signature without valid boot code, through either random bad luck or damage to the 
existing boot code, but an invalid signature pretty well indicates you are lacking boot code, so we will install it now using 
the "update" command: 
fdisk:*1> update
Machine code updated.
fdisk:*1>
We also have to "flag" a partition as "active" so the boot ROM knows what partition to boot from: 
fdisk:*1> f 1