MSA Storage
cancel
Showing results for 
Search instead for 
Did you mean: 

NSR reset by itself ?

 
SOLVED
Go to solution
CA1326359
Occasional Advisor

NSR reset by itself ?

we got a newly installed NSR M2402 and suddenly this weekend it reset by itself with the folowing error. Did sommone have a idee Y?

09/24/2005 17:26:29 9d07h20m17.90s Assertion failed: 0, file ../ps_driver.c, line 2916
1888. 09/24/2005 17:26:29 9d07h20m17.90s Assertion failed (continued): 2916
1889. 09/24/2005 17:27:02 0d00h00m15.42s New device is added to location 2/0/0/0
1890. 09/24/2005 17:27:02 0d00h00m15.42s New device is added to location 2/0/1/0
09/24/2005 17:27:02 0d00h00m15.61s Unit restart and initialization, Firmware Version: 5.6 Build Level: 5.6.69
1902. 09/24/2005 17:27:03 0d00h00m16.41s FC Port 0 Link is UP.
4 REPLIES 4
CA713937
Honored Contributor
Solution

Re: NSR reset by itself ?

What version of firmawre do you have in the NSR?

We recently released 5.6.78. Here's the change list:

BugFix:
Fixed between versions 5669 and 5678
TLB and Assertion fixes.

BugFix:
Fixed between versions 5669 and 5678
Fix for a Veritas Netbackup move issue in partitioned libraries where physical slot number does not match partition slot number.

BugFix:
Fixed between versions 5669 and 5678
Fixes for partition spanning frames in ESL E Series Cross Linked Libraries.

BugFix:
Fixed between versions 5669 and 5678
Fix for a multi-initiator issue where some hosts lose communication with a tape drive.

BugFix:
Fixed between versions 5669 and 5678
Fix for false reporting of "topology incomplete" by interface manager/Command View TL.

Enhancement:
Fixed between versions 5669 and 5678
Added support for dual-SAN cabinet controller connectivity in ESL E (via SCSI over IP protocol).

I'm pretty sure one of the assertion fixes was for one generated in ps_driver.c

(and to answer the question in the title, yes an assertion will cause the NSR to reset itself)
The journey IS the reward.
CA1326359
Occasional Advisor

Re: NSR reset by itself ?

Thanks for your quik reply. I've seen yesterday the new firware 5.6.78 relase (we are curently at 5.6.69). But I was anable to find the change made from 5.6.69 so your reply have a great value for me and confirm that I should do the move quikly.

By the way, yesterday night, 1 drive on a strorage node got a bad block,and after the HBA #2 give error "did not respond within the timeout period" and finaly the NSR chanel 2 lose all connection to the librairy connect to port 2 FC and scsi. woaw! a single drive failure can disable all the backup on one chanel. I never experience that with the previous MDR.

Can somebody comment on this?
CA713937
Honored Contributor

Re: NSR reset by itself ?

Yes, one of the assertions addressed in the 5.6.78 firmware can occur after a drive has encountered a hard write error.

The MDR and NSRs are different hardware/firmware architectures.

The fix list can be found in HP L&TT "get files from web" by selecting the firmware (device) name and then clicking on the details button. It should also be included where we post individual files under the software and downloads section (not sure if they are posted that way for the NSR).
The journey IS the reward.
CA1326359
Occasional Advisor

Re: NSR reset by itself ?

wow! after the upgrade to ver 5.6.78 a month ago, the reset disapered until last night with the following error:

1250. 11/28/2005 22:17:23 0d04h56m30.35s CHK COND with Sense Key=0x3, ASC=0xC, ASCQ=0x0 from SCSI LUN 3/0/1/0

1251. 11/28/2005 22:17:23 0d04h56m30.35s SCSI UDC Error. Port 12 Target 1, S_ID 0x670400, CDB 0x0A, Device Type 1

1252. 11/28/2005 22:17:23 0d04h56m30.35s CHK COND with Sense Key=0x3, ASC=0xC, ASCQ=0x0 from SCSI LUN 3/0/1/0

1253. 11/28/2005 22:17:23 0d04h56m30.36s EXCEPTION: TLB Load Exception Type : 02

1254. 11/28/2005 22:17:23 0d04h56m30.37s Address : 80171A6C (inside sendFCP_IU)

1255. 11/28/2005 22:17:24 0d04h56m30.37s Return Address : 801703E4 (inside fc4_send_req)

1256. 11/28/2005 22:17:24 0d04h56m30.37s Virtual Address: 00000018 Task : psOutQ

All my running backup failed and all my tru64 node send bus reset when tape load !!!

Wath a mess!!!

we also got some backup saveset who are not using the tape drive compression, and use it after a tape change ??? (very strange, same saveset).