From owner-freebsd-current@FreeBSD.ORG Fri Dec 17 15:49:44 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4424116A4CF for ; Fri, 17 Dec 2004 15:49:44 +0000 (GMT) Received: from web52806.mail.yahoo.com (web52806.mail.yahoo.com [206.190.39.170]) by mx1.FreeBSD.org (Postfix) with SMTP id A101143D55 for ; Fri, 17 Dec 2004 15:49:43 +0000 (GMT) (envelope-from atkin901@yahoo.com) Received: (qmail 6121 invoked by uid 60001); 17 Dec 2004 15:49:42 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=q8kQ/cRK/1bP9awyhB+i0e7uHCGri6UyZTD4xqohxEo6I58IACnXx6zbly/LCTP47A2rm3f5D933WHaIVaYMjmHu+YJycZbK6VvKOmJGi5C/maVaEG/tauKTjJZoCPwLuSdPEESUqXd7iu7YknMqBH/OjwPDOmxHedBDXNq+BfI= ; Message-ID: <20041217154942.6119.qmail@web52806.mail.yahoo.com> Received: from [205.229.151.150] by web52806.mail.yahoo.com via HTTP; Fri, 17 Dec 2004 07:49:42 PST Date: Fri, 17 Dec 2004 07:49:42 -0800 (PST) From: Mark Atkinson To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: RE: Unable to mount root from SATA drive 12.15.2004 -current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Dec 2004 15:49:44 -0000 Mark Atkinson wrote: >> acd0: CDROM at ata0-master >> UDMA33 >> ad16: 114473MB [232581/16/63] at >> ata8-master SATA150 >> kern_symlink = 0 >> Trying to mount root from ufs:/dev/ad12s1a >> kernel_vmount = 2 >> >> Manual root filesystem specification: >> : Mount using > filesystem >> >> eg. ufs:da0s1a >> ? List valid disk boot devices >> Abort manual input >> >> mountroot> ? >> panic: Root mount failed, startup aborted. >> Uptime: 46s >> Ok, it turns out that the (I believe anyway) the pci-express code, or some other recent change added recently now detects the onboard raid controller on this new mboard, and thus mucked with the device numbers. However, the 'mountroot>' code seems b0rked. Since using 'ufs:/dev/ad16s1a' fails, as well as '?' and 'ufs:ad16s1a'. Only turning off the controller in bios to return the numbering back to ad12 worked. (I didn't try the 'set' method at the boot loader). -- othermark atkin901 at nospam dot yahoo dot com (!wired)?(coffee++):(wired); __________________________________ Do you Yahoo!? Yahoo! Mail - Easier than ever with enhanced search. Learn more. http://info.mail.yahoo.com/mail_250