Storage Boards Cleanup
To make it easier to find information about HPE Storage products and solutions, we are doing spring cleaning. This includes consolidation of some older boards, and a simpler structure that more accurately reflects how people use HPE Storage.
Tape Libraries and Drives
cancel
Showing results for 
Search instead for 
Did you mean: 

MSL5060 drive firmware upgrade failed....why not?

Jung.S.H
Occasional Contributor

MSL5060 drive firmware upgrade failed....why not?

model : MSL5060 Ultrium 230
libray firmware : 4.30
drive frimware : E30W -> E38W

During the firmware upgrade failed.....

Main > Identity > Firmware Update >
-----------------------------------------------------------------------------------------------------------
You can update firmware on these devices. Type the corresponding number to select/clear, then type 'start'.
See the command list for additional help.

Device Current Rev New Rev Status
------ ----------- ------- ------
1 [ ] Library (MSL5000 Series) 0430 not selected
2 [X] Drive 1 (Ultrium 1-SCSI) E30W E38W pending
3
4 +- Informational: hp L&TT - Firmware Update -----------------------------------------------------+
5 | |
| Firmware update failed |
| |
| |
| |
| Exception: Application Exception 1020 (Logical Device: non-fatal I/O failure, function will |
| continue) |
| |
| |
| |
| Exception: I/O Exception (Error: 2133 - I/O: Command Incomplete) |
| |
| |
+- Press any key to continue --------------------------------------------------------------------+


======================================================================
=========== Syslog =================================================
======================================================================

Mar 23 16:48:59 vmunix: SCSI: isrEscape Controller at 0/2/0/0.
Mar 23 16:48:59 vmunix:
Mar 23 16:48:59 vmunix: SCSI: First party detected bus hang (HTH) -- lbolt: 534634084, dev:
cb051000
Mar 23 16:48:59 vmunix: lbp->state: 30008
Mar 23 16:48:59 vmunix: lbp->offset: ffffffff
Mar 23 16:48:59 vmunix: lbp->nominalOffset: 270
Mar 23 16:48:59 vmunix: lbp->Cmdindex: 9
Mar 23 16:48:59 vmunix: lbp->last_nexus_index: 27
Mar 23 16:48:59 vmunix: lbp->nexus_index: 28
Mar 23 16:48:59 vmunix: uCmdSent: 900da40 uNexus_offset: 2d6a0
Mar 23 16:48:59 vmunix: last lbp->puStatus [0000000040205680]:
Mar 23 16:48:59 vmunix: 00031100 00031100 00031100 00031100
Mar 23 16:48:59 vmunix: next lbp->puStatus [0000000040205690]:
Mar 23 16:48:59 vmunix: From most recent interrupt:
Mar 23 16:48:59 vmunix: ISTAT: 0a, SIST0: 40, SIST1: 01, DSTAT: 80, DSPS: 00
000000
Mar 23 16:48:59 vmunix: lsp: 0x0000000056001700
Mar 23 16:48:59 vmunix: 00031100 00031100 00031100 00031100
Mar 23 16:48:59 vmunix: bp->b_dev: cb051000
Mar 23 16:48:59 vmunix: scb->io_id: 5d80008
Mar 23 16:48:59 vmunix: scb->cdb: 3b 05 01 00 00 00 00 00 00 00
Mar 23 16:48:59 vmunix: lbolt_at_timeout: 534693860, lbolt_at_start: 5346338
60
Mar 23 16:48:59 vmunix: lsp->state: 4205
Mar 23 16:48:59 vmunix: Jump Table entry [0000000040200100]: 00001100 85ffc288
Mar 23 16:48:59 vmunix: DSAtbl->host_iocb_index: 9
Mar 23 16:48:59 vmunix: DSAtbl->host_iocb_addr: 2da40
Mar 23 16:48:59 vmunix: stored scratcha: 0x31100
Mar 23 16:48:59 vmunix: scratch_lsp: 0x0000000056001700
Mar 23 16:48:59 vmunix: c8xx_iocb [ffffffff85ffcb00]:
Mar 23 16:48:59 vmunix: 0900da40 00001100 85ffc288 bf010f00
Mar 23 16:48:59 vmunix: 00000001 0002da20 0000000a 0002da28
Mar 23 16:48:59 vmunix: Pre-DSP script dump [ffffffff85ffc250]:
Mar 23 16:48:59 vmunix: 1a000000 00000018 e27c0004 00028700
Mar 23 16:48:59 vmunix: e2600004 0002da3c 7c36fb00 00000000
Mar 23 16:48:59 vmunix: Script dump [ffffffff85ffc270]:
Mar 23 16:48:59 vmunix: 898b0000 000001e8 888b0000 000001e0
Mar 23 16:48:59 vmunix: 828a0000 ffffffc8 83830000 00000268
Mar 23 16:48:59 vmunix: NCR chip register dump for: 0x400200a
Mar 23 16:48:59 vmunix: 00: SCNTL3: bf SCNTL2: 80 SCNTL1: 10 SCNTL0
: da
Mar 23 16:48:59 vmunix: 04: GPREG: 0a SDID: 01 SXFER: 0f SCID:47
Mar 23 16:48:59 vmunix: 08: SBCL: 22 SSID: 80 SOCL: 02 SFBR:00
Mar 23 16:48:59 vmunix: 0c: SSTAT2: 00 SSTAT1: 0a SSTAT0: 01 DSTAT80
Mar 23 16:48:59 vmunix: 10: DSA: 85ffcb00
Mar 23 16:48:59 vmunix: 14: MBOX1: 00 MBOX0: 00 ISTAT1: 00 ISTAT08
Mar 23 16:48:59 vmunix: 1c: TEMP: 85ffcaa0
Mar 23 16:48:59 vmunix: 24: DCMDDBC: 898b0000
Mar 23 16:48:59 vmunix: 28: DNAD: 85ffc270
Mar 23 16:48:59 vmunix: 2c: DSP: 85ffc278
Mar 23 16:48:59 vmunix: 30: DSPS: 000001e8
Mar 23 16:48:59 vmunix: 34: SCRATCHA: 00031100
Mar 23 16:48:59 vmunix: 38: DCNTL: a1 DWT: 00 DIEN: 7f DMODE4c
Mar 23 16:48:59 vmunix: 3c: ADDER: 85ffc460
Mar 23 16:48:59 vmunix: 40: SIST1: 00 SIST0: 00 SIEN1: 97 SIEN08f
Mar 23 16:48:59 vmunix: 44: GPCNTL: 2f MACNTL: 00 SWIDE: 00 SLPAR00
Mar 23 16:48:59 vmunix: 48: RESPID1: 00 RESPID0: 80 STIME1: 00 STIME0

please ....answer me~!!~
2 REPLIES
Claudio Ruzza_1
Valued Contributor

Re: MSL5060 drive firmware upgrade failed....why not?

Are you using the latest LTT (3.5 sr2)?
Have you tried to re-inquire your library and drive after the apparently unsuccessfull upgrade?
With HP LTT sometimes you get an error even if the firmware upgrade of your drive has been successfull.
Is your drive still functional?

HTH
Claudio
Derek_31
Valued Contributor

Re: MSL5060 drive firmware upgrade failed....why not?

We had a ton of firmware update problems on a MSL5030 the other week. Apparently there is a very specific firmware update order that one needs to do with devices that are somewhat old. Ours were sitting on the shelf for 1+ years. The order that worked for us was:

1. Leave the built-in router card at the old firmware. Do NOT update to the latest (5.6.xx I think).

2. Update the MSL to 0430.

3. Update the LTO drives to E38W.

4. Update the storage router to the latest version.

Doing the storage router first caused immense grief and would result in failed tape drive and MSL updates. Apparently the latest router firmware does not at all like older MSL/LTO firmware. We spent 2 days and 3 storage routers to figure out the problem. Thanks HP! Great compatability testing.