- Community Home
- >
- Storage
- >
- Data Protection and Retention
- >
- StoreEver Tape Storage
- >
- MSL5052 tape library NSR reboot and error issue
StoreEver Tape Storage
1752297
Members
4449
Online
108786
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-12-2006 12:53 AM
09-12-2006 12:53 AM
MSL5052 tape library NSR reboot and error issue
Last night our MSL rebooted unexpectedly with the following error:
2012. 09/11/2006 21:04:40 38d09h14m16.42s EXCEPTION: TLB Load Exception Type : 02
2013. 09/11/2006 21:04:40 38d09h14m16.42s Address : 801337A8 (inside fcpTrns_sendSpoofResponse)
2014. 09/11/2006 21:04:40 38d09h14m16.42s Return Address : 8013377C (inside fcpTrns_sendSpoofResponse)
2015. 09/11/2006 21:04:40 38d09h14m16.43s Virtual Address: 00000018 Task : psOutQ
2016. 09/11/2006 21:05:46 0d00h00m42.50s New device is added to location 0/0/0
2017. 09/11/2006 21:05:46 0d00h00m42.50s New device is added to location 0/1/0
2018. 09/11/2006 21:05:46 0d00h00m42.50s New device is added to location 1/2/0
2019. 09/11/2006 21:05:46 0d00h00m42.62s FC Port 0 Link is UP.
2020. 09/11/2006 21:05:46 0d00h00m42.62s Unit restart and initialization, Firmware Version: 5.6 Build Level: 5.6.78
Previous and following events include:
2002. 09/09/2006 09:13:03 35d21h22m40.15s SCSI UDC Error. Port 0 Target 0, S_ID 0xFFFFFF, CDB[0] 0x00, Device Type 31
2003. 09/09/2006 09:23:34 35d21h33m11.14s SCSI UDC Error. Port 0 Target 0, S_ID 0xFFFFFF, CDB[0] 0x00, Device Type 31
2004. 09/11/2006 07:05:10 37d19h14m46.66s CHK COND with Sense Key=0x3, ASC=0x11, ASCQ=0x0 from SCSI LUN 0/1/0
and
2021. 09/12/2006 01:07:19 0d04h02m15.60s CHK COND with Sense Key=0x3, ASC=0x11, ASCQ=0x0 from SCSI LUN 0/1/0
We are running Windows 2003 with DP 5.5. The MSL is fiber connected and zoned properly. I've looked around and seen that the CHK COND messages could be attributed to a firmware issue or the RsetPTRLO option on a connected servers' HBA. We have several servers zoned into the tape library but only 1 of them reported the reboot via an Insight Manager event. The Insight Manager trap flags are 16 for the drives and controller.
2012. 09/11/2006 21:04:40 38d09h14m16.42s EXCEPTION: TLB Load Exception Type : 02
2013. 09/11/2006 21:04:40 38d09h14m16.42s Address : 801337A8 (inside fcpTrns_sendSpoofResponse)
2014. 09/11/2006 21:04:40 38d09h14m16.42s Return Address : 8013377C (inside fcpTrns_sendSpoofResponse)
2015. 09/11/2006 21:04:40 38d09h14m16.43s Virtual Address: 00000018 Task : psOutQ
2016. 09/11/2006 21:05:46 0d00h00m42.50s New device is added to location 0/0/0
2017. 09/11/2006 21:05:46 0d00h00m42.50s New device is added to location 0/1/0
2018. 09/11/2006 21:05:46 0d00h00m42.50s New device is added to location 1/2/0
2019. 09/11/2006 21:05:46 0d00h00m42.62s FC Port 0 Link is UP.
2020. 09/11/2006 21:05:46 0d00h00m42.62s Unit restart and initialization, Firmware Version: 5.6 Build Level: 5.6.78
Previous and following events include:
2002. 09/09/2006 09:13:03 35d21h22m40.15s SCSI UDC Error. Port 0 Target 0, S_ID 0xFFFFFF, CDB[0] 0x00, Device Type 31
2003. 09/09/2006 09:23:34 35d21h33m11.14s SCSI UDC Error. Port 0 Target 0, S_ID 0xFFFFFF, CDB[0] 0x00, Device Type 31
2004. 09/11/2006 07:05:10 37d19h14m46.66s CHK COND with Sense Key=0x3, ASC=0x11, ASCQ=0x0 from SCSI LUN 0/1/0
and
2021. 09/12/2006 01:07:19 0d04h02m15.60s CHK COND with Sense Key=0x3, ASC=0x11, ASCQ=0x0 from SCSI LUN 0/1/0
We are running Windows 2003 with DP 5.5. The MSL is fiber connected and zoned properly. I've looked around and seen that the CHK COND messages could be attributed to a firmware issue or the RsetPTRLO option on a connected servers' HBA. We have several servers zoned into the tape library but only 1 of them reported the reboot via an Insight Manager event. The Insight Manager trap flags are 16 for the drives and controller.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-12-2006 06:44 PM
09-12-2006 06:44 PM
Re: MSL5052 tape library NSR reboot and error issue
2004. 09/11/2006 07:05:10 37d19h14m46.66s CHK COND with Sense Key=0x3, ASC=0x11, ASCQ=0x0 from SCSI LUN 0/1/0
this is indicating a medium error read not recovered error
2002. 09/09/2006 09:13:03 35d21h22m40.15s SCSI UDC Error. Port 0 Target 0, S_ID 0xFFFFFF, CDB[0] 0x00, Device Type 31
This is indicating a Unexpected Disconnect on the device in SCSI Parallel port O
I think that you should troubleshoot your drive, or scsi connection between NSR and drive to see if errors on the scsi path cause trouble to the NSR and causing the reboot.
The cause may also be a bad cartidge.
You can use LTT and run acceptance test to identify the cause of the problem
Marino
this is indicating a medium error read not recovered error
2002. 09/09/2006 09:13:03 35d21h22m40.15s SCSI UDC Error. Port 0 Target 0, S_ID 0xFFFFFF, CDB[0] 0x00, Device Type 31
This is indicating a Unexpected Disconnect on the device in SCSI Parallel port O
I think that you should troubleshoot your drive, or scsi connection between NSR and drive to see if errors on the scsi path cause trouble to the NSR and causing the reboot.
The cause may also be a bad cartidge.
You can use LTT and run acceptance test to identify the cause of the problem
Marino
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP