<?xml version="1.0" standalone="yes"?>
<?xml-stylesheet type="text/xsl" href="..\..\XSLTemplates\ErrorsStyleSheet.xsl"?>
<Error>
<ErrorNumber>33602</ErrorNumber>
<ErrorFamily>Non-Volatile Storage</ErrorFamily>
<ErrorMessage>
STG: Storage medium is corrupt
</ErrorMessage>
<AppliesTo>
<UnnumberedList>
<ListItem><Text>Gravure</Text></ListItem>
<ListItem><Text>Japanese_Newspaper_OEM_Engine</Text></ListItem>
<ListItem><Text>Lotem_400_Fiber_Head_Machine</Text></ListItem>
<ListItem><Text>Lotem_800_Fiber_Head_Machine</Text></ListItem>
<ListItem><Text>Lotem_Quantum</Text></ListItem>
<ListItem><Text>Magnus_400</Text></ListItem>
<ListItem><Text>Magnus_800</Text></ListItem>
<ListItem><Text>Magnus_VLF</Text></ListItem>
<ListItem><Text>SAT_SNIF</Text></ListItem>
<ListItem><Text>Slave_MCE_Firmware</Text></ListItem>
<ListItem><Text>Thermoflex</Text></ListItem>
<ListItem><Text>Think_Motion_Controller</Text></ListItem>
<ListItem><Text>Trendsetter_400/800</Text></ListItem>
<ListItem><Text>Trendsetter_NEWS</Text></ListItem>
<ListItem><Text>Trendsetter_Series_4</Text></ListItem>
</UnnumberedList>
</AppliesTo>
<ServiceInformation>
<DescriptionText><text>
The non-volatile storage medium (Flash or Battery-backed SRAM) is corrupt.  This
error occurs when corrupted data in Nvs causes the storage subsystem to fail,
since it relies on the integrity of the data in Nvs in order to find, read and
write storage keys.
</text></DescriptionText>
</ServiceInformation>
<OperatorAction>
<DescriptionText><text>
Run the "stg verify" command to attempt to recover from Nvs corruption.  Then
reboot.  If this does not solve the problem, then record the error number and
report it, along with a short description of the operation which caused the
error to occur (if possible), to Creo Service.
</text></DescriptionText>
</OperatorAction>
<Availability>
<DescriptionText><text>
This error is reported.
</text></DescriptionText>
</Availability>
<Cause>
A power failure may have occurred during a Nvs write operation.
A failed write operation results in an incomplete storage key existing in Nvs.
Since Nvs now contains an invalid entry, the storage subsystem can no longer
reliably access the Nvs, and is considered corrupt.
</Cause>
<Cause>
The Nvs device itself is damaged, or there is some other hardware problem.
Although highly unlikely to occur, a physical defect or hardware problem will
also cause this error.
</Cause>
<LastModified>
08-JAN-2001
Added detail.
</LastModified>
<SeeAlso>
<UnnumberedList>
<Link><LinkAddress>../commands/stg_verify_flash.xml</LinkAddress><LinkTitle>Command: stg verify flash</LinkTitle></Link>
<Link><LinkAddress>../commands/stg_verify_ram.xml</LinkAddress><LinkTitle>Command: stg verify ram</LinkTitle></Link>
<Link><LinkAddress>../commands/stg_verify_temp.xml</LinkAddress><LinkTitle>Command: stg verify temp</LinkTitle></Link>
</UnnumberedList>
</SeeAlso>
<OtherLinks>
<Link><LinkAddress>..\..\ShowAllErrors.htm</LinkAddress><LinkTitle>Firmware 1 Error Index</LinkTitle></Link>
<Link><LinkAddress>..\..\ShowAllCommands.htm</LinkAddress><LinkTitle>Firmware 1 Command Index</LinkTitle></Link>
<Link><LinkAddress>..\..\ShowAllParameters.htm</LinkAddress><LinkTitle>Firmware 1 Parameter Index</LinkTitle></Link>
</OtherLinks>
<Updated>
Updated: Thu Jul 17 07:22:59 2008 PST
</Updated>
<Links>
</Links>
</Error>
