On Sun, 02 Nov 2008 21:55:19 -0500
Nick Holland <[EMAIL PROTECTED]> wrote:
> Rafael Cunha de Almeida wrote:
> > Hello,
> >
> > I'm having trouble booting my new opebsd installation. I was able to
> > boot usihg the CD and I tried to use installboot to record the
> > biosboot to the PBR. I booted with -s option, so I'd start in single
> > user mode and I mounted /usr to /mnt/.
> >
> > Then I did:
> > % /mnt/mdec/installboot /boot /mnt/mdec/biosboot sd0
> > ...
> > installboot: broken MBR
>
> What you describe is not clear.
> Why you are trying to do what you are trying to do is also unclear.
>
> IF you booted from the CD, you were running bsd.rd, so /boot
> would be on the ramdisk, and you were trying to put hooks to the
> ramdisk's /boot into sd0's PBR. Hopefully, it's clear why that
> won't work, though if that is your only problem, the error message
> is a bit cryptic.
>
>
> IF you used the CD to boot the OS off the disk, don't know why you
> mounted /usr to a strange location, or booted single user mode, etc.
I booted to the OS of the disk, I used:
boot> boot hd0a:/bsd.mp -s
At first I tried without -s, but installboot complained about the
partition being mounted. Reading the documentation I found out that I
had to boot in single user mode or in insecure kernel mode in order to
be able to do the changes. So that's what I did.
I mounted /usr to /mnt because when I logged as a single user nothing
was mounted, so I just mounted the /usr partition there out of habit
of always using /mnt together with mount. Sorry if that made it
confusing :-(.
> (and if you did boot bsd.rd off the CD, not sure why you wanted to
> go "single user". Probably doesn't change much, since bsd.rd isn't
> really multi-user, anyway)
>
> hm. also interesting: that prompt you show. Something is fishy.
>
> > I also tried:
> > % /mnt/mdec/installboot /boot /mnt/mdec/biosboot sd0a
> > installboot: superblock: devread: lseek: invalid argument
>
> same problem, plus an additional one, sd0a is not right.
Yeah, I thought maybe, if I don't want to mess with MBR, I could
overwrite only PBR using that command. Seems like I was wrong, though.
> > I have grub currently installed on MBR. OpenBSD is on
> > linux's /dev/sda2. Does anyone know what could be wrong? Of course, I'd
> > like it better if I don't have to destroy in order to get this
> > working :-).
>
> 1) you are using the commands wrong.
> 2) I don't know why you are even trying to use those commands.
>
> What is prompting you to try to install your own boot loader?
> Obviously, you think there is a problem, but I don't know why,
> and why this problem occurred in the first place needs to be
> investigated. The boot loader is normally installed by the
> installation process, if something went wrong there, we really
> should look at what and why.
I have linux installed on this machine and I use grub to boot it. I
installed OpenBSD on a new partition. The installation went well as far
as I could tell. So I edited the grub menu to include OpenBSD's
partition. I used this (on linux, OpenBSD's partition is at /dev/sda2):
rootnoverify (hd0,1)
makeactive
chainloader +1
Then grub gave me error 13:
Invalid or unsupported executable format
So I thought something went wrong during OpenBSD's installation. I was
able to boot to the OpenBSD system using the CD (boot hd0a:/bsd.mp), so
I thought the problem could only be on the bootloader.
Now, looking back on other e-mails on the list, I see that Michael had
a related problem. Seems like things worked out when he used the
installboot from openbsd 4.3. I could check out if that solves my
problem, then we could be looking at a regression here.
