From owner-freebsd-current Sun Jan 24 15:58:25 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA09322 for freebsd-current-outgoing; Sun, 24 Jan 1999 15:58:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA09314 for ; Sun, 24 Jan 1999 15:58:20 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id PAA05648; Sun, 24 Jan 1999 15:58:04 -0800 (PST) (envelope-from dillon) Date: Sun, 24 Jan 1999 15:58:04 -0800 (PST) From: Matthew Dillon Message-Id: <199901242358.PAA05648@apollo.backplane.com> To: Chris Knight Cc: current@FreeBSD.ORG Subject: Re: Can't mount root. Really need help... References: <4.1.19990124140032.0098e840@pop2.ghostwheel.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From the boot prompt you should be able to specify the correct root device. Try: boot: /kernel -a The problem is probably the breakage other people have described, with sd0sNa turning into sd0a or da0a or something like that. -Matt Matthew Dillon :Greetings, : : I have learned a very valuable lesson. No matter how many time I have :made world, I shouldn't do it while I'm tired. Last night I synced my tree :and made world. I rebooted, and was going to remake my kernel after the :boot. That became an impossibility. : :After the the message "Waiting 15 seconds fopr SCSI devices to settle", and :before the listing of my SCSI devices is this ominous message: : :ffs_mountroot: can't find rootvperror 6: panic: cannot mount root (2) : :At the end of the SCSI device listing, the system starts a reboot. : :Any help in either understanding what happened or getting the box back :online appreciated! : :-ck To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message