From owner-freebsd-questions@FreeBSD.ORG Mon Apr 9 13:56:37 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D495516A405 for ; Mon, 9 Apr 2007 13:56:37 +0000 (UTC) (envelope-from derek@computinginnovations.com) Received: from betty.computinginnovations.com (dsl081-227-250.chi1.dsl.speakeasy.net [64.81.227.250]) by mx1.freebsd.org (Postfix) with ESMTP id 545F613C4BA for ; Mon, 9 Apr 2007 13:56:35 +0000 (UTC) (envelope-from derek@computinginnovations.com) Received: from p28.computinginnovations.com (dhcp-10-20-30-100.computinginnovations.com [10.20.30.100]) (authenticated bits=0) by betty.computinginnovations.com (8.13.8/8.12.11) with ESMTP id l39DtsIh069729; Mon, 9 Apr 2007 08:55:55 -0500 (CDT) Message-Id: <6.0.0.22.2.20070409085317.025d9bd0@mail.computinginnovations.com> X-Sender: derek@mail.computinginnovations.com X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22 Date: Mon, 09 Apr 2007 08:55:26 -0500 To: L Goodwin , freebsd-questions@freebsd.org From: Derek Ragona In-Reply-To: <563773.34036.qm@web58106.mail.re3.yahoo.com> References: <563773.34036.qm@web58106.mail.re3.yahoo.com> Mime-Version: 1.0 X-ComputingInnovations-MailScanner-Information: Please contact the ISP for more information X-ComputingInnovations-MailScanner: Found to be clean X-ComputingInnovations-MailScanner-From: derek@computinginnovations.com X-Spam-Status: No Content-Type: text/plain; charset="us-ascii"; format=flowed X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: Boot failure after installation X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Apr 2007 13:56:37 -0000 At 12:56 AM 4/9/2007, L Goodwin wrote: >Hello. I tried posting this issue a few hours ago, but it did not appear >in my inbox, so I'm >trying once more. I've included details of the install in case it matters >(sorry about length). > >I'm having trouble getting FreeBSD 6.2 to boot after installation. After a >"successful" install, >(re-)boot always fails with "DISK BOOT FAILURE, INSERT SYSTEM DISK AND >PRESS ENTER". > >In order to boot the install CD on this machine, I have to disable ACPI by >selecting >"2. Boot FreeBSD with ACPI disabled" from the boot loader menu (the AWARD >BIOS does not allow >for disabling ACPI from the BIOS setup program). >At the end of a "successful" install, the installer asks "ACPI was >disabled during boot. >Would you like to disable it permanently?", to which I choose "Yes". > >I am choosing to perform a "Standard" install. > >Here are my FDISK selections: > >Select Drive(s): "da0" (first SCSI drive of 6 9GB drives) > >These are my selections in FDISK Partition Editor (before entering "Q"): >---------------------------------------------------------------------------------------------- >Disk name: da0 FDISK Partition Editor >DISK Geometry: 1115 cyls/255 heads/63 sectors = 17912475 sectors (8746MB) > >Offset Size(ST) End Name PType Desc Subtype > Flags > >0 63 62 - 12 unused 0 >63 17912412 17912474 da0s1 8 freebsd 165 A >17912475 3765 17916239 - 12 unused 0 >---------------------------------------------------------------------------------------------- > >Install Boot Manager for drive da0?: Selected "BootMgr" (Install the >FreeBSD Boot Manager) >Select Drive(s): "da0" selected for Boot Manager (tab to "OK", press ENTER). > >FreeBSD Disklabel Editor (create BSD Paritions): Select "A" (Auto Defaults)... >---------------------------------------------------------------------------------------------- >Disk: da0 Partition name da0s1 Free: 17912412 blocks (8746MB) > >Part Mount Size Newfs Part Mount Size Newfs >---- ----- ---- ----- ---- ----- ---- ----- >da0s1a / 512MB UFS2 Y >da0s1b swap 486MB SWAP >da0s1d /var 1267MB UFS2+s Y >da0s1e /tmp 512MB UFS2+s Y >da0s1f /usr 5968MB UFS2+s Y >---------------------------------------------------------------------------------------------- >...then enter "Q" (Finish). > >Choose Distributions: Select "A Minimal". >Choose Installation Media: "1 CD/DVD" (burned my own from >FreeBSD-6.2-disk1 ISO image) >"All filesystem information written correctly"... >Distribution extracted successfully... >"Congratulations! You now have FreeBSD installed on your system" (but >can't boot!). >Final Configuration: "No" to most questions (configure later). Yes to these: > Ethernet or SLIP/PPP network devices: fxp0 (Intel EtherExpress > Pro/100B PCI Fast Ethernet card > IPv6 configuration of the interfaces?: No > DHCP: No > Bring up fxp0 interface right now?: Yes Failed (only entered hostname > --will complete later) > Network gateway?: No > inetd?: No > SSH login?: Yes > anonymous FTP?: No > NFS server?: No > NFS client?: No > customize system console settings?: No > machine's time zone?: Yes > CMOS clock set to UTC?: No > Region: "2 America -- North and South" > Country or Region: "45 United States" > Time zone: "19 Pacific Time" ("PDT") > Linux binary compatibility?: No > PS/2 mouse?: Yes (test OK) > "ACPI was disabled during boot. Would you like to diswable it > parmanently?": Yes > Browse FreeBSD package collection?: No > Add initial user accounts?: No > set system manager's password: (done) > Visit general configuration menu one more time?: No > >FreeBSD/i386 6.2-RELEASE - sysinstall Main Menu: Exit Install > >Last thing to print to screen: >--------------------------------------------------------------------------------------------- >Boot from ATAPI CD-ROM : Failure ... >DISK BOOT FAILURE, INSERT SYSTEM DISK AND PRESS ENTER >--------------------------------------------------------------------------------------------- > >The first message is expected, as there is no disk in the CD-ROM drive. >If I set Boot Sequence to "C only" in BIOS setup, only the second message >appears. > >Am I doing something wrong here? Make sure your System BIOS is not set to not allow writing to the boot area, often this is called boot sector virus protection in some BIOS's. Go into your SCSI BIOS and make sure it is set to be bootable and has the correct disk set for booting from. -Derek -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support.