Re: Repairing "kernel not found"
What is odd is that the machine booted FreeBSD perfectly at least 5-6 times before I ran into the weird "ps" error and then it would not boot. I still need to figure out what caused the problem in the first place. For the moment, is there a way to reinstall just the core 5.4 kernel distribution files, but not anything else? Is it legitimate to do a recursive copy of all the boot files on the CD, ie: /dist/boot to the twed1s1a slice's /boot directory. Then I do the boot0cfg and disklabel command and then fixes any boot manager config files. Would that work? Fred. Giorgos Keramidas wrote: On 2005-09-06 19:34, "Frederick N. Brier" <[EMAIL PROTECTED]> wrote: 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. Hmmm, isn't it a job of the system BIOS to present a "disk" from the twe controller? Not sure why this would fail; I haven't used twe so far. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Repairing "kernel not found"
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" <[EMAIL PROTECTED]> 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 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Repairing "kernel not found"
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. Please point me to a howto or docs on how to repair an installation without wiping out all the files and packages I have already installed/loaded/configured on this system. Thank you. Frederick N. Brier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Reinstalling the standard boot manager
How do I reinstall just the standard MBR/Boot Manager without effecting anything else or accidentally doing a reinstall? Frederick N. Brier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
How do I diagnose and fix a boot problem?
I had an old FreeBSD 4.8 server and wanted to upgrade it to 5.4. So I backed it up to both DVD and to another 5.4 system. The only change in the hardware was adding a Zonet ZEN3300E gigabit PCI adapter (Realtek RTL8169S-32). It is an old dual 600 P3 with 1GB RAM and a 3Ware 7000-2 controller with 2 160GB drives. I wiped the system and started from scratch with a standard (everything) install. I added the updated packages and got Samba, Apache2, the TWiki installed with all the shared files and twiki files restored. The system was rebooted at least 5-6 times to make sure everything started up properly, and it did great. I was just tweaking the sshd settings so that I could run cygwin XFree86 over ssh, and did a "ps" to get the pid of sshd, and ps came back with an error message. I had never seen this before and so figured perhaps a reboot was in order. So I did and ended up with this:: -- FreeBSD/i386 bootstrap loader, Revision 0.8 Hit [Enter] to boot immediately, or any other key for command prompt. Booting [kernel]... can't load 'kernel' can't load 'kernel.old' Type '?' for a list of commands, 'help' for more detailed help. ok -- So I booted using floppies and a CD (the SCSI CD is not bootable - old Adaptec controller) and loaded the Live CD (disk 1). Going into Fixit mode, I mounted the first slice. Everything was fine no damage. The kernel was there with the same date and size as the version on the Live CD. I read through the Handbook section 12.3. None of the files had a recent timestamp. I thought perhaps the MBR a file had been corrupted. I tried the command "disklabel -B twed0s1" which executed with no errors. When I tried the command "fdisk -B -b /boot/boot0 twed0" It failed saying it could not find /dev/twed0 or if the correct directory was /dev, then twedo could not be found". Yet the device file was in /dev, the values looked reasonable, and df and other file system utilities were returning valid values. I tried rebooting again and looked variable values. Currdev and Loaddev are both "disk1s1a" which I am not sure is correct, but I get an error message if I try to change it to twed0s1a. Not sure what to try next. I don't know what the problem is or what caused the it. Any help or hints as to how to diagnose the problem or fix this would be greatly appreciated. Thank you. Frederick N. Brier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Multiple IP addresses in a Jail
Perhaps there is another way to do this, but I am trying to layout as fault tolerant a network architecture as possible. Most rack mounted boxes come with at least 2 Ethernet ports for what one would assume is to have each go to a separate switch (or to act as a firewall). If either switch goes Tango Uniform, the network is still up. But if my processes are running in Jails and I create an IP alias for each network interface for the jail, I need to specify 2 IP addresses for the Jail, not one. I had heard there was a patch to do this and that it had been added to FreeBSD 5.3. Is this not the case? Is there a patch? Is there another way to do this? Thank you. Frederick N. Brier Multideck Corporation ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: sysinstall in a jail
I do not know whether this is the proper way of doing it, but I mounted the CD using mount -v -t cd9660 /dev/acd0c /usr/jail/myjail/dist Then I went back into the jail'ed environment, started up sysinstall, selected Configure/Media, choosing File System, specifying /dist, then selecting Packages, and it worked. Fred. Frederick N. Brier wrote: I am running into a problem installing packages via sysinstall within a jail using the CD media. I did a minimal install, but added the /usr/src directory. I followed the directions to setup a jail and copied /stand/sysinstall into the jail subdirectory. As per the directions, I then started up the jail and ran sysinstall. But when I attempt to install off of the cdrom media, I get the following error: "Error mounting /dev/acdoc on /dist: Operation not permitted (1)". Now it makes sense that a jail might not be allowed to mount a system device. My confusion is that these were the instructions and I have not seen any posts saying this is a problem. Is there a way to give the jail permission to access the CD device? Should I mount the CD from the host (outside the jail) but to a subdirectory the jail has access to? Such as /usr/jail/myjail/dist? Versus /dist? Thank you for any suggestions. Frederick N. Brier ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
sysinstall in a jail
I am running into a problem installing packages via sysinstall within a jail using the CD media. I did a minimal install, but added the /usr/src directory. I followed the directions to setup a jail and copied /stand/sysinstall into the jail subdirectory. As per the directions, I then started up the jail and ran sysinstall. But when I attempt to install off of the cdrom media, I get the following error: "Error mounting /dev/acdoc on /dist: Operation not permitted (1)". Now it makes sense that a jail might not be allowed to mount a system device. My confusion is that these were the instructions and I have not seen any posts saying this is a problem. Is there a way to give the jail permission to access the CD device? Should I mount the CD from the host (outside the jail) but to a subdirectory the jail has access to? Such as /usr/jail/myjail/dist? Versus /dist? Thank you for any suggestions. Frederick N. Brier ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
