From owner-freebsd-questions Mon Apr 20 14:18:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA22492 for freebsd-questions-outgoing; Mon, 20 Apr 1998 14:18:41 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from omega.noc.easynet.net (omega.noc.easynet.net [195.40.1.227]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA22320 for ; Mon, 20 Apr 1998 21:18:13 GMT (envelope-from matts@omega.noc.easynet.net) Received: (qmail 29735 invoked by uid 1975); 20 Apr 1998 21:18:00 -0000 Message-ID: <19980420211800.29734.qmail@omega.noc.easynet.net> Date: Mon, 20 Apr 1998 22:18:00 +0100 From: Matt Saunders To: freebsd-questions@FreeBSD.ORG Subject: Re: Problems overwriting old BSDI disks? Mail-Followup-To: freebsd-questions@FreeBSD.ORG References: <19980420134031.21892.qmail@omega.noc.easynet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i (FreeBSD 2.2.6-STABLE i386) In-Reply-To: ; from Doug White on Mon, Apr 20, 1998 at 02:09:37PM -0700 Organization: Easynet Group plc Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Apr 20, Doug White wrote: > On Mon, 20 Apr 1998, Matt Saunders wrote: > > > We've upgraded a number of our machines to FreeBSD 2.2.(5|6) from > > BSDI BSD/OS 3.1. Each and every time we do this (reusing the old BSDI > > hard disk) sysinstall hangs shortly after it runs, at the "probing > > devices" screen. > > Are you sure it's hung and not reprobing the disks several times? It does > this on my laptop -- takes about 45 seconds to a minute to complete. I > don't have old UFS partitions laying around tho. I don't think it's hung - I've left it a good 5-10 minutes to try to sort itself out... > > This is on pretty standard IDE-only hardware. > > > > The only solution seems to be to completely wipe out the old system > > with something like DOS fdisk which works, but is a pain. > > Sort of -- it could be confusing sysinstall because it looks like a UFS > volume but isn't quite. We worked around this by zapping the boot sector of disk with MSDOS fdisk. If it's indicative of something not quite right in sysinstall then maybe someone knows how to fix it. :-) Cheers, Matt. -- M a t t S a u n d e r s Systems Engineer Easynet Group plc http://www.easynet.net/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message