Date: Sun, 25 Apr 2004 14:47:54 -0400 (EDT) From: Andre Guibert de Bruet <andy@siliconlandmark.com> To: current@freebsd.org Subject: Re: "setrootbyname failed" leads to "ffs_mountroot: can't find rootvp" on boot. Message-ID: <20040425143948.B21538@alpha.siliconlandmark.com> In-Reply-To: <20040425133933.P21538@alpha.siliconlandmark.com> References: <20040425133933.P21538@alpha.siliconlandmark.com>
next in thread | previous in thread | raw e-mail | index | archive | help
(I'm replying to myself... I know... :) ) On Sun, 25 Apr 2004, Andre Guibert de Bruet wrote: > (Sources pulled from CVS at Sun Apr 25 16:50:55 UTC 2004, an hour ago). > > I'm getting the following at the bottom of a boot -s -v (I haven't run > installworld yet): > > Mounting root from ufs:/dev/ad4s1a > setrootbyname failed > ffs_mountroot: can't find rootvp > Root mount failed: 6 > > Manual root filesystem specification: > <fstype>:<device> Mount <device> using filesystem <fstype> > eg. ufs:da0s1a > ? List valid disk boot devices > <empty line> Abort manual input > > mountroot> > > I can revert back to the old kernel without any problems, so I don't think > that it's something about my /dev/ad4s1a slice that's causing this. I've > read UPDATING and I don't see anything of particular relevance. The > machine in question is a custom built Dual Athlon MP 2000 running on a > ASUS A7M-266D with all of the peripherals listed in the attached boot -v. I figured I'd give a quick update, so that people aren't running around looking for a problem in a sea of commits. Sources pulled from CVS using -D"2 days ago" boot. I've run installworld and mergemaster and will try to locate the commit that causes the problem once the system comes back up. Andy > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/ >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040425143948.B21538>