From owner-freebsd-questions@FreeBSD.ORG Sat Jan 22 01:14:11 2005 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 9CA5416A4CE for ; Sat, 22 Jan 2005 01:14:11 +0000 (GMT) Received: from mg1.works.net.au (mg1.works.net.au [203.22.251.250]) by mx1.FreeBSD.org (Postfix) with ESMTP id A943643D55 for ; Sat, 22 Jan 2005 01:14:10 +0000 (GMT) (envelope-from markjose@coolcats.net.au) Received: from coolcats.ozdial.net.au (coolcats.ozdial.net.au [203.22.251.39]) by mg1.works.net.au (8.12.11/linuxconf) with ESMTP id j0M1E85r012106 for ; Sat, 22 Jan 2005 12:14:08 +1100 Received: from mafxp (dialup-126.53.194.203.acc03-dryb-mel.comindico.com.au [203.194.53.126])j0M1E2w16745 for ; Sat, 22 Jan 2005 12:14:02 +1100 From: "markjose" To: Date: Sat, 22 Jan 2005 12:14:01 +1100 Message-ID: <001c01c5001f$a8fce7a0$7e35c2cb@mafxp> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2605 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Importance: Normal X-MG1-Works-MailScanner-Information: Please contact the ISP for more information X-MG1-Works-MailScanner: Found to be clean X-MG1-Works-MailScanner-SpamCheck: not spam, SpamAssassin (score=-4.285, required 5, BAYES_00 -4.90, RCVD_IN_NJABL_DUL 0.53, RCVD_IN_SORBS_DUL 0.09) X-MailScanner-From: markjose@coolcats.net.au Subject: "ffs_mountroot: can't find rootvp 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, 22 Jan 2005 01:14:11 -0000 Greetings, I have just built a kernel (after a fresh install of 5.3 CD release), and have encountered this message: Mounting root from ufs:/dev/ad2s1a Setroutbyname failed ffs_mountroot: can't find rootvp Root mount failed: 6 The reason it failed is because now the kernel detects the ata disk (master on the secondary) as ad0 rather than previously ad2 (eg using /stand/sysinstall). Why? Cheers