Date: Thu, 22 Dec 1994 11:54:30 From: SMMCGEE@ncbc.ncbc.mn.org (Sean McGee) To: questions@freebsd.org Subject: Newbie- Invisible Kernels Message-ID: <m0rKs8o-0002E2C@kksys.skypoint.net>
next in thread | raw e-mail | index | archive | help
system: FreeBSD 1.1 **[2.0 ordered :-)]**
486 dx 8meg
Adaptec 1542CF SCSI controller
1gig Seagate ST31200N
Problem: Main kernel and backup kernel not found.
In my ignorance as a new un*x user, I moved the kernel
to a directory other than the root. I realized my error and
tried to move it back, but my commands were apparently
not understood due to the fact that it couldn't find the kernel.
The sad thing is that I had made a back-up kernel which was
also accidently moved with the main kernel with the use of an
asterick. (386bsd = kernel, 386bsd.backup = backup kernel)
#cd /temp
#mv /386* ./ (After this command, I noticed that my commands
were not recognized from a second machine that
was telnetting in. So I attempted to undo my error
from the console.)
#mv ./386* /
mv: command not found
#ls
ls:comand not found
etc.....
I couldn't do anything, not even a 'halt'. So I rebooted. And, of
course, 386bsd was not found on wd0a. The strange thing is that I
manually mounted sd0a from a boot disk and found both kernels right
were they have always been (apparently 'mv' worked earlier). My next
step was to use a backup disk that boots and copies the kernel to wd0a,
but the message said it was not configured. So I tried copying the
kernel to sd0a. It was successful, yet on reboot 386bsd IS found on
sd0a partition but gets a far as configuring my devices and reboots
itself (after the 'wt0 not found at 0x300' message) - continous loop!!!!.
What do I do now? And what is causing my kernels to be "invisible"?
SEAN MCGEE SMMCGEE@ncbc.ncbc.mn.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m0rKs8o-0002E2C>