[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: "Using Disk: 0 Partition: 3" problem
- To: "'Nick Nauwelaerts'" <nick_(_at_)_wanadoo_(_dot_)_be>
- Subject: RE: "Using Disk: 0 Partition: 3" problem
- From: Vazquez Javier <j_(_dot_)_vazquez_(_at_)_nzz_(_dot_)_ch>
- Date: Tue, 18 Dec 2001 17:01:19 +0100
- Cc: "'misc_(_at_)_openbsd_(_dot_)_org'" <misc_(_at_)_openbsd_(_dot_)_org>
i had this problems some months ago and i only had it with machines that had
formerly installed linux --> lilo! if you've installed linux on that machine
IMHO you can't just install openbsd over it without deinstalling lilo from
your mbr first ("lilo -U" or something like that?).
as far as i see you allready wiped linux off your disk, maybe you should
take a look at your disk manufactureres website and find a tool to
lowlevel-format your disk.
From: Nick Nauwelaerts [mailto:nick_(_at_)_wanadoo_(_dot_)_be]
Sent: Dienstag, 18. Dezember 2001 16:42
Subject: Re: "Using Disk: 0 Partition: 3" problem
On Wed, 12 Dec 2001 23:13:33 -0700
Kjell Wooding <kjell_(_at_)_tash_(_dot_)_pintday_(_dot_)_org> wrote:
> > This problem has been around for a while (at least since ver 2.6). I
> > thought it was peculiar to older machines, but your hardware all
> > fairly new. The machine I had problems with booted fine under Linux
> > FreeBSD, but failed under OBSD. So, the "BIOS compatibility" problem
> > may be unique to OBSD.
> I'm working on this issue right now. If there are any adventurous
> out there who'd like to to some testing for me (and who have
> a machine that experiences this problem when the OpenBSD MBR is
> please send me mail
Fiddling around a bit more I found the following:
This machine has the boot.conf error 20 problem I explained in a
previous post in this thread, some other machines I admin exhibit the
Now, when I compile a new kernel and then mv it into place with:
mv /bsd /bsd.old
mv ./bsd /bsd
it fails to boot. Entering an ls at the boot> prompt either doesn't show
the file or says it's size 0. Either way it fails to boot that kernel.
And now for the twist.
If I compile the same kernel, same options on the same machine but copy
it instead of moving it it works:
cp /bsd /bsd.old
cp ./bsd /bsd
boot> ls now shows the correct size, it boots without any problems.
Any idea why this happens?
Visit your host, monkey.org