Date: 17 May 2003 06:33:31 -0500 From: Teilhard Knight <teilhk@Phreaker.net> To: FreeBSD <freebsd-questions@freebsd.org> Subject: Re: About my problem Message-ID: <1053171211.14356.7.camel@arlette.love.dad> In-Reply-To: <20030514131341.X6141@Gina.esfm.ipn.mx> References: <1052896702.3300.17.camel@arlette.love.dad> <20030514093825.GB64005@happy-idiot-talk.infracaninophile.co.uk> <1052928350.3342.20.camel@arlette.love.dad> <20030514131341.X6141@Gina.esfm.ipn.mx>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 2003-05-14 at 13:16, Eduardo Viruena Silva wrote: > On Wed, 14 May 2003, Teilhard Knight wrote: > > > On Wed, 2003-05-14 at 04:38, Matthew Seaman wrote: > > > On Wed, May 14, 2003 at 02:18:22AM -0500, Teilhard Knight wrote: > > > > For those who do not know what I am talking about, this is what is > > > > happening to me: > > > > > > > > > > > > I have compiled my kernel. Everything seems to be all right, > > > > except that on boot it cannot mount root. > > > > > > > > It displays: "mounting root from ufs:ad2s2a", and a failure message. > > > > > > > > Now, I am left at boot with an inquire for a manual root filesystem > > > > specification., like this: > > > > > > > > <fstype><device> mount <device> using filesystem <fstype> > > > > > > > > eg. ufs:/dev/da0s1a > > > > > > > > ? List valid disk boot devices > > > > > > > > <empty line> abort manual imput > > > > > > > > mountroot> > > > > > > > > > > > > The HD where FreeBSD is installed is ad2 in my previous kernel and in > > > > this new one it is ad1. I have now found out that this is the source of > > > > the problem. I checked the partition table, and the slices are called > > > > ad2s2a --> ad2s2g. If this is the case, no way I can mount root on a > > > > disk called ad1 with those slices. > > > > > > > > So, I'll pose a different question. Do you know of a possible way I can > > > > make my new kernel to spot my HD as ad2? To me this is the only solution > > > > possible. > > > > > > Hmmm... It's not impossible to recover from the situation you're in > > > without having to do anything unaesthetic, like re-installing. It is, > > > however, fairly tricky and requires use of some quite unfriendly > > > commands. > > > > > > Your aim is simply to edit /etc/fstab and change all references to ad2 > > > over to ad1. Since the fstab is not correct for your current machine, > > > you can't boot to multiuser mode. You can, however, boot to single > > > user mode with the root partition you tell the kernel as above. After > > > power-on, interrupt the 10 second count down, and at the boot loader > > > prompt type: > > > > > > set root_disk_unit=1 > > > boot /kernel -s > > > your system seems to ve 4.x. > your kernel is, somehow, badly created. > > why don't you try the generic kernel that [I hope] must be there > > boot /kernel.GENERIC -s > or > boot /kernel.old -s > > and follow the instruction given by Mattew. This is one of those occasions I'm regretting to be so impatient. Matthew had the right answer soon after I posted I couldn't boot anymore. Instead of installing 5.0, I should have re-installed 4.8 and compiled my kernel the right way now. Well, the end result is that I have another compiled kernel in 5.0 with booting problems, grrr. Teilhard Knight The Extraterrestrial Who ate my sandwich?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1053171211.14356.7.camel>