From owner-freebsd-questions@FreeBSD.ORG Sat Jan 10 15:12:50 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 20CFF16A4CE for ; Sat, 10 Jan 2004 15:12:50 -0800 (PST) Received: from redix.it (host49-169.pool8172.interbusiness.it [81.72.169.49]) by mx1.FreeBSD.org (Postfix) with SMTP id 3B1F143D39 for ; Sat, 10 Jan 2004 15:12:43 -0800 (PST) (envelope-from roberto@redix.it) Received: (qmail 27251 invoked by uid 72); 10 Jan 2004 23:12:41 -0000 Received: from 151.30.78.110 (SquirrelMail authenticated user roberto) by mail.redix.it with HTTP; Sun, 11 Jan 2004 00:12:41 +0100 (CET) Message-ID: <1095.151.30.78.110.1073776361.squirrel@mail.redix.it> Date: Sun, 11 Jan 2004 00:12:41 +0100 (CET) From: roberto@redix.it To: Alexander.Farber@t-online.de User-Agent: SquirrelMail/1.4.2 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 Importance: Normal cc: freebsd-questions@freebsd.org Subject: Re: Swapped disks and now stuck in the mountroot> prompt X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Jan 2004 23:12:50 -0000 I run into the same problem: I've installed FreeBSD 4.9 on a ide0:0 (primary IDE, master hd) then ported the hard disk on a second PC and installed as ide1:0 (secondary IDE, master hd). When booting the kernel start probing devices but halts when it try to mount the root file system with the following message: mount root from ufs:/dev/ad0s1a root mount failed: 6 At the prompt I've tried with ufs:/dev/ad2s1a but it does not work. The problem is that the kernel (in some way that I do not know) is instructed to load /dev/ad0s1a as root file system (yes at this stage the config file /etc/fstab is not involved yet, becouse it is no available until the root file system will be mounted). The solution is to instruct the kernel with the right device: ad2s1a seems to be wrong... I'm working on it... Bye Roberto