NSR Reboots during backups

[Alun Rodgers]

We experienced a rackmounted NSR M2402 reboot during our backups lastnight, this is not the first time it has happened.

The errors logged are as follows:

1196. 11/30/2006 19:17:05 3d03h03m25.59s CHK COND with Sense Key=0x3, ASC=0xC, ASCQ=0x0 from SCSI LUN 3/2/4/0
1197. 11/30/2006 19:17:05 3d03h03m25.60s EXCEPTION: TLB Load Exception Type : 02
1198. 11/30/2006 19:17:05 3d03h03m25.60s Address : 80142CEC (inside fcpTrns_sendSpoofResponse)
1199. 11/30/2006 19:17:05 3d03h03m25.60s Return Address : 80142CC0 (inside fcpTrns_sendSpoofResponse)
1200. 11/30/2006 19:17:05 3d03h03m25.60s Virtual Address: 00000018 Task : psOutQ
1201. 11/30/2006 19:17:36 0d00h00m15.18s New device is added to location 3/0/1/0
1202. 11/30/2006 19:17:36 0d00h00m15.18s New device is added to location 3/0/2/0
1203. 11/30/2006 19:17:36 0d00h00m15.18s New device is added to location 3/0/3/0
1204. 11/30/2006 19:17:36 0d00h00m15.18s New device is added to location 3/1/1/0
1205. 11/30/2006 19:17:36 0d00h00m15.18s New device is added to location 3/1/2/0
1206. 11/30/2006 19:17:36 0d00h00m15.19s New device is added to location 3/1/3/0
1207. 11/30/2006 19:17:36 0d00h00m15.19s New device is added to location 3/2/4/0
1208. 11/30/2006 19:17:36 0d00h00m15.19s New device is added to location 3/2/5/0
1209. 11/30/2006 19:17:37 0d00h00m15.34s Unit restart and initialization, Firmware Version: 5.6 Build Level: 5.6.8c
1210. 11/30/2006 19:17:37 0d00h00m15.50s FC Port 0 Link is UP.
1211. 11/30/2006 19:17:41 0d00h00m19.45s Voltage normal
1212. 11/30/2006 19:17:41 0d00h00m19.47s Fan Tray Is Present
1213. 11/30/2006 19:17:41 0d00h00m19.53s Fan RPM normal
1214. 11/30/2006 19:17:41 0d00h00m19.59s Power Supply normal

This caused 11 backup jobs to fail overnight.

The NSR and backup server are zoned correctly into an HP Coreswitch 2/64 Fibre switch running 5.0.5a

The Server attaches to the NSR via an FCA2101 HBA running 1.70a1 and 3.92a2

The MSL5026SL and MSL5052SL are running 0516 and the SDLT110 drives are running V85.

Thanks,

Alun.

[rich pattison]

SK/ASC/ASCQ codes suggest it might have started with a medium error/write error from an attached drive (3/2/4/0 ?).

Do you have any errors reported from any of the drives ?. Do you have support tickets ??
Is it possible to trace if the same media was used on previous occurances ??