From owner-freebsd-questions@FreeBSD.ORG Fri Feb 15 21:21:30 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9E2B816A46C for ; Fri, 15 Feb 2008 21:21:30 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 1995813C4D5; Fri, 15 Feb 2008 21:21:29 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <47B60259.6000303@FreeBSD.org> Date: Fri, 15 Feb 2008 22:21:29 +0100 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031) MIME-Version: 1.0 To: Deian Popov References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: freebsd dead after attempt on upgrade from 6.2 to 6.3 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: Fri, 15 Feb 2008 21:21:30 -0000 Deian Popov wrote: > Hello, > > I'm pretty stuck with the death of my bsd machine after attempt on upgrade > from 6.2 to 6.3. Some time ago, I successfully upgraded from 6.1 to > 6.2following the steps in the manual > > 1) cvsup source to specific release > 2) buildworld > 3) buildkernel > 4) installkernel > 5) boot > 6) mergemaster -p > 7) installworld > 8) mergemaster > 9) boot > > Now, after completing steps 1 to 5 the system won't boot and stucks at the > following prompt > > bsd: Trying to mount root from ufs:/dev/ad1s1a > bsd: mountroot> > > the prompt has "?" command which shows available boot devices. The only > device present there is my floppy (fd0) > > I can choose to boot to loader prompt but have no idea how to recorver, and > more interesting, to figure out why that failure occurred? Check the kernel boot messages to see why your ad1 did not get probed. Did the ata driver report an error? Did it attach the drive under a different device number? Kris