From owner-freebsd-questions Sun Oct 25 02:14:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA25531 for freebsd-questions-outgoing; Sun, 25 Oct 1998 02:14:02 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from caboose.zip.com.au (caboose.zip.com.au [203.12.97.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA25509 for ; Sun, 25 Oct 1998 02:13:59 -0800 (PST) (envelope-from davidj@zip.com.au) Received: from david (cartman68.zip.com.au [61.8.20.196]) by caboose.zip.com.au (8.9.1/8.9.1) with SMTP id VAA19074 for ; Sun, 25 Oct 1998 21:13:18 +1100 Reply-To: "David James" From: "David James" To: "Freebsd-Questions@Freebsd.Org" Subject: Primary partition set inactive after freebsd shutdown Date: Sun, 25 Oct 1998 21:16:03 +1100 Message-ID: <000001be0000$78af31a0$c414083d@david> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have two hard IDE disks. The primary master has one partition, which is Win95 (old style FAT), and has the BootEasy boot manager on it. The primary slave has a primary dos, an extended dos, and a FreeBSD partition. Ordinarily, the win95 partition is set active so I can boot from it. However, when I start the computer after using FreeBSD I find that it cannot boot because there are no active partitions. To fix it I have to use a win95 boot disk and FDISK to set it active. The problem does not occur when I start the computer after using win95. (By "start the computer" I mean either reboot or switch it on.) This problem only started after I flash-upgraded my BIOS. My motherboard is ABIT LX6, upgraded from the release version to version DR. After the upgrade I noticed that win95 went weird, but after rebooting a few times for it to re-detect and re-install the plug and play hardware it was fine. FreeBSD didn't have any problems _running_ after the BIOS change, just that it won't reboot properly. There was a post to this mailing list about a month ago describing the same symptoms, except it was immediately after installing FreeBSD that the problem occurred. The problem was diagnosed as a SysCommander (boot manager) problem, but my experience suggests that there's something else gone wrong. (by the way, is there any shorter URL to refer to a mailing list post? :-) Any suggestions on how to fix the problem, or what further information is needed to solve it, are greatly appreciated. Thanks in advance :) David James davidj@zip.com.au (please reply to me as I am not on the list) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message