From owner-freebsd-questions Mon Apr 20 20:24:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA08487 for freebsd-questions-outgoing; Mon, 20 Apr 1998 20:24:44 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA08399 for ; Tue, 21 Apr 1998 03:24:23 GMT (envelope-from dwhite@gdi.uoregon.edu) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.7/8.8.8) with SMTP id UAA18069; Mon, 20 Apr 1998 20:24:18 -0700 (PDT) (envelope-from dwhite@gdi.uoregon.edu) Date: Mon, 20 Apr 1998 20:24:18 -0700 (PDT) From: Doug White Reply-To: Doug White To: Matt Saunders cc: freebsd-questions@FreeBSD.ORG Subject: Re: Problems overwriting old BSDI disks? In-Reply-To: <19980420211800.29734.qmail@omega.noc.easynet.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 20 Apr 1998, Matt Saunders wrote: > 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... Hm. Odd. > > > 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. :-) We'd have to reproduce to debug against, and I don't think any of us are willing to buy BSDi at this point. (someone got a spare copy and want to hack? :) Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message