V880 Crashed due to a disk failure

Asset ID:	1-72-1523775.1
Update Date:	2018-02-16
Keywords:

Solution Type Problem Resolution Sure

Solution 1523775.1 : V880 Crashed due to a disk failure

Applies to:

Sun Fire V890 Server - Version All Versions to All Versions [Release All Releases]
Sun Fire V880 Server - Version All Versions to All Versions [Release All Releases]
Sun Fire V480 Server - Version All Versions to All Versions [Release All Releases]
Sun Fire V490 Server - Version All Versions to All Versions [Release All Releases]
Sun Fire V880z Visualization Server - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Symptoms

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

System crashed after disk failure

The system was in a continual panic/reset loop.

ERROR: OpenBoot Diagnostics failed
WARNING: Device /pci@8,600000/SUNW,qlc@2 being marked with 'status' == fail
Rebooting with command: boot
Boot device: disk File and args:
|/-\||/-\|/-\|/-\sorry, variable 'kobj_map_space_len' is not defined in the 'kernel'

SunOS Release 5.8 Version Generic_117350-45 64-bit
Copyright 1983-2003 Sun Microsystems, Inc. All rights reserved.
|/-\|/-\|/-\|/-\ Cannot mount root on /pseudo/md@0:0,1,blk fstype ufs

panic[cpu3]/thread=10408000: vfs_mountroot: cannot mount root

0000000010407970 genunix:vfs_mountroot+70 (10436c00, 0, 0, 104702b2, 80, 14)
%l0-3: 0000000010436c00 000000001043a3a0 000000b0fe000000 0000000010436e88
%l4-7: 0000000000000000 00000000104139e0 00000000000c1a2d 0000000000001a2d
0000000010407a20 genunix:main+8c (104101f0, 2000, 10407ec0, 10408030, fff2, 100543ac)
%l0-3: 0000000000000001 0000000000000001 0000000000000015 0000000000000f6a
%l4-7: 0000000010429a48 00000000104760e0 00000000000da368 0000000000000368

skipping system dump - no dump device configured
rebooting...
Resetting ...

A hard reset was done on the system, with auto-boot disabled and the system was booted up into OBP.
While Running Obdiag a disk is shown to not spin up.

Testing /pci@8,600000/network@1
Testing /pci@8,600000/SUNW,qlc@2

ERROR : Disk 4 is not spinning.
DEVICE : /pci@8,600000/SUNW,qlc@2
SUBTEST : selftest:loop-tests:inquiry-test:disk-test
CALLERS : disk-test
MACHINE : Sun Fire 880
SERIAL# : 50912930
DATE : 01/22/2013 13:04:42 GMT
CONTR0LS: diag-level=max test-args=

Error: /pci@8,600000/SUNW,qlc@2 selftest failed, return code = 1
Testing /pci@9,700000/ebus@1/i2c@1,2e
Testing /pci@9,700000/ebus@1/i2c@1,30
Testing /pci@9,700000/ebus@1/i2c@1,50002e
Testing /pci@9,700000/ebus@1/i2c@1,500030
Testing /pci@9,700000/ebus@1/bbc@1,0
Testing /pci@9,700000/ebus@1/bbc@1,500000
Testing /pci@8,700000/scsi@1
Testing /pci@9,700000/network@1,1
Testing /pci@9,700000/usb@1,3
Testing /pci@9,700000/ebus@1/gpio@1,300600
Testing /pci@9,700000/ebus@1/pmc@1,300700
Testing /pci@9,700000/ebus@1/rtc@1,300070

WARNING: Device /pci@8,600000/SUNW,qlc@2 already marked with 'status' == fail

For additional information on OBDiag see:

Sun Fire[TM] Servers (V280R, V480, V490, V880, V890):OBDiag Troubleshooting (Doc ID 1383378.1)

For OBDiag Disk specific information see:

Using obdiag to troubleshoot internal drives on the Sun Fire(TM)V880 server. (Doc ID 1008827.1)

After unseating the disk, the OS booted successfully into single user (due to FS corruption) fsck was run and the system was brought up in multi user.

Cause

The system will not boot because the disk installed is holding down the bus.
The test run shows disk 4 did not spin up.
The data is enough to justify disk replacement.

Solution

Failed disk 4 needs to be replaced following the common replacement procedure for V880 server.

References

<NOTE:1272278.1> - Sun Fire V880 - V890 How to Replace a Faulty Disk Drive:ATR:918:0 [Video]

Attachments

This solution has no attachment