List Info

Thread: Re: Is there a macppc/MBR/ofwboot copy bug?




Re: Is there a macppc/MBR/ofwboot copy bug?
country flaguser name
Netherlands
2007-05-09 08:36:29
On Wed, 9 May 2007, Michael Dexter wrote:

> Hello all,
> 
> <Sorry if this is not hard-wrapped, several terminal
screens are used>
> 
> I finally figured out the problem of the ofwboot file
not being copied during installation and I am pretty sure
that an answer is not published.
> 
> I take this to be either an installer bug or a
documentation bug as the following warning is given during
installation but without instructions on how to perform the
task or the variables required to perform it (on a mac mini
with 80GB drive):
> 
> 
> Formatting 1MB MSDOS boot partition...done.
> 
> You *MUST* setup the OpenBSD disklabel to include the
MSDOS-formatted boot
> partition as the 'i' partition. If the 'i' partition is
missing or not the
> MSDOS-formatted boot partition, then the kernel
required to boot
> OpenBSD cannot be installed.
> 
> # Inside MBR partition 3: type A6 start 3024 size
156298464
> 
> Treating sectors 3024-156301488 as the OpenBSD portion
of the disk.
> You can use the 'b' command to change this.
> 
> Initial label editor (enter '?' for help at any
prompt)
> >
> 
> 
> This tells us three useful things:
> 
> 1. We need the MSDOS 'i' partition.
> 2. The OpenBSD partition starts at offset 3024 and...
> 3. You can use the 'b' option to change this.
> 
> 
> Because the installer next puts you into interactive
disklabel, it neither reports the fdisk output nor gives you
the option to type '!fdisk wd0'
> 
> You can quit the installation and run 'fdisk wd0' but
it will probably not allow you to restart the installation
as you are already in the disk setup section.
> 
> What fdisk WOULD report is:
> 
>  #: id    C   H  S -    C   H  S [       start:     
size   ]
>
------------------------------------------------------------
------------
> *0: 06    0   0  2 -    2   0 33 [           1:       
2048 ] DOS > 32MB  
>  1: 00    0   0  0 -    0   0  0 [           0:        
  0 ] unused      
>  2: 00    0   0  0 -    0   0  0 [           0:        
  0 ] unused      
>  3: A6    3   0  1 - 155060  15 63 [        3024:  
156298464 ] OpenBSD 
> 
> Beyond confirming that the MSDOS MBR partition was
created, it tells us the missing 4th and 5th  pieces of
information:
> 
> 4. The MSDOS "portion of the disk" starts at
offset 1 and
> 5. Has a size of 2048.
> 
> Should one try to use interactive disklable to create
the 'i' partition as instructed, disklabel will PREVENT you
from setting its correct offset of 1 as it already knows it
is in the 3rd MBR/fdisk partition starting at 3024.
> 
> To resolve this, one must temporarily tell disklabel
that the "OpenBSD portion" is offset 1 and create
the MSDOS 'i' partition:
> 
> > b <enter>
> Starting sector: [3024] 1 <enter>
> Size ('*' for entire disk): [156298464] <enter>
> > a i <enter>
> offset: [1] <enter>
> size: [156298464] 2048 <enter>
> FS type: [4.2BSD] MSDOS <enter>
> mount point: [none] <enter, not /mnt2 for
installation as this may go to fstab>
> > b <enter>
> Starting sector: [1] 3024 <enter, returning to where
we started>
> Size ('*' for entire disk): [156298464] <enter>
> > p <continue with normal labling from here>
> ...
> 16 partitions:
> #        size    offset    fstype    [fsize   bsize   
cpg]
>  c: 156301488         0    unused         0       0
>  i:      2048         1     MSDOS

Why go through all this trouble? The initial disk label
already
contains the correct i partition. Issue the p command at the
disklabel
prompt and you should see it when you first enter
disklabel(8) after
MBR creation. 

If your initial disklabel does not contain the i partition,
that is
the bug we should try to figure out.

So please verify the output of the p command, before you do
anything
else in disklabel. 

	-Otto


Re: Is there a macppc/MBR/ofwboot copy bug?
country flaguser name
Latvia
2007-05-09 11:18:06
>So please verify the output of the p command, before you
do anything
>else in disklabel. 

Alas, it did not and that what led to this adventure. fdisk
would show the MSDOS and OpenBSD MBR partitions but
disklabel does not report any beyond c.

I have tried this with both 4.0 and 4.1 on a Mac mini.

Michael.

P.S. The instructions correctly suggest that stopping the
install process with ctrl-z would allow for viewing fdisk
output and the like.

Also, is there any logic to how the 'i' partition is mapped
to the below-OpenBSD mbr/fdisk partition? How might one
point to the other possible mbr partitions?

And, for what it's worth, I am curious if while the
installer supports HFS partitions, will the OS? I see an
hfsplus packages but it uses both strange command
conventions (no mount_hfs...) and refers to a dead web
site.


[1-2]

about | contact  Other archives ( Real Estate discussion Medical topics )