Sun Microsystems, Inc.  Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-1007353.1
Update Date:2009-09-24
Keywords:

Solution Type  Problem Resolution Sure

Solution  1007353.1 :   Netra[TM] X1 fails to boot to factory loaded preinstalled Solaris  


Related Items
  • Sun Netra X1 Server
  •  
Related Categories
  • GCS>Sun Microsystems>Servers>Entry-Level Servers
  •  

PreviouslyPublishedAs
210147


Symptoms
Trying to boot a new Netra[TM] X1 system from the pre-installed Solaris
image can cause it to hang or drop to the ok prompt after giving
the ip address during the system identification process.

Resolution
Workaround:
1. Boot the system in single user mode.
OK boot -s
2. Put the entry for the host (ipaddress and hostname) in /etc/hosts file.
e.g: xxx.xxx.xxx.xxx  hostname  loghost
xxx.xxx.xxx.xxx --> ipaddress of the machine
hostname        --> Host name of the machine
3. Make sure that the network cable is plugged into the NET 0 (dmfe0
interface) port.
4. Create a file  /etc/hostname.dmfe0 with the hostname of the machine in it.
5. Put the hostname entry in the /etc/nodename file.
6. Edit the /etc/.sysIDtool.state file to make all the flags set to 1.
e.g: the file should read as follows.
/etc/.sysIDtool.state
1       # System previously configured?
1       # Bootparams succeeded?
1       # System is on a network?
1       # Extended network information gathered?
1       # Autobinder succeeded?
1       # Network has subnets?
1       # root password prompted for?
1       # locale and term prompted for?
1       # security policy in place
sun  -- (depends on the terminal type that you feed in during the system
configuration)
7. init 0
8. Boot the system.
The system should prompt you for security policy and the root password.
9. Configure the system for nameservice (NIS,NIS+ etc) manually, if necessary.


Product
Netra X1 Server

Internal Comments
Please add customers with this issue to bug id 4484985.

Authors: Duraikannu Karunakaran & Karthikeyan Karuppiah.

Previously Published As
27894

Change History
Date: 2003-05-20
User Name: Administrator
Action: Migration from KMSCreator
Comment: updated by : Nita Streit
comment : Mary Grace left doc in locked status. Unlocking doc so I can issue it.
date : Mar 25, 2003



updated by : Nita Streit
comment : Document OK to issue per Mary Grace. There
is no way to actually do tech testing, but she feels
comfortable with issuing doc in current state.
date : Mar 25, 2003



updated by : Mary Grace San Fillippo
comment : Read the doc. spelling is fine and word is understandable.
Seems like a network issue if the customer is going
to manually add the network info.
date : Mar 19, 2003



updated by : Stephen P. Brown
comment : This is a INSTBOOT document, not NETADM.
No way to test this,plus the bug Id:
4484985 list the bug/symptom as unreproducible.

date : Feb 3, 2003



updated by : Thom Chumley
comment : Made public for the supportforum.sun.com/recovery effort
date : Sep 18, 2001



updated by : Alan Pereira
comment : Selected Category and Audience.
date : Aug 1, 2001



updated by : Alan Pereira
comment : Reissuing with selected Category and Audience.
date : Aug 1, 2001



updated by : Alan Pereira
comment : Reviewed against Validation Checklist.
Minor editorial changes.
date : Jul 27, 2001



updated by : Duraikannu Karunakaran
comment : No comment
date : Jul 25, 2001



updated by : Juli Rasmussen
comment : I just changed the wording of the first paragraph.
date : Jul 25, 2001



updated by : Duraikannu Karunakaran
comment : Article created.
date : Jul 24, 2001
Version: 0
Product_uuid
29a39cf6-0a18-11d6-9f37-85b88d95fe76|Netra X1 Server

Attachments
This solution has no attachment
  Copyright © 2011 Sun Microsystems, Inc.  All rights reserved.
 Feedback