Sun Microsystems, Inc.  Sun System Handbook - ISO 4.1 October 2012 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-1271235.1
Update Date:2012-05-15
Keywords:

Solution Type  Problem Resolution Sure

Solution  1271235.1 :   SL8500 - 3407 Manifest Problem Read Failure java.io.FileNotFoundException  


Related Items
  • Sun StorageTek SL8500 Modular Library System
  •  
Related Categories
  • PLA-Support>Sun Systems>TAPE>Tape Hardware>SN-TP: SL3000-8500 Library
  •  


3407 Manifest problem read failure java.io.FileNotFoundException: /mnt/flash/new/manifest1.txt (No such file or directory)=/mnt/flash/new/manifest1.txt (No such file or directory)

In this Document
Symptoms
Changes
Cause
Solution


Applies to:

Sun StorageTek SL8500 Modular Library System - Version Not Applicable and later
Information in this document applies to any platform.
Checked for relevance on 15-May-2012.

Symptoms

Bots fail to initialize and a power cycle of the library is required to recover.

Full error message is :

3407 Manifest problem read failure java.io.FileNotFoundException: /mnt/flash/new/manifest1.txt (No such file or directory)=/mnt/flash/new/manifest1.txt (No such file or directory)

RC3407

Changes

Brand new install and microcode was just applied. 

During the install of a new SL8500 library, and upon opening the door,  gets an error.

Cause

When this error appears the manifest file has become corrupted or wiped out.

Solution

Download same code to the library that's currently running.  ie  If microcode level is FRS_4.73,  redownload FRS_4.73. 

After successful download and unpack of microcode to the SL8500.

Using SLConsole, go to Tools menu,  then Diagnostics.

Choose the Activate tab.

Change the target pulldown to SL8500 code.

Choose the appropriate version of microcode.

Then push the Activate button in top right of window.

As the microcode gets applied, you will see a list of files either getting skipped or updated.  Verify  if any files got updated. 

If files got updated,  then a reboot is needed to complete the changes. 

If this does not correct the problem,  the manifest file must be corrected via the CLI interface by Oracle Backline Support or a Field Rep. 



Attachments
This solution has no attachment
  Copyright © 2012 Sun Microsystems, Inc.  All rights reserved.
 Feedback