07-02-2009
racbern, I happen to know exactly what you are doing here.
DN2, this is post install, there are some application parameters and sizing questions that have to be answered after the first boot.
You can do exactly the same as on Sparc, the only difference is that you need to update the grub kernel boot like to add "-B console=ttya" to the kernel line, then you get the console on the text based ILOM and you can continue to answering the configuration questions.
The easiest way to get this working is to do the first run using autoexpect and then edit the generated script.
9 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
I am trying to find an approach that has been effective for automating the installation of Solaris 10 x86 using Jumpstart technology. I have configured an Jumpstart server and a Solaris dhcp server with appropriate macros for passing the client information about its boot environment. The problem is... (7 Replies)
Discussion started by: chajo19
7 Replies
5. 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
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 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
9. 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
LEARN ABOUT SUNOS
root_archive
root_archive(1M) root_archive(1M)
NAME
root_archive - manage bootable miniroot archives
SYNOPSIS
/boot/solaris/bin/root_archive pack archive root
/boot/solaris/bin/root_archive unpack archive root
/boot/solaris/bin/root_archive packmedia solaris_image root
/boot/solaris/bin/root_archive unpackmedia solaris_image root
The root_archive utility is used to manage bootable miniroot archives and is currently only available on platforms. The utility can pack
and unpack boot/root archives in both ufs and hsfs (iso9660) format. It will always generate ufs archives.
root_archive also uses the lofi file driver to export a file as a block device (see lofi(7D)) and mount to mount or unmount file systems
and remote resources (see mount(1M)). root_archive requires the same privileges that are needed to run these commands.
SUBCOMMANDS
The root_archive command has the following subcommands:
pack archive root
Pack from the image found under the root directory to the archive.
unpack archive root
Unpack from the archive to an unpacked image under the root directory.
packmedia solaris_image root
Pack the solaris image to the root directory.
unpackmedia solaris_image root
Unpack the solaris image from the root directory.
For packmedia and unpackmedia, other items that do not go into the ramdisk image are copied or uncopied (see cpio(1)) as well. Specifi-
cally, this includes all the packaging databases needed for pkgadd and the other packaging utilities to succeed which are not used in the
running and hence pruned to conserve memory.
EXAMPLES
Example 1: Unpacking the Solaris x86 install image
The following command unpacks the current Solaris image from the root directory:
# root_archive unpackmedia
/export/nv/solarisdvd.nvx_dvd/latest /export/Boot
Where /export/nv/solarisdvd.nvx_dvd/latest represents a path to a Solaris x86 install image and /export/Boot is a directory that will be
purged or created, as necessary.
Example 2: Packing the Solaris x86 install image
The following command packs the current Solaris image to the root directory:
# root_archive packmedia
/export/nv/solarisdvd.nvx_dvd/latest /export/Boot
The following exit values are returned:
0
The command completed successfully.
1
The command exited due to an error.
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
|Interface Stability |Stable |
+-----------------------------+-----------------------------+
cpio(1), bootadm(1M), mount(1M), attributes(5), lofi(7D)
26 Sep 2005 root_archive(1M)