From owner-freebsd-questions Thu Jan 27 4:15: 9 2000 Delivered-To: freebsd-questions@freebsd.org Received: from ms1.meiway.com (ms1.meiway.com [212.73.210.73]) by hub.freebsd.org (Postfix) with ESMTP id 6FECB14E7E for ; Thu, 27 Jan 2000 04:15:04 -0800 (PST) (envelope-from lconrad@Go2France.com) Received: from sv [212.73.210.75] by ms1.meiway.com with ESMTP (SMTPD32-5.05) id A7122AFC0276; Thu, 27 Jan 2000 13:16:18 +0100 Message-Id: <4.2.2.20000127125645.01756100@mail.Go2France.com> X-Sender: lconrad%Go2France.com@mail.Go2France.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Thu, 27 Jan 2000 13:14:28 +0100 To: freebsd-questions@freebsd.org From: Len Conrad Subject: 3.4 .iso images produce "invalid partition table" 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 On an old Pent 120 and now on a new P2-350, we cannot complete a fresh install of 3.4-Rel from the "bare-bones" .iso images. All apparently goes well, no errors, we get to the final "remove diskettes" msg (we assume this means the install procedure sees nothing else to do), and it cold boots. "invalid partition table" (we had chosen "normal" boot option) Both of these machines have been running 3.1R and 3.2R for months without incident. Todays partitioning was simply inherited from the previous install, relabeling the slices as before and opting for Y to newfs on each. So now we have two machines down and we are hurting. Would appreciate any quick suggestions on how to proceed. Thanks, Len To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message