"setrootbyname failed" leads to "ffs_mountroot: can't find rootvp" on boot.
From: Andre Guibert de Bruet (andy_at_siliconlandmark.com)
Date: 04/25/04
- Previous message: Randy Bush: "Re: xterm -C not working"
- Next in thread: Andre Guibert de Bruet: "Re: "setrootbyname failed" leads to "ffs_mountroot: can't find rootvp" on boot."
- Reply: Andre Guibert de Bruet: "Re: "setrootbyname failed" leads to "ffs_mountroot: can't find rootvp" on boot."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sun, 25 Apr 2004 13:50:43 -0400 (EDT) To: current@freebsd.org
Hi,
It's been a while and I guess that's a good thing. I recently tried
updating a CURRENT system from April 4th sources to bleeding edge HEAD
(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.
Any ideas before I start binary searching for the latest bootable kernel?
Andy
> Andre Guibert de Bruet | Enterprise Software Consultant >
> Silicon Landmark, LLC. | http://siliconlandmark.com/ >
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
- TEXT/PLAIN attachment: setrootbyname.boot.problem.txt
- Previous message: Randy Bush: "Re: xterm -C not working"
- Next in thread: Andre Guibert de Bruet: "Re: "setrootbyname failed" leads to "ffs_mountroot: can't find rootvp" on boot."
- Reply: Andre Guibert de Bruet: "Re: "setrootbyname failed" leads to "ffs_mountroot: can't find rootvp" on boot."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|