Lsi_sas errors with Event ID 129 and 11 (6944 Views)
Reply
Occasional Advisor
IviJ
Posts: 10
Registered: ‎11-21-2011
Message 1 of 4 (6,944 Views)
Accepted Solution

Lsi_sas errors with Event ID 129 and 11

Event Type:       Warning

Event Source:   Lsi_sas

Event Category: None

Event ID:           129

Date:                08.03.2012

Time:                18:50:03

User:                N/A

Computer:         SBALDC01

Description:

The description for Event ID ( 129 ) in Source ( Lsi_sas ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: \Device\RaidPort1.

Data:

0000: 0f 00 10 00 01 00 68 00   ......h.

0008: 00 00 00 00 81 00 04 80   ......€

0010: 04 00 00 00 00 00 00 00   ........

0018: 00 00 00 00 00 00 00 00   ........

0020: 00 00 00 00 00 00 00 00   ........

0028: 00 00 00 00 00 00 00 00   ........

0030: 00 04 00 00 81 00 04 80   ......€

 

------------------------------------------------------------------------------------------------

 

Event Type:       Error

Event Source:   Lsi_sas

Event Category: None

Event ID:           11

Date:                08.03.2012

Time:                18:50:04

User:                N/A

Computer:         SBALDC01

Description:

The driver detected a controller error on \Device\RaidPort1.

 

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Data:

0000: 0f 00 10 00 01 00 68 00   ......h.

0008: 00 00 00 00 0b 00 04 c0   .......À

0010: 00 00 14 31 00 00 00 00   ...1....

0018: 00 00 00 00 00 00 00 00   ........

0020: 00 00 00 00 00 00 00 00   ........

0028: 00 00 00 00 00 00 00 00   ........

0030: 00 00 00 00 0b 00 04 c0   .......À

 

 

Hi I have on my Proliant server running Windows 2003 SP2 with DP 6.11 sind a few days now crashed backups with the errors above. Backup Job starts and after writing over 200M it comes up with the errors in DP below.

 

[Major] From: BMA@dc01.local "HP:Ultrium 2-SCSI_dc01"  Time: 07.03.2012 20:55:56
[90:51]   Tape0:0:4:0C
 Cannot write to device ([1117] The request could not be performed because of an I/O device error. )

[Major] From: BMA@dc01.local "HP:Ultrium 2-SCSI_dc01"  Time: 07.03.2012 21:22:01
[90:181]  Cannot backspace segment. ([1117] The request could not be performed because of an I/O device error. )

[Major] From: BMA@dc01.local "HP:Ultrium 2-SCSI_dc01"  Time: 07.03.2012 21:32:01
[90:51]   Tape0:0:4:0C
 Cannot write to device ([1117] The request could not be performed because of an I/O device error. )

[Major] From: BMA@dc01.local "HP:Ultrium 2-SCSI_dc01"  Time: 07.03.2012 21:32:01
[90:159]  Apparently SCSI Unit Attention.

[Minor] From: BMA@dc01.local "HP:Ultrium 2-SCSI_dc01"  Time: 07.03.2012 21:32:01
[90:158]  Skipping write. (Apparently SCSI Unit Attention).

[Major] From: BMA@dc01.local "HP:Ultrium 2-SCSI_dc01"  Time: 07.03.2012 21:32:01
[90:162]  Skipping write of filemark. (Apparently SCSI Unit Attention).

[Major] From: BMA@dc01.local "HP:Ultrium 2-SCSI_dc01"  Time: 07.03.2012 21:32:01
[90:162]  Skipping write of filemark. (Apparently SCSI Unit Attention).

[Critical] From: BMA@dc01.local "HP:Ultrium 2-SCSI_dc01"  Time: 07.03.2012 21:32:01
[90:56]   Tape0:0:4:0C
 Cannot close device (Trailing filemark(s) could not be written.)

[Critical] From: BMA@dc01.local "HP:Ultrium 2-SCSI_dc01"  Time: 07.03.2012 21:32:12
Trailing filemark(s) could not be written.
[Critical] From: BMA@dc01.local "HP:Ultrium 2-SCSI_dc01"  Time: 07.03.2012 21:32:23
IPC Cannot Allocate Shared Memory Segment
[Critical] From: BMA@dc01.local "HP:Ultrium 2-SCSI_dc01"  Time: 07.03.2012 21:32:34
IPC Cannot Allocate Shared Memory Segment
[Critical] From: BMA@dc01.local "HP:Ultrium 2-SCSI_dc01"  Time: 07.03.2012 21:32:45
IPC Cannot Allocate Shared Memory Segment
[Normal] From: BMA@dc01.local "HP:Ultrium 2-SCSI_dc01"  Time: 07.03.2012 21:32:45
 ABORTED Media Agent "HP:Ultrium 2-SCSI_dc01"

 

Is the SAS card faulty or the drive?

IviJ
Please use plain text.
Frequent Advisor
Eric_de_Lange
Posts: 63
Registered: ‎08-09-2011
Message 2 of 4 (6,942 Views)

Re: Lsi_sas errors with Event ID 129 and 11

Event ID 129 emans that a SCSI reset has been issued for Port 1 on the Raid controller. Is that where the Ultrium tape drive is connected to ? (note: A SCSI reset is usually the last resort to get a non-responsive SCSI device back to a communicating state.) If that is the case and this configuration has been working before then the issue is likely media/drive related.

 

- first off check that the cables are still seated correctly (did you know that science was almost starting to doubt Einstein because of an incorrectly connected cable ?)

- on your host, install HP Library and Tape Tools and run the drive asessment test. This will test the drive and it's communication. If that fails, involve the hardware vendor. Also run tests with a new tape.

lastly, make sure that the Ultrium runs recent firmware. You can assess this through HP Library and Tape tools as well.

 

L&TT lives here:

http://h18000.www1.hp.com/products/storageworks/ltt/index.html

 

best,

-Eric

 

Please use plain text.
Occasional Advisor
IviJ
Posts: 10
Registered: ‎11-21-2011
Message 3 of 4 (6,938 Views)

Re: Lsi_sas errors with Event ID 129 and 11

The Tape is attached at Port 1 and the backup was running fine without any problems. As we replaced the old Ultrium 2 drive with this Ultrium 4 / LSI SAS Controller I also checked in January that the newest firmware was applied plus I updated DP6.11 with the newest patches.

 

Everything was running fine until last week when the errors startet with this ID 129 and 11.

 

I run the LLT health check and make a update with the outcome.

IviJ
Please use plain text.
Occasional Advisor
IviJ
Posts: 10
Registered: ‎11-21-2011
Message 4 of 4 (6,919 Views)

Re: Lsi_sas errors with Event ID 129 and 11

After sending in the LTT Logs to HP they told me that the drive has a hardware error. After replacing it the backup works again fine.

IviJ
Please use plain text.
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation