Jumpstarting a Netra X1

I'm trying to jumpstart a Netra X1 with a Solaris 8 01/01 system. It starts out fine, even getting its ip address, but fails to load the boot image. The error before slipping to the ok prompt is:
Cannot load drivers for /pci@1f,0/ethernet@c
Can't load the root filesystem
I downloaded the patches from http://sunsolve.sun.com/private-cgi/retrieve.pl?doc=salert%2F25969, but I'm still not getting any love. Has anyone else run into this issue with the X1?

did it work. I'm having the same problem here. I used infodoc 26310 Solaris 10/00 with the Netra X1 updates from www.sun.com/netra

Similar Messages

Sol8 Jumpstart problem... client rebooting ??

Hi all,
I'm Jumpstarting a Netra T1AC200 with Sol8 and about 75% in to the finish script, the client reboots unexpectedly. I've changed the order of the finish script, and it's not a specific component of that which is causing the reboot. The Netra's need specific patches in order to be Jumpstarted. It had worked perfectly many times before, then I upgraded to a newer rev. of the patch and now I'm having problems. I also cannot find the original patches on sunsolve anymore. Anyone ever experience this, or have any ideas?
Thanks,
Eric
patches used:
108528-07 (also tried -08)
110383-01
109793-07

Hi - I'm having the same problem except that I'm using the original CD - not a copy. Did you ever firgure out what was causing the following error:
ERROR: Install boot image /cdrom/sol_9_404_sparc/Solaris_9/Tools/Boot does not exist
Check that boot image exists, or use [-t] to
specify a valid boot image elsewhere.

Installation failed when using Jumpstart Server to install SUN Netra T1 200

I have a problem to install a couple of Sun Netra T1 200 Servers with a Jumpstart Server. The Jumpstart Server is set up and I have executed the add_install_client Script. If I boot the Server which should to be installed the server crashes after getting the assigned IP-Address with a software fault.
Attached i will sent the Jumpstart-Client-Output and the config Files of the Jumpstart-Server.
****Netra T1 Server Output, while configured as an Jumpstart client:****
ok boot net -install
Resetti
LOM event: +2h28m47s host reset
ng ...
`
Netra T1 200 (UltraSPARC-IIe 500MHz), No Keyboard
OpenBoot 4.0, 1024 MB memory installed, Serial #16692502.
Ethernet address 8:0:20:fe:b5:16, Host ID: 80feb516.
Executing last command: boot net -install
Boot device: /pci@1f,0/pci@1,1/network@c,1 File and args: -install
Timeout waiting for ARP/RARP packet
Timeout waiting for ARP/RARP packet
Timeout waiting for ARP/RARP packet
Timeout waiting for ARP/RARP packet
2ae00 Warning: boot will not enable cache
Requesting Internet address for 8:0:20:fe:b5:16
Enter filename [kernel/sparcv9/unix]:
Enter default directory for modules [platform/SUNW,UltraAX-i2/kernel /platform/sun4u/kernel /kernel /usr/kernel]:
SunOS Release 5.8 Version Generic_108528-13 64-bit
Copyright 1983-2001 Sun Microsystems, Inc. All rights reserved.
whoami: no domain name
panic[cpu0]/thread=300010a9ba0: Can't invoke , error 2
000002a1000f7a40 genunix:icode+274 (ffbefff0, 0, 300010a7b88, 0, ffbefffc, ffffffffffffffff)
%l0-3: 00000000ffbefffc 0000000000000000 0000000000002000 000002a10000fd20
%l4-7: 0000000000000bb8 0000000010423a00 000000001041b2f8 00000000000007a9
syncing file systems... done
skipping system dump - no dump device configured
rebooting...
Resetti
LOM event: +2h36m51s host reset
ng ...
p
Netra T1 200 (UltraSPARC-IIe 500MHz), No Keyboard
OpenBoot 4.0, 1024 MB memory installed, Serial #16692502.
Ethernet address 8:0:20:fe:b5:16, Host ID: 80feb516.
Executing last command: boot
Boot device: disk File and args:
SunOS Release 5.8 Version Generic_108528-13 64-bit
Copyright 1983-2001 Sun Microsystems, Inc. All rights reserved.
configuring IPv4 interfaces: eri0.
Hostname: infrasrv
The system is coming up. Please wait.
checking ufs filesystems
/dev/rdsk/c1t0d0s4: is stable.
/dev/rdsk/c1t0d0s6: is stable.
Starting IPv4 routing daemon.
starting rpc services: rpcbind done.
Setting netmask of eri0 to 255.255.255.0
Setting default IPv4 interface for multicast: add net 224.0/4: gateway infrasrv
syslog service starting.
Print services started.
Jun 26 04:48:14 infrasrv sendmail[220]: My unqualified host name (infrasrv) unknown; sleeping for retry
volume management starting.
The system is ready.
infrasrv console login: root
Password:
Last login: Thu Jun 26 02:13:59 on console
Jun 26 04:48:24 infrasrv login: ROOT LOGIN /dev/console
Sun Microsystems Inc. SunOS 5.8 Generic Patch October 2001
Sun Microsystems Inc. SunOS 5.8 Generic Patch October 2001
# uname -i
SUNW,UltraAX-i2
# ^[[A
^[[A: not found
# uname -m
sun4u
*****Config Files of the Jumpstart-Server******************
Sysidcfg
bootparams
bash-2.03# more bootparams
infrasrv root=adminws:/cdrom/sol_8_202_sparc/s0/Solaris_8/Tools/Boot install=ad
minws:/export/install boottype=:in sysid_config=adminws:/export/sysidcfg install
_config=adminws:/export/config rootopts=:rsize=32768
bash-2.03#
rules
bash-2.03# more rules
#       @(#)rules 1.12 94/07/27 SMI
# The rules file is a text file used to create the rules.ok file for
# a custom JumpStart installation. The rules file is a lookup table
# consisting of one or more rules that define matches between system
# attributes and profiles.
# This example rules file contains:
#   o syntax of a rule used in the rules file
#   o rule_keyword and rule_value descriptions
#   o rule examples
# See the installation manual for a complete description of the rules file.
# RULE SYNTAX:
# [!]rule_keyword rule_value [&& [!]rule_keyword rule_value]... begin profile fi
# nish
# "[ ]" indicates an optional expression or field
# "..." indicates the preceding expression may be repeated
# "&&" used to "logically AND" rule_keyword and rule_value pairs together
# "!" indicates negation of the following rule_keyword
# rule_keyword a predefined keyword that describes a general system
# attribute. It is used with the rule_value to match a
# system with the same attribute to a profile.
# rule_value a value that provides the specific system attribute
# for the corresponding rule_keyword. A rule_value can
# be text or a range of values (NN-MM).
# To match a range of values, a system's value must be
# greater than or equal to NN and less than or equal to MM.
# begin a file name of an optional Bourne shell script
# that will be executed before the installation begins.
# If no begin script exists, you must enter a minus sign (-)
# in this field.
# profile a file name of a text file used as a template by the
# custom JumpStart installation software that defines how
# to install Solaris on a system.
# finish a file name of an optional Bourne shell script
# that will be executed after the installation completes.
# If no finish script exists, you must enter a minus sign (-)
# in this field.
# Notes:
# 1. You can add comments after the pound sign (#) anywhere on a line.
# 2. Rules are matched in descending order: first rule through the last rule.
# 3. Rules can be continued to a new line by using the backslash (\) before
# the carriage return.
# 4. Don't use the "*" character or other shell wildcards, because the rules
# file is interpreted by a Bourne shell script.
# RULE_KEYWORD AND RULE_VALUE DESCRIPTIONS
# rule_keyword rule_value Type rule_value Description
# any minus sign (-) always matches
# arch text system's architecture type
# domainname text system's domain name
# disksize text range system's disk size
# disk device name (text)
# disk size (MBytes range)
# hostname text system's host name
# installed text text system's installed version of Solaris
# disk device name (text)
# OS release (text)
# karch text system's kernel architecture
# memsize range system's memory size (MBytes range)
# model 'text' system's model number
# network text system's IP address
# totaldisk range system's total disk size (MBytes range)
# RULE EXAMPLES
# The following rule matches only one system:
# hostname sample_host - host_class set_root_pw
# The following rule matches any system that is on the 924.222.43.0 network
# and has the sun4c kernel architecture:
# Note: The backslash (\) is used to continue the rule to a new line.
#network 924.222.43.0 && \
# karch sun4c - net924_sun4c -
# The following rule matches any sparc system with a c0t3d0 disk that is
# between 400 to 600 MBytes and has Solaris 2.1 installed on it:
#arch sparc && \
# disksize c0t3d0 400-600 && \
# installed c0t3d0s0 solaris_2.1 - upgrade -
# The following rule matches all x86 systems:
#arch i386 x86-begin x86-class -
# The following rule matches any system:
#any - - any_machine -
hostname infrasrv - infrasrv_class -
hostname msm_srv1 - msm_srv_class -
hostname msm_srv2 - msm_srv_class -
bash-2.03#
class
bash-2.03# more infrasrv_class
install_type initial_install
system_type standalone
partitioning explicit
filesys c0t0d0s0 2048 /
filesys c0t0d0s1 10
filesys c0t0d0s3 1024 swap
filesys c0t0d0s4 2048 /var
filesys c0t0d0s5 2048 /opt
filesys c0t0d0s6 free /export
cluster SUNWCXall
bash-2.03# more msm_srv_class
install_type initial_install
system_type standalone
partitioning explicit
filesys c0t0d0s0 2048 /
filesys c0t0d0s1 10
filesys c0t0d0s3 1024 swap
filesys c0t0d0s4 2048 /var
filesys c0t0d0s5 free /opt
cluster SUNWCXall
bash-2.03#
ethers
bash-2.03# more ethers
8:00:20:fe:b5:16 infrasrv
bash-2.03#
hosts
bash-2.03# more hosts
# Internet host table
127.0.0.1 localhost
192.168.0.220 adminws loghost
192.168.0.210 infrasrv
192.168.0.200 tc
bash-2.03#
dfstab
bash-2.03# more dfstab
# Place share(1M) commands here for automatic execution
# on entering init state 3.
# Issue the command '/etc/init.d/nfs.server start' to run the NFS
# daemon processes and the share commands, after adding the very
# first entry to this file.
# share [-F fstype] [ -o options] [-d "<text>"] <pathname> [resource]
# .e.g,
# share -F nfs -o rw=engineering -d "home dirs" /export/home2
share -d "jumpstart conf dir" /export/config
share -F nfs -o ro,anon=0 /export/install
share -F nfs -o ro,anon=0 /cdrom/sol_8_202_sparc/s0/Solaris_8/Tools/Boot
bash-2.03#
tftpboot
bash-2.03# pwd
/tftpboot
bash-2.03# ls -al
total 348
drwxrwxr-x 2 root other 512 Jun 26 11:45 .
drwxr-xr-x 24 root root 512 Jun 26 11:45 ..
lrwxrwxrwx 1 root other 26 Jun 26 11:45 C0A800D2 -> inetboot.SUN4U.Solaris_8-1
lrwxrwxrwx 1 root other 26 Jun 26 11:45 C0A800D2.SUN4U -> inetboot.SUN4U.Solaris_8-1
-rwxr-xr-x 1 root other 159416 Jun 26 11:45 inetboot.SUN4U.Solaris_8-1
-rw-r--r-- 1 root other 318 Jun 26 11:45 rm.192.168.0.210
lrwxrwxrwx 1 root other 1 Jun 26 11:45 tftpboot -> .
bash-2.03#

Hi,
It seems to me that you have not created a proper sysidcfg file. From your post, it looks to me like your sysidcfg contains no entries. This is why it prompts you to enter the kernel path. Look on docs.sun.com for a guide to creating the sysidcfg file .

Solaris 10 Network Install on Netra t1.

I'm trying to install Solaris on several Netra machines that I have. None of them have CD-ROMs and none of them have an OS installed. I've been trying to setup an Ultra 80 as an install server per the instructions found in "Solaris 10 Installation Guide: Network-Based Installations" part number: 817-5504. The boot image is on the hard drive, but from there the instructions don't seem to apply to my case. These instructions seem to assume you have running machines that have a hostname and all the network settings configured. I've been looking all over the place to see if there are instructions to setup a hostname/ip config in openboot or in lom, but I haven't seen anything. The installation instructions just tell you to type "boot net - nowin" at the ok prompt, but I don't know if it searches for a DHCP server for IP config or if I have to set it myself. And with no OS installed, I can't just log in and set all these options up in Solaris. Typing "boot net" just returns the message "Timeout waiting for ARP/RARP packet" over and over again.
If I have to setup the Ultra 80 as a DHCP server I'll probably have to have a little instruction on that as well, if anyone knows docs for that. The Netra setup guides also seem to focus more on initial setup with an OS already installed rather than resetting or starting from scratch.

If you have no plans to install Solaris 10 on recent X86 hardware you might try running Solaris 8 or 9 as your install server, configuration for the legacy bootparamd-based Jumpstart is pretty straightforward, well documented and doesn't require DHCP.
The Netra T1s do not use DHCP to obtain boot parameters. I don't even know if the Solaris DHCP server can be configured to emulate legacy Jumpstart raprd/bootparamd. IIRC there was a way but it was not well documented, or maybe one just runs rarpd, rpc.bootparamd, and dhcpd at the same time.

Netra T1 AC200 problems booting into single user

I have a stack of Sun Netra T1 AC200's. I installed them all with Solaris 8 10/01 from my
Jumpstart server. I allready have about a hundred U1,U5 and U10's installed from this server so I know it should work. I have, however not installed any Netra's with it before.
My problem is that I have no problem booting the Netra's after I have installed them, but if you try to
boot into single user with fex. "boot -s" then it would display the usual "Type control-d to proceed with normal startup, or give root password for system maintenance". Problem is that no matter what I type, I don't get a reaction!!
I have everything on console, and I checked that all my connectors are correct and of the type specified in the Netra user manual.
Strange thing is that halting and jumping into the LOM works without problems, same goes for kicking the system down to single user from multiuser...
I've also checked with installing Solaris 8 04/01, but same thing happens there.. I can't have three faulty machines either...
All leads and helpful hints are welcome as I've checked and checked, but can't find anything out of the ordinary...
On beforehand thanks,
Thomas

What does "printenv input-device" show you? My thinking is that maybe LOM might have control at this point. It should probably be "keyboard" or "ttya".
Also check that root's shell is bin/sh in /etc/passwd.

Netra t1 200 & Solaris 10 Device problem

I'm trying to install Solaris 10 from CD on a netra t1 everytime though it gets to creating devices and fails with this error
Customizing system files
- Mount points table (/etc/vfstab)
- Unselected disk mount points (/var/sadm/system/data/vfstab.unselected)
- Network host addresses (/etc/hosts)
- Network host addresses (/etc/hosts)
- Environment variables (/etc/default/init)
Cleaning devices
Customizing system devices
- Physical devices (/devices)
- Logical devices (/dev)
ERROR: Could not install devices (/devices)
ERROR: Could not set up system devices
Could not set up system devices
my system info is.
LOM version: v3.7
LOM checksum: db3a
LOM firmware part# 258-7871-13
Microcontroller: H8/3437S
LOM firmware build Dec 21 2000 10:12:19
Firmware CORE Release 1.0.17 created 2003/10/6 17:9
Release 4.0 Version 17 created 2003/10/06 17:10
cPOST version 1.0.17 created 2003/10/6
CORE 1.0.17 2003/10/06 17:
Is it best to install solaris 8 first then do an upgrade.

Think I've gotten to the bottom of this.
I found this while setting up a jumpstart server on my linux box (Boy do I never want to have to do that again).
http://www.unix.com/showthread.php?s=d2375b8773b38973e8fc741 0f9a000ab&p=68985#post68985
What it pointed out was that the boot cdrom has 2 slices one hsfs and one ufs, I suspect that during the install the netra for some reason has problems with this.

Netra T1 105 Solaris 10

Hi there,
I sucessfully installed Solaris 10 on my Netra T1 105, but when booting from the Jumpstart-Server, I saw that the machine tries to use old informations that seem to be stored on the hostid-chip. So, I wated to ask, if there's a documentation how to erase or modify this information (hostname, ip-addresses...).
Also I wated to know, if anybody has an idea of updating the installed LLOMLite Software?
Thanks for an answers
Thorsten

Well, the SPARC machines only stores one thing; their hostid and ethernet address (ok, thats two things). When you jumpstart a SPARC machine, it makes an ARP request with its ethernet address, and then the jumpstart server responds with a hostname, the client then uses the hostname to find its IP address.
So you probably got an old IP/Hostname on your jumpstart server, if you don't there is probably another server on your network which has old information.
As to LOM; there used to be a patch for it, cant remember which one though.

Solaris 10 jumpstart for V240 fails

Hello there !
i am trying to jumpstart a v240 machine from a jumpstart
server, which contains the media dump (of solaris 10 sparc)
from a CD . But initially the jumpstart is started the pacakges
are installed properly and the patches are also installed properly
(10 recommended patches) . After that the machine reboots for
the first time and throws an error message as mentioned below
Architecture for package SUNWcaRebooting with command: boot
Boot device: /pci@1c,600000/scsi@2/disk@0,0:a File and args:
SunOS Release 5.10 Version Generic_125100-09 64-bit
Copyright 1983-2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
glm: cannot load driver
Cannot load drivers for /pci@1c,600000/scsi@2/disk@0,0:a
Can't load the root filesystem
Type 'go' to resume
{1} ok
I am successfully able to jumpstart v240 machines with solaris 9.
dont know if anything is missing in media.
Pls let me know ur ideas..

Hello All,
I would love to know if someone has a solution to this as I am seeing a similar issue with a slightly different setup.
Solaris 8 and Netra 240. I get the same result with and without patches and finish scripts. After the jumpstart and the failed boot attempt from disk. I can boot from cd, copy the glm driver from the cd to disk, and then everything works as it should. Obviously this is not a solution but only a work around.
Is it something to do with the SCSI hardware architecture used in the *240s?
Edited by: Gareth_Mann on Oct 2, 2007 7:41 PM

Jumpstart of Solaris 10 halts when "Discovering additional network..."

Installing Solaris 10 using jumpstart from Solaris 9 server, using JASS 4.2 (Solaris Security Toolkit 4.2.0)
However, the install just hangs after the following printout:
Discovering additional network configuration...
I tried snoop on the install server, but that does not catch any packets after the stalling.
The machines are connected via a router, but broadcast should be transmitted and installing Solaris 9 was OK.
Client is added in ethers, using NIS.
Any hints?
Gerhard
~> sudo snoop -o nov.cap november
Using device /dev/bge0 (promiscuous mode)
93384
ok boot net - install
Resett
LOM event: +38d+3h18m33s host reset
ing ...
Sun Netra X1 (UltraSPARC-IIe 500MHz), No Keyboard
OpenBoot 4.0, 512 MB memory installed, Serial #51100009.
Ethernet address 0:3:ba:b:b9:69, Host ID: 830bb969.
Executing last command: boot net - install
Boot device: /pci@1f,0/ethernet@c File and args: - install
Timeout waiting for ARP/RARP packet
SunOS Release 5.10 Version Generic 64-bit
Copyright 1983-2005 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
Configuring devices.
Using RPC Bootparams for network configuration information.
Attempting to configure interface dmfe1...
Skipped interface dmfe1
Attempting to configure interface dmfe0...
Configured interface dmfe0
Beginning system identification...
Searching for configuration file(s)...
Using sysid configuration file 10.1.0.51:/opt/SUNWjass/Sysidcfg/Solaris_10/sysidcfg
Search complete.
Discovering additional network configuration...
NFS server app01 not responding still trying
NFS server app01 not responding still trying

The IP subnets are not technically the same (10.1/16 and 10.2/16), but they are handled by the same router.
Normal operation and Solaris9 jumpstart is fine. I got the same problem when I tried jumpstart in the same subnet as the jumpstart server.
The Solaris10 installer is doing something unexpected when detecting setting. Something like checking that address with DHCP is the same as the one gotten initially ( I do not believe this is the problem, this is just in the area where I believe that there is problems).
Any specific hints?

Anyone installs Solaris 10 in a Netra X1 ??

Hi !!
Excuse me for the tiny english,isn't my native languaje, I'm spanish ;-)
I'm trying to install Solaris 10 OS in my Netra X1. This machine doesn't have CD/DVD-ROM device, so I'm trying to install over the network. Also I have a Ultra10 working (with Solaris 10 too), which that's ready with installserver shared by NFS (step by step from documentation). Using 'add_client_install' with Ultra10 MAC address etc all good.
I can boot the setup program from the Netra X1 (I can see it with LOM throught terminal), and I can configure the net, timezone, packages to install etc. Also I can configure the slices in the disk (original IDE disk from Sun that becomes with the machine)
All's fine, but before the install program fails to finish (before the 100% installing packages). The fail consist in some errors than "Can't write /etc/vfstab" and similar.
The Solaris 10 installation always fails in this moment :-(
Well, trying again, reboot the machine (reboot in the middle of Solaris 10's setup program) and the sol10's kernel loads ok, but can't find /sbin/init and other files, so I doesn't boot properly.
Trying to change install server (deleting install server files and rebuilding again), downloading new DVD ISOs from Internet, and
i got the same error. Installing core, OEM or End-user cluster packages got the same error.
Please, help me with this question ... �Thank you very much!

I have successfully installed Solaris 10 on 6 Netra X1 using jumpstart. 5 with single disk and 1 with mirrored disks.
If there is nothing wrong with the target disk or the installation image then I would guess the installer is complaining that the size of one of the slices is too small. You could try installing with just a swap partition and put all the rest in the root partition.

Problem jumpstarting a Solaris 9 SPARC from Solaris 10 x86

Hi all,
I'm going to install a couple of servers using Jumpstart, but I've run
into a problem so I'm kinda in panic.
This is the net boot:
Executing last command: boot net - install
Boot device: /pci@1f,0/pci@1,1/network@c,1 File and args: - install
Timeout waiting for ARP/RARP packet
29200 panic - boot: Could not mount filesystem.
Program terminated
ok
I've setup the jumpstart server on my x86 PC, which is Solaris 10 final
with JET 3.7.3. Since I'm jumpstarting Solaris 9 onto a SPARC machine, I
had to do copy_solaris_media over NFS, since I can't mount the SPARC
ISO-CD1 on my x86. The install server seems to be OK, at least it didn't
complain during setup.
The log entry from sniffing the JS server:
3266 1:15:25.48103 aaa -> xxx WHO C port=33345
3267 1:15:25.48427 aaa -> xxx WHO C port=33345
3268 1:15:25.48636 aaa -> xxx WHO C port=33345
3269 1:15:25.48748 aaa -> xxx SYSLOG C port=32775 BAD.FMT:
3270 1:15:25.49044 aaa -> xxx SYSLOG C port=32775 BAD.FMT:
3271 1:15:25.49283 aaa -> xxx SYSLOG C port=32775 BAD.FMT:
3272 1:15:25.49394 aaa -> xxx PORTMAP R GETPORT port=32775
3273 1:15:25.49541 aaa -> xxx PORTMAP R GETPORT port=32775
3274 1:15:25.49673 aaa -> xxx PORTMAP R GETPORT port=32775
3275 1:15:25.49867 aaa -> xxx PORTMAP R GETPORT port=32775
/etc/bootparams:
xxx root=aaa:/opt/install/media/Solaris_9/Solaris_9/Tools/Boot
install=192.168.4.5:/opt/install/media/Solaris_9 boottype=:in
sysid_config=192.168.4.5:/opt/jet/Clients/xxx
install_config=192.168.4.5:/opt/jet rootopts=:rsize
32768
term=:vt100
Any idea what could be wrong? It stops at 29200, wheres Solaris 10 runs
further up to 38000 something.
Jumpstarting the Solaris 10 onto the same SPARC works perfectly, using
the exact same configuration files.
Thanks

Hi all,
I managed to solve the problem.
This is very weird! can someone explain why this happens?
Output for working Solaris 10 boot:
Executing last command: boot net -v
Boot device: /pci@1f,0/pci@1,1/network@c,1 File and args: -v
38600 Using RARP/BOOTPARAMS...
Internet address is: 192.168.4.6
hostname: xxx
Requesting Ethernet address for: 192.168.4.5
Found 192.168.4.5 @ 0:0:86:1f:f7:92
root server: aaa (192.168.4.5)
root directory: /opt/install/media/Solaris_10/Solaris_10/Tools/Boot
Size: 0x704c8+0x1b8d2+0x2e1ba Bytes
Output for non-working Solaris 9 boot:
Executing last command: boot net -v
Boot device: /pci@1f,0/pci@1,1/network@c,1 File and args: -v
Timeout waiting for ARP/RARP packet
29200 Using RARP/BOOTPARAMS...
Internet address is: 192.168.4.6
hostname: xxx
Found 192.168.4.5 @ 0:0:86:1f:f7:92
root server: aaa (192.168.4.5)
root directory: /opt/install/media/Solaris_9/Solaris_9/Tools/Boot
panic - boot: Could not mount filesystem.
Program terminated
ok
I then replaced /tftpboot/inetboot.SUN4U.Solaris_9-1 with /tftpboot/inetboot.SUN4U.Solaris_10-1 from the Solaris 10 tree, renamed /tftpboot/inetboot.SUN4U.Solaris_10-1 to /tftpboot/inetboot.SUN4U.Solaris_9-1
Voila!
Now works.
inetboot.SUN4U.Solaris_9-1 was not corrupt (must be some internal bootimage bug related to Netra-T1?).
Old bootimage: "inetboot.SUN4U.Solaris_9-1", 152376 bytes, "sum" 3662 and 298.
New bootimage: "inetboot.SUN4U.Solaris_9-1" (Sol 10 image), 214880 bytes, "sum" 53512 and 420.
By the way I was using latest Solaris 9/04, u7

"couldn't set locale correctly" after jumpstart

Hi Guru,
I've encountered the message of
"couldn't set locale correctly" after jumpstart install of solaris 8 in Netra Sun machine.
I found the Java version is 1.2.2,
may I know how can I upgrade to Java 1.4.2?
Kindly advice.
Thank you very much.
Regard,
Goon Fui

Hi,
Looks like the locale is not set correctly.
You may set your environment.
From bash shell
bash# export LC_ALL=C
bash# export LANG=C
for c -shell.
setenv LC_ALL C
setenv LANG C
Hope this helps.
Regards
Pravat
Anytime I restart a server or perform any other
functions in my DSCC console I get errors saying
"couldn't set locale correctly". Everything works
fine but I still get the errors.
When I do a "locale" at the prompt I get the
following:
LANG=
LC_CTYPE="C"
LC_NUMERIC="C"
LC_TIME="C"
LC_COLLATE="C"
LC_MONETARY="C"
LC_MESSAGES="C"
LC_ALL=
Can anyone tell me what I need to do to fix this
problem?
Thanks,
MattIn your m/c fonts may not have set properly

E1000g interface as a jumpstart network card?

I searched but could not find the answer. I've got an Ultra 80 with a Intel Pro-1000 card in one of the PCI slots.
Is there any way to use this card to boot for "boot net"???
Just curious...
Joe C.
PS - My end goal is to use this port to jumpstart the machine using gigabit instead of the default
hme0 card which is 10/100.

Not every device can be detected and used by the OBP. However, I think you might have to try 'watch-net-all' instead of just 'watch-net'.
You might also try 'show-devs'. That will show you a ton of devices. But since you know what slot the card is in, you can look for paths that match it. Use this document to see what the path will be on your machine:
<http://sunsolve.sun.com/handbook_pub/validateUser.do?target=Systems/Example/documents/21216>
or for just your Ultra-80:
Ultra[TM] 80, 420R, Netra[TM] t 1400/1405
PCI Slot 1          /pci@1f,2000/<device>@1,*          33/66mhz-32/64bit-3.3V
PCI Slot 2          /pci@1f,4000/<device>@4,*          33mhz-32/64bit-5V
PCI Slot 3          /pci@1f,4000/<device>@2,*          33mhz-32/64bit-5V
PCI Slot 4          /pci@1f,4000/<device>@5,*          33mhz-32/64bit-5V
If nothing matches that path, then the device isn't seen by the OBP and can't be used for booting.
Darren

Solaris 9 Jumpstart Failure

Greetings.
I am in the process of changing a system over to Solaris 9 (9/04) from Solaris 8 (we cannot move to Solaris 10 due to ClearCase incompatiblities).
We use flash archives in our jumpstart process. The master system is created using a very Spartin profile (SUNWCreq with a number of other required packages). There are also a number of additional tweaks made to the master system to stop unrequired services, deamons, etc. The only additional patches installed are the Java cluster patches.
I have been able to successfully jumpstart the jumpstart server host from CD. However any attempts to jumpstart other clients using the jumpstart server have failed. I suspect that it is related to the inability to copy the sysidcfg file during the jumpstart process.
The address for the jumpstart server is 10.1.1.1; the hostname is n1; the MAC address is 0:3:ba:35:80:88
The address for the jumpstart client is 10.1.1.34; the hostname is n34; the MAC address is 0:3:ba:14:c6.
On the jumpstart server some of the relevant files are included below.
/etc/bootparams:
n34 root=n1:/jumpstart/OS/Solaris_9_2004-09/Solaris_9/Tools/Boot install=n1:/jumpstart/OS/Solaris_9_2004-09 boottype=:in sysid_config=n1:/jumpstart/Sysidcfg install_config=n1:/jumpstart rootopts=:rsize=32768
/etc/hosts:
# Internet host table
127.0.0.1 localhost
10.1.1.1 n1 oam1a loghost
10.1.1.2 n2 db1a
10.1.1.34 n34
/etc/ethers:
0:3:ba:14:c6:cd n34
/etc/dfs/dfstab:
share -F nfs -o ro,anon=0 /jumpstart
share -F nfs -o ro,anon=0 /jumpstart/OS/Solaris_9_2004-0�9
/tftpboot directory:
lrwxrwxrwx 1 root root 26 Aug 8 10:36 0A010122 -> inetboot.SUN4U.Solaris_9-1
lrwxrwxrwx 1 root root 26 Aug 8 10:36 0A010122.SUN4U -> inetboot.SUN4U.Solaris_9-1
-rwxr-xr-x 1 root root 152376 Aug 8 10:36 inetboot.SUN4U.Solaris_9-1
-rw-r--r-- 1 root root 313 Aug 8 10:36 rm.10.1.1.34
ls -l /jumpstart/Sysidcfg/sysidcfg:
-rw-r--r-- 1 root root 375 Aug 4 17:12 /jumpstart/Sysidcfg/sysidcfg
/jumpstart/Sysidcfg/sysidcfg:
system_locale=en_AU
timezone=Australia/NSW
name_service=none
root_password=<removed for this post>
terminal=xterm
network_interface=primary { protocol_ipv6=no netmask=255.255.240.0 default_route
=10.1.0.1 }
timeserver=localhost
timeserver=47.153.235.110
Once the install is started on the client the following output is generated (note the sysidcfg copy failure):
ok boot net - install
Res
LOM event: +21h32m35s host reset
etting ...
�
Netra 120 (UltraSPARC-IIe 648MHz), No Keyboard
OpenBoot 4.0, 1024 MB memory installed, Serial #51693261.
Ethernet address 0:3:ba:14:c6:cd, Host ID: 8314c6cd.
Executing last command: boot net - install
Boot device: /pci@1f,0/pci@1,1/network@c,1 File and args: - install
SunOS Release 5.9 Version Generic_117171-07 64-bit
Copyright 1983-2003 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
whoami: no domain name
Configuring /dev and /devices
Using RPC Bootparams for network configuration information.
Skipping interface eri1
Configured interface eri0
Searching for configuration file(s)...
cp: cannot create /etc/sysidcfg: Permission denied
chmod: WARNING: can't change /etc/sysidcfg
Using sysid configuration file 10.1.1.1:/jumpstart/Sysidcfg/sysidcfg
Search complete.
WARNING: IP: Hardware address '00:03:ba:35:80:88' trying to be our address 010.001.001.001!
WARNING: IP: Hardware address '00:03:ba:35:80:88' trying to be our address 010.001.001.001!
The IP address conflict is with the jumpstart server. The address for the jumpstart server is 10.1.1.1. The warning message is generated for a number of minutes after it starts. I figure that it is caused by the inability to copy the sysidcfg file.
This same system can be installed successfully using a Solaris 8 jumpstart configuration.
Note that the client system is currently installed with Solaris 8.
I did use the command "boot net -v - install" from the OK prompt, but no additional information was provided relating to when the sysidcfg file could not be copied.
If anyone has any ideas about what could be causing this problem or has any information about additional debugging which could be used to figure out this issue, I would greatly appreciate your thoughts.
Thanks in advance.
Cheers,
Jason.

Ideas.. Hmm, none which seems that correct, but you could try some things.
If it gets the wrong IP that could explain why it fails to copy the sysidcfg file.
First you could try and do a snoop on the ethernet address;
snoop ether 0:3:ba:14:c6:cd
(you could also try the -v flag to increase the verbosity).
The things you should look for are arp/rarp requests, the jumpstart client will use arp/rarp to determine its IP address, snoop will show you which server that responds, and what address it gets, futher more its a good idea to verify that the response to the bootparams requests comes from the correct server.
Of course there might be other oddnesses as well.
Was the data you provided extracts? If it was you should check the /etc/ethers and /etc/bootparams for duplicates entries, so there are no other occourances of the clients ehternet address in /etc/ethers, and no bogus entries starting with * or the same hostname in /etc/bootparams.
If you added the client manually you could always try and use the Tools/rm_install_client and Tools/add_install_client scripts to add it again, these script sometimes detect problems with the configuration.
Lastly you didn't show us your /etc/nsswitch.conf file, but i assume that it has "files" first for the ethers, hosts and bootparams entries?
Good luck
//Magnus

How to change the default JET (JumpStart) password

I am using JET (Jumpstart Enterprise Toolkit) to jumpstart my servers. The default password, boajrOmU7GFmY, is saved in a encrypted form in jumpstart.conf. I want to change it, how do I know the encrypted form of my new password?
Tom

Usage: orapwd file=<fname> password=<password> entries=<users>
where
file - name of password file (mand),
password - password for SYS and INTERNAL (mand),
entries - maximum number of distinct DBA and OPERs (opt),
There are no spaces around the equal-to (=) character.

Jumpstarting a Netra X1

Similar Messages

Maybe you are looking for