Date: Tue, 06 Sep 2005 19:34:28 -0400 From: "Frederick N. Brier" <fbrier@multideck.com> To: Giorgos Keramidas <keramida@ceid.upatras.gr> Cc: freebsd-questions@freebsd.org Subject: Re: Repairing "kernel not found" Message-ID: <431E2784.3060801@multideck.com> In-Reply-To: <20050906152850.GA28262@orion.daedalusnetworks.priv> References: <431DB202.2070603@multideck.com> <20050906152850.GA28262@orion.daedalusnetworks.priv>
next in thread | previous in thread | raw e-mail | index | archive | help
More info. If I "ls" either before or after setting the bootpath or module_path environment variables, the response is: "open '/' failed: no such file or directory". The "load kernel" command returns: "can't file 'kernel'". Do I need to load a module so that the 3Ware drive "twe" is loaded? The loaddev and currdev variables are both set to "disk1s1a:" Thank you again. Fred. Giorgos Keramidas wrote: >On 2005-09-06 11:13, "Frederick N. Brier" <fbrier@multideck.com> wrote: > > >>Giorgos Keramidas was kind enough to point me at the boot0cfg command >>and I had already tried the disklabel command, but my 5.4 system still >>won't boot. The boot0cfg and disklabel commands executed fine, but it >>is still saying it can't find or load the kernel file despite it being >>in the correct directory on the correct slice. >> >> > >You can interrupt the boot loader and at the OK prompt run "ls" to see >what the loader has mounted as the root partition. Then, assuming that >you locate your kernel in ``/boot/kernel/kernel'', loading a specific >kernel can be done with: > > OK set bootfile=/boot/kernel/kernel > OK set module_path=/boot/kernel > OK load kernel > OK boot > > > > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?431E2784.3060801>