VSM - FSC3BC8 and FSC8E4B Warm Boots with Possible Data Corruption

(Doc ID 1444608.1)

Last updated on JULY 19, 2015

Applies to:

Sun StorageTek VSM System - Version 4 to 5C [Release 4.0 to 5.0]
Information in this document applies to any platform.

Symptoms

VSM took a warm boot.  SIM sent to the console will reflect FSC7596 (warm boot taken) with FSC3BC8 and/or FSC8E4B. 

The SIM will display on the host console as a SLS6659I message that will include 32 sense bytes of information.  Sense bytes 22 and 23 will contain 7596.  Sense bytes 30 and 31 will contain either 3BC8 or 8E4B.

FSC3BC8 indicates the subsystem encountered a timeout condition and took a warm boot to recover.

The FSC8E4B warm start indicates that the VTV being accessed at the time of the warm start had a data integrity issue. The data integrity issue in this event is permanent. The VTV will need to be deleted from the buffer and recalled from physical tape or recreated.

A precursor of encountering this problem can be ECAM timeouts.  See the Solution, Workaround portion of this document for more information regarding the potential ECAM timeouts.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms