From owner-freebsd-questions Thu Jan 29 05:31:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA07960 for questions-outgoing; Thu, 29 Jan 1998 05:31:06 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA07948 for ; Thu, 29 Jan 1998 05:30:57 -0800 (PST) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.8.7/8.8.7) with ESMTP id NAA05199; Thu, 29 Jan 1998 13:30:41 GMT (envelope-from kpielorz@tdx.co.uk) Message-ID: <34D08482.3A7580EA@tdx.co.uk> Date: Thu, 29 Jan 1998 13:30:42 +0000 From: Karl Pielorz Organization: TDX X-Mailer: Mozilla 4.04 [en] (WinNT; I) MIME-Version: 1.0 To: Cliff Addy CC: questions@FreeBSD.ORG Subject: Re: Upgrading motherboard, won't boot References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe questions" Did the embedded 2940 see the drive as it came up? Have you tried CTRL-A to configure the SCSI adaptor? - and make sure it's settings are the same as the old SCSI adaptor? My P6SAS board (supermicro) arrived with SCSI booting disabled, and IDE booting enabled, with no IDE drives - I got the same errors as your seeing... :-( Regards, Karl Pielorz Cliff Addy wrote: > > I'm trying to upgrade the motherboard in one of our servers running 2.2.2 > from a SuperMicro+Cyrix166 to a SuperMicro+PPro200. However, when the new > mb went in, it could't boot from the drive, saying "Missing operating > system." > > The drive is a 4gb seagate UW scsi. It was running off of an Adaptec > 2940UW, the new mb has the 2940 integrated. What's strange is that I > stuck in an old, flaky F/W Micropolis drive that had 2.2.1 and it booted > just fine off the new mb. > > Any ideas what could be causing this? I can't imaging kernel config has > anything to do with it, the message seems to imply that the MBR is goofy, > but not goofy enough to keep it from booting off the old mb. > > Cliff