Sun Fire[TM] V440 server: Not All The Internal Disks Show Up.

Asset ID:	1-72-1003733.1
Update Date:	2018-02-14
Keywords:

Solution Type Problem Resolution Sure

Solution 1003733.1 : Sun Fire[TM] V440 server: Not All The Internal Disks Show Up.

Applies to:

Sun Fire V440 Server - Version Not Applicable and later
Sun Netra 440 Server - Version Not Applicable and later
All Platforms

Symptoms

There are physically, four internal disks installed in the Sun Fire[TM] V440 server. The outputs of the commands "format", "iostat -e", "probe-scsi", as well as any SCSI error messages, don't include all the disks you would expect to see.

Cause

Various possible causes.

Solution

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

When a RAID(Redundant Array of Inexpensive Disks) volume is created using the internal RAID capabilities of the Sun Fire V440 server, it takes whatever internal disks are used, and removes their "c1tXd0" identity. They are then referenced as a "volume" comprised of "targets".Following, is an example:

This Sun Fire V440 server has four internal 73 GB disks...

But, the output of the format command shows:

AVAILABLE DISK SELECTIONS:
0. c1t0d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@1f,700000/scsi@2/sd@0,0
1. c1t2d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@1f,700000/scsi@2/sd@2,0
2. c1t3d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@1f,700000/scsi@2/sd@3,0

So, what commands can be used to determine if a RAID volume has been created, and has disks in use?

There are basically two methods to confirm the presence of a RAID volume in a Sun Fire V440 server:

A. From Solaris[TM] Operating System(OS), use the raidctl command to see whether Raid volumes are present in the system.

Example command output :

 # raidctl -l
RAID            RAID            RAID            Disk
Volume          Status          Disk            Status
------------------------------------------------------
c1t0d0          OK              c1t0d0          OK
c1t1d0          OK

From the above raidctl output, there is a volume c1t0d0, comprising of two internal disks c1t0d0 and c1t1d0. Also, note that the disk showing in the top of this output, is the primary disk for this mirrored volume. In this case, c1t0d0 is the primary, and c1t1d0 is the secondary disk.

B. From the Online Boot PROM(OBP), by using the probe-scsi-all command

Example output:

 {3} ok probe-scsi-all
/pci@1f,700000/scsi@2,1

 /pci@1f,700000/scsi@2
Target 0
Unit 0   Disk     HITACHI DK32EJ36NSUN36G PQ0B    71132959 Blocks, 34732 MB
Volume 1
Unit 0   Disk     LSILOGIC1030 IM       IM1000    71132927 Blocks, 34732 MB
Target 3
Unit 0   Disk     HITACHI DK32EJ36NSUN36G PQ0B    71132959 Blocks, 34732 MB

 {3} ok

Note: "LSILOGIC1030", indicates it is a RAID volume, and the volume number would be used as the boot disk or boot-device, if that is correct - for example: "boot disk1" would boot from the RAID volume set. Notice target 2 is also not present, as it is likely part of the RAID set volume 1.

ALSO:

Apart from these two methods, the iostat command can also be used, to check the RAID Volume.

In this output, iostat -e shows sd1 as an LSILOGIC disk:

 sd0      Soft Errors: 1 Hard Errors: 0 Transport Errors: 0
Vendor: TOSHIBA  Product: DVD-ROM SD-C2612 Revision: 1011 Serial No:
Size: 0.00GB <0 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 1 Predictive Failure Analysis: 0
sd1      Soft Errors: 7 Hard Errors: 0 Transport Errors: 0
Vendor: LSILOGIC Product: 1030 IM       IM Revision: 1000 Serial No:
Size: 73.40GB <73400057856 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 7 Predictive Failure Analysis: 0
sd3      Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: SEAGATE  Product: ST373307LSUN72G  Revision: 0507 Serial No: 0417B7C643
Size: 73.40GB <73400057856 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 0 Predictive Failure Analysis: 0
sd4      Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: SEAGATE  Product: ST373307LSUN72G  Revision: 0507 Serial No: 0417B79ZCW
Size: 73.40GB <73400057856 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 0 Predictive Failure Analysis: 0

The format utility's inquiry command will show if it is an LSILOGIC disk:

 # format
Searching for disks...done

 AVAILABLE DISK SELECTIONS:
0. c1t0d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
/pci@1f,700000/scsi@2/sd@0,0
1. c1t2d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
/pci@1f,700000/scsi@2/sd@2,0
2. c1t3d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
/pci@1f,700000/scsi@2/sd@3,0
Specify disk (enter its number): 0
selecting c1t0d0
[disk formatted]
Warning: Current Disk has mounted partitions.

 FORMAT MENU:
disk       - select a disk
type       - select (define) a disk type
partition  - select (define) a partition table
current    - describe the current disk
format     - format and analyze the disk
repair     - repair a defective sector
label      - write label to the disk
analyze    - surface analysis
defect     - defect list management
backup     - search for backup labels
verify     - read and display labels
save       - save new disk/partition definitions
inquiry    - show vendor, product and revision
volname    - set 8-character volume name
!<cmd>     - execute <cmd>, then return
quit
format> inq
Vendor:   LSILOGIC
Product:  1030 IM       IM
Revision: 1000
format>

All of the above methods can be used to find out whether the RAID volume is present in the system or not. Once the RAID volume is created, the secondary disk of the RAID volume will disappear from Solaris OS and OBP device tree's. Once you delete the RAID volume, then all disks will re-appear in Solaris OS and OBP device tree's.

So, if all 4 disks in a Sun Fire V440 server cannot be seen, use the above methods, to check for the presence of a RAID volume first. If there is no RAID volume, and the system reports less than 4 disks present, troubleshoot for any further disk related issues.

Previously Published As
79929

Attachments

This solution has no attachment