From owner-freebsd-questions Thu Jan 29 05:24:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA07048 for questions-outgoing; Thu, 29 Jan 1998 05:24:37 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from federation.addy.com (federation.addy.com [207.239.68.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA07043 for ; Thu, 29 Jan 1998 05:24:31 -0800 (PST) (envelope-from fbsdlist@federation.addy.com) Received: from localhost (fbsdlist@localhost) by federation.addy.com (8.8.5/8.6.12) with SMTP id IAA25286 for ; Thu, 29 Jan 1998 08:24:30 -0500 (EST) Date: Thu, 29 Jan 1998 08:24:30 -0500 (EST) From: Cliff Addy To: questions@FreeBSD.ORG Subject: Upgrading motherboard, won't boot Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe questions" 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