10-04-2011
I want to thank you all for your help. Unfortunately, this server was totally reconfigured and I will never know what was causing the problem.
10 More Discussions You Might Find Interesting
1. Solaris
All,
I have a problem with booting up of servers. I am involved in application programming(Perl/Shell), but don't have much hardware knowledge about the Sun Solaris Server's we use.
Our Development Servers are located at a remote place from the Development Centre. Every time there is a Power... (1 Reply)
Discussion started by: rahulrathod
1 Replies
2. Solaris
Hi,
I'm running containers/zones on Solaris 10:
SunOS be2900 5.10 Generic_118833-33 sun4u sparc SUNW,Netra-T12
zoneadm list -vc gives:
ID NAME STATUS PATH
0 global running /
1 bvsmapp01 running /zones/bvsmapp01
2... (3 Replies)
Discussion started by: jabberwocky
3 Replies
3. Solaris
Hey there, I m writing a system managament tool, which for Solaris-land, will have functionality to check currently up zones, compare with those up at the "last good system reference point ", and also find out which zones will be up on a system reboot.
dumpadm list -v gives me the current... (1 Reply)
Discussion started by: shriyer
1 Replies
4. Solaris
I have setup NIS+ server and Client on my server and after I reboot. It is not booting. What may be the problem? (3 Replies)
Discussion started by: mokkan
3 Replies
5. UNIX for Dummies Questions & Answers
Hello Everyone,
First: English is not my native language, sorry.
I was given today on the work of a SUN Enterprse 220r, then I was going to install Debian-sparc, but the server remains in the boot process in a loop of the Fork interpreter depends (begin to load with power-up) starts the... (4 Replies)
Discussion started by: snap
4 Replies
6. Solaris
Hi all,
I am getting boot time message for sun E420R server. I need urgent help.
Hardware Power ON
CPU Offline (not present)
Master CPU : 0000.0001.0055.11a0
CPU Offline (not present)
CPU Offline (not present)
Master E$ : 0000.0000.0040.0000
Button Power ON (0 Replies)
Discussion started by: PUSHPARAJA
0 Replies
7. Solaris
Hi Can any on help me
Zones are not booting showing installed state
---------- Post updated at 01:39 PM ---------- Previous update was at 01:38 PM ----------
ave5ubab
---------- Post updated at 01:44 PM ---------- Previous update was at 01:39 PM ----------
abcdefghijklmnopqrstuv (4 Replies)
Discussion started by: upender
4 Replies
8. Solaris
Hello
I have an old sun fire v250 server that I am trying to revive.
I am trying to boot it from cdrom to install the OS (Solaris 10). The original data in the disk is corrupt and I am trying to do a new clean install. However I encounter the following errors.
Does it look like the disk itself... (1 Reply)
Discussion started by: br1an
1 Replies
9. Solaris
Hi,
anyone please let us know how to write shell script to find the missing mountpoints after server reboot.
i want to take the mountpount information before server reboot, and validate the mountpoints after server reboot if any missing.please let us know the shell script from begining to end as... (24 Replies)
Discussion started by: VenkatReddy786
24 Replies
10. Solaris
Hello,
This is Solaris-10 server, running with 4 non-global zones.
This server was hung today and I had to reboot it forcefully from console. Then root file-system was not clean and I had to run fsck from failsafe mode. After it came back in run-level-3, lot of services are showing in... (3 Replies)
Discussion started by: solaris_1977
3 Replies
LEARN ABOUT NETBSD
kloader
KLOADER(4) BSD Kernel Interfaces Manual KLOADER(4)
NAME
kloader -- in-kernel bootloader
SYNOPSIS
options KLOADER
options KLOADER_KERNEL_PATH=""/netbsd""
DESCRIPTION
The kloader is the in-kernel bootloader for platforms that do not have a proper firmware.
Some platforms supported by NetBSD do not have a firmware that can boot the NetBSD kernel. Examples are game consoles (dreamcast port), and
handhelds (hpcarm, hpcmips, and hpcsh ports). On such platforms the bootloader is usually a host program that runs under the native OS.
This means that rebooting NetBSD is a lengthy process of booting into the native OS first, launching the bootloader program, and finally
booting NetBSD again. This problem is addressed by kloader, which allows the currently running kernel to serve as a bootloader for the ker-
nel being booted, thus avoiding the burden of booting into the native OS first.
When kloader is configured into the kernel, a call to reboot(2) causes the kloader to load the new kernel into memory, and arrange for con-
trol to be passed to the new kernel -- just like a standalone bootloader does. The new kernel then boots in the ordinary manner.
SEE ALSO
reboot(2), boot(8), reboot(8)
HISTORY
kloader first appeared in NetBSD 1.6.
BUGS
kloader ignores howto and bootstr arguments passed to the reboot(2) system call, and reboots the system with the previous boot settings.
kloader doesn't support booting compressed kernels.
The hpcarm port doesn't support kloader yet.
BSD
April 3, 2004 BSD