[OpenIndiana-discuss] How should a disk partition layout looks like

[Carsten Grzemba]

Am 06.01.23 11:43 schrieb Toomas Soome  <tsoome at me.com>: 
> 
> 
> 
> > On 6. Jan 2023, at 12:06, Carsten Grzemba via openindiana-discuss <openindiana-discuss at openindiana.org> wrote:
> > 
> > I have a disk installed with Openindiana and installboot shows bootloader at cxt0d0s1 and has not cxt0d0p1
> > The disk will not recognized by BIOS for boot but it boots if selected in loader.
> > 
> > On other resources shows EFI boot files on cxt0d0p1.
> > 
> > Is p1 partition necessary for boot?
> > How looks like a correct disk partitioning nowadys?
> > 
> 
> sX is partition from either GPT or VTOC
> 
> p0 is whole disk
> p1-p4 are MBR primary partitions and p5.. are extended.
> 
> With GPT you have MBR in absolute sector 0 and only one partition defined (EFI), this is “protective” MBR and meant to tell non-GPT aware partition programs that you have partition defined. GPT itself is on absolute sector 1 and followed by partition array.
> 
> Classic Solaris x86 partitioning is MBR + VTOC, you are supposed to have one Solaris2 MBR primary partition per disk and on that partition you have VTOC. 
> 
> With zpool “whole disk” setup, you will get GPT partitioning, with s0[, s1] and s8 defined (GPT does not allow overlapping partitions). Depending if zpool create -B was used, you may or may not have efi system partition.
> 
> MBR + VTOC scheme is assuming you have single Solaris2 MBR (primary) partition, in it you have VTOC table and it has to be manually described (usually has root, backup (s2) and boot slices).
> 
> rgds,
> toomas
> 

 
I have: 

 Total disk size is 60799 cylinders Cylinder size is 64260 (512 byte) blocks Cylinders Partition Status Type Start End Length % ========= ====== ============ ===== === ====== === 1 EFI 0 60799 60800 100 # prtvtoc /dev/rdsk/c3t0d0s0
* /dev/rdsk/c3t0d0s0 EFI partition map
*
* Dimensions:
* 512 bytes/sector
* 3906963456 sectors
* 3906963389 accessible sectors
*
* Flags:
* 1: unmountable
* 10: read-only
*
* Unallocated space:
* First Sector Last
* Sector Count Sector
* 34 222 255
*
* First Sector Last
* Partition Tag Flags Sector Count Sector Mount Directory 0 12 00 256 524288 524543 1 4 00 524544 3906422495 3906947038 8 11 00 3906947039 16384 3906963422
 
 

but installboot show boot files on s1



# installboot -V -i /dev/rdsk/c3t0d0s1
PMBR block from /dev/rdsk/c3t0d0p0:
Format: loader (illumos)
Signature: 0xaa55 (valid)
UniqueMBRDiskSignature: 0x5f107
Loader STAGE1_STAGE2_LBA: 524544
Loader STAGE1_STAGE2_SIZE: 1
Loader STAGE1_STAGE2_UUID: f24d9e68-cfe1-6158-8448-dc2a119643a3 VBR block from /dev/rdsk/c3t0d0s1:
Format: loader (illumos)
Signature: 0xaa55 (valid)
UniqueMBRDiskSignature: 0
Loader STAGE1_STAGE2_LBA: 525568
Loader STAGE1_STAGE2_SIZE: 279
Loader STAGE1_STAGE2_UUID: f24d9e68-cfe1-6158-8448-dc2a119643a3 Boot block from /dev/rdsk/c3t0d0s1:
Boot Block Extended Info Header: magic: EXTINFO version: 1 flags: 0 extended version string offset: 71 extended version string size: 16 hashing type: 1 (MD5) hash offset: 54 hash size: 16
Extended version string: 1.1-2022.09.04.1
MD5 hash: cadb10776e17f7ff8d53653ae3b8e9c2 # installboot -V -i /dev/rdsk/c3t0d0s2
open: I/O error
# installboot -V -i /dev/rdsk/c3t0d0s0
Booting pcfs from EFI labeled disks requires the boot partition.

Is s1 the correct location? Should BIOS recognizes the boot disk?


-- 
Carsten