Customizing JumpStart Framework for Installation and Recovery
- Building a Bootable Installation from CD-ROM
- Recovering a Failed System with JumpStart
- Altering the Boot Process
- Adding Utilities and Manual Pages
- Meeting Challenges Unique to the Miniroot
- Summary
Like this article? We recommend
Like this article? We recommend
Like this article? We recommend
The JumpStart system is useful for much more than installing the Solaris OE. This chapter examines the more powerful, yet often overlooked, aspects of the JumpStart system. In several ways, the JumpStart system is like a scripting language, the JumpStart framework provides a toolkit of operators that can be used individually or combined. These operators function well individually, but their true power is realized when they are combined.
NOTE
This chapter provides techniques that can produce configurations that would not be supported by Sun Enterprise Services. However, that lack of support should not detract from the value of the techniques presented.
This chapter examines the boot and installation processes, demonstrating how to adapt these processes for custom system installation and system recovery. This chapter discusses the following topics:
Building and testing a bootable installation CD-ROM
Recovering a failed system with JumpStart
Altering the boot process
Adding utilities and manual pages
Meeting challenges unique to the miniroot
Building a Bootable Installation from CD-ROM
There may be some situations when it is not possible to use a JumpStart server, yet it is necessary to perform an automated (hands-free) installation of the Solaris OE. This section details a procedure to create a bootable installation CD-ROM, which is essentially putting a JumpStart server onto a CD. This CD can then be used to effect a standardized, automated Solaris OE installation from the CD. This technique is especially useful in environments where disk space limitations or networking constraints do not allow for a JumpStart server.
This section examines the structure of a bootable Solaris 8 OE (for a SPARC machine) CD and discusses the appropriate modifications to the default installation scripts that allow a JumpStart installation to be done from CD. Further, this section describes how to create a bootable Solaris 8 OE installation CD for the SPARC platform. Additionally, a Solaris 8 OE system with the CD Read/Write (CDRW) utilities installed is used to write the Solaris 8 OE bootable installation CD. Although several different approaches and software applications are available for writing CDs, this section uses commands available only in the standard Solaris 8 OE to write the bootable installation CD.
The structure of the bootable installation CD can vary with different versions of the Solaris OE, partly because of changes required for the support of additional hardware architectures. Additionally, changes to the Solaris OE from version to version may necessitate changes in the CD or the number of CDs required to install the Solaris OE.
Versions of the Solaris OE can vary structurally, but the concepts and procedures presented here can be adapted or extended to create a bootable installation CD for any of the current versions of the Solaris OE.
Bootable CD Structure
A bootable Solaris OE CD has several components in common with any other hard disk. The boot CD is divided into several partitions (or slices), and a Volume Table Of Contents (VTOC) provides the location and sizes of these slices. In addition to the VTOC, a typical installation CD has six slices. Although the Solaris OE imposes the partitioning of the CD into six slices, it is important to note that the CD is written as one session—this fact is important when the CD is written.
Following is an examination of the VTOC and the six slices of the Solaris 8 OE installation CD.
Volume Table of Contents
The VTOC is located at cylinder 0, sector 0 on the CD. You can examine the VTOC of any disk device with the prtvtoc command. The VTOC of the Solaris 8 OE Software CD (the installation CD) is as follows:
server01# /etc/init.d/volmgt stop
server01# prtvtoc /dev/dsk/c0t6d0s0
* /dev/dsk/c0t6d0s0 partition map
*
* Dimensions:
* 512 bytes/sector
* 640 sectors/track
* 1 tracks/cylinder
* 640 sectors/cylinder
* 2048 cylinders
* 2048 accessible cylinders
*
* Flags:
* 1: unmountable
* 10: read-only
*
* Unallocated space:
* First Sector Last
* Sector Count Sector
* 1301760 2560 1304319
*
* First Sector Last
* Partition Tag Flags Sector Count Sector Mount Directory
0 4 10 0 1128960 1128959
1 2 10 1128960 172800 1301759
2 0 00 1301760 2560 1304319
3 0 00 1304320 2560 1306879
4 0 00 1306880 2560 1309439
5 0 00 1309440 2560 1311999
server01# /etc/init.d/volmgt start
NOTE
You must stop the CD and diskette volume management in order to execute the prtvtoc command on a CD. Restart volume management after executing prtvtoc. All filesystems mounted from the CD will be unmounted and become inaccessible while volume management is stopped.
In contrast to a hard disk, the disk geometry that the Solaris OE uses for a CD provides no distinction between a cylinder and a track. As the prtvtoc output illustrates, the disk label used for a CD defines a cylinder as being composed of one track. Further, the prtvtoc output verifies that each track is defined as having 640 sectors and that one sector is equal to 512 bytes.
Note that the Solaris OE requires that all UFS filesystems align on a cylinder boundary. For a CD, this means that all UFS filesystems on the CD must begin on a sector that is a multiple of 640.
Slices
By reading the VTOC, the Solaris OE sees the CD as having six slices. The contents of those six slices are as follows:
Slice 0 contains the Solaris OE packages to be installed and is the High Sierra File System (HSFS) partition of the CD.
Slice 1 contains the generic kernel and the directory that becomes the system's / (root) directory after boot.
Slice 2 contains the boot block for the sun4c architecture.
Slice 3 contains the boot block for the sun4m architecture.
Slice 4 contains the boot block for the sun4d architecture.
Slice 5 contains the boot block for the sun4u architecture.
Slices 2 through 5 are there only to provide hardware-architecture-specific boot blocks. As new hardware architectures are added and old architectures reach their end-of-life, the uses of these slices may change. The file .slicemapfile in the top-level directory of slice 0 contains the mapping of a slice to the architecture supported.
As noted earlier, slice 0 is on the HSFS partition and all other slices are on the UFS partitions. Slice 0 is also the largest of the slices and can incorporate any unused space on the CD. The procedures detailed in this section augment the installation procedures in slice 0. However, there is a fixed upper limit in available space for slice 0 that limits our modifications. The total space available on a standard CD is 640 Mbytes. The distribution media for Solaris 8 OE supports four architectures. If the bootable installation CD being created needs to support only one architecture, the space (slices) used by the unneeded architectures can be incorporated into slice 0, enlarging slice 0 but losing the ability to boot other architectures from that CD.
It is also interesting to note that, other than the boot block, the only content of slices 2 through 5 is the file .SUNW-boot-redirect in the top-level directory of each of those partitions. This file contains the character 1, which redirects the OpenBoot PROM (OBP) boot loader to load the kernel from partition 1. This mechanism was added with Solaris 2.5 OE as a means of taking advantage of the hardware-independent nature of the kernel to optimize the utilization of space on the CD.
Procedure Overview
Generally, this procedure extracts the contents of slice 0, then splices the desired installation behaviors into the contents of slice 0. The modifications made to slice 0 are to configure the bootable installation CD to partition c0t0d0 as the boot device. The modifications then enable a fully automated installation of the Solaris 8 OE. The profile specifies that a full Solaris OE is installed (the SUNWCall package cluster) with the exception of the Power Management facility.
At a high level, the procedure to create a bootable CD is as follows:
Create and populate a work area.
Modify the installation behaviors of slice 0.
Assemble the individual slices into one CD session and write them to the bootable installation CD.
Test the bootable installation CD.
You can also use this procedure to create a bootable CD without the JumpStart software installation behaviors by omitting step 2.
Procedure Specifics
For this example, server01 is an Ultra Enterprise 420R server running the Solaris 8 OE with the Solaris 8 OE CD creation utilities installed and configured as a JumpStart server. server01 has a CD-ROM writer connected at c3t2d0 (identified as cdrom1 by the cdrw -l command).
Creating and Populating a Work Area
Verify the presence of the Solaris OE CD creation utilities. The Solaris 8 OE installation media is already mounted, and /bicd8 is used as the work area. /bicd8 is a 2-Gbyte UFS filesystem.
Create /bicd8 in the following manner:
server01# pkginfo SUNWmkcd SUNWcdrw system SUNWcdrw CD read and write utility for Solaris system SUNWmkcd CD creation utilities server01# newfs -m 1 /dev/rdsk/c0t1d0s0 newfs: construct a new filesystem /dev/rdsk/c0t1d0s0: (y/n)? y /dev/rdsk/c0t1d0s0: 4194828 sectors in 1452 cylinders of 27 tracks, 107 sectors 2048.3MB in 46 cyl groups (32 c/g, 45.14MB/g, 7488 i/g) super-block backups (for fsck -F ufs -o b=#) at: 32, 92592, 185152, 277712, 370272, 462832, 555392, 647952, 740512, 833072, 925632, 1018192, 1110752, 1203312, 1295872, 1388432, 1480992, 1573552, 1666112, 1758672, 1851232, 1943792, 2036352, 2128912, 2221472, 2314032, 2406592, 2499152, 2591712, 2684272, 2776832, 2869392, 2958368, 3050928, 3143488, 3236048, 3328608, 3421168, 3513728, 3606288, 3698848, 3791408, 3883968, 3976528, 4069088, 4161648, server01# mkdir /bicd8 server01# mount /dev/dsk/c0t1d0s0 /bicd8Populate the work area by extracting the partitions from the Solaris 8 OE software CD.
Since the contents of slice 0 will be manipulated, use cpio to copy out partition 0.
Since no changes are made to the contents of slices 1 through 5, use dd to take those slices off the CD.
Before extracting slices 1 through 5, stop CD and diskette volume management.
NOTE
All filesystems mounted from the CD will be unmounted while volume management is stopped.
server01# cd /cdrom/sol_8_401_sparc/s0 server01# mkdir /bicd8/s0 server01# find . -print |cpio -pudm /bicd8/s0 server01# cd /bicd8 server01# /etc/init.d/volmgt stop server01# for i in 1 2 3 4 5 > do > dd if=/dev/dsk/c0t6d0s${i} of=sol8.s${i} bs=512 > done 172800+0 records in 172800+0 records out 2560+0 records in 2560+0 records out 2560+0 records in 2560+0 records out 2560+0 records in 2560+0 records out 2560+0 records in 2560+0 records outAdditionally, since the slice layout of the bootable installation CD being created will not vary from the slice layout of the Solaris 8 OE Software CD, the VTOC from the Software CD can be used later for the bootable installation CD.
Use dd to take the VTOC from the CD, and at this point, restart volume management.
server01# dd if=/dev/dsk/c0t6d0s0 of=/bicd8/sol8.cdrom.vtoc \ > bs=512 count=1 1+0 records in 1+0 records out server01# /etc/init.d/volmgt start
Several choices are available if the slice layout of the CD being created needs to vary from that of the Software CD (for example, if the VTOC needs to be changed). Use CD creation software—such as the toolkit for building bootable CDs, available from Sun Professional Services, Gear Pro for UNIX, or Young Minds—to generate a correct and valid VTOC. Or create a new VTOC and disk label programmatically by creating and writing the dkl_vtoc and dk_label structures, respectively. See the Solaris system file /usr/include/sys/dklabel.h for more information on these structures.
Modifying Installation Behaviors of Slice 0
Modify the default installation behaviors in slice 0 by deleting the contents of the .install_config directory and adding the desired JumpStart rules and profile to this directory. Note that the parsed rules.ok file (the output from the check script), not the rules file, must be placed in the .install_config directory. If any begin or finish scripts are being used, place them in the .install_config directory as well.
Modify slice 0 as follows.
server01# cd /jumpstart server01# rm /bicd8/s0/.install_config/* server01# cat /jumpstart/Profiles/S8-Server.profile install_type initial_install system_type standalone partitioning explicit root_device c0t0d0s0 # # 1.5GB / and 512MB swap on a 2GB disk # filesys rootdisk.s0 691:2040 / filesys rootdisk.s1 1:690 swap cluster SUNWCall package SUNWpmowm delete package SUNWpmowr delete package SUNWpmowu delete package SUNWpmr delete package SUNWpmu delete package SUNWpmux delete server01# cp /jumpstart/Profiles/S8-server.profile \ > /bicd8/s0/.install_config server01# cat rules any - - S8-server.profile - server01# ./check Validating rules... Validating profile S8-server.profile... The custom JumpStart configuration is ok. server01# cp rules.ok /bicd8/s0/.install_config
The setup of the installation profile directory is controlled by the profind script. You must modify this script to redirect the configuration directory environment variable (${SI_CONFIG_DIR}) used by the JumpStart software to the .install_config directory on the bootable installation CD.
Edit the bicd8/s0/Solaris_8/Tools/Boot/usr/sbin/install.d/profind shell script and replace the cdrom() function with the following function:
cdrom() { # # stub images, indicated by the file /tmp/.preinstall # if [ -f /tmp/.preinstall ]; then mount -o ro -F lofs ${CD_CONFIG_DIR} ${SI_CONFIG_DIR} >/dev/null 2>&1 if [ $? -eq 0 ]; then verify_config "defaults" "CDROM" fi fi gettext " <<< using CD default >>>"; echo # added bicd8 rmdir ${SI_CONFIG_DIR} # added bicd8 ln -s /cdrom/.install_config ${SI_CONFIG_DIR} # added bicd8 exit 0 # added bicd8 }This modification instructs the installation process to use the .install_config directory that was populated with the desired JumpStart software profiles and rules file.
Assembling and Writing Slices to Bootable Installation CD
At this point, the VTOC, the modified slice 0, and the unmodified slices 1 through 5 are written to the bootable installation CD being created. The individual slices are combined into one image to be written to a blank CD.
It is important to keep in mind that slice 0 of the Solaris 8 OE CD is at almost 100 percent utilization of the total available space of slice 0. Further, the Solaris 8 OE product is on two CDs because all of the software package will not fit on one CD. If the modified slice 0 exceeds the size of the original slice 0, you must either create a new VTOC or remove unneeded files from slice 0. Also keep in mind that the iso9660 filesystem has some overhead, which increases the image (created by mkisofs) as well.
Create an automated install CD (without having to swap CDs during the installation), by removing from slice 0 those software packages that will not be installed or are not needed by the installation client.
Additionally, removing unneeded files from slice 0 is much simpler than handcrafting a VTOC. A good place to start removing unneeded files is the Product subdirectory. Rarely does a Solaris OE installation require all the packages from the Product directory. For example, most servers do not (and should not) have the power management packages installed. Removing the power management packages before executing the mkisofs command helps minimize the size of the created iso9660 HSFS image.
Remember that the profile you are using should reflect these changes to the Product directory; that is, don't try to install the removed packages. The removed packages should also be removed from the software package cluster definition file, /bicd8/s0/Solaris_8/Product/.clustertoc.
Before combining and writing the CD, execute the mkisofs command to convert the modified slice 0 in the /bicd8/s0 work area into an HSFS filesystem.
Since no changes to the miniroot or supported architectures are required, extract slices 1 through 5 from the Solaris 8 OE software CD and write them, unchanged, to the bootable installation CD being created.
It is important to note that mkisofs creates a VTOC at offset 0 within this image.
Use dd to remove this invalid VTOC from the HSFS image by skipping the first 512-byte block. For this example, the unneeded power management packages are removed from the Product directory before the iso9660 filesystem is created from /bicd/s0.
server01# cd /bicd8/s0/Solaris_8/Product server01# rm -rf SUNWpmowr/* SUNWpmowu/* SUNWpmr/* SUNWpmux/* server01# cd /bicd8 server01# mkisofs -R -d -L -l -o /bicd8/sol8.S0 /bicd8/s0 . . . Total extents actually written = 282170 Total translation table size: 0 Total rockridge attributes bytes: 4246465 Total directory bytes: 24463360 Path table size(bytes): 175770 Max brk space used 167a000 282170 extents written (551 Mb) server01# dd if=/bicd8/sol8.S0 of=/bicd8/new.sol8.s0 bs=512 skip=1 1128679+0 records in 1128679+0 records out server01# rm /bicd8/sol8.S0
The VTOC specifies a size for slice 0, so slice 0 must be padded to maintain the validity of the VTOC and maintain the correct cylinder boundaries. The size of the pad is computed by adding 1 to the number of sectors in the HSFS slice 0 image (this accounts for the VTOC) then subtracting that sum from the number of sectors (reported by prtvtoc) in the unmodified slice 0 on the CD.
Create the pad by using dd to read the appropriate number of zeros from /dev/zero.
server01# bc 1128960-(1128679+1) 280 server01# dd if=/dev/zero of=pad.s0 bs=512 count=280 280+0 records in 280+0 records out
As with any automated installation, sysidtool needs all installation client identification information such as host name, IP address, time zone, etc. The location of this information depends on whether the installation client is connected to a network or off-network during the installation. If the installation client is connected to a network during installation, this information must be available from a name service such as NIS+ or NIS, or provided from the /etc/bootparams, /etc/ethers, and sysidcfg files from a host on the network. The minimum entries required in the /etc/bootparams file are as follows:
server01# cat /etc/bootparams client06 sysid_config=server01:/jumpstart/Sysidcfg/Solaris_8
The sysidcfg file specified by /etc/bootparams contains the following:
server01# cat /jumpstart/Sysidcfg/Solaris_8/sysidcfg system_locale=en_US timezone=US/Pacific network_interface=primary {netmask=255.255.255.0 protocol_ipv6=no} terminal=vt100 security_policy=NONE root_password=Q7jsh1m6IztTU name_service=NONE timeserver=localhostTo perform an automated installation without network connectivity, you must have placed a sysidcfg file in the /etc directory of the filesystem image taken from slice 1 of the Solaris 8 OE CD.
Mount the filesystem image file by using the Solaris 8 OE loopback file driver administration commands.
After mounting the filesystem image, use standard Solaris OE commands to remove the symbolic link for the default sysidcfg file and to copy a complete sysidcfg file to the filesystem image.
server01# cat /bicd8/sysidcfg system_locale=en_US timezone=US/Pacific network_interface=primary {hostname=client06 ip_address=10.1.1.9 netmask=255.255.255.0 protocol_ipv6=no} terminal=vt100 security_policy=NONE root_password=Q7jsh1m6IztTU name_service=NONE timeserver=localhost server01# lofiadm -a /bicd8/sol8.s1 /dev/lofi/1 server01# mount /dev/lofi/1 /mnt server01# ls -al /mnt/etc/sysidcfg lrwxrwxrwx 1 root other 24 Nov 28 16:38 /mnt/etc/sysidcfg -> ../tmp/root/etc/sysidcfg server01# rm /mnt/etc/sysidcfg server01# cp /bicd8/sysidcfg /mnt/etc/sysidcfg server01# umount /mnt server01# lofiadm -d /dev/lofi/1NOTE
For the off-network automated installation, the host name, IP address, netmask, and IPv6 specification must be in the sysidcfg file.
See Chapter 11, "System Cloning," for a fully automated technique for a JumpStart software installation with no network connectivity, using the WebStart Flash extensions.
Concatenate the VTOC, HSFS image, padding, and unmodified images of slices 1 through 5 into one image and write it to the CD writer on device c3t2d0 with the cdrw command:
server01# cat sol8.cdrom.vtoc new.sol8.s0 pad.s0 \ sol8.s1 sol8.s2 sol8.s3 sol8.s4 sol8.s5 >bicd8.image server01# cdrw -d cdrom1 -i bicd8.image Initializing device...done. Writing track 1...done. done. Finalizing (Can take up to 4 minutes)...done.
Testing the Bootable Installation CD
To validate the newly created bootable installation CD, place it in the CD drive of the installation client, client06. For this example, the client is off-network while the installation occurs and the sysidcfg file in the /etc directory of slice 1 of the CD was modified, as shown in step 3 of "Procedure Specifics" on page 5. After the OBP boot cdrom command is issued, client06 boots from the CD and performs an automated installation of the Solaris 8 OE.
Issue the boot cdrom command with the - install options to initiate the automated installation:
screen not found.
{0} ok boot cdrom - install
Boot device: /pci@1f,4000/scsi@3/disk@6,0:f File and args: - install
SunOS Release 5.8 Version Generic_108528-05 64-bit
Copyright 1983-2000 Sun Microsystems, Inc. All rights reserved.
Configuring /dev and /devices
Using RPC Bootparams for network configuration information.
SUNW,hme0 : No response from Ethernet network : Link down -- cable problem?
Skipping interface hme0
SUNW,hme0 : No response from Ethernet network : Link down -- cable problem?
The system is coming up. Please wait.
SUNW,hme0 : No response from Ethernet network : Link down -- cable problem?
Starting remote procedure call (RPC) services: sysidns done.
Starting Solaris installation program...
Searching for JumpStart directory...
SUNW,hme0 : No response from Ethernet network : Link down -- cable problem?
<<< using CD default >>>
Checking rules.ok file...
Using profile: S8-server.profile
Executing JumpStart preinstall phase...
Searching for SolStart directory...
Checking rules.ok file...
Using begin script: install_begin
Using finish script: patch_finish
Executing SolStart preinstall phase...
Executing begin script "install_begin"...
Begin script install_begin execution completed.
Processing default locales
- Specifying default locale (en_US)
Processing profile
- Selecting cluster (SUNWCall)
- Deselecting package (SUNWpmowm)
- Deselecting package (SUNWpmowr)
- Deselecting package (SUNWpmowu)
- Deselecting package (SUNWpmr)
- Deselecting package (SUNWpmu)
- Deselecting package (SUNWpmux)
- Selecting locale (en_US)
Installing 64 bit Solaris packages
- Selecting all disks
- Configuring boot device
- Using disk (c0t0d0) for "rootdisk"
- Configuring / (c0t0d0s0)
- Configuring swap (c0t0d0s1)
- Deselecting unmodified disk (c0t1d0)
- Deselecting unmodified disk (c1t8d0)
- Deselecting unmodified disk (c1t9d0)
- Deselecting unmodified disk (c1t10d0)
- Deselecting unmodified disk (c1t11d0)
- Deselecting unmodified disk (c1t12d0)
- Deselecting unmodified disk (c1t13d0)
- Deselecting unmodified disk (c2t0d0)
- Deselecting unmodified disk (c2t1d0)
- Deselecting unmodified disk (c2t2d0)
- Deselecting unmodified disk (c2t3d0)
- Deselecting unmodified disk (c2t4d0)
- Deselecting unmodified disk (c2t5d0)
Verifying disk configuration
- WARNING: Unused disk space (c0t0d0)
- WARNING: Changing the system's default boot device in the EEPROM
Verifying space allocation
- Total software size: 737.00 Mbytes
Preparing system for Solaris install
Configuring disk (c0t0d0)
- Creating Solaris disk label (VTOC)
Creating and checking UFS filesystems
- Creating / (c0t0d0s0)
Beginning Solaris software installation
Starting software installation
SUNWxwrtx...done. 736.96 Mbytes remaining.
SUNWxwrtl...done. 736.91 Mbytes remaining.
SUNWwbapi...done. 736.40 Mbytes remaining.
.
. (package listing deleted for brevity)
.
SUNWnamos...done. 257.17 Mbytes remaining.
SUNWnamow...done. 257.09 Mbytes remaining.
SUNWnamox...done. 256.90 Mbytes remaining.
Completed software installation
Customizing system files
- Mount points table (/etc/vfstab)
- Unselected disk mount points (/var/sadm/system/data/vfstab.unselected)
- Network host addresses (/etc/hosts)
Customizing system devices
- Physical devices (/devices)
- Logical devices (/dev)
Installing boot information
- Installing boot blocks (c0t0d0s0)
- Updating system firmware for automatic rebooting
Installation log location
- /a/var/sadm/system/logs/install_log (before reboot)
- /var/sadm/system/logs/install_log (after reboot)
Installation complete
Executing SolStart postinstall phase...
Executing finish script "patch_finish"...
Finish script patch_finish execution completed.
Executing JumpStart postinstall phase...
The begin script log 'begin.log'
is located in /var/sadm/system/logs after reboot.
The finish script log 'finish.log'
is located in /var/sadm/system/logs after reboot.
syncing filesystems... done
rebooting...
Resetting ...
screen not found.
Can't open input device.
Keyboard not present. Using ttya for input and output.
Sun Ultra 60 UPA/PCI (2 X UltraSPARC-II 450MHz), No Keyboard
OpenBoot 3.27, 2048 MB memory installed, Serial #13100146.
Ethernet address 8:0:20:c8:ff:fa, Host ID: 80c8fffa.
Initializing Memory
Rebooting with command: boot
Boot device: disk:a File and args:
SunOS Release 5.8 Version Generic_108528-05 64-bit
Copyright 1983-2000 Sun Microsystems, Inc. All rights reserved.
configuring IPv4 interfaces: hme0.
Hostname: client06
Configuring /dev and /devices
Configuring the /dev directory (compatibility devices)
The system is coming up. Please wait.
Configuring network interface addresses: hme0
SUNW,hme0 : No response from Ethernet network : Link down -- cable problem?
SUNW,hme0 : No response from Ethernet network : Link down -- cable problem?
.
SUNW,hme0 : No response from Ethernet network : Link down -- cable problem?
SUNW,hme0 : No response from Ethernet network : Link down -- cable problem?
RPC: Timed out
SUNW,hme0 : No response from Ethernet network : Link down -- cable problem?
SUNW,hme0 : No response from Ethernet network : Link down -- cable problem?
Starting IPv4 routing daemon.
starting rpc services: rpcbind done.
System identification is completed.
Setting netmask of hme0 to 255.255.255.0
SUNW,hme0 : No response from Ethernet network : Link down -- cable problem?
Setting default IPv4 interface for multicast:
add net 224.0/4: gateway client06
syslog service starting.
Print services started.
volume management starting.
The system is ready.
client06 console login:
NOTE
The repeated warnings about the lack of network response and the RPC time-out error during the postinstallation boot are due to the installation client being disconnected from the network.