10-07-2008
Usually when I'm building x86 servers using Jumpstart the drives do not have an OS on them, so the phase that boots from disk fails and then tries network, which kicks off the Jumpstart, once built the next reboot boots from disk normally. I do not know of a way to tell the BIOS from Jumpstart to change the boot priority.
Some systems, like the X2200, give the option to hit a key during BIOS load to boot from network for that boot. I use that a lot too.
10 More Discussions You Might Find Interesting
1. Solaris
Hi
I just configured a jumpstart server for x86 and sparc clients. I don't use a dhcp server, so I configured /etc/ethers and did add_install_client to update /etc/bootparams. The sparc installation ist working, but the x86 installation stops after CD1 was successfully installed.
What I did:
I... (2 Replies)
Discussion started by: Jay_Fisi
2 Replies
2. Solaris
I need a little help figuring out why my custom jumpstart network installation is dumping me to a manual install.
I am trying to install Solaris 10 (unattended) over the wire from my jumpstart server to an HP Proliant DL380 server but I'm having difficulties with the unattended part.
So, what... (2 Replies)
Discussion started by: alias.256
2 Replies
3. Solaris
Does anyone know how to Jumpstart a Solaris 10 x86 system without the GUI?
I would like to keep the Jumpstart and/or Flash Archive install in a console text mode if possible but I've not had much luck finding instructions. I'm guessing this is going to be accomplished from the grub menu with a... (5 Replies)
Discussion started by: alias.256
5 Replies
4. Solaris
Can I use a Jumpstart enviroment on x86 to install a sparc64 client?
The idea is to install Solaris in an virtual environment (Sun Virtual Box) running on a pc (AMD), configure a Jumpstart server, and have a SUN Ultra 60 (sparc64) installed via the Jumpstart server.
The SUN has no cdrom... (4 Replies)
Discussion started by: eldiablo
4 Replies
5. Solaris
Hi All,
Is there a possible way to fully automate Solaris x86 jumpstart or make the x86 jumpstart unattended?
I'm currently checking the possible options on how can I do the x86 jumpstart to be kicked off during midnight.
We have an automated jumpstart (start to run from midnight) for... (2 Replies)
Discussion started by: racbern
2 Replies
6. Solaris
Hi friends ,
i have on ultra 10 Sparc machine . Due to some problem my OS is fully corrupted , so i am planning to install again but my problem is the cd drive in Ultra 10 machine is not working.
Now i am planning to use Jumpstart installation method to install my server.
But i... (4 Replies)
Discussion started by: vr_mari
4 Replies
7. Solaris
client boots fine, it gets the ip 192.168.0.10 and the bootfile. Then there is :
SunOS 5.10 Version Generic_141445-09 32-bit"
...
Configuring devices.
Custom JumpStart
Reading ZFS config: done
Setting up Java. Please wait ...
NOTE: Not enough memory for graphical installation. Graphical... (4 Replies)
Discussion started by: TomSu
4 Replies
8. Solaris
I have a jumpstart client that is not requesting the tftp boot file. The rarp function is working, hostname and ip are set ok, but it hangs after that.
tcpdump output:
jumpstart-server:/var/lib/tftpboot# tcpdump -i eth1
tcpdump: verbose output suppressed, use -v or -vv for full protocol... (6 Replies)
Discussion started by: skitch
6 Replies
9. Solaris
I am trying to install Solaris x86 using the Jumpstart server. I run the add_install_client command with appropriate options, and reboot my x86 Target box. The installation starts fine and unattended. After the installation completes and the target goes for a re-boot, it does not boot from the HDD... (9 Replies)
Discussion started by: hemalsid
9 Replies
10. Solaris
Installing Solaris x86 using jumpstart does not set the hostname for the target. Any idea where do we need to specify hostname to be set for jumpstart installation. (1 Reply)
Discussion started by: hemalsid
1 Replies
REBOOT(8) BSD System Manager's Manual REBOOT(8)
NAME
reboot, halt, fastboot, fasthalt -- stopping and restarting the system
SYNOPSIS
halt [-lnpq] [-k kernel]
reboot [-dlnpq] [-k kernel]
fasthalt [-lnpq] [-k kernel]
fastboot [-dlnpq] [-k kernel]
DESCRIPTION
The halt and reboot utilities flush the file system cache to disk, send all running processes a SIGTERM (and subsequently a SIGKILL) and,
respectively, halt or restart the system. The action is logged, including entering a shutdown record into the user accounting database.
The options are as follows:
-d The system is requested to create a crash dump. This option is supported only when rebooting, and it has no effect unless a dump
device has previously been specified with dumpon(8).
-k kernel
Boot the specified kernel on the next system boot. If the kernel boots successfully, the default kernel will be booted on successive
boots, this is a one-shot option. If the boot fails, the system will continue attempting to boot kernel until the boot process is
interrupted and a valid kernel booted. This may change in the future.
-l The halt or reboot is not logged to the system log. This option is intended for applications such as shutdown(8), that call reboot
or halt and log this themselves.
-n The file system cache is not flushed. This option should probably not be used.
-p The system will turn off the power if it can. If the power down action fails, the system will halt or reboot normally, depending on
whether halt or reboot was called.
-q The system is halted or restarted quickly and ungracefully, and only the flushing of the file system cache is performed (if the -n
option is not specified). This option should probably not be used.
The fasthalt and fastboot utilities are nothing more than aliases for the halt and reboot utilities.
Normally, the shutdown(8) utility is used when the system needs to be halted or restarted, giving users advance warning of their impending
doom and cleanly terminating specific programs.
SEE ALSO
getutxent(3), boot(8), dumpon(8), nextboot(8), savecore(8), shutdown(8), sync(8)
HISTORY
A reboot utility appeared in Version 6 AT&T UNIX.
BSD
October 11, 2010 BSD