Re: PC Engines APU2 boot problem

[Raimo Niskanen]

On Wed, Feb 17, 2021 at 02:05:27PM +0100, Raimo Niskanen wrote:
> On Wed, Feb 17, 2021 at 12:36:57PM +0100, Stefan Sperling wrote:
> > On Wed, Feb 17, 2021 at 12:08:52PM +0100, Raimo Niskanen wrote:
> > > Hello misc!
> > > 
> > > I have problem booting an APU2 from SD card and USB stick.
> > > It boots fine from the mSATA disk where I have the OpenBSD installation
> > > that I have upgraded several times using sysupgrade(8).
> > > 
> > > I have tried to write install67.fs and install68.img to an SD card and to
> > > an USB stick from a Linux machine using e.g
> > > dd if=install67.fs of=/dev/sdc bs=1M
> > > 
> > > On the APU:s serial console, I press [F10] to get a boot prompt, and then
> > > select the SD card or the USB stick.  The kernel is loaded and the last
> > > printout is "Entry point: 0x..." something.  The next line
> > > [ELF ... whatnot] does not come.  After a while the APU resets and boots
> > > again, or sometimes hangs.
> > 
> > Before loading a kernel the serial console needs to be enabled with:
> > 
> >   stty com0 115200
> >   set tty com0
> > 
> > On an installed system /etc/boot.conf is usually set up to do this
> > automatically but manual setup is still required when booting from
> > other media.
> 
> Oh, bummer!  Of course.  I hope it is such a stupid mistake!
> I will try when I get a new opportunity...
> 
> Thank you very much.

Confirmed.  It was nothing more than that silly beginner's mistake.
Than you for the cluestick!

-- 

/ Raimo Niskanen, Erlang/OTP, Ericsson AB

Re: PC Engines APU2 boot problem

[Raimo Niskanen]

On Wed, Feb 17, 2021 at 12:36:57PM +0100, Stefan Sperling wrote:
> On Wed, Feb 17, 2021 at 12:08:52PM +0100, Raimo Niskanen wrote:
> > Hello misc!
> > 
> > I have problem booting an APU2 from SD card and USB stick.
> > It boots fine from the mSATA disk where I have the OpenBSD installation
> > that I have upgraded several times using sysupgrade(8).
> > 
> > I have tried to write install67.fs and install68.img to an SD card and to
> > an USB stick from a Linux machine using e.g
> > dd if=install67.fs of=/dev/sdc bs=1M
> > 
> > On the APU:s serial console, I press [F10] to get a boot prompt, and then
> > select the SD card or the USB stick.  The kernel is loaded and the last
> > printout is "Entry point: 0x..." something.  The next line
> > [ELF ... whatnot] does not come.  After a while the APU resets and boots
> > again, or sometimes hangs.
> 
> Before loading a kernel the serial console needs to be enabled with:
> 
>   stty com0 115200
>   set tty com0
> 
> On an installed system /etc/boot.conf is usually set up to do this
> automatically but manual setup is still required when booting from
> other media.

Oh, bummer!  Of course.  I hope it is such a stupid mistake!
I will try when I get a new opportunity...

Thank you very much.

Cheers
-- 

/ Raimo Niskanen, Erlang/OTP, Ericsson AB

PC Engines APU2 boot problem

[Raimo Niskanen]

Hello misc!

I have problem booting an APU2 from SD card and USB stick.
It boots fine from the mSATA disk where I have the OpenBSD installation
that I have upgraded several times using sysupgrade(8).

I have tried to write install67.fs and install68.img to an SD card and to
an USB stick from a Linux machine using e.g
dd if=install67.fs of=/dev/sdc bs=1M

On the APU:s serial console, I press [F10] to get a boot prompt, and then
select the SD card or the USB stick.  The kernel is loaded and the last
printout is "Entry point: 0x..." something.  The next line
[ELF ... whatnot] does not come.  After a while the APU resets and boots
again, or sometimes hangs.

The BIOS is factory installed SeaBIOS 1.10... something.

Can I expect a BIOS upgrade (flashrom) to solve this?  I might have had 2
USB sticks in when booting, might that provoke a bug?

This machine should boot OpenBSD 6.7 from at least an USB stick, right?

Cheers
-- 

/ Raimo Niskanen, Erlang/OTP, Ericsson AB

Re: PC Engines APU2 boot problem

[Stefan Sperling]

On Wed, Feb 17, 2021 at 12:08:52PM +0100, Raimo Niskanen wrote:
> Hello misc!
> 
> I have problem booting an APU2 from SD card and USB stick.
> It boots fine from the mSATA disk where I have the OpenBSD installation
> that I have upgraded several times using sysupgrade(8).
> 
> I have tried to write install67.fs and install68.img to an SD card and to
> an USB stick from a Linux machine using e.g
> dd if=install67.fs of=/dev/sdc bs=1M
> 
> On the APU:s serial console, I press [F10] to get a boot prompt, and then
> select the SD card or the USB stick.  The kernel is loaded and the last
> printout is "Entry point: 0x..." something.  The next line
> [ELF ... whatnot] does not come.  After a while the APU resets and boots
> again, or sometimes hangs.

Before loading a kernel the serial console needs to be enabled with:

  stty com0 115200
  set tty com0

On an installed system /etc/boot.conf is usually set up to do this
automatically but manual setup is still required when booting from
other media.

Re: Dual boot problem

[Greg Thomas]

On Sun, Jun 28, 2020 at 1:13 PM Greg Thomas 
wrote:

> On Sun, Jun 28, 2020 at 9:25 AM Nick Holland 
> wrote:
>
>>
>> from your dmesg:
>> sd0 at scsibus1 targ 0 lun 0: 
>> naa.5000c500b98a130c
>> sd0: 953869MB, 512 bytes/sector, 1953525168 sectors, thin
>> sd1 at scsibus1 targ 1 lun 0: 
>> naa.500a07510369b769
>> sd1: 488386MB, 512 bytes/sector, 1000215216 sectors, thin
>> sd2 at scsibus1 targ 2 lun 0: 
>> naa.5002538844584d30
>> sd2: 244198MB, 512 bytes/sector, 500118192 sectors, thin
>>
>> ERR M basically means that biosboot(8), which is "tagged" with the
>> physical location of /boot(8) on the disk, doesn't see the marker
>> that indicates that what it is pointing at is actually /boot.  The
>> windows 10 boot loader is pulling from a disk other than sd0, the pbr
>> is pointing at something "correct" if it were sd0, but the Windows
>> boot loader is trying to pull it from whatever the new default disk
>> is.  Maybe.
>>
>> There may be some bcdedit magic that can say "boot from this other disk"
>> which might solve your problem, but I have no idea.  A lame way of
>> doing this might be to shrink your Windows partition by 1G, and install
>> your OpenBSD root partition there, and the rest on sd0.
>>
>
> Rad, thanks Nick!  I'm going to poke around with BCDEasy or whatever that
> 3rd party software is since it'll be easier to figure out rather than
> reading through all the bcdedit documentation.  I swear back in the Windows
> ntldr days that I was running Windows and OpenBSD on separate disks so I
> think this should be doable with their current boot loader.
>
> Worse comes to worse I'll go with your last suggestion!
>

I couldn't find any magic with bcdedit/BCDEasy so I shrunk my Windows
partition, did a minimal install of OpenBSD way out there at the end of
sd2, copied over some of /etc, and it's all good.

nihilanon$ fdisk sd2
Disk: sd2 geometry: 31130/255/63 [500118192 Sectors]
Offset: 0 Signature: 0xAA55
Starting Ending LBA Info:
 #: id  C   H   S -  C   H   S [   start:size ]
---
*0: 07  0  32  33 -191  24  25 [2048: 3067904 ] NTFS

 1: 07191  56  58 -  30875 167  12 [ 3072000:   492945408 ] NTFS

 2: A6  30875 167  13 -  31130 158   4 [   496017408: 4096000 ] OpenBSD

 3: 00  0   0   0 -  0   0   0 [   0:   0 ] unused


Next up is OpenVPN, and deciding if I should stick with -stable (most
probably) or start trying snapshots again.

Re: Dual boot problem

[Greg Thomas]

On Sun, Jun 28, 2020 at 12:34 PM Clay Daniels 
wrote:

>
> I too need a Windows install, but I have moved it to my older 2014 machine
> and kept my self-built toy for BSD. I think I need to buy me another SSD to
> run NetBSD too. ;-)
>

Yeah, I'm super fortunate to have found this pretty much unused X220 so I
could just keep the beat up old X220 for Windows.

Re: Dual boot problem

[Greg Thomas]

On Sun, Jun 28, 2020 at 9:25 AM Nick Holland 
wrote:

>
> from your dmesg:
> sd0 at scsibus1 targ 0 lun 0: 
> naa.5000c500b98a130c
> sd0: 953869MB, 512 bytes/sector, 1953525168 sectors, thin
> sd1 at scsibus1 targ 1 lun 0: 
> naa.500a07510369b769
> sd1: 488386MB, 512 bytes/sector, 1000215216 sectors, thin
> sd2 at scsibus1 targ 2 lun 0: 
> naa.5002538844584d30
> sd2: 244198MB, 512 bytes/sector, 500118192 sectors, thin
>
> ERR M basically means that biosboot(8), which is "tagged" with the
> physical location of /boot(8) on the disk, doesn't see the marker
> that indicates that what it is pointing at is actually /boot.  The
> windows 10 boot loader is pulling from a disk other than sd0, the pbr
> is pointing at something "correct" if it were sd0, but the Windows
> boot loader is trying to pull it from whatever the new default disk
> is.  Maybe.
>
> There may be some bcdedit magic that can say "boot from this other disk"
> which might solve your problem, but I have no idea.  A lame way of
> doing this might be to shrink your Windows partition by 1G, and install
> your OpenBSD root partition there, and the rest on sd0.
>

Rad, thanks Nick!  I'm going to poke around with BCDEasy or whatever that
3rd party software is since it'll be easier to figure out rather than
reading through all the bcdedit documentation.  I swear back in the Windows
ntldr days that I was running Windows and OpenBSD on separate disks so I
think this should be doable with their current boot loader.

Worse comes to worse I'll go with your last suggestion!

Greg

Re: Dual boot problem

[Clay Daniels]

On Sun, Jun 28, 2020 at 11:25 AM Nick Holland 
wrote:

> On 2020-06-27 21:50, Greg Thomas wrote:
> > Hey folks, I'm trying to avoid buggin y'all, but I'm down to my last two
> > tasks, setting up dual boot with Windows 10 and setting up OpenVPN.  I'm
> > currently trying to troubleshoot "Loading  ERR M" while using Windows
> > BCD.  I can boot no problem when selecting my boot drive while starting
> up
> > my Thinkpad X220.
> >
> > I installed a couple of weeks ago using pretty much all defaults.
> ...
> > nihilanon# fdisk sd0
> > Disk: sd0 geometry: 121601/255/63 [1953525168 Sectors]
> > Offset: 0 Signature: 0xAA55
> > Starting Ending LBA Info:
> >  #: id  C   H   S -  C   H   S [   start:size ]
> >
> ---
> >  0: 00  0   0   0 -  0   0   0 [   0:   0 ]
> unused
> >  1: 00  0   0   0 -  0   0   0 [   0:   0 ]
> unused
> >  2: 00  0   0   0 -  0   0   0 [   0:   0 ]
> unused
> > *3: A6  0   1   2 - 121600 254  63 [  64:  1953520001 ]
> OpenBSD
>
> I'm not seeing a windows partition here.  And it appears your OpenBSD
> partition is using the entire disk.  Oh. Your computer has three disks
> in it...your Windows install is on a second/third disk?  I don't think
> that is going to work.
>
> from your dmesg:
> sd0 at scsibus1 targ 0 lun 0: 
> naa.5000c500b98a130c
> sd0: 953869MB, 512 bytes/sector, 1953525168 sectors, thin
> sd1 at scsibus1 targ 1 lun 0: 
> naa.500a07510369b769
> sd1: 488386MB, 512 bytes/sector, 1000215216 sectors, thin
> sd2 at scsibus1 targ 2 lun 0: 
> naa.5002538844584d30
> sd2: 244198MB, 512 bytes/sector, 500118192 sectors, thin
>
> ERR M basically means that biosboot(8), which is "tagged" with the
> physical location of /boot(8) on the disk, doesn't see the marker
> that indicates that what it is pointing at is actually /boot.  The
> windows 10 boot loader is pulling from a disk other than sd0, the pbr
> is pointing at something "correct" if it were sd0, but the Windows
> boot loader is trying to pull it from whatever the new default disk
> is.  Maybe.
>
> There may be some bcdedit magic that can say "boot from this other disk"
> which might solve your problem, but I have no idea.  A lame way of
> doing this might be to shrink your Windows partition by 1G, and install
> your OpenBSD root partition there, and the rest on sd0.
>
> Nick.
>
>
I have used Rod Smith's rEFInd boot manager for some time, and started out
installing it in a Windows partition's efi boot section, but it also works
as a stand alone boot usb to pick up all UEFI installations on the entire
computer, either same disk multi-boot or a separate disks on the same
machine. Right now I have FreeBSD 13.0 Current on the spinning disk &
OpenBSD 6.7 -current on the M2 SSD drive. Bear in mind Refind works only
for UEFI, not MBR. If I load NetBSD to the SSD drive as a MBR install, I
have to drop down to the BIOS and pick the boot order there.

I too need a Windows install, but I have moved it to my older 2014 machine
and kept my self-built toy for BSD. I think I need to buy me another SSD to
run NetBSD too. ;-)

Clay

Re: Dual boot problem

[Nick Holland]

On 2020-06-27 21:50, Greg Thomas wrote:
> Hey folks, I'm trying to avoid buggin y'all, but I'm down to my last two
> tasks, setting up dual boot with Windows 10 and setting up OpenVPN.  I'm
> currently trying to troubleshoot "Loading  ERR M" while using Windows
> BCD.  I can boot no problem when selecting my boot drive while starting up
> my Thinkpad X220.
> 
> I installed a couple of weeks ago using pretty much all defaults.
...
> nihilanon# fdisk sd0
> Disk: sd0 geometry: 121601/255/63 [1953525168 Sectors]
> Offset: 0 Signature: 0xAA55
> Starting Ending LBA Info:
>  #: id  C   H   S -  C   H   S [   start:size ]
> ---
>  0: 00  0   0   0 -  0   0   0 [   0:   0 ] unused
>  1: 00  0   0   0 -  0   0   0 [   0:   0 ] unused
>  2: 00  0   0   0 -  0   0   0 [   0:   0 ] unused
> *3: A6  0   1   2 - 121600 254  63 [  64:  1953520001 ] OpenBSD

I'm not seeing a windows partition here.  And it appears your OpenBSD 
partition is using the entire disk.  Oh. Your computer has three disks
in it...your Windows install is on a second/third disk?  I don't think
that is going to work.

from your dmesg:
sd0 at scsibus1 targ 0 lun 0:  naa.5000c500b98a130c
sd0: 953869MB, 512 bytes/sector, 1953525168 sectors, thin
sd1 at scsibus1 targ 1 lun 0:  naa.500a07510369b769
sd1: 488386MB, 512 bytes/sector, 1000215216 sectors, thin
sd2 at scsibus1 targ 2 lun 0:  naa.5002538844584d30
sd2: 244198MB, 512 bytes/sector, 500118192 sectors, thin

ERR M basically means that biosboot(8), which is "tagged" with the
physical location of /boot(8) on the disk, doesn't see the marker
that indicates that what it is pointing at is actually /boot.  The
windows 10 boot loader is pulling from a disk other than sd0, the pbr
is pointing at something "correct" if it were sd0, but the Windows
boot loader is trying to pull it from whatever the new default disk
is.  Maybe.

There may be some bcdedit magic that can say "boot from this other disk"
which might solve your problem, but I have no idea.  A lame way of 
doing this might be to shrink your Windows partition by 1G, and install
your OpenBSD root partition there, and the rest on sd0.

Nick.

Dual boot problem

[Greg Thomas]

Hey folks, I'm trying to avoid buggin y'all, but I'm down to my last two
tasks, setting up dual boot with Windows 10 and setting up OpenVPN.  I'm
currently trying to troubleshoot "Loading  ERR M" while using Windows
BCD.  I can boot no problem when selecting my boot drive while starting up
my Thinkpad X220.

I installed a couple of weeks ago using pretty much all defaults.

nihilanon$ disklabel sd0

# /dev/rsd0c:
type: SCSI
disk: SCSI disk
label: ST1000LM049-2GH1
duid: f251a360129c9562
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 255
sectors/cylinder: 16065
cylinders: 121601
total sectors: 1953525168
boundstart: 64
boundend: 1953520065
drivedata: 0

16 partitions:
#size   offset  fstype [fsize bsize   cpg]
  a:  2097152   64  4.2BSD   2048 16384 12960 # /
  b: 33807608  2097216swap# none
  c:   19535251680  unused
  d:  8388576 35904832  4.2BSD   2048 16384 12960 # /tmp
  e: 74955232 44293408  4.2BSD   2048 16384 12960 # /var
  f: 12582912119248640  4.2BSD   2048 16384 12960 # /usr
  g:  2097152131831552  4.2BSD   2048 16384 12960 #
/usr/X11R6
  h: 41943040133928704  4.2BSD   2048 16384 12960 #
/usr/local
  i:  4194304175871744  4.2BSD   2048 16384 12960 # /usr/src
  j: 12582912180066048  4.2BSD   2048 16384 12960 # /usr/obj
  k:629145600192648960  4.2BSD   4096 32768 26062 # /home

nihilanon# fdisk sd0
Disk: sd0 geometry: 121601/255/63 [1953525168 Sectors]
Offset: 0 Signature: 0xAA55
Starting Ending LBA Info:
 #: id  C   H   S -  C   H   S [   start:size ]
---
 0: 00  0   0   0 -  0   0   0 [   0:   0 ] unused

 1: 00  0   0   0 -  0   0   0 [   0:   0 ] unused

 2: 00  0   0   0 -  0   0   0 [   0:   0 ] unused

*3: A6  0   1   2 - 121600 254  63 [  64:  1953520001 ]
OpenBSD

Since my install is on sd0 I ran the dd command from the FAQ:

dd if=/dev/rsd0a of=openbsd.pbr bs=512 count=1

I moved the PBR to Windows, and ran the bcdedit commands listed in the FAQ plus

bcdedit /set {bootmgr} displaybootmenu yes
bcdedit /set {bootmgr} timeout 12

Thanks for any pointers.  I'm going to re-run the dd command in case I
chose the wrong disk somehow earlier.

Greg

OpenBSD 6.7 (GENERIC.MP) #182: Thu May  7 11:11:58 MDT 2020
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 17041059840 (16251MB)
avail mem = 16511991808 (15747MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xdae9c000 (64 entries)
bios0: vendor LENOVO version "8DET76WW (1.46 )" date 06/21/2018
bios0: LENOVO 4286CTO
acpi0 at bios0: ACPI 4.0
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SLIC SSDT SSDT SSDT HPET APIC MCFG ECDT ASF!
TCPA SSDT SSDT UEFI UEFI UEFI
acpi0: wakeup devices LID_(S3) SLPB(S3) IGBE(S4) EXP4(S4) EXP7(S4)
EHC1(S3) EHC2(S3) HDEF(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i7-2640M CPU @ 2.80GHz, 2791.35 MHz, 06-2a-07
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 99MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.1.2, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM) i7-2640M CPU @ 2.80GHz, 2790.95 MHz, 06-2a-07
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 1, core 0, package 0
cpu2 at mainbus0: apid 2 (application processor)
cpu2: Intel(R) Core(TM) i7-2640M CPU @ 2.80GHz, 2790.96 MHz, 06-2a-07
cpu2: 

Re: Boot problem after power failure in OpenBSD 6.2 and later versions

[Sebastian Benoit]

augusta bonaventura(augusta...@gmail.com) on 2018.04.21 10:55:54 +0300:
> There is no problem when I reboot many times. Whenever I turn off power
> supply hardly, it comes with problem.
> it is not a solution for me to implement the solutions you specify. I
> installed/updated(boot-kernel) it several times after our correspondence
> with you.
> I have done the same process many times in 6.1, but I have not had a
> problem.
> I think, the tests i've made and the problems i've experienced originate
> from the 6.2 version of the change.

earlier you wrote:

> I am installing on the hardware mentioned below in OpenBSD 6.2 and 6.3
> versions. When the Login menu comes, I turn off power supply (only 1 time)
> for a power failure test. When the device reboots, it reboots itself when
> it comes to the "boot>" menu.

you say this is repeatable?

Does it also happen when you let the system sit at the login prompt for some
time, say 5 minutes, before pulling the plug?

When it happens, can you still boot with

   > boot /bsd.booted

or, if /bsd.booted does not exist, with

   > boot /obsd

at the bootloader prompt?

/Benno

 
> 2018-04-21 4:43 GMT+03:00 IL Ka :
> 
> > Reinstalling the operating system seems to solve the problem.
> >>
> > Almost never you need to reinstall OpenBSD.
> >
> > There are only 2 parts that could be broken in your case:
> > boot(8) and kernel itself (/bsd).
> > Both could be downloaded from CD or ftp.OpenBSD.org website
> >
> > That is why I told you to try to boot CD kernel using your boot(8) (and
> > vice versa)
> > to check which one is broken and then replace it.
> >
> > But you reinstalled OS, so we will not know it.
> >
> > But my main question is different: Why does this problem happen in the
> >> release 6.2 and later versions? The same process does not cause the problem
> >> in version 6.1.
> >>
> > I do not know..
> > Unexpected reboot is always some kind of lottery, that is why people use
> > backups and even store /etc/ in vcs
> > and OpenBSD has /altroot where it copies kernel and other files
> >
> > FFS does its best to save filesystem metadata (unless you enable async
> > mount option explicitly, which you did not do I am sure)
> > and fsck (fsck -f ?) almost always helps.
> >
> > It could be that it has nothing to do with OpenBSD version: just an
> > accident
> >
> >
> 

-- 

Re: Boot problem after power failure in OpenBSD 6.2 and later versions

[augusta bonaventura]

There is no problem when I reboot many times. Whenever I turn off power
supply hardly, it comes with problem.
it is not a solution for me to implement the solutions you specify. I
installed/updated(boot-kernel) it several times after our correspondence
with you.
I have done the same process many times in 6.1, but I have not had a
problem.
I think, the tests i've made and the problems i've experienced originate
from the 6.2 version of the change.

2018-04-21 4:43 GMT+03:00 IL Ka :

> Reinstalling the operating system seems to solve the problem.
>>
> Almost never you need to reinstall OpenBSD.
>
> There are only 2 parts that could be broken in your case:
> boot(8) and kernel itself (/bsd).
> Both could be downloaded from CD or ftp.OpenBSD.org website
>
> That is why I told you to try to boot CD kernel using your boot(8) (and
> vice versa)
> to check which one is broken and then replace it.
>
> But you reinstalled OS, so we will not know it.
>
> But my main question is different: Why does this problem happen in the
>> release 6.2 and later versions? The same process does not cause the problem
>> in version 6.1.
>>
> I do not know..
> Unexpected reboot is always some kind of lottery, that is why people use
> backups and even store /etc/ in vcs
> and OpenBSD has /altroot where it copies kernel and other files
>
> FFS does its best to save filesystem metadata (unless you enable async
> mount option explicitly, which you did not do I am sure)
> and fsck (fsck -f ?) almost always helps.
>
> It could be that it has nothing to do with OpenBSD version: just an
> accident
>
>

Re: Boot problem after power failure in OpenBSD 6.2 and later versions

[IL Ka]

>
> Reinstalling the operating system seems to solve the problem.
>
Almost never you need to reinstall OpenBSD.

There are only 2 parts that could be broken in your case:
boot(8) and kernel itself (/bsd).
Both could be downloaded from CD or ftp.OpenBSD.org website

That is why I told you to try to boot CD kernel using your boot(8) (and
vice versa)
to check which one is broken and then replace it.

But you reinstalled OS, so we will not know it.

But my main question is different: Why does this problem happen in the
> release 6.2 and later versions? The same process does not cause the problem
> in version 6.1.
>
I do not know..
Unexpected reboot is always some kind of lottery, that is why people use
backups and even store /etc/ in vcs
and OpenBSD has /altroot where it copies kernel and other files

FFS does its best to save filesystem metadata (unless you enable async
mount option explicitly, which you did not do I am sure)
and fsck (fsck -f ?) almost always helps.

It could be that it has nothing to do with OpenBSD version: just an accident

Re: Boot problem after power failure in OpenBSD 6.2 and later versions

[Solène Rapenne]

Le 2018-04-20 21:41, augusta bonaventura a écrit :

Hi,

I am installing on the hardware mentioned below in OpenBSD 6.2 and 6.3
versions. When the Login menu comes, I turn off power supply (only 1 
time)
for a power failure test. When the device reboots, it reboots itself 
when

it comes to the "boot>" menu.

However, even though I tried at least 10 times in 6.1 and earlier 
versions,

I did not encounter such a problem.

So, What is the difference between OpenBSD versions ? What might be the
cause of this situation? What kind of solution do you offer?

Thanks.

OpenBSD 6.1 dmesg output:



After the power failure, can you try to fsck and see what happens ?
You can use a CD or an usb install support for this.

Re: Boot problem after power failure in OpenBSD 6.2 and later versions

[augusta bonaventura]

Reinstalling the operating system seems to solve the problem.
But my main question is different: Why does this problem happen in the
release 6.2 and later versions? The same process does not cause the problem
in version 6.1.
Reinstalling the operating system every time can not be a solution, right?

2018-04-21 0:00 GMT+03:00 IL Ka :

> Please provide list of disks reported by boot(8) (i.e. hd0..)
>
> Try to boot CD kernel from your disk boot ]
> i.e: boot from harddrive, and in boot> prompt try
> something like "cd0:/6.3/bsd" (not sure about exact syntax, check man)
>
> If it does not work, then you need to reinstall your boot and kernel from
> /altroot or cd or openbsd website.
>  (and you will
> need to reinstall biosboot also (see installboot(8))
>
>
> On Fri, Apr 20, 2018 at 11:48 PM, augusta bonaventura <
> augusta...@gmail.com> wrote:
>
>> It is constantly restarting itself without of any message.
>> When I type in "boot -s", the device reboots itself again.
>> As you said, I booted from flash / cdrom and fsck all the partitions, but
>> that did not help either.
>> Also I checked /bsd exists on root
>> However, the system can not be booted.
>>
>> I dont know what is the weakness.
>> Thanks.
>>
>> 2018-04-20 23:34 GMT+03:00 IL Ka :
>>
>>> Does it reboot itself without of any message?
>>>
>>> Try to break in boot(8) menu (by clicking any key when boot prompt
>>> created)
>>> and boot kernel in single user mode (boot -s).
>>>
>>> If it does not help, boot from flash/cdrom (as you probably done
>>> accroding to dmesg) and fsck your harddrive/ssd partitions.
>>> Are they clean?
>>> Mount them, and check /bsd exists on root (.a)
>>>
>>>
>>> On Fri, Apr 20, 2018 at 11:23 PM, augusta bonaventura <
>>> augusta...@gmail.com> wrote:
>>>
 It means OpenBSD is constantly restarting itself.

 2018-04-20 23:01 GMT+03:00 IL Ka :

> > When the device reboots, it reboots itself when
> >  it comes to the "boot>" menu.
>
> What do you mean "reboots itself "?
>
> boot(8) reboots your machine instead of booting kernel with out of any
> output?
>
>

>>>
>>
>

Re: Boot problem after power failure in OpenBSD 6.2 and later versions

[IL Ka]

Please provide list of disks reported by boot(8) (i.e. hd0..)

Try to boot CD kernel from your disk boot ]
i.e: boot from harddrive, and in boot> prompt try
something like "cd0:/6.3/bsd" (not sure about exact syntax, check man)

If it does not work, then you need to reinstall your boot and kernel from
/altroot or cd or openbsd website.
 (and you will
need to reinstall biosboot also (see installboot(8))


On Fri, Apr 20, 2018 at 11:48 PM, augusta bonaventura 
wrote:

> It is constantly restarting itself without of any message.
> When I type in "boot -s", the device reboots itself again.
> As you said, I booted from flash / cdrom and fsck all the partitions, but
> that did not help either.
> Also I checked /bsd exists on root
> However, the system can not be booted.
>
> I dont know what is the weakness.
> Thanks.
>
> 2018-04-20 23:34 GMT+03:00 IL Ka :
>
>> Does it reboot itself without of any message?
>>
>> Try to break in boot(8) menu (by clicking any key when boot prompt
>> created)
>> and boot kernel in single user mode (boot -s).
>>
>> If it does not help, boot from flash/cdrom (as you probably done
>> accroding to dmesg) and fsck your harddrive/ssd partitions.
>> Are they clean?
>> Mount them, and check /bsd exists on root (.a)
>>
>>
>> On Fri, Apr 20, 2018 at 11:23 PM, augusta bonaventura <
>> augusta...@gmail.com> wrote:
>>
>>> It means OpenBSD is constantly restarting itself.
>>>
>>> 2018-04-20 23:01 GMT+03:00 IL Ka :
>>>
 > When the device reboots, it reboots itself when
 >  it comes to the "boot>" menu.

 What do you mean "reboots itself "?

 boot(8) reboots your machine instead of booting kernel with out of any
 output?


>>>
>>
>

Re: Boot problem after power failure in OpenBSD 6.2 and later versions

[augusta bonaventura]

It is constantly restarting itself without of any message.
When I type in "boot -s", the device reboots itself again.
As you said, I booted from flash / cdrom and fsck all the partitions, but
that did not help either.
Also I checked /bsd exists on root
However, the system can not be booted.

I dont know what is the weakness.
Thanks.

2018-04-20 23:34 GMT+03:00 IL Ka :

> Does it reboot itself without of any message?
>
> Try to break in boot(8) menu (by clicking any key when boot prompt created)
> and boot kernel in single user mode (boot -s).
>
> If it does not help, boot from flash/cdrom (as you probably done accroding
> to dmesg) and fsck your harddrive/ssd partitions.
> Are they clean?
> Mount them, and check /bsd exists on root (.a)
>
>
> On Fri, Apr 20, 2018 at 11:23 PM, augusta bonaventura <
> augusta...@gmail.com> wrote:
>
>> It means OpenBSD is constantly restarting itself.
>>
>> 2018-04-20 23:01 GMT+03:00 IL Ka :
>>
>>> > When the device reboots, it reboots itself when
>>> >  it comes to the "boot>" menu.
>>>
>>> What do you mean "reboots itself "?
>>>
>>> boot(8) reboots your machine instead of booting kernel with out of any
>>> output?
>>>
>>>
>>
>

Re: Boot problem after power failure in OpenBSD 6.2 and later versions

[IL Ka]

Does it reboot itself without of any message?

Try to break in boot(8) menu (by clicking any key when boot prompt created)
and boot kernel in single user mode (boot -s).

If it does not help, boot from flash/cdrom (as you probably done accroding
to dmesg) and fsck your harddrive/ssd partitions.
Are they clean?
Mount them, and check /bsd exists on root (.a)


On Fri, Apr 20, 2018 at 11:23 PM, augusta bonaventura 
wrote:

> It means OpenBSD is constantly restarting itself.
>
> 2018-04-20 23:01 GMT+03:00 IL Ka :
>
>> > When the device reboots, it reboots itself when
>> >  it comes to the "boot>" menu.
>>
>> What do you mean "reboots itself "?
>>
>> boot(8) reboots your machine instead of booting kernel with out of any
>> output?
>>
>>
>

Re: Boot problem after power failure in OpenBSD 6.2 and later versions

[augusta bonaventura]

It means OpenBSD is constantly restarting itself.

2018-04-20 23:01 GMT+03:00 IL Ka :

> > When the device reboots, it reboots itself when
> >  it comes to the "boot>" menu.
>
> What do you mean "reboots itself "?
>
> boot(8) reboots your machine instead of booting kernel with out of any
> output?
>
>

Re: Boot problem after power failure in OpenBSD 6.2 and later versions

[IL Ka]

 > When the device reboots, it reboots itself when
>  it comes to the "boot>" menu.

What do you mean "reboots itself "?

boot(8) reboots your machine instead of booting kernel with out of any
output?

Boot problem after power failure in OpenBSD 6.2 and later versions

[augusta bonaventura]

Hi,

I am installing on the hardware mentioned below in OpenBSD 6.2 and 6.3
versions. When the Login menu comes, I turn off power supply (only 1 time)
for a power failure test. When the device reboots, it reboots itself when
it comes to the "boot>" menu.

However, even though I tried at least 10 times in 6.1 and earlier versions,
I did not encounter such a problem.

So, What is the difference between OpenBSD versions ? What might be the
cause of this situation? What kind of solution do you offer?

Thanks.

OpenBSD 6.1 dmesg output:

# dmesg
OpenBSD 6.1 (GENERIC.MP) #20: Sat Apr  1 13:45:56 MDT 2017
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 17068920832 (16278MB)
avail mem = 16546938880 (15780MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x8d344000 (69 entries)
bios0: vendor American Megatrends Inc. version "5.12" date 12/19/2017
bios0: _ _
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC FPDT MCFG SSDT FIDT SSDT SSDT UEFI SSDT LPIT
WSMT SSDT SSDT DBGP DBG2 DMAR ASF!
acpi0: wakeup devices PEGP(S4) PEG0(S4) PEGP(S4) PEG1(S4) PEGP(S4) PEG2(S4)
PXSX(S4) RP09(S4) PXSX(S4) RP10(S4) PXSX(S4) RP11(S4) PXSX(S4) RP12(S4)
PXSX(S4) RP13(S4) [...]
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz, 3408.00 MHz
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: TSC frequency 340800 Hz
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 23MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz, 3408.00 MHz
cpu1:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 4 (application processor)
cpu2: Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz, 3408.00 MHz
cpu2:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 0, core 2, package 0
cpu3 at mainbus0: apid 6 (application processor)
cpu3: Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz, 3408.00 MHz
cpu3:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 0, core 3, package 0
cpu4 at mainbus0: apid 1 (application processor)
cpu4: Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz, 3408.00 MHz
cpu4:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT
cpu4: 256KB 64b/line 8-way L2 cache
cpu4: smt 1, core 0, package 0
cpu5 at mainbus0: apid 3 (application processor)
cpu5: Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz, 3408.00 MHz
cpu5:

Re: Boot problem OpenBSD 6.2 amd64 softraid keydisk

[Raimo Niskanen]

On Mon, Jan 22, 2018 at 11:16:29AM +0100, Stefan Sperling wrote:
> On Mon, Jan 22, 2018 at 10:08:30AM +0100, Raimo Niskanen wrote:
> > Hello misc@!
> > 
> > I just wanted to share a problem and a solution that I encountered.  Just
> > posting to maybe help someone else in the future, and perhaps a developer
> > feels that improving a particular error message could be important enough.
> > 
> > My goal was to create an installation with a fully encrypted hard drive
> > using a keydisk, and at first reboot into the installed system I got this:
> > 
> > Booting from hard disk...
> > Using drive 0, partition 3.
> > Loading..
> > probing: pc0 com0 com1 mem[638K 3582M 496M a20=on]
> > disk: hd0+ hd1+ hd2 sr0*
> > >> OpenBSD/amd64 BOOT 3.33
> > unknown KDF type 2
> > open(sr0a:/etc/boot.conf): Operation not permitted
> > boot>
> > 
> > The error message "unknown KDF type 2" is the one that maybe could
> > be improved...
> 
> This error message has already been improved in -current by sunil@ in r1.3 of
> http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/lib/libsa/softraid.c
> The message now says ""keydisk not found".

Excellent!

-- 

/ Raimo Niskanen, Erlang/OTP, Ericsson AB

Re: Boot problem OpenBSD 6.2 amd64 softraid keydisk

[Stefan Sperling]

On Mon, Jan 22, 2018 at 10:08:30AM +0100, Raimo Niskanen wrote:
> Hello misc@!
> 
> I just wanted to share a problem and a solution that I encountered.  Just
> posting to maybe help someone else in the future, and perhaps a developer
> feels that improving a particular error message could be important enough.
> 
> My goal was to create an installation with a fully encrypted hard drive
> using a keydisk, and at first reboot into the installed system I got this:
> 
> Booting from hard disk...
> Using drive 0, partition 3.
> Loading..
> probing: pc0 com0 com1 mem[638K 3582M 496M a20=on]
> disk: hd0+ hd1+ hd2 sr0*
> >> OpenBSD/amd64 BOOT 3.33
> unknown KDF type 2
> open(sr0a:/etc/boot.conf): Operation not permitted
> boot>
> 
> The error message "unknown KDF type 2" is the one that maybe could
> be improved...

This error message has already been improved in -current by sunil@ in r1.3 of
http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/lib/libsa/softraid.c
The message now says ""keydisk not found".

Boot problem OpenBSD 6.2 amd64 softraid keydisk

[Raimo Niskanen]

Hello misc@!

I just wanted to share a problem and a solution that I encountered.  Just
posting to maybe help someone else in the future, and perhaps a developer
feels that improving a particular error message could be important enough.

My goal was to create an installation with a fully encrypted hard drive
using a keydisk, and at first reboot into the installed system I got this:

Booting from hard disk...
Using drive 0, partition 3.
Loading..
probing: pc0 com0 com1 mem[638K 3582M 496M a20=on]
disk: hd0+ hd1+ hd2 sr0*
>> OpenBSD/amd64 BOOT 3.33
unknown KDF type 2
open(sr0a:/etc/boot.conf): Operation not permitted
boot>

The error message "unknown KDF type 2" is the one that maybe could
be improved...

The mistake was that I used an USB keydisk size 16 GB and kept an 8 GB
MSDOS section at the start of the disk, then the OpenBSD section
with an 'a' 8 GB 4.2BSD partition and a 'd' 1 2048 sectors RAID partition
for the keydisk.  You see where this is heading...

The keydisk partition was simply out of reach for the boot(8, amd64)
program.  The boot command "machine diskinfo" gave a hint since the disk
geometry there had fewer cylinders than what fdisk(8) had said, i.e it said
(if I recall correctly) C,H,S=1024,255,65, i.e the infamous 8.4 GB limit,
while in fdisk the disk appeared to have about 1900 cylinders.

So I moved the OpenBSD section to the start of the disk, the keydisk
partition to the start of the OpenBSD section, and the MSDOS section
at the end of the disk, and the installation booted.

Best regards
-- 

/ Raimo Niskanen, Erlang/OTP, Ericsson AB

boot problem - freeze after wskbd console keyboard

[Alex Greif]

I have the following problem with a current snapshot, but also with an older 
5.9 snaphot, so it might be more a hardware issue.

Installation from the install61.iso works fine

The problem is that while booting (in normal and also in single user mode) the 
boot process halts at the line
   wskbd0 at pckbd0: consolekeyboard

I tried the following changes which all did not help:
   - disabling acpi (in boot -c)
   - install on SATA HDD or M.2 SSD (samsung 960 pro)
   - install with GPT or with MBR
   - use PS2 keyboard or USB keyboard
   - BIOS changes like disable hyper threading, disable all USBs, etc

The PC configuration is as follows:
   - Mainboard Asus z270k
   - CPU i7 7700k
   - 32 GB RAM
   - M.2 Samsung pro 500gb

thanks for any help.

Alex.

Re: Boot problem custom Kernel 5.7

[Oliver]

On Sat, 11 Jul 2015, Joel Rees wrote:

 2015/07/10 22:12 Oliver open...@0f.de:
 
  Hello,
 
  On Tue, 09 Jun 2015, Theo de Raadt wrote:
  entry point at 0x1000160 [7205c766, 3404, 24448b12, 1080a304]
  == At this point the system reboots. No further messages.

 Your kernel is probably too large.  A limitation in the bootblocks.
Do you mean the kernel with the ramdisk or without? What would be the
best way to workaround this limit? Decrease ramdisk size?
Remove driver/options from the kernel?
  
   Those are your changes, outside the OpenBSD tree.  You are on your own.
  I just want to say that this problem is fixed in OpenBSD 5.8-beta. The
  problem is not the bootloader. Can someone point me to the right
 direction to
  backport the changes to 5.7?
 
  Thanks,
 
  Oliver
 
 Is it fixed, or is it just randomly working?
It now works all the time. So something was fixed in current. With 5.7 it
never worked. Even with a very small ramdisk. I always run into the boot loop.

Re: Boot problem custom Kernel 5.7

[Joel Rees]

2015/07/10 22:12 Oliver open...@0f.de:

 Hello,

 On Tue, 09 Jun 2015, Theo de Raadt wrote:
 entry point at 0x1000160 [7205c766, 3404, 24448b12, 1080a304]
 == At this point the system reboots. No further messages.
   
Your kernel is probably too large.  A limitation in the bootblocks.
   Do you mean the kernel with the ramdisk or without? What would be the
   best way to workaround this limit? Decrease ramdisk size?
   Remove driver/options from the kernel?
 
  Those are your changes, outside the OpenBSD tree.  You are on your own.
 I just want to say that this problem is fixed in OpenBSD 5.8-beta. The
 problem is not the bootloader. Can someone point me to the right
direction to
 backport the changes to 5.7?

 Thanks,

 Oliver

Is it fixed, or is it just randomly working?

Re: Boot problem custom Kernel 5.7

[Oliver]

Hello,

On Tue, 09 Jun 2015, Theo de Raadt wrote:
entry point at 0x1000160 [7205c766, 3404, 24448b12, 1080a304]
== At this point the system reboots. No further messages. 
   
   Your kernel is probably too large.  A limitation in the bootblocks.
  Do you mean the kernel with the ramdisk or without? What would be the
  best way to workaround this limit? Decrease ramdisk size?
  Remove driver/options from the kernel?
 
 Those are your changes, outside the OpenBSD tree.  You are on your own.
I just want to say that this problem is fixed in OpenBSD 5.8-beta. The
problem is not the bootloader. Can someone point me to the right direction to
backport the changes to 5.7?

Thanks,

Oliver

more on 5.7 boot problem with xhci

[pstern]

hello:

A little more detail on the problem with freezing in 5.7 stable install

With verbose reporting turned on during the booting process, I see the 
following:


probing for pchb*
pchb returned 0
probing for geodesc*
geodesc probe returned 0
probing for pcib
pcib probe returned 0
probing for hme*
hme probe returned 0
probing for pcic*
pcic probe returned 0
xhci probe won
xhci0 at pci0 dev 20 function 0 Intel 8 Series xHCI rev 0x04: msi
probing for usb*
usb probe returned 1
usb probe won
usb0 at xhci0: USB revision 3.0
probing for uhub*
uhub probe returned 10
uhub probe won
uhub0 at usb0 Intel xHCI root hub rev 3.00/1.00 addr 1

At that point the system hangs.

A usb mouse and keyboard were plugged into the usb 2.0 ports on the 
computer. Same report if they are plugged into the usb 3.0 ports.


If I configure the kernel to disable xhci during boot, it boots normally 
and successfully using ehci. Hope this is useful.


peter

Boot problem custom Kernel 5.7

[Oliver]

Hello,

for around 10 years I build a custom cd bootable version of OpenBSD.
The project was started with OpenBSD 3.4 and is updated with each
OpenBSD release. 

Basically I take the GERNERIC kernel configuration and change
config  bsd swap generic
to
config  bsd root on rd0a

And I also add:
option  RAMDISK_HOOKS
option  MINIROOTSIZE=4480
pseudo-device   rd  1

The rest are changes to the ramdisk configuration. I added mount_mfs
to the ramdisk and some scripts to boot from cd.

Starting with OpenBSD 5.7 I cannot build a bootable kernel and
I don't know why. The kernel build itself shows no errors, but
when I boot from CD I get:

Booting from DVD/CD...
CD-ROM: E0
Loading /CDBOOT
probing: pc0 com0 mem[639K 698; a20=on]
disk: hd0+ cd0
 OpenBSD/amd64 CDBOOT 3.23
boot
cannot open cd0a:/etc/random.seed: No such file or directory
booting cd0a:/bsd.gz: 5798084+2048752+2532360+0+589824=0xa782d8
entry point at 0x1000160 [7205c766, 3404, 24448b12, 1080a304]
== At this point the system reboots. No further messages. 

Booting with -c results also in a reboot.

Then I took the RAMDISK_CD configuration and added option MFS.
This time the kernel boots with the customised ramdisk, but
the RAMDISK_CD lacks some features like the pf firewall. Adding
more features to the RAMDISK_CD configuration I cannot compile
the kernel anymore.

So the question is what can I do to find out the cause of the problem
or maybe someone has already a clue what the problem is.

Thanks,

Oliver

Re: Boot problem custom Kernel 5.7

[Theo de Raadt]

 entry point at 0x1000160 [7205c766, 3404, 24448b12, 1080a304]
 == At this point the system reboots. No further messages. 

Your kernel is probably too large.  A limitation in the bootblocks.

Re: Boot problem custom Kernel 5.7

[Theo de Raadt]

   entry point at 0x1000160 [7205c766, 3404, 24448b12, 1080a304]
   == At this point the system reboots. No further messages. 
  
  Your kernel is probably too large.  A limitation in the bootblocks.
 Do you mean the kernel with the ramdisk or without? What would be the
 best way to workaround this limit? Decrease ramdisk size?
 Remove driver/options from the kernel?

Those are your changes, outside the OpenBSD tree.  You are on your own.

Re: Boot problem custom Kernel 5.7

[Josh Grosse]

On 2015-06-09 13:34, Oliver wrote:

On Tue, 09 Jun 2015, Theo de Raadt wrote:


 entry point at 0x1000160 [7205c766, 3404, 24448b12, 1080a304]
 == At this point the system reboots. No further messages.

Your kernel is probably too large.  A limitation in the bootblocks.

Do you mean the kernel with the ramdisk or without? What would be the
best way to workaround this limit? Decrease ramdisk size?
Remove driver/options from the kernel?


Back when I was building live CDs/DVDs, I used GENERIC or GENERIC.MP
kernels with cd0a as the root filesystem, and MFS mounted /etc, /var,
/root, /tmp, /home, and /dev.  Read-only filesystems on media were all
CD9660.

I ran into cdboot(8) issues with very large /usr/local filesystems
(e.g. KDE and Gnome).  My simple circumvention was to vnconfig(8)
/usr/local from an .iso image file after boot completed.

Re: Boot problem custom Kernel 5.7

[Oliver]

On Tue, 09 Jun 2015, Theo de Raadt wrote:

  entry point at 0x1000160 [7205c766, 3404, 24448b12, 1080a304]
  == At this point the system reboots. No further messages. 
 
 Your kernel is probably too large.  A limitation in the bootblocks.
Do you mean the kernel with the ramdisk or without? What would be the
best way to workaround this limit? Decrease ramdisk size?
Remove driver/options from the kernel?

boot problem. in short

[Andrej Elizarov]

Hi all.

I have some situation, my machine will not boot after installing
amd64_obsd4.5_stable.
amd64, 250G harddrive (first physical).

0. 1 Primary 100G NTFS (WindowsXP), 1 Secondary 100G NTFS (just data)
1. have free 36G at the end of drive.
2. in windows make blank primary partition (with powerquest Partition
Manager) at all 36G
3. install obsd in this partition
4. reboot

Then BIOS, POST,.. and black screen with blinking cursor.


(By the way, there was similiar behavior, when i mount ntfs partition in
obsd, and forget umount it. After rebooting got black screen.
After mount/umount once again all was correct.)

Any ideas how to fix?

Re: boot problem. in short

[Neal Hogan]

On Fri, Jun 5, 2009 at 6:36 AM, Andrej Elizarov vigilan...@gmail.comwrote:

 Hi all.

 I have some situation, my machine will not boot after installing
 amd64_obsd4.5_stable.
 amd64, 250G harddrive (first physical).

 0. 1 Primary 100G NTFS (WindowsXP), 1 Secondary 100G NTFS (just data)
 1. have free 36G at the end of drive.
 2. in windows make blank primary partition (with powerquest Partition
 Manager) at all 36G
 3. install obsd in this partition
 4. reboot

 Then BIOS, POST,.. and black screen with blinking cursor.


spitball
bootloader?
e.g., http://www.gnu.org/software/grub/
/spitball




 (By the way, there was similiar behavior, when i mount ntfs partition in
 obsd, and forget umount it. After rebooting got black screen.
 After mount/umount once again all was correct.)

 Any ideas how to fix?

Re: boot problem. in short

[Andrej Elizarov]

I try some bootloaders to boot this partition, like MagickBoot and some
others (from Hiren's BootCD). Nope.
I try reinstall windows - it only copy files to hd, then reboot to continue
installation from hd - and again black screen.



2009/6/5 Neal Hogan nealho...@gmail.com



 On Fri, Jun 5, 2009 at 6:36 AM, Andrej Elizarov vigilan...@gmail.comwrote:

 Hi all.

 I have some situation, my machine will not boot after installing
 amd64_obsd4.5_stable.
 amd64, 250G harddrive (first physical).

 0. 1 Primary 100G NTFS (WindowsXP), 1 Secondary 100G NTFS (just data)
 1. have free 36G at the end of drive.
 2. in windows make blank primary partition (with powerquest Partition
 Manager) at all 36G
 3. install obsd in this partition
 4. reboot

 Then BIOS, POST,.. and black screen with blinking cursor.


 spitball
 bootloader?
 e.g., http://www.gnu.org/software/grub/
 /spitball




 (By the way, there was similiar behavior, when i mount ntfs partition in
 obsd, and forget umount it. After rebooting got black screen.
 After mount/umount once again all was correct.)

 Any ideas how to fix?

Re: boot problem. in short

[Josh Grosse]

On Fri, 5 Jun 2009 16:33:17 +0400, Andrej Elizarov wrote
 I try some bootloaders to boot this partition, like MagickBoot and some
 others (from Hiren's BootCD). Nope.
 I try reinstall windows - it only copy files to hd, then reboot to continue
 installation from hd - and again black screen.

[SNIP]

  Any ideas how to fix?

1. Boot OpenBSD installation media
2. At Install/Update/Shell prompt, select shell.
3. Examine MBR of boot drive:

# fdisk boot drive (e.g.: sd0, wd0)

Is there an MBR partition table?  Is a partition flagged as boot?
Repair as necessary, per fdisk(8) man page

4.  Install MBR program onto boot drive, preserving repaired MBR table

# fdisk -u your boot drive  

Re: boot problem. in short

[Josh Grosse]

I'd written:

 4.  Install MBR program onto boot drive, preserving repaired MBR table

 # fdisk -u your boot drive

You probably do not want to use OpenBSD's fdisk to rewrite the MBR program, it
will clear the NT disk signature.

Re: boot problem. in short

[Andrej Elizarov]

Thanks, i'll try.
Just an idea. Signature is already cleared. How can i test it?

2009/6/5 Josh Grosse j...@jggimi.homeip.net

 I'd written:

  4.  Install MBR program onto boot drive, preserving repaired MBR table
 
  # fdisk -u your boot drive

 You probably do not want to use OpenBSD's fdisk to rewrite the MBR program,
 it
 will clear the NT disk signature.

Re: boot problem. in short

[Josh Grosse]

On Fri, Jun 05, 2009 at 10:53:53PM +0400, Andrej Elizarov wrote:
 Thanks, i'll try.
 Just an idea. Signature is already cleared. How can i test it?

Step 1.  Google for nt disk signature.
Step 2.  Open the top search result, Windows NT: Disk Management Basics, 
 a link at microsoft.com.
Step 3.  Search forward for disk signature.
Step 4.  Read this paragraph.
Step 5.  Think.
Step 6.  Search forward for disk signature again.  Look at the comments about
 the disk signature under the section labelled Master Boot Record,
 that shows a hexdump output of the first sector of a drive.
Step 7.  Think again.

The contents of this first sector can be edited.  The dd(1) program included 
with the ramdisk kernel will allow you copy the sector to a file on 
removeable media such as diskette or USB stick.  A hex editor would be
required on another platform could be used, then dd once again could be
deployed to write the modified sector back to hard drive.

Re: Dual boot problem

[Andrei]

Josh Grosse wrote:
 
 On Mon, 7 Apr 2008 11:04:41 -0700 (PDT), Andrei wrote
 
 I have PC with two OpenBSD 4.2 - bootable harddisks. Clearly I can
 boot from either of them by setting a boot sequence in BIOS or by
 typing boot hdXa:/bsd in the boot prompt (X = 0 or 1).
 
 What I want is to specify a boot hdd without boot-time user
 intervention. Thus, imagine I run OpenBSD on hd0, I want to specify
 what hd1 shell be used as bootable on the next reboot.
 
 See boot.conf(5), set image may be what you are looking for.
 

Thanks Josh, this works fine. The reason I did not consider boot.conf at the
beginning is that it concerns second-stage bootstrap, while I was trying to
find a solution first-stage bootstrap. 

 Andrei

-- 
View this message in context: 
http://www.nabble.com/Dual-boot-problem-tp16538144p16548546.html
Sent from the openbsd user - misc mailing list archive at Nabble.com.

Re: Dual boot problem

[Girish Venkatachalam]

On 01:00:04 Apr 08, Andrei wrote:
 
 Thanks Josh, this works fine. The reason I did not consider boot.conf at the
 beginning is that it concerns second-stage bootstrap, while I was trying to
 find a solution first-stage bootstrap. 
 
Then you have to do it manually.

OpenBSD is not very convenient for multiboot or for having more than one
OpenBSD on the same disk.

-Girish

Re: : Dual boot problem

[Raimo Niskanen]

On Tue, Apr 08, 2008 at 01:00:04AM -0700, Andrei wrote:
 Josh Grosse wrote:
  
  On Mon, 7 Apr 2008 11:04:41 -0700 (PDT), Andrei wrote
  
  I have PC with two OpenBSD 4.2 - bootable harddisks. Clearly I can
  boot from either of them by setting a boot sequence in BIOS or by
  typing boot hdXa:/bsd in the boot prompt (X = 0 or 1).
  
  What I want is to specify a boot hdd without boot-time user
  intervention. Thus, imagine I run OpenBSD on hd0, I want to specify
  what hd1 shell be used as bootable on the next reboot.
  
  See boot.conf(5), set image may be what you are looking for.

I'd say set device ... is what you are looking for.
I have a bootable USB pen drive that only contains
/boot
/etc/boot.conf
that boots OpenBSD from the hard drive when I have not
wanted to touch the MBR code. It contains:
set device hd1a
set howto -c
the last line to push the boot into UKC since I need
to disable acpi. And it is hd1a since boot(8) see
the USB pen drive as first hard disk.

  
 
 Thanks Josh, this works fine. The reason I did not consider boot.conf at the
 beginning is that it concerns second-stage bootstrap, while I was trying to
 find a solution first-stage bootstrap. 

OpenBSD's MBR does no fancy tricks. It only boots the first
partition on the hard drive marked as bootable.

You may be able to get the BIOS to boot the second hard drive,
but not from a running OS for the next boot.

GRUB installed to MBR can do it, but needs a partition
to exist in. So then it will be its second stage bootloader
that does the selection. And you will have to modify
menu.lst in the GRUB installation, so the GRUB installation
will have to be writable from OpenBSD.

As you found out OpenBSD's boot(8) can do it.
You will have to modify /etc/boot.conf on the 
hard drive the BIOS boots.

And there are of course other bootloaders out there...



 
  Andrei
 
 -- 
 View this message in context: 
 http://www.nabble.com/Dual-boot-problem-tp16538144p16548546.html
 Sent from the openbsd user - misc mailing list archive at Nabble.com.

-- 

/ Raimo Niskanen, Erlang/OTP, Ericsson AB

Re: : Dual boot problem

[Louis V. Lambrecht]

Not quite, you don't need a specific partition for grub.Grub only needs 
to be installed

on the BIOS first boot device.
Which can be a hard drive, a floppy, a cdrom, an usb key...

On a hard drive with only OpenBSD slices, grub will usually be installed 
on the

first slice, the one with the largest volume label. The BIOS boot one.

At boot, the mbr jumps to the /grub directory, loads some stages and 
reads the

menu.lst.
Grub has the ability to mark partition types (keyword parttype) and
mark a partition active (define root(x,y) and keyword makeactive)
just as any fdisk would do (you eventually can partition a disk from 
within grub).


There is some info, even without the need to install it first:
/usr/ports/sysutils/grub/files/README.OpenBSD and a menu example
/usr/ports/sysutils/grub/files/menu.lst

As you will see, the trick is to mark unused OpenBSD slices with another
identifier.

Would you want to by-pass the grub's choices menu, (no intervention)
you only would have to write different menu.lst.xxx files and mv the one
you need at next reboot.

Fwiw, my default menu is on the hard drive, simple entry.
When messing around I boot from an usb key.

Raimo Niskanen wrote:

On Tue, Apr 08, 2008 at 01:00:04AM -0700, Andrei wrote:
  

Josh Grosse wrote:


On Mon, 7 Apr 2008 11:04:41 -0700 (PDT), Andrei wrote

  

I have PC with two OpenBSD 4.2 - bootable harddisks. Clearly I can
boot from either of them by setting a boot sequence in BIOS or by
typing boot hdXa:/bsd in the boot prompt (X = 0 or 1).

What I want is to specify a boot hdd without boot-time user
intervention. Thus, imagine I run OpenBSD on hd0, I want to specify
what hd1 shell be used as bootable on the next reboot.


See boot.conf(5), set image may be what you are looking for.
  


I'd say set device ... is what you are looking for.
I have a bootable USB pen drive that only contains
/boot
/etc/boot.conf
that boots OpenBSD from the hard drive when I have not
wanted to touch the MBR code. It contains:
set device hd1a
set howto -c
the last line to push the boot into UKC since I need
to disable acpi. And it is hd1a since boot(8) see
the USB pen drive as first hard disk.

  

Thanks Josh, this works fine. The reason I did not consider boot.conf at the
beginning is that it concerns second-stage bootstrap, while I was trying to
find a solution first-stage bootstrap. 



OpenBSD's MBR does no fancy tricks. It only boots the first
partition on the hard drive marked as bootable.

You may be able to get the BIOS to boot the second hard drive,
but not from a running OS for the next boot.

GRUB installed to MBR can do it, but needs a partition
to exist in. So then it will be its second stage bootloader
that does the selection. And you will have to modify
menu.lst in the GRUB installation, so the GRUB installation
will have to be writable from OpenBSD.

As you found out OpenBSD's boot(8) can do it.
You will have to modify /etc/boot.conf on the 
hard drive the BIOS boots.


And there are of course other bootloaders out there...



  

 Andrei

--
View this message in context: 
http://www.nabble.com/Dual-boot-problem-tp16538144p16548546.html
Sent from the openbsd user - misc mailing list archive at Nabble.com.

Re: : : Dual boot problem

[Raimo Niskanen]

On Tue, Apr 08, 2008 at 02:54:48PM +0200, Louis V. Lambrecht wrote:
 Not quite, you don't need a specific partition for grub.Grub only needs 
 to be installed
 on the BIOS first boot device.
 Which can be a hard drive, a floppy, a cdrom, an usb key...
 

Thank you for your correction.

I looked at an OpenBSD 4.1 machine and did
not find grub in neither the packages nor
the ports tree. So I erroneously assumed
a non-OpenBSD aware grub was needed.

 On a hard drive with only OpenBSD slices, grub will usually be installed 
 on the
 first slice, the one with the largest volume label. The BIOS boot one.
 
 At boot, the mbr jumps to the /grub directory, loads some stages and 
 reads the
 menu.lst.
 Grub has the ability to mark partition types (keyword parttype) and
 mark a partition active (define root(x,y) and keyword makeactive)
 just as any fdisk would do (you eventually can partition a disk from 
 within grub).
 
 There is some info, even without the need to install it first:
 /usr/ports/sysutils/grub/files/README.OpenBSD and a menu example
 /usr/ports/sysutils/grub/files/menu.lst
 
;
:
 Raimo Niskanen wrote:
:
:
 GRUB installed to MBR can do it, but needs a partition
 to exist in. So then it will be its second stage bootloader
 that does the selection. And you will have to modify
 menu.lst in the GRUB installation, so the GRUB installation
 will have to be writable from OpenBSD.
 
:
:

-- 

/ Raimo Niskanen, Erlang/OTP, Ericsson AB

Re: Dual boot problem

[Andrei]

Girish Venkatachalam-2 wrote:
 
 On 01:00:04 Apr 08, Andrei wrote:
  
 Thanks Josh, this works fine. The reason I did not consider boot.conf at
 the
 beginning is that it concerns second-stage bootstrap, while I was trying
 to
 find a solution first-stage bootstrap. 
  
 Then you have to do it manually.
 
 OpenBSD is not very convenient for multiboot or for having more than one
 OpenBSD on the same disk.
 
 -Girish
 

Yes, I noticed it. BTW, I managed to use more than one OpenBSD on different
partitions of the same disk.
The trick was to use 'A6' partition ID only for the active OpenBSD
partition, and use another ID for all the rest ones. At least this worked
for OpenBSD 4.2, I am not sure if this issue is planned to be fixed in
future releases.

-- 
View this message in context: 
http://www.nabble.com/Dual-boot-problem-tp16538144p16561041.html
Sent from the openbsd user - misc mailing list archive at Nabble.com.

Re: : : Dual boot problem

[Louis V. Lambrecht]

Cm'on Raimo. Tssk! Tssk!
http://www.openbsd.org/cgi-bin/cvsweb/ports/sysutils/grub/files/

I mostly use openports.se, rather than searching my own filesystem
which is not quite conforming to the standard file hierarchy. :-)

Raimo Niskanen wrote:

On Tue, Apr 08, 2008 at 02:54:48PM +0200, Louis V. Lambrecht wrote:
  
Not quite, you don't need a specific partition for grub.Grub only needs 
to be installed

on the BIOS first boot device.
Which can be a hard drive, a floppy, a cdrom, an usb key...




Thank you for your correction.

I looked at an OpenBSD 4.1 machine and did
not find grub in neither the packages nor
the ports tree. So I erroneously assumed
a non-OpenBSD aware grub was needed.

  
On a hard drive with only OpenBSD slices, grub will usually be installed 
on the

first slice, the one with the largest volume label. The BIOS boot one.

At boot, the mbr jumps to the /grub directory, loads some stages and 
reads the

menu.lst.
Grub has the ability to mark partition types (keyword parttype) and
mark a partition active (define root(x,y) and keyword makeactive)
just as any fdisk would do (you eventually can partition a disk from 
within grub).


There is some info, even without the need to install it first:
/usr/ports/sysutils/grub/files/README.OpenBSD and a menu example
/usr/ports/sysutils/grub/files/menu.lst



;
:
  

Raimo Niskanen wrote:


:
:
  

GRUB installed to MBR can do it, but needs a partition
to exist in. So then it will be its second stage bootloader
that does the selection. And you will have to modify
menu.lst in the GRUB installation, so the GRUB installation
will have to be writable from OpenBSD.

  

:
:

Dual boot problem

[Andrei]

Hi all,

I have PC with two OpenBSD 4.2 - bootable harddisks. Clearly I can
boot from either of them by setting a boot sequence in BIOS or by
typing boot hdXa:/bsd in the boot prompt (X = 0 or 1).

What I want is to specify a boot hdd without boot-time user
intervention. Thus, imagine I run OpenBSD on hd0, I want to specify
what hd1 shell be used as bootable on the next reboot.

installboot(8) offers what I need, but it can't be used for cross-
device installboots.

If possible, I'd like to solve this without any dedicated bootloaders
like grub. If you convince me that using bootloader is better
alternative, I would not mind much.

Note that run everything in VMware, so I am not afraid to screw-up
things.

All suggestions are welcome.

Andrei

-- 
View this message in context: 
http://www.nabble.com/Dual-boot-problem-tp16538144p16538144.html
Sent from the openbsd user - misc mailing list archive at Nabble.com.

Re: Dual boot problem

[Josh Grosse]

On Mon, 7 Apr 2008 11:04:41 -0700 (PDT), Andrei wrote

 I have PC with two OpenBSD 4.2 - bootable harddisks. Clearly I can
 boot from either of them by setting a boot sequence in BIOS or by
 typing boot hdXa:/bsd in the boot prompt (X = 0 or 1).
 
 What I want is to specify a boot hdd without boot-time user
 intervention. Thus, imagine I run OpenBSD on hd0, I want to specify
 what hd1 shell be used as bootable on the next reboot.

See boot.conf(5), set image may be what you are looking for.

dual boot problem

[akonsu]

hello,

i have openbsd on the first partition on my hard drive, and windows xp on
the second partition.
i made the windows partition active.

this is the command that i used to get the openbsd's mbr:

dd if=/dev/rwd0c of=mbr count=1

i copied the file mbr to my windows partition and added the following line
in to c:\boot.ini

c:\mbr=openbsd

when i select this line from the ntldr menu, nothing happens, it just shows
the menu again.

apparently my mbr file is wrong because when i created one using Gilles
Vollant's bootpart (http://www.winimage.com) and used it, it loaded openbsd
successfully.

i can use the mbr file created by bootpart but i would like to understand
what i was doing wrong...

please help.

thanks
konstantin

Re: dual boot problem

[Przemyslaw Nowaczyk]

On Wed, May 24, 2006 at 11:56:20PM -0700, akonsu wrote:
 this is the command that i used to get the openbsd's mbr:
 
 dd if=/dev/rwd0c of=mbr count=1

 
actually you need the pbr (partition boot record) not the mbr, look at FAQ 4.8,
your command should look like:
dd if=/dev/rwd0a of=name bs=512 count=1

-- 
Przemyslaw Nowaczyk [EMAIL PROTECTED]
CS student @ Poznan University of Technology

Re: dual boot problem

[Paul de Weerd]

On Wed, May 24, 2006 at 11:56:20PM -0700, akonsu wrote:
| hello,
|
| i have openbsd on the first partition on my hard drive, and windows xp on
| the second partition.
| i made the windows partition active.
|
| this is the command that i used to get the openbsd's mbr:
|
| dd if=/dev/rwd0c of=mbr count=1

Try /dev/rwd0a, see FAQ4.8.

Cheers,

Paul 'WEiRD' de Weerd

--
[++-]+++.+++[---].+++[+
+++-].++[-]+.--.[-]
 http://www.weirdnet.nl/

[demime 1.01d removed an attachment of type application/pgp-signature]

Re: dual boot problem

[Jan Johansson]

akonsu [EMAIL PROTECTED] wrote:
 dd if=/dev/rwd0c of=mbr count=1

Here is your error

dd if=/dev/rwd0a of=pbr count=1

For the NTLDR you want the PBR (Partition Boot Record) not the
MBR (Master Boot Record). I changed the of= for correct the
terminology the important part is the if= device. I usually use

dd if=/dev/rwd0a of=/mnt/OpenBSD.pbr bs=512 count=1

where /mnt is the mountpoint of a small FAT partiton that is
active.

Re: dual boot problem

[viq]

On Thursday 25 May 2006 09:22, Jan Johansson wrote:
 akonsu [EMAIL PROTECTED] wrote:
  dd if=/dev/rwd0c of=mbr count=1

 Here is your error

 dd if=/dev/rwd0a of=pbr count=1

 For the NTLDR you want the PBR (Partition Boot Record) not the
 MBR (Master Boot Record). I changed the of= for correct the
 terminology the important part is the if= device. I usually use

 dd if=/dev/rwd0a of=/mnt/OpenBSD.pbr bs=512 count=1

 where /mnt is the mountpoint of a small FAT partiton that is
 active.

While at the subject, you need to run this every time you upgrade bootblocks. 
What would be the result of not updating bootblocks when upgrading from 
snapshot? Or not rerunning that command when updating them?
-- 
viq

Re: dual boot problem

[Jan Johansson]

viq [EMAIL PROTECTED] wrote:
 While at the subject, you need to run this every time you
 upgrade bootblocks.  What would be the result of not updating
 bootblocks when upgrading from snapshot?

Sounds dangerous to me. Will old bootblocks be able to boot the
kernel?

 Or not rerunning that command when updating them?

It will say Err M after you choose OpenBSD from NTLDR.

Use the bootblock from the CD but load the kernel from hd0 by
typing boot hd0a:/bsd at the boot prompt. Then rerun the
command to update your your PBR-file.

Re: dual boot problem

[Nick Holland]

viq wrote:

On Thursday 25 May 2006 09:22, Jan Johansson wrote:

akonsu [EMAIL PROTECTED] wrote:

dd if=/dev/rwd0c of=mbr count=1

Here is your error

dd if=/dev/rwd0a of=pbr count=1

For the NTLDR you want the PBR (Partition Boot Record) not the
MBR (Master Boot Record). I changed the of= for correct the
terminology the important part is the if= device. I usually use

dd if=/dev/rwd0a of=/mnt/OpenBSD.pbr bs=512 count=1

where /mnt is the mountpoint of a small FAT partiton that is
active.


While at the subject, you need to run this every time you upgrade bootblocks. 
What would be the result of not updating bootblocks when upgrading from 
snapshot? 


depends.

The boot code doesn't change dramatically often.  Last time it happened, 
it was the changes that permitted OpenBSD to boot beyond the 8G point on 
BIOSs which permitted it.  I personally tested around 50 different 
machines to make sure it worked, and several hundred other reports were 
provided by other users and developers.  And when a last minute 
improvement was discovered, I had to re-run those tests. :)


So...avoiding updating the boot blocks is usually harmless...you would 
be replacing code with the exact same code.  Now that I've said that, it 
will probably change, and in an important way.


 Or not rerunning that command when updating them?

As indicated by others, the system won't boot.

The inode for the second-stage boot loader (/boot) is hard-coded in the 
PBR.  Change that inode, you have a problem, because what the NTLDR does 
is invoke the PBR that was saved...IN THE PAST.  So, that PBR will end 
up trying to pull in and run who-knows-what...and will likely fail.


Ugly?  Well, before that bootloader change, the actual physical blocks 
were coded in the PBR, which meant recopying the file /boot would break 
the boot process.  The current process is actually very robust, 
recopying the /boot file doesn't change the inode number normally.  The 
normal upgrade processes are done in such a way that the inode isn't 
changed, so this will rarely be a problem.


The good news, almost by definition, a multi-booting machine isn't at 
some remote location...it's in front of you, thus easy to repair. 
(yeah, I am sure someone has a weird setup.  whatever).



Nick.

Re: dual boot problem

[Nick Guenther]

On 5/25/06, Nick Holland [EMAIL PROTECTED] wrote:

viq wrote:
 On Thursday 25 May 2006 09:22, Jan Johansson wrote:
 akonsu [EMAIL PROTECTED] wrote:
 For the NTLDR you want the PBR (Partition Boot Record) not the
 MBR (Master Boot Record). I changed the of= for correct the
 terminology the important part is the if= device. I usually use

 dd if=/dev/rwd0a of=/mnt/OpenBSD.pbr bs=512 count=1

 where /mnt is the mountpoint of a small FAT partiton that is
 active.

 While at the subject, you need to run this every time you upgrade bootblocks.
 What would be the result of not updating bootblocks when upgrading from
 snapshot?

depends.

The boot code doesn't change dramatically often.  [...]

  Or not rerunning that command when updating them?

As indicated by others, the system won't boot.
[...]


Excellent! I had the exact same problem (and also solved it with
winimage, which is a disugsting app). Thanks to Nick for his clear
explanation, and others for the solution in simple terms. This list is
always so informative.

-Nick (#2)

Laptop boot problem with APM enabled

[Lars Hansson]

I recently got a new laptop and while it does work well with OpenBSD it only
does so if I disable APM.
Below is the dmesg's both from a failed boot with APM enabled and a working one
where APM is disabled.
The machine in question is a Neo Q-Note 350S, aka Clevo M350S.

= APM enabled =
OpenBSD 3.8-current (GENERIC) #224: Sat Oct 29 13:52:43 MDT 2005
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel(R) Celeron(R) M processor 1.30GHz (GenuineIntel 686-class) 1.30 
GHz
cpu0: 
FPU,V86,DE,PSE,TSC,MSR,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,ACPI,MMX,FXSR,SSE,SSE2,SS,TM,SBF
real mem  = 232300544 (226856K)
avail mem = 205123584 (200316K)
using 2861 buffers containing 11718656 bytes (11444K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(1c) BIOS, date 07/26/05, BIOS32 rev. 0 @ 0xfd810
apm0 at bios0: Power Management spec V1.2
uvm_fault(0xd05c22e0, 0x4000, 0, 1) - e
kernel: page fault trap, code=0
Stopped at  trap+0x15f:movzbl  0(%edx),%eax
ddb ps
PID PPIDPGRPUID S   FLAGS   WAITCOMMAND
*   0   -1  0   0   7   0x80204 swapper
ddb trace
trap() at trap+0x15f
--- trap (number 4) ---
curpcb(9ce00040,1,530a,12387227) at 0x4a39
ddb

= APM disabled =
OpenBSD 3.8-current (GENERIC) #224: Sat Oct 29 13:52:43 MDT 2005
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel(R) Celeron(R) M processor 1.30GHz (GenuineIntel 686-class) 1.30 
GHz
cpu0: 
FPU,V86,DE,PSE,TSC,MSR,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,ACPI,MMX,FXSR,SSE,SSE2,SS,TM,SBF
real mem  = 232300544 (226856K)
avail mem = 205123584 (200316K)
using 2861 buffers containing 11718656 bytes (11444K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(1c) BIOS, date 07/26/05, BIOS32 rev. 0 @ 0xfd810
apm at bios0 function 0x15 not configured
pcibios0 at bios0: rev 2.1 @ 0xfd810/0x7f0
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdf50/144 (7 entries)
pcibios0: PCI Interrupt Router at 000:02:0 (SiS 85C503 System rev 0x00)
pcibios0: PCI bus #2 is the last bus
bios0: ROM list: 0xc/0xc000 0xcc000/0xa000 0xdc000/0x4000!
cpu0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 SiS 661 PCI rev 0x11
ppb0 at pci0 dev 1 function 0 SiS 648FX AGP rev 0x00
pci1 at ppb0 bus 1
vga1 at pci1 dev 0 function 0 SiS 6330 VGA rev 0x00: aperture at 0xe800, 
size 0x40
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
pcib0 at pci0 dev 2 function 0 SiS 85C503 System rev 0x25
pciide0 at pci0 dev 2 function 5 SiS 5513 EIDE rev 0x00: 661: DMA, channel 0 
configured to compatibility, channel 1 configured to compatibility
wd0 at pciide0 channel 0 drive 0: FUJITSU MHT2040AT
wd0: 16-sector PIO, LBA, 38154MB, 78140160 sectors
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5
atapiscsi0 at pciide0 channel 1 drive 0
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0: PHILIPS, CDRW/DVD SCB5265, TX01 SCSI0 5/cdrom 
removable
cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2
SiS 7013 Modem rev 0xa0 at pci0 dev 2 function 6 not configured
auich0 at pci0 dev 2 function 7 SiS 7012 AC97 rev 0xa0: irq 5, SiS7012 AC97
ac97: codec id 0x414c4740 (Avance Logic ALC202)
ac97: codec features headphone, 20 bit DAC, 18 bit ADC, Realtek 3D
audio0 at auich0
ohci0 at pci0 dev 3 function 0 SiS 5597/5598 USB rev 0x0f: irq 11, version 
1.0, legacy support
usb0 at ohci0: USB revision 1.0
uhub0 at usb0
uhub0: SiS OHCI root hub, rev 1.00/1.00, addr 1
uhub0: 3 ports with 3 removable, self powered
ohci1 at pci0 dev 3 function 1 SiS 5597/5598 USB rev 0x0f: irq 9, version 
1.0, legacy support
usb1 at ohci1: USB revision 1.0
uhub1 at usb1
uhub1: SiS OHCI root hub, rev 1.00/1.00, addr 1
uhub1: 3 ports with 3 removable, self powered
ehci0 at pci0 dev 3 function 3 SiS 7002 USB rev 0x00: irq 9
usb2 at ehci0: USB revision 2.0
uhub2 at usb2
uhub2: SiS EHCI root hub, rev 2.00/1.00, addr 1
uhub2: 6 ports with 6 removable, self powered
sis0 at pci0 dev 4 function 0 SiS 900 10/100BaseTX rev 0x91: irq 11, address 
00:90:f5:47:6d:6a
rlphy0 at sis0 phy 1: RTL8201L 10/100 PHY, rev. 1
cbb0 at pci0 dev 14 function 0 ENE CB-1410 CardBus rev 0x01: irq 5
isa0 at pcib0
isadma0 at isa0
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pmsi0 at pckbc0 (aux slot)
pckbc0: using irq 12 for aux slot
wsmouse0 at pmsi0 mux 0
pcppi0 at isa0 port 0x61
midi0 at pcppi0: PC speaker
spkr0 at pcppi0
sysbeep0 at pcppi0
npx0 at isa0 port 0xf0/16: using exception 16
cardslot0 at cbb0 slot 0 flags 0
cardbus0 at cardslot0: bus 2 device 0 cacheline 0x0, lattimer 0x20
pcmcia0 at cardslot0
biomask effd netmask effd ttymask 
pctr: 686-class user-level performance counters enabled
mtrr: Pentium Pro MTRR support
dkcsum: wd0 matches BIOS drive 0x80
root on wd0a
rootdev=0x0 rrootdev=0x300 rawdev=0x302

Re: Laptop boot problem with APM enabled

[Marco Peereboom]

Hey could you try the latest snap on this box please?

On Wed, Nov 02, 2005 at 11:02:08AM +0800, Lars Hansson wrote:
 I recently got a new laptop and while it does work well with OpenBSD it only
 does so if I disable APM.
 Below is the dmesg's both from a failed boot with APM enabled and a working 
 one
 where APM is disabled.
 The machine in question is a Neo Q-Note 350S, aka Clevo M350S.
 
 = APM enabled =
 OpenBSD 3.8-current (GENERIC) #224: Sat Oct 29 13:52:43 MDT 2005
 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
 cpu0: Intel(R) Celeron(R) M processor 1.30GHz (GenuineIntel 686-class) 1.30 
 GHz
 cpu0: 
 FPU,V86,DE,PSE,TSC,MSR,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,ACPI,MMX,FXSR,SSE,SSE2,SS,TM,SBF
 real mem  = 232300544 (226856K)
 avail mem = 205123584 (200316K)
 using 2861 buffers containing 11718656 bytes (11444K) of memory
 mainbus0 (root)
 bios0 at mainbus0: AT/286+(1c) BIOS, date 07/26/05, BIOS32 rev. 0 @ 0xfd810
 apm0 at bios0: Power Management spec V1.2
 uvm_fault(0xd05c22e0, 0x4000, 0, 1) - e
 kernel: page fault trap, code=0
 Stopped at  trap+0x15f:movzbl  0(%edx),%eax
 ddb ps
   PID PPIDPGRPUID S   FLAGS   WAITCOMMAND
 * 0   -1  0   0   7   0x80204 swapper
 ddb trace
 trap() at trap+0x15f
 --- trap (number 4) ---
 curpcb(9ce00040,1,530a,12387227) at 0x4a39
 ddb
 
 = APM disabled =
 OpenBSD 3.8-current (GENERIC) #224: Sat Oct 29 13:52:43 MDT 2005
 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
 cpu0: Intel(R) Celeron(R) M processor 1.30GHz (GenuineIntel 686-class) 1.30 
 GHz
 cpu0: 
 FPU,V86,DE,PSE,TSC,MSR,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,ACPI,MMX,FXSR,SSE,SSE2,SS,TM,SBF
 real mem  = 232300544 (226856K)
 avail mem = 205123584 (200316K)
 using 2861 buffers containing 11718656 bytes (11444K) of memory
 mainbus0 (root)
 bios0 at mainbus0: AT/286+(1c) BIOS, date 07/26/05, BIOS32 rev. 0 @ 0xfd810
 apm at bios0 function 0x15 not configured
 pcibios0 at bios0: rev 2.1 @ 0xfd810/0x7f0
 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdf50/144 (7 entries)
 pcibios0: PCI Interrupt Router at 000:02:0 (SiS 85C503 System rev 0x00)
 pcibios0: PCI bus #2 is the last bus
 bios0: ROM list: 0xc/0xc000 0xcc000/0xa000 0xdc000/0x4000!
 cpu0 at mainbus0
 pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
 pchb0 at pci0 dev 0 function 0 SiS 661 PCI rev 0x11
 ppb0 at pci0 dev 1 function 0 SiS 648FX AGP rev 0x00
 pci1 at ppb0 bus 1
 vga1 at pci1 dev 0 function 0 SiS 6330 VGA rev 0x00: aperture at 
 0xe800, size 0x40
 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
 wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
 pcib0 at pci0 dev 2 function 0 SiS 85C503 System rev 0x25
 pciide0 at pci0 dev 2 function 5 SiS 5513 EIDE rev 0x00: 661: DMA, channel 
 0 configured to compatibility, channel 1 configured to compatibility
 wd0 at pciide0 channel 0 drive 0: FUJITSU MHT2040AT
 wd0: 16-sector PIO, LBA, 38154MB, 78140160 sectors
 wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5
 atapiscsi0 at pciide0 channel 1 drive 0
 scsibus0 at atapiscsi0: 2 targets
 cd0 at scsibus0 targ 0 lun 0: PHILIPS, CDRW/DVD SCB5265, TX01 SCSI0 5/cdrom 
 removable
 cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2
 SiS 7013 Modem rev 0xa0 at pci0 dev 2 function 6 not configured
 auich0 at pci0 dev 2 function 7 SiS 7012 AC97 rev 0xa0: irq 5, SiS7012 AC97
 ac97: codec id 0x414c4740 (Avance Logic ALC202)
 ac97: codec features headphone, 20 bit DAC, 18 bit ADC, Realtek 3D
 audio0 at auich0
 ohci0 at pci0 dev 3 function 0 SiS 5597/5598 USB rev 0x0f: irq 11, version 
 1.0, legacy support
 usb0 at ohci0: USB revision 1.0
 uhub0 at usb0
 uhub0: SiS OHCI root hub, rev 1.00/1.00, addr 1
 uhub0: 3 ports with 3 removable, self powered
 ohci1 at pci0 dev 3 function 1 SiS 5597/5598 USB rev 0x0f: irq 9, version 
 1.0, legacy support
 usb1 at ohci1: USB revision 1.0
 uhub1 at usb1
 uhub1: SiS OHCI root hub, rev 1.00/1.00, addr 1
 uhub1: 3 ports with 3 removable, self powered
 ehci0 at pci0 dev 3 function 3 SiS 7002 USB rev 0x00: irq 9
 usb2 at ehci0: USB revision 2.0
 uhub2 at usb2
 uhub2: SiS EHCI root hub, rev 2.00/1.00, addr 1
 uhub2: 6 ports with 6 removable, self powered
 sis0 at pci0 dev 4 function 0 SiS 900 10/100BaseTX rev 0x91: irq 11, 
 address 00:90:f5:47:6d:6a
 rlphy0 at sis0 phy 1: RTL8201L 10/100 PHY, rev. 1
 cbb0 at pci0 dev 14 function 0 ENE CB-1410 CardBus rev 0x01: irq 5
 isa0 at pcib0
 isadma0 at isa0
 pckbc0 at isa0 port 0x60/5
 pckbd0 at pckbc0 (kbd slot)
 pckbc0: using irq 1 for kbd slot
 wskbd0 at pckbd0: console keyboard, using wsdisplay0
 pmsi0 at pckbc0 (aux slot)
 pckbc0: using irq 12 for aux slot
 wsmouse0 at pmsi0 mux 0
 pcppi0 at isa0 port 0x61
 midi0 at pcppi0: PC speaker
 spkr0 at pcppi0
 sysbeep0 at pcppi0
 npx0 at isa0 port 0xf0/16: using exception 16
 cardslot0 at cbb0 slot 0 flags 0
 cardbus0 at cardslot0: bus 2 device 0 cacheline 0x0, lattimer 0x20
 pcmcia0 at 

Re: Laptop boot problem with APM enabled

[Lars Hansson]

On Tue, 1 Nov 2005 21:40:32 -0600
Marco Peereboom [EMAIL PROTECTED] wrote:

 Hey could you try the latest snap on this box please?

Almost exactly the same thing happens with the November 1 snapshot.
Only one line is different:
uvm_fault(0xd05c23e0, 0x4000, 0, 1) - e

---
Lars Hansson

boot-problem

[Roelof Wobben]

Hello,

After installing Openbsd 3.7 i have accidently booted the process before i
could copy openbsd.pbr to win xp.

Is there a way i could get into Openbsd with the installation cd so i could
copy openbsd.pbr or do i have to do the installation again.

Roelof

Re: boot-problem

[Emil Khatib]

You could try to label your OpenBSD as active with any partitioning
software, copy openbsd.pbr and then do the contrary to get Win booting back.
I'm sure that there is a more efficient way, but I'm not an expert in
OpenBSD :P

On 10/9/05, Roelof Wobben [EMAIL PROTECTED] wrote:

 Hello,

 After installing Openbsd 3.7 i have accidently booted the process before i
 could copy openbsd.pbr to win xp.

 Is there a way i could get into Openbsd with the installation cd so i
 could
 copy openbsd.pbr or do i have to do the installation again.

 Roelof

Re: boot-problem

[Andreas Bihlmaier]

 Hello,
 
 After installing Openbsd 3.7 i have accidently booted the process before i
 could copy openbsd.pbr to win xp.
 
 Is there a way i could get into Openbsd with the installation cd so i could
 copy openbsd.pbr or do i have to do the installation again.
 

0.) READ THE FAQ !!!

(currently waiting for my mvme147 to copy sboot, thus I have time for a more
specific answer):
1.) Boot from the install cd 
2.) Type 'S' for Shell
3.) mount a (with FAT) preformated floppy ( mount /dev/fd0c /mnt )
4.) do the copying ( dd if=/dev/r[a-z][a-z][0-9]c of=/mnt/openbsd.pr bs=512
count=1)
5.) umount /mnt
6.) reboot
7.) be happy

Regards,
ahb

Re: boot-problem

[steven mestdagh]

On Sun, Oct 09, 2005 at 08:26:19PM +0200, Roelof Wobben wrote:
 Hello,
 
 After installing Openbsd 3.7 i have accidently booted the process before i
 could copy openbsd.pbr to win xp.

Accidentally? Are you positive your installation is finished?

 Is there a way i could get into Openbsd with the installation cd so i could
 copy openbsd.pbr or do i have to do the installation again.

(assuming your installation was really finished...)
The installation cd boots the OpenBSD kernel. After that, choose the shell
option, mount your disk, copy the file as needed.

OR you can use boot -a at the boot prompt, then it will ask for your root
device and boot into your installed OpenBSD system. note that in this case
you will still be using the RAMDISK kernel from the cd, not the usual
GENERIC kernel...


Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm

Re: boot-problem

[Matthew Weigel]

Roelof Wobben wrote:

Hello,

After installing Openbsd 3.7 i have accidently booted the process before i
could copy openbsd.pbr to win xp.

Is there a way i could get into Openbsd with the installation cd so i could


Yes.  That's what the (S)hell is for in
  (I)nstall, (U)pgrade or (S)hell?

Since you only need to get the PBR, you can do the dd(1) step without 
even mounting anything.  You can then mount a floppy drive, USB memory 
stick, etc. to copy over the PBR so you can get at it under Windows.

--
 Matthew Weigel

Re: CARP interface incorrectly comes up as INIT on boot - PROBLEM IDENTIFIED

[Tim]

Tim t-openbsd at timdarby.net writes:

 
 I'm using CARP under 3.7 release version on two boxes that aren't firewalls,
 so
 no pfsync involved and CARP configured as described in the FAQ.  What I'm
 seeing
 is that the box I've designated as BACKUP always boots with carp0 as INIT
 and

After some experimentation, it turns out that if I create 3 or more carp
interfaces on the same physical interface, then carp0 always comes up as INIT on
boot.  I have replicated this on two other machines, so this is not just a 
fluke.

Tim

Re: CARP interface incorrectly comes up as INIT on boot - PROBLEM IDENTIFIED

[Jason Dixon]

On Oct 8, 2005, at 12:18 AM, Tim wrote:

After some experimentation, it turns out that if I create 3 or more  
carp
interfaces on the same physical interface, then carp0 always comes  
up as INIT on
boot.  I have replicated this on two other machines, so this is not  
just a fluke.


Wrong.  Here are the carp interfaces from a test server.  The first  
two (carp0, carp1) are for an arp-balance config on fxp1.  The next  
two (carp2, carp3) are another arp-balance config on fxp0.  The last  
three I just created to test your claim.  They were all added to  
fxp1, giving me five carp interfaces on fxp1.  Note that none of  
these interfaces are in INIT.



carp0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
carp: BACKUP carpdev fxp1 vhid 1 advbase 1 advskew 0
groups: carp
inet 192.168.0.20 netmask 0xff00 broadcast 255.255.255.0
carp1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
carp: BACKUP carpdev fxp1 vhid 2 advbase 1 advskew 100
groups: carp
inet 192.168.0.20 netmask 0xff00 broadcast 255.255.255.0
carp2: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
carp: BACKUP carpdev fxp0 vhid 1 advbase 1 advskew 0
groups: carp
inet 10.0.0.1 netmask 0xff00 broadcast 255.255.255.0
carp3: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
carp: BACKUP carpdev fxp0 vhid 2 advbase 1 advskew 100
groups: carp
inet 10.0.0.1 netmask 0xff00 broadcast 255.255.255.0
carp4: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
carp: MASTER carpdev fxp1 vhid 3 advbase 1 advskew 0
groups: carp
inet 192.168.0.80 netmask 0xff00 broadcast 255.255.255.0
carp5: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
carp: MASTER carpdev fxp1 vhid 4 advbase 1 advskew 0
groups: carp
inet 192.168.0.81 netmask 0xff00 broadcast 255.255.255.0
carp6: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
carp: MASTER carpdev fxp1 vhid 5 advbase 1 advskew 0
groups: carp
inet 192.168.0.82 netmask 0xff00 broadcast 255.255.255.0


--
Jason Dixon
DixonGroup Consulting
http://www.dixongroup.net

Re: CARP interface incorrectly comes up as INIT on boot - PROBLEM IDENTIFIED

[Jason Dixon]

On Oct 8, 2005, at 12:49 AM, Tim wrote:

Sorry, I wasn't clear in my post.  I meant to say 3 or more  
interfaces created as backup.  I can add as many master carp  
interfaces as I want and it seems to be fine.  Try adding a 3rd  
backup carp to one of your physical interfaces and let me know what  
happens.


(Posting back to list)

Wrong again.  Works fine, even with 3 or more interfaces in BACKUP.

carp0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
carp: BACKUP carpdev fxp1 vhid 1 advbase 1 advskew 100
groups: carp
inet 192.168.0.20 netmask 0xff00 broadcast 255.255.255.0
carp1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
carp: BACKUP carpdev fxp1 vhid 2 advbase 1 advskew 0
groups: carp
inet 192.168.0.20 netmask 0xff00 broadcast 255.255.255.0
carp2: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
carp: BACKUP carpdev fxp0 vhid 1 advbase 1 advskew 100
groups: carp
inet 10.0.0.1 netmask 0xff00 broadcast 255.255.255.0
carp3: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
carp: BACKUP carpdev fxp0 vhid 2 advbase 1 advskew 0
groups: carp
inet 10.0.0.1 netmask 0xff00 broadcast 255.255.255.0
carp4: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
carp: BACKUP carpdev fxp1 vhid 3 advbase 1 advskew 0
groups: carp
inet 192.168.0.80 netmask 0xff00 broadcast 255.255.255.0
carp5: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
carp: BACKUP carpdev fxp1 vhid 4 advbase 1 advskew 0
groups: carp
inet 192.168.0.81 netmask 0xff00 broadcast 255.255.255.0
carp6: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
carp: BACKUP carpdev fxp1 vhid 5 advbase 1 advskew 0
groups: carp
inet 192.168.0.82 netmask 0xff00 broadcast 255.255.255.0


--
Jason Dixon
DixonGroup Consulting
http://www.dixongroup.net

Re: Sad boot problem (boot.conf: invalid argument)

[Stuart Henderson]

--On 09 June 2005 19:00 -0600, Tobias Weingartner wrote:


On Thursday, June 9, Luciano ES wrote:

Hello, Stuart. The answers to your latest questions:

On 09/06/05 at 12:11, Stuart Henderson wrote in 7K:

 How does 'fdisk wd0' look?

- The second slice (offset 63) was marked as unknown. Then I fixed
it with OpenBSD's fdisk. Now it is marked as OpenBSD. The problem is
that I have done that many times. The OpenBSD gets lost
mysteriously. Often, between two reboots of OpenBSD (without booting
any other system).


Something is overwriting it.  Where does your 'a' slice begin?
What is the output of 'disklabel wd0'?


Email from o.p. with URLs to text files with the information doesnbt
seem to have made it to the list, Ibll include it below for reference
and paste in the disklabels for ease of use;

# /dev/rwd0c:
type: ESDI
disk: ESDI/IDE disk
label: ST3120022A
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 16
sectors/cylinder: 1008
cylinders: 16383
total sectors: 234441648
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0# microseconds
track-to-track seek: 0# microseconds
drivedata: 0

16 partitions:
# sizeoffset  fstype [fsize bsize  cpg]
 a:   102406563  4.2BSD   2048 16384  328 # Cyl 
0*-  1015
 b:   1024128   1024128swap   # Cyl  1016 
-  2031
 c: 234441648 0  unused  0 0  # Cyl 0 
-232580
 d:   1024128   2048256  4.2BSD   2048 16384  328 # Cyl  2032 
-  3047
 e:   9625392   3072384  4.2BSD   2048 16384  328 # Cyl  3048 
- 12596
 f:204624  12697776  4.2BSD   2048 16384  204 # Cyl 12597 
- 12799
 g:   2054115  12902400  4.2BSD   2048 16384  328 # Cyl 12800 
- 14837*
 i:   1847475  14956515   MSDOS   # Cyl 
14837*- 16670*
 j: 32004  16804116  ext2fs   # Cyl 
16670*- 16702*
 k:   2618532  16836183 unknown   # Cyl 
16702*- 19300*
 l:  10361862  19454778  ext2fs   # Cyl 
19300*- 29579
 m:  10361862  29816703  ext2fs   # Cyl 
29580*- 39859*
 n:  10329732  40178628  ext2fs   # Cyl 
39859*- 50107*
 o:  31535532  50508423   MSDOS   # Cyl 
50107*- 81392*
 p:  25189857  82044018   MSDOS   # Cyl 
81392*-106382*


[and from bsd.rd with broken MBR partition table]
 c: 234441648 0  unused  0 0  # Cyl 0 
-232580
 i:   1847475  14956515   MSDOS   # Cyl 
14837*- 16670*
 j:  1495645263 unknown   # Cyl 
0*- 14837*
 k: 32004  16804116  ext2fs   # Cyl 
16670*- 16702*
 l:   2618532  16836183 unknown   # Cyl 
16702*- 19300*
 m:  10361862  19454778  ext2fs   # Cyl 
19300*- 29579
 n:  10361862  29816703  ext2fs   # Cyl 
29580*- 39859*
 o:  10329732  40178628  ext2fs   # Cyl 
39859*- 50107*
 p:  31535532  50508423   MSDOS   # Cyl 
50107*- 81392*


 Forwarded Message 
Date: 09 June 2005 00:42 -0300
From: Luciano ES [EMAIL PROTECTED]
To: Stuart Henderson [EMAIL PROTECTED]
Cc: misc@openbsd.org
Subject: Re: Sad boot problem (boot.conf: invalid argument)

Hello, Stuart.  Thanks for sending  me a  copy of your  reply. I
don't  know if  anyone else  has added  anything to  this thread
because I subscribe in digest mode.  So here is all the info you
told me to post, with comments.

First off, the boot error message:

http://tinyurl.com/8qexk

So I booted with the CD and used the (S)hell. Here is dmesg:

http://tinyurl.com/7wwdg

And here is the first attempt at disklabel:

http://tinyurl.com/8ezsx

That's weird, isn't it? OpenBSD has disappeared completely. So I
ran fdisk and saw that the slice was marked unknown instead of
OpenBSD.  Hmmm...  That reminds  me  of  a  page I  read  that
actually complains about problems with OpenBSD's fdisk:

http://geodsoft.com/howto/dualboot/

This tutorial  makes several  complaints about  OpenBSD's fdisk.
And, in my own experience, it  was clearly difficult not to lose
the slice's  ID every  now and  then with  no apparent  cause. I
found myself fixing the OpenBSD slice's  ID all the time. And it
only happens with OpenBSD. If I boot into Linux and run fdisk, I
see that slice  correctly identified as OpenBSD. Then  I go back
to OpenBSD and it still won't  boot. It still will see the slice
as unknown. And it does not accept IDs set with Linux's fdisk.
It really must be done by OpenBSD's fdisk. Grrr...

So I did  it again: changed the ID with  OpenBSD's fdisk and ran
disklabel again:

http://tinyurl.com/bowlc

Ha! There it is now. So  I recorded another dmesg, but there was
no difference. So I removed the CD and rebooted. Yay! It worked!
OpenBSD is booting off the hard disk again.

But for how

Re: Sad boot problem (boot.conf: invalid argument)

[Stuart Henderson]

--On 09 June 2005 00:42 -0300, Luciano ES wrote:


First off, the boot error message:

Loading...
probing: pc0 com0 com1 apm mem [508K 254M a20=on]
disk: fd0 hd0+* hd1+* hd2*

OpenBSD/i386 BOOT 2.06

open(hd0a:/etc/boot.conf): Invalid argument
boot
booting hd0a:/bsd: open hd0a:/bsd: Invalid argument
 failed(22). will try /obsd


http://www.openbsd.org/faq/faq14.html#Boot386
ok, * means that no BSD disklabel was found, which isn't a surprise if
the fdisk partition was somehow lost as there wouldn't be anywhere to
look for a disklabel. This is also reported in the dmesg;


http://tinyurl.com/7wwdg



wd0: no disk label
wd1: no disk label
wd2: no disk label


If the label isn't present, you'd expect to have a default label
generated from the fdisk partitions (but of course this has just the
one 'container' BSD partition, not each individual partitions with the
filesystems for / /usr /var etc), which fits with the disklabels you
gave.

How does 'fdisk wd0' look? Have you used any disk tools on the drive
from another OS which might have changed the MBR? Are you loading the
OpenBSD boot directly from MBR, or is there some other bootmanager in
the way? Any chance some program might have decided that the OpenBSD
partition is bogus because it doesn't know the type, and decides to
change it?


# /dev/rwd0c:
type: ESDI
disk: ESDI/IDE disk
label: ST3120022A
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 16
sectors/cylinder: 1008
cylinders: 16383
total sectors: 234441648
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0# microseconds
track-to-track seek: 0# microseconds
drivedata: 0

# sizeoffset  fstype [fsize bsize  cpg]
  a:   102406563  4.2BSD   2048 16384  328 # Cyl 

0*-  1015
  b:   1024128   1024128swap   # Cyl 

1016 -  2031
  c: 234441648 0  unused  0 0  # Cyl 

0 -232580
  d:   1024128   2048256  4.2BSD   2048 16384  328 # Cyl 

2032 -  3047
  e:   9625392   3072384  4.2BSD   2048 16384  328 # Cyl 

3048 - 12596
  f:204624  12697776  4.2BSD   2048 16384  204 # Cyl 

12597 - 12799
  g:   2054115  12902400  4.2BSD   2048 16384  328 # Cyl 

12800 - 14837*
  i:   1847475  14956515   MSDOS   # Cyl 

14837*- 16670*
  j: 32004  16804116  ext2fs   # Cyl 

16670*- 16702*
  k:   2618532  16836183 unknown   # Cyl 

16702*- 19300*
  l:  10361862  19454778  ext2fs   # Cyl 

19300*- 29579
  m:  10361862  29816703  ext2fs   # Cyl 

29580*- 39859*
  n:  10329732  40178628  ext2fs   # Cyl 

39859*- 50107*
  o:  31535532  50508423   MSDOS   # Cyl 

50107*- 81392*
  p:  25189857  82044018   MSDOS   # Cyl 

81392*-106382*

-and-


16 partitions:
# sizeoffset  fstype [fsize bsize  cpg]
  c: 234441648 0  unused  0 0  # Cyl 

0 -232580
  i:   1847475  14956515   MSDOS   # Cyl 

14837*- 16670*
  j:  1495645263 unknown   # Cyl 

0*- 14837*
  k: 32004  16804116  ext2fs   # Cyl 

16670*- 16702*
  l:   2618532  16836183 unknown   # Cyl 

16702*- 19300*
  m:  10361862  19454778  ext2fs   # Cyl 

19300*- 29579
  n:  10361862  29816703  ext2fs   # Cyl 

29580*- 39859*
  o:  10329732  40178628  ext2fs   # Cyl 

39859*- 50107*
  p:  31535532  50508423   MSDOS   # Cyl 

50107*- 81392*

The listed partitions cover 50% of the HD, so I guess there are
probably other partitions. disklabel only supports partitions a-p
(which is why the MSDOS partition disappears when the others are moved
to the next letter when the unknown OpenBSD partition becomes 'j'). I
don't know if any problems are exposed by using so many partitions
(other than not being able to mount some of them from OpenBSD), but
when you deal with corner cases, there's more chance of finding
problems.


This tutorial  makes several  complaints about  OpenBSD's fdisk.
And, in my own experience, it  was clearly difficult not to lose
the slice's  ID every  now and  then with  no apparent  cause.


I haven't really found that myself, but the most I've done is dual-boot
OpenBSD and Windows on one box with two fdisk partitions using ntldr
(as described in the faq), so it's a far less complex setup. Never seen
a partition-type change with OpenBSD tools except when deliberately
doing so with fdisk...

Re: Sad boot problem (boot.conf: invalid argument)

[Luciano ES]

Hello, Stuart. The answers to your latest questions:

On 09/06/05 at 12:11, Stuart Henderson wrote in 7K:

How does 'fdisk wd0' look?

- The second slice (offset 63) was marked as unknown. Then I fixed it with
OpenBSD's fdisk. Now it is marked as OpenBSD. The problem is that I have
done that many times. The OpenBSD gets lost mysteriously. Often, between
two reboots of OpenBSD (without booting any other system).

Have you used any disk tools on the drive
from another OS which might have changed the MBR?

- After, and only after I had the problem, I tried using Linux's fdisk a
couple of times. But it didn't work, so I gave up. But I hadn't got
anywhere near the MBR until the problem occurred for the first time. And,
like I said, the slice also loses its OpenBSD ID mysteriously between two
reboots of OpenBSD.

Are you loading the
OpenBSD boot directly from MBR, or is there some other bootmanager in
the way? Any chance some program might have decided that the OpenBSD
partition is bogus because it doesn't know the type, and decides to
change it?

- I am using Grub with these options:

rootnoverify (hd0,1)
makeactive
chainloader +1

Always worked fine with Windows, Linux, FreeBSD and NetBSD.

Thank you again for your attention.

-- 
Luciano ES
Santos, SP - Brasil

Re: Sad boot problem (boot.conf: invalid argument)

[Tobias Weingartner]

On Thursday, June 9, Luciano ES wrote:
 Hello, Stuart. The answers to your latest questions:
 
 On 09/06/05 at 12:11, Stuart Henderson wrote in 7K:
 
 How does 'fdisk wd0' look?
 
 - The second slice (offset 63) was marked as unknown. Then I fixed it with
 OpenBSD's fdisk. Now it is marked as OpenBSD. The problem is that I have
 done that many times. The OpenBSD gets lost mysteriously. Often, between
 two reboots of OpenBSD (without booting any other system).

Something is overwriting it.  Where does your 'a' slice begin?
What is the output of 'disklabel wd0'?

--Toby.

Re: Sad boot problem (boot.conf: invalid argument)

[Arnaud Bergeron]

On 6/9/05, Luciano ES [EMAIL PROTECTED] wrote:
 Hello, Stuart. The answers to your latest questions:
 
 On 09/06/05 at 12:11, Stuart Henderson wrote in 7K:
 
 How does 'fdisk wd0' look?
 
 - The second slice (offset 63) was marked as unknown. Then I fixed it with
 OpenBSD's fdisk. Now it is marked as OpenBSD. The problem is that I have
 done that many times. The OpenBSD gets lost mysteriously. Often, between
 two reboots of OpenBSD (without booting any other system).
 
 Have you used any disk tools on the drive
 from another OS which might have changed the MBR?
 
 - After, and only after I had the problem, I tried using Linux's fdisk a
 couple of times. But it didn't work, so I gave up. But I hadn't got
 anywhere near the MBR until the problem occurred for the first time. And,
 like I said, the slice also loses its OpenBSD ID mysteriously between two
 reboots of OpenBSD.
 
 Are you loading the
 OpenBSD boot directly from MBR, or is there some other bootmanager in
 the way? Any chance some program might have decided that the OpenBSD
 partition is bogus because it doesn't know the type, and decides to
 change it?
 
 - I am using Grub with these options:
 
 rootnoverify (hd0,1)
 makeactive
 chainloader +1
 

From what I know of grub (don't remember what version, It was like 6
months ago), you need to put

rootnoverify (hd0,1a)

(assuming you boot from the 'a' slice).  I have absolutely no idea if
this causes the problem but maybe it can help.

 Always worked fine with Windows, Linux, FreeBSD and NetBSD.
 
 Thank you again for your attention.
 
 --
 Luciano ES
 Santos, SP - Brasil
 
 


-- 
They allowed us to set up a separate division almost, that is physically,
geographically, psychologically and spiritually different from what Bill 
himself calls the Borg
 - Peter Moore, V.P. in charge of Xbox 360 marketing at Microsoft.

Sad boot problem (boot.conf: invalid argument)

[Luciano ES]

Hi to all. I have been interested in BSD for about a year and have tried
all of the three most popular free ones.

I would like to start by saying something good: OpenBSD was a very pleasant
surprise to me. After trying FreeBSD and NetBSD, I left OpenBSD to the end
of the queue because of so many bad things I had heard about it, like it's
slow or it's too difficult. I didn't find any of this while testing it.
Instead, this is my favorite BSD so far and I actually think I could use it
every day instead of Linux. I also want to build a server, BTW.

Now, the bad thing. Contrasting with the very good experience I had in my
tests, I have already installed it three times because of a problem that
beats the heck out of me. You certainly have heard about it before:

disk: fd0 hd0+
 OpenBSD/i386 BOOT 2.02
open(hd0a:/etc/boot.conf: Invalid argument
boot
booting hd0a:/bsd: open hd0a:/bsd: Invalid argument
 failed(22). will try /obsd
 boot
 booting hd0a:/obsd: open hd0a:/obsd: Invalid argument
 failed(22). will try /bsd.old
 
My first line is different from disk: fd0 hd0+ because I have three hard
disks. And I guess it's not BOOT 2.02 anymore. I have OpenBSD 3.7.
Actually, I copied the block above from the archives:

http://archives.neohapsis.com/archives/openbsd/2003-11/0143.html

It was very sad. In the first time, I could boot with the cd:

boot boot hd0a:/bsd

But I couldn't find out how to fix the system and boot without the CD.
Reinstalling didn't work either. Neither did deleting and recreating the
disk labels. Actually, even if I format the slice with another file system,
the disk labels are still there when I try to reinstall. The only method
that worked for me was the following:

- Format the slice with another file system. In my case, ext2.

- Boot into Linux and copy an awful lot of data to that slice until no
space is left.

- Boot with the CD and reinstall everything all over again.

Yes, this method actually worked twice and had me piloting OpenBSD again.
That's when I tested OpenBSD and found it so good. But it only survives
about 4 or 5 reboots until that nasty problem bites me again. And in the
last two times, booting with boot hd0a:/bsd didn't work either.

Then I just gave up. What I have now is an unbootable slice. If I had
actual data in there, I wouldn't know what to do to have it back. But what
is also a very bad consequence is that now I am afraid of OpenBSD. All the
time during my tests, I stared nervously at the boot sequence waiting for
the strange problem to happen again. And, sure enough, it's happened three
times already in less than two days. I really liked all the rest of the
experience, but I don't think I'll have the courage to actually use it. I
almost formatted the slice to install something else and left OpenBSD
behind, but decided to take a shot and ask for a little enlightenment here.

Back to that message I found in the archives, it seems that the person that
signs as herk solved the problem with a BIOS update. Actually, I found
another case in Google of someone who had the same problem and also solved
the problem with a BIOS update.

But I don't want to go that way. I do not feel comfortable at all updating
my BIOS. Lots of things can go wrong and trash my motherboard. Besides, I
really would like someone to tell me why that has to be the only way if:

- I never had that problem with FreeBSD;

- I never had that problem with NetBSD;

- I never had that problem with Windows 95, 98 or 2000 (this machine never
saw and never will see XP);

- I never had that problem with any of the 10 or more Linux distros I have
tried, over 30 if we count multiple versions of these 10 distros as
individual distros.

In light of these facts, what would the technical explanation be for such a
discouraging flaw not to be viewed and addressed as a bug or, at least, a
shortcoming of OpenBSD?

Of course, alternative and effective solutions to my problem would be
greatly appreciated, but for now I only beg that you gentlemen at least
tell me, in very clear wording, why it is not considered a bug if it only
seems to happen with OpenBSD.

Many thanks in advance for your time and attention.

-- 
Luciano Espirito Santo
Santos, SP - Brasil

Sad boot problem (boot.conf: invalid argument)

[Luciano ES]

I am sorry, I forgot to say that my motherboard is an Asus A7N 266 VM. I am
sure that someone will want to know.

-- 
Luciano Espirito Santo
Santos, SP - Brasil

Re: Sad boot problem (boot.conf: invalid argument)

[Stuart Henderson]

--On 08 June 2005 21:22 -0300, Luciano ES wrote:


Now, the bad thing. Contrasting with the very good experience I had
in my tests, I have already installed it three times because of a
problem that beats the heck out of me. You certainly have heard about
it before:

disk: fd0 hd0+

OpenBSD/i386 BOOT 2.02

open(hd0a:/etc/boot.conf: Invalid argument
boot
booting hd0a:/bsd: open hd0a:/bsd: Invalid argument
 failed(22). will try /obsd
 boot
 booting hd0a:/obsd: open hd0a:/obsd: Invalid argument
 failed(22). will try /bsd.old

My first line is different from disk: fd0 hd0+ because I have three
hard disks. And I guess it's not BOOT 2.02 anymore. I have OpenBSD
3.7. Actually, I copied the block above from the archives:


Well, you want help with your problem, not someone else's problem from 
2003, with a very different bootloader...


Copy the exact message from your system. Either type it from the 
screen, being very careful that you don't miss any punctuation 
characters etc., or use a serial console as described on 
http://www.openbsd.org/faq/faq4.html#getdmesg


Output from disklabel might be useful, and you should include dmesg too.


But I couldn't find out how to fix the system and boot without the CD.
Reinstalling didn't work either. Neither did deleting and recreating
the disk labels. Actually, even if I format the slice with another
file system, the disk labels are still there when I try to reinstall.
The only method that worked for me was the following:


You can usually clear a disklabel by overwriting the start of the 
partition by dd'ing /dev/zero over it.