Date: Thu, 8 May 2003 13:43:51 -0700 From: Brooks Davis <brooks@one-eyed-alien.net> To: Tim Kientzle <kientzle@acm.org> Cc: freebsd-stable@freebsd.org Subject: Re: Can't boot from ad4: Device Not Configured? Message-ID: <20030508204351.GA23694@Odin.AC.HMC.Edu> In-Reply-To: <3EBAC016.7020108@acm.org> References: <20030508221553.B89449-100000@voo.doo.net> <3EBAC016.7020108@acm.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--lrZ03NoBR/3+SXJZ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, May 08, 2003 at 01:37:42PM -0700, Tim Kientzle wrote: > b) It doesn't get that far. > (The root hasn't yet been mounted, so the > contents of /dev would seem to be immaterial. > If you can't read the disk, it doesn't really > matter what's on it. ;-) Before root is mounted for real, it is actually mounted. /sbin/init attempts to remount / properly using the device listed in /etc/fstab and will fail to mount it if the entry does not exist in /dev. I ran into this exact problem (ad4 and everything) before when I moved my root disk to a PCI ATA controler. As I recall the two issues I had where a bogus fstab entry and not creating all the necessicary entries to get ad4s1a in /dev. -- Brooks --lrZ03NoBR/3+SXJZ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+usGGXY6L6fI4GtQRAimiAJ4hLDwsGekvWz5V2dDHPNxf57fvXACfSxey CTVzx06PEaXE9dM9Y6eKr3k= =116O -----END PGP SIGNATURE----- --lrZ03NoBR/3+SXJZ--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030508204351.GA23694>