Diagnosing Boot Issues on V210/V240/V215/V245/V440/V445, T1000/T2000, V480/V490/V880/V890 servers

Asset ID:	1-75-1002932.1
Update Date:	2017-05-23
Keywords:

Solution Type Troubleshooting Sure

Solution 1002932.1 : Diagnosing Boot Issues on V210/V240/V215/V245/V440/V445, T1000/T2000, V480/V490/V880/V890 servers

Applies to:

Sun Fire T2000 Server - Version All Versions and later
Sun Fire V445 Server - Version All Versions and later
Sun Fire V880z Visualization Server - Version All Versions and later
Sun Fire V890 Server - Version All Versions and later
Sun Fire V240 Server - Version All Versions and later
All Platforms

To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in the My Oracle Support Community, SPARC Legacy servers.

Purpose

This article deals with diagnosing issues booting off disk for V210/V240/V215/V245/V440/V445, T1000/T2000, V480/V490/V880/V890 servers.

Troubleshooting Steps

Steps to Follow
Troubleshooting Steps for System boot issues

If the system is unable to boot. You need to determine if it is a disk problem or a controller problem.

Verify autoboot is set to false, and reset the system.

ok printenv auto-boot

auto-boot = true

ok setenv auto-boot False

auto-boot = false

ok reset-all
Verify device is present. Run a probe-scsi-all command make sure the controller is seen and it lists targets. If it lists targets then be sure it lists the drive you are trying to boot off.

ok probe-scsi-all

/pci@1d,700000/scsi@4,1

/pci@1d,700000/scsi@4

Target 0

Unit 0 Disk SEAGATE ST336607LSUN36G 0207

This shows one scsi controller (/pci@1d,700000/scsi@4) and one target (Target 0) off that controller. This is the boot drive. If the target can be seen or multiple targets can be seen off the same path. The controller should be ok.
Verify device alias is correct. Check the boot device to be sure it points to the right drive. See <Document 1004267.1> Verify device alias is correct, for a boot device..
Verify the disk is present. Check and be sure the drive is working. To do this the system needs to be booted off a alternate media. See <Document 1005531.1> Verify Disk is Present When Booting From Alternate Media
At this point, if you have validated that each troubleshooting step above is true for your environment, and the issue still exists, further troubleshooting is required. Gather explorer data (if possible) from the system. Then contact MOS for additional support.

Product
Sun Fire V890 Server
Sun Fire V880z Visualization Server
Sun Fire V880 Server
Sun Fire V490 Server
Sun Fire V480 Server
Sun Fire V440 Server
Sun Fire V240 Server

Sunfire 280r Server

Internal Comments
Audited/updated 11/19/09 - Ian.Macdonald@Sun.COM, Entry Level SPARC Content Team Member

For internal Sun use only.
This document contains normalized content and is managed
by the the Domain Lead(s) of the respective domains. To notify
content owners of a knowledge gap contained in this document,
and/or prior to updating this document, please contact the domain
engineers that are managing this document via the "Document
Feedback" alias(es) listed below:" We participate
as SMEs in this Normalization Project. Could you please confirm the
names for the domain lead and Document feedback alias(es) that are
associated with this normalization project and should be included
in the internal section: Normalization Lead: Jim Robbins Domain
Engineer/Lead : Josh Freeman Document feedback alias :
VSP-SPARC-Normalization@sun.com

Normalized, boot, disk
Previously Published As
91377

Change History
Published using interim normalization rules supplied by the Normalization Program
Date: 2007-12-28
User Name: 31620
Action: Approved
Comment: Published using interim normalization rules supplied by the Normalization Program Team: (circa mid-December 2007)

o Content visibility is appropriate
o External links are in the proper format
o No internal-only links
o Normalized keyword present
o No in-line images
o Consistent use of language and grammar
o No WTS available
o Product metadata seems appropriate
o Summary and Symptoms sections not present, but doc works
o Resolution Path, Steps to follow seem logical and numbered
where appropriate
o Feedback aliases present
o Links only tested to one level down and are in the correct format

References

<NOTE:1004267.1> - Verify device alias is correct, for a boot device.
<NOTE:1005531.1> - Verify Disk is Present When Booting From Alternate Media

Attachments

This solution has no attachment