How to identify a missing device(s) on V210/V240/V214/V245/V440/V445, T1000/T2000, V480/V490/V880/V890 servers

Asset ID:	1-71-1013117.1
Update Date:	2011-12-27
Keywords:

Solution Type Technical Instruction Sure

Solution 1013117.1 : How to identify a missing device(s) on V210/V240/V214/V245/V440/V445, T1000/T2000, V480/V490/V880/V890 servers

Applies to:

Sun Fire V445 Server
Sun Fire V490 Server
Sun Fire V880 Server
Sun Fire V890 Server
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, Entry-Level Servers.

Goal

This document describes some procedures to identify and diagnose a missing disk drive or controller on How to identify a missing device(s) on V210/V240/V214/V245/V440/V445, Tx000, V480/V490/V880/V890 servers.

Solution

Steps to Follow
Steps to follow

To verify that the device is present, the user can run the command probe-scsi-all. This is an OBP level command, so first you will need to make sure that the system is able to get to the ok prompt. For proper command usage refer to Document 1005013.1. Before using this procedure verify the auto-boot parameter is set to false :

{0} ok printenv auto-boot
auto-boot = false
{0} ok reset-all
{0} ok probe-scsi-all

Note: the OBP command probe-scsi or probe-scsi-all must be followed by the reset-all command before re-booting, otherwise, a subsequent "boot" may hang the system.

Refer to Document 1005013.1 for details.

At the OS level check that the device is present and mounted by using the format utility. The devices reported in format output should match the devices reported in probe-scsi-all. Here is an example for the Sun Fire[TM] V880/V890:

# format
AVAILABLE DISK SELECTIONS:
0. c1t0d0   /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e0177e1bd1,0
1. c1t1d0   /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e017814ad1,0
2. c1t2d0   /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e0177d8d21,0
3. c1t3d0   /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e0177cb291,0
4. c1t4d0   /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w2100001862f43f21,0
5. c1t5d0   /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e017ab3861,0

{7} ok probe-scsi-all
/pci@8,600000/SUNW,qlc@2
LiD HA LUN --- Port WWN --- ----- Disk description -----
0 0 0 500000e0177e1bd1 FUJITSU MAX3147FCSUN146G1103
1 1 0 500000e017814ad1 FUJITSU MAX3147FCSUN146G1103
2 2 0 500000e0177d8d21 FUJITSU MAX3147FCSUN146G1103
6 6 0 5080020000254339 SUNW SUNWGS INT FCBPL922A
3 3 0 500000e0177cb291 FUJITSU MAX3147FCSUN146G1103
4 4 0 2100001862f43f21 SEAGATE ST314655FSUN146G0691
5 5 0 500000e017ab3861 FUJITSU MAX3147FCSUN146G1103

In this example the line with SUNW is for the internal controller. If the drives reported in probe-scsi-all do not show in format at OS level, one of the reasons could be that the drivers for these devices are not bundled in Solaris[TM] and need to be installed separately. For more details in cases like these, you may refer to Document 1004782.1.

In some cases a device may not be present due to the following error:

1. c1t1d0 /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e011bfca91,0

If the user has not started to format a disk drive, and sees the <drive not available: formatting> message in the format output, then it is possible that the reported disk drive is faulty. Refer to Document 1005475.1 for details.

In systems with hardware RAID functionality (Sun Fire[TM] V440/V445, V215/V245, T1000/T2000), the internal drives are managed by the raidctl utility, so it will report both the present drives, as well as the missing drives:

RAID    Volume   RAID        RAID       Disk
Volume Type     Status      Disk       Status
-----------------------------------------------
c1t0d0 IM       DEGRADED    c1t0d0     OK
                             c1t1d0     MISSING

Note: In systems supporting hardware RAID with the internal drives (V440/V445, V215/V245, T1000/T2000) the devices could be missing due to a configured RAID volume. The drives that are members of a RAID volume do no longer appear in the probe-scsi-all, iostat -e and format

output, and only the volume is displayed. Here is an example for T2000 with 4 drives (two of them are members of volume c0t2d0):

AVAILABLE DISK SELECTIONS:

0. c0t0d0 /pci@780/pci@0/pci@9/scsi@0/sd@0,0
1. c0t1d0 /pci@780/pci@0/pci@9/scsi@0/sd@1,0
2. c0t2d0 /pci@780/pci@0/pci@9/scsi@0/sd@2,0

When multiple devices (drives, etc.) are missing or having problem on the same device path, the suspected component will be the controller for that path. This could also be an I2C bus problem - the i2c bus is the path to the disk backplane that OBP or Solaris[TM] use to find and communicate with the devices on the backplane. Use the OBP command show-devs to verify if multiple devices are missing or having problems on the same device path. Here is an example for Sun Fire[TM] V880/V890:

ERROR: Couldn't read value from FCAL Disk Backplane 0 !
ERROR: Can't set internal FCAL Disk Backplane selectable ID's!
ERROR: Can't open Disk Backplane 0 FRUPROM
{3} ok
ERROR: Can't access LM75 device!

In case of such errors you will likely be missing many (but not necessarily all) of the following devices from the device tree in the output of show-devs:

/pci@9,700000/ebus@1/i2c@1,30/fru@0,ae
/pci@9,700000/ebus@1/i2c@1,30/fru@0,ac
/pci@9,700000/ebus@1/i2c@1,30/fru@0,a8
/pci@9,700000/ebus@1/i2c@1,30/temperature-sensor@0,9c
/pci@9,700000/ebus@1/i2c@1,30/ioexp@0,8a
/pci@9,700000/ebus@1/i2c@1,30/ioexp@0,88
/pci@9,700000/ebus@1/i2c@1,30/controller@0,58
/pci@9,700000/ebus@1/i2c@1,30/controller@0,1c
/pci@9,700000/ebus@1/i2c@1,30/controller@0,1a
/pci@9,700000/ebus@1/i2c@1,30/controller@0,16

This technical procedure is made available through My Oracle Support (MOS), please contact MOS for assistance.

REFERENCES:

Document 1005013.1 probe-scsi-all may fail without reset-all on all Sun[TM] Systems
Document 1004782.1 Probe-scsi-all see disks but boot -r, devfsadm , and drvconfig fail to add disks to OS
Document 1005475.1 What is the meaning of the message: <drive not available: formatting> from the Solaris [TM] format utility

Product

Sun Fire V890 Server
Sun Fire V880 Server
Sun Fire V490 Server
Sun Fire V445 Server
Sun Fire V480 Server
Sun Fire V440 Server
Sun Fire V245 Server
Sun Fire V215 Server
Sun Fire V240 Server
Sun Fire V210 Server
Sun Fire T2000 Server
Sun Fire T1000 Server

@ Internal Comments
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:

[email protected]

REFERENCES:
Document 1003733.1 Sun Fire[TM] V440 server: Not All The
Internal Disks Show Up
Document 1018834.1 Sun Fire[TM] Server: Advanced DPM
(Daktari Personality Module) Troubleshooting Techniques
normalized, drive, controller, device warnings
Previously Published As 91389

Change History
Date: 2009-11-18
User name: Dencho Kojucharov
Action: Updated
Comments: Currency check, audited by Entry-Level SPARC Content Lead
Date: 2007-12-18
User Name: 71396
Action: Approved
Comment: Performed final review of article.
Updated trademarking.
Publishing.
Version: 3

Date: 2007-12-18
User Name: 71396
Action: Accept
Comment:
Version: 0
Date: 2007-12-18
User Name: 102144
Action: Approved
Comment: ok for review
Version: 0

Product_uuid
5d2816fe-5e51-11d7-8de2-d7bc0dd226fc|Sun Fire V890 Server
29726712-0a18-11d6-8636-c7e996b581dc|Sun Fire V880 Server
5c71fc02-5e51-11d7-8add-8938754df22a|Sun Fire V490 Server
eb738cf6-d4ad-11da-a742-080020a9ed93|Sun Fire V445 Server

Attachments

This solution has no attachment