Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 14 Jul 2000 09:59:27 +0930
From:      Greg Lehey <grog@lemis.com>
To:        John Baldwin <jhb@FreeBSD.ORG>
Cc:        freebsd-questions@FreeBSD.ORG, "Anders Chr. Skoe" <skoe@owlnet.rice.edu>
Subject:   Re: Anyone resolved "Missing operating system" issue?
Message-ID:  <20000714095926.C27141@wantadilla.lemis.com>
In-Reply-To: <XFMail.000713172553.jhb@FreeBSD.org>
References:  <20000712112242.C29642@wantadilla.lemis.com> <XFMail.000713172553.jhb@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday, 13 July 2000 at 17:25:53 -0700, John Baldwin wrote:
>
> On 12-Jul-00 Greg Lehey wrote:
>> On Tuesday, 11 July 2000 at 11:35:58 -0500, Anders Chr. Skoe wrote:
>>> Howdy, folks!
>>>
>>> unfortunately, this email follows a pretty good history of posts regarding
>>> the "Missing operating system" error.  we install 3.2 with no problems on
>>> our western digital WDE4360-1807A3, but it just won't boot.  our bios is
>>> the adaptec AHA 2940 Ultra/Ultra W BIOS v1.23.
>>>
>>> a) if we only create a freebsd partition, and try to boot it, we get the
>>> infamous "Missing operating system" error.
>>>
>>> b) if we create both dos & freebsd partitions, we get to the boot manager,
>>> but selecting freebsd doesn't work.  we've tried putting the freebsd
>>> partition first as well as the dos partition first, but it makes no
>>> difference.  we've also tried various combinations of partition sizes.
>>>
>>> c) setting the drive geometry to 4095/64/32 doesn't help (someone
>>> suggested this in an earlier mail).
>>>
>>> d) using FDISK we've set the active partition to the freebsd
>>> partition.  it doesn't help.
>>>
>>> e) we can boot from the floppy & cdrom drives.
>>>
>>> we would really appreciate some useful feedback 'cause it's drivin' us
>>> crazy.
>>
>> This sounds like a geometry issue.  Have you selected LBA in the BIOS
>> setup?  If so, have you tried both "dangerously dedicated" and
>> Microsoft compatible partitions?
>
> Eek!  Don't use dangerously dedicated on SCSI.  It causes SCSI disks
> to break horribly.

I've never seen any problems using "dangerously dedicated" on SCSI.
I've been doing it all the time for over 8 years.  Care to explain
your claim?

Greg
--
When replying to this message, please copy the original recipients.
For more information, see http://www.lemis.com/questions.html
Finger grog@lemis.com for PGP public key
See complete headers for address and phone numbers


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000714095926.C27141>