07-10-2017
Quote:
Originally Posted by
Corona688
Looks like a botched kernel upgrade. Your modules do not match the kernel you are booting with.
what does it mean the modules do not match the kernel? It was P2V from the physical machine. It should be the same. Any resolution?
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
I'm not sure if this is the right forum to post.
I had following setup before installing SUSE Linux:
Windows 98 installed on Primary partition
Windows XP installed on Extended Partition
When I installed SUSE, it shared space from primary partition and shrunk the size of Windows... (4 Replies)
Discussion started by: patras
4 Replies
2. Solaris
I had installed solaris 10 on 440 on disk 0. I had done ufsrestore on disk1 from tape and then rebooted
Rebooting with command: boot disk1
Boot device: /pci@1f,700000/scsi@2/disk@1,0 File and args:
SunOS Release 5.10 Version Generic_118833-24 64-bit
Copyright 1983-2006 Sun Microsystems,... (3 Replies)
Discussion started by: vr76413
3 Replies
3. OS X (Apple)
Hi friends I am newbiee to MACOS ,the thing is that i installed MAC OS X86 10.5.6 into my VAIO-VGN-CR343N series without any problem and after rebooting I was unable to boot into macos and tried options like -v -f but no progress..can somebody help me (1 Reply)
Discussion started by: srinivas2828
1 Replies
4. Hardware
I have a problem with one of my Sun 280R servers.
I'm unable to boot it. I've managed to get to the {ok} prompt from the RSC card.
Please see output below
ok show-devs
/virtual-memory
/memory
/aliases
/options
/openprom
/chosen
/packages
/openprom/client-services... (2 Replies)
Discussion started by: soliberus
2 Replies
5. Red Hat
Hello,
I have a test PC running Fedora 10. Friday evening it was working fine, I have some perl scripts which are scheduled to run every morning.
But when I started work this morning, I found I cannot ping the machine. When I switched on the monitor, I saw the GRUB promt :(. I am not sure... (10 Replies)
Discussion started by: SivaramaRaju
10 Replies
6. Ubuntu
I am not able to boot into my ubuntu. Grub gives me this message
How do I boot linux? (6 Replies)
Discussion started by: locoroco
6 Replies
7. Solaris
This is what is displayed on the screen as the system tries to boot and then hangs:
0>Test CPU(s)....Done
0>Interrupt Crosscall....|
SC Alert: DHCP negotiation failed, perhaps misconfigured or no DHCP server avail
able
Done
0>Init Memory....|
SC Alert: Host System has Reset
'Done
0>PLL... (2 Replies)
Discussion started by: kenosongo
2 Replies
8. Red Hat
hi guys,
I was using kernel-3.1.2-1 in fedora 16. then updated to kernel-3.1.4-1. after reboot now grub shows command prompt instead of boot menu. i tried to load manually with:
set root=(hd0,msdos3)
linux /vmlinuz-3.1.4-1.fc16.x86_64
initrd /initramfs-3.1.4-1.fc16.x86_64.imgbut in the middle... (0 Replies)
Discussion started by: majid.merkava
0 Replies
9. Solaris
Update:
The / file system (/dev/rdsk/c1t0d0s0) is being checked
fsck unable to stat
WARNING - unable to repair the / filesystem. Run fsck manually (fsck -F ufs /dev/rdsk/c1t0d0s0).
Root password for system maintenance (control-d to bypass):
I am unable to hit control-d to by pass.
I... (50 Replies)
Discussion started by: br1an
50 Replies
10. Ubuntu
Hi;
I had Windows Server 2003 and performed a fresh Ubuntu Server 15 installation.
After installation, Ubuntu server not booting
I guess there is boot problem conflicting with my old Windows Server.
This is my pastebin:
http://paste.ubuntu.com/13851828/
Any help to start my new... (1 Reply)
Discussion started by: gc_sw
1 Replies
LEARN ABOUT NETBSD
rbootd
RBOOTD(8) BSD System Manager's Manual RBOOTD(8)
NAME
rbootd -- HP remote boot server
SYNOPSIS
rbootd [-ad] [-i interface] [config_file]
DESCRIPTION
The rbootd utility services boot requests from Hewlett-Packard workstations over a local area network. All boot files must reside in the
boot file directory; further, if a client supplies path information in its boot request, it will be silently stripped away before processing.
By default, rbootd only responds to requests from machines listed in its configuration file. If the client doesn't supply a file name (HP700
series machines don't), the first one listed for this machine will be supplied.
The options are as follows:
-a Respond to boot requests from any machine. The configuration file is ignored if this option is specified.
-d Run rbootd in debug mode. Packets sent and received are displayed to the terminal.
-i interface
Service boot requests on specified interface. If unspecified, rbootd searches the system interface list for the lowest numbered,
configured ``up'' interface (excluding loopback). Ties are broken by choosing the earliest match.
Specifying config_file on the command line causes rbootd to use a different configuration file from the default.
The configuration file is a text file where each line describes a particular machine. A line must start with a machine's Ethernet address
followed by an optional list of boot file names. An Ethernet address is specified in hexadecimal with each of its six octets separated by a
colon. The boot file names come from the boot file directory. The ethernet address and boot file(s) must be separated by white-space and/or
comma characters. A pound sign causes the remainder of a line to be ignored.
Here is a sample configuration file:
#
# ethernet addr boot file(s) comments
#
08:00:09:0:66:ad SYSHPBSD # snake (4.3BSD)
08:00:09:0:59:5b # vandy (anything)
8::9:1:C6:75 SYSHPBSD,SYSHPUX # jaguar (either)
rbootd logs status and error messages via syslog(3). A startup message is always logged, and in the case of fatal errors (or deadly signals)
a message is logged announcing the server's termination. In general, a non-fatal error is handled by ignoring the event that caused it (e.g.
an invalid Ethernet address in the config file causes that line to be invalidated).
The following signals have the specified effect when sent to the server process using the kill(1) command:
SIGHUP Drop all active connections and reconfigure.
SIGUSR1 Turn on debugging, do nothing if already on.
SIGUSR2 Turn off debugging, do nothing if already off.
FILES
/dev/bpf packet-filter device
/etc/rbootd.conf configuration file
/tmp/rbootd.dbg debug output
/usr/mdec/rbootd directory containing boot files
/var/run/rbootd.pid process id
SEE ALSO
kill(1), socket(2), signal(3), syslog(3)
BUGS
If multiple servers are started on the same interface, each will receive and respond to the same boot packets.
BSD
December 11, 1993 BSD