From owner-freebsd-questions Tue Jan 23 12:43:43 2001 Delivered-To: freebsd-questions@freebsd.org Received: from mail.utexas.edu (wb2-a.mail.utexas.edu [128.83.126.136]) by hub.freebsd.org (Postfix) with SMTP id 8A4E937B402 for ; Tue, 23 Jan 2001 12:43:25 -0800 (PST) Received: (qmail 9916 invoked by uid 0); 23 Jan 2001 20:43:24 -0000 Received: from chepe.cc.utexas.edu (HELO chepe.mail.utexas.edu) (128.83.135.25) by umbs-smtp-2 with SMTP; 23 Jan 2001 20:43:24 -0000 Message-Id: <4.3.2.7.2.20010123143017.00b138b0@mail.utexas.edu> X-Sender: oscars@mail.utexas.edu X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Tue, 23 Jan 2001 14:42:09 -0600 To: questions@freebsd.org From: Oscar Ricardo Silva Subject: Re: Installation of FreeBSD fails on machine with large disks In-Reply-To: <011101c08579$6fc28550$0f10a7d1@phantom> References: <4.3.2.7.2.20010123112121.00b535c0@mail.utexas.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In an answer to a reply: this machine is about 6 months old. The BIOS successfully recognizes the size of the large drives. In the FDISK portion of the install, I had been selecting "A" to use the entire disk and then "N" to accept dangerously dedicated, but that wasn't working. I've been doing some additional reading and apparently, the new boot0 won't work with "dangerously dedicated". This is according to John Baldwin in: So in another attempted install, I still chose "A" to use the entire disk, but this time selected "YES", for a true partition entry, and also set that partition as bootable. In the next section, I was asked to install a Boot Manager for the drive and I selecte "S" to install a Standard MBR (no boot manager). The machine may have three drives, but there will only be one operating system so I don't see a need for a Boot Manager, just the standard MBR. I then created my partitions on ad0 in the following manner: ad0s1a / 2000MB ad0s1b swap 512MB ad0s1e /var 10000MB ad0s1f /usr 20500MB I then selected which Distribution I wanted to install, and I selected "ALL". After this I went through the post-installation configuration and that finished. This time, when I rebooted the machine I get a different message: "Missing Operating System" Not sure what I need to do now. I've followed the different install methods suggested in the mail archives as well as on this list. As before, any information or suggestions would be appreciated. Oscar At 03:16 PM 1/23/01 -0500, Gerald T. Freymann, you wrote: > I think I ran into the same problem not too long ago. When you did the >initial setup... In the FDISK Partition Editor, choose 'A' to use the >entire disk. At the warning, choose 'NO' to accept dangerously dedicated >disk. (We want no MS-DOS partitions here!) Press 'Q' to continue > >I have just updated at least 4 boxes in our company, and one suffered from >the problem you described. After a couple full loads and getting foiled at >the reboot, I finally just selected A for entire disk and voila. > >-Gerry > >--original message >The drives are all 32GB and all on the ATA-33 bus. I have tried installing >FreeBSD 4.1 and 4.2 but each time, when the machine boots after the >install, I get a prompt: > >No /boot/loader > > >>FreeBSD/i386 BOOT >Default: 0:ad(0,a)/kernel >boot: >No /kernel > > >>FreeBSD/i386 BOOT >Default: 0:ad(0,a)/kernel >boot: > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message