- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- SCSI error in syslog
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
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
Discussion Boards
Community
Resources
Forums
Blogs
- 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
02-07-2007 03:11 PM
02-07-2007 03:11 PM
SCSI error in syslog
i'm getting the following error in syslog, what might be the problem, scsi card and tape drives are climed only, when i run the backup script i'm getting following error, why the scsi is resetting?
Feb 8 02:02:59 iman vmunix: SCSI: Resetting SCSI -- lbolt: 29030688, bus: 7 pat
h: 0/3/0/0
Feb 8 02:02:59 iman vmunix: SCSI: Reset detected -- lbolt: 29030688, bus: 7 pat
h: 0/3/0/0
Feb 8 02:03:05 iman vmunix: SCSI: isrEscape Controller at 0/3/0/0.
Feb 8 02:03:05 iman vmunix: SCSI: First party detected bus hang (HTH) -- lbolt:
29031248, dev: cd073040
Feb 8 02:03:05 iman vmunix: lbp->state: 30008
Feb 8 02:03:05 iman vmunix: lbp->offset: ffffffff
Feb 8 02:03:05 iman vmunix: lbp->nominalOffset: 450
Feb 8 02:03:05 iman vmunix:
Feb 8 02:03:05 iman above message repeats 2 times
Feb 8 02:03:05 iman vmunix: lbp->Cmdindex: 4
Feb 8 02:03:05 iman vmunix: lbp->last_nexus_index: 2
Feb 8 02:03:05 iman vmunix: lbp->nexus_index: 3
Feb 8 02:03:05 iman vmunix: uCmdSent: 4005900 uNexus_offset: a560c
Feb 8 02:03:05 iman vmunix: last lbp->puStatus [0000000041225600]:
Feb 8 02:03:05 iman vmunix: 00031300 00031300 00031300 00000000
Feb 8 02:03:05 iman vmunix: next lbp->puStatus [00000000412257f0]:
Feb 8 02:03:05 iman vmunix: 00031300 00031300 00031300 00031300
Feb 8 02:03:05 iman vmunix: From most recent interrupt:
Feb 8 02:03:05 iman vmunix: ISTAT: 0a, SIST0: 40, SIST1: 01, DSTAT:
80, DSPS: 00000000
Feb 8 02:03:05 iman vmunix: lsp: 0x000000004c0bfc00
Feb 8 02:03:05 iman vmunix: bp->b_dev: cd073040
Feb 8 02:03:05 iman vmunix: scb->io_id: 70f345d
Feb 8 02:03:05 iman vmunix: scb->cdb: 00 00 00 00 00 00
Feb 8 02:03:05 iman vmunix: lbolt_at_timeout: 29032028, lbolt_at_sta
rt: 29031028
Feb 8 02:03:05 iman vmunix: lsp->state: 4205
Feb 8 02:03:05 iman vmunix: Jump Table entry [0000000041220300]: 00001300 87
fde288
Feb 8 02:03:05 iman vmunix: DSAtbl->host_iocb_index: 4
Feb 8 02:03:05 iman vmunix: DSAtbl->host_iocb_addr: a5900
Feb 8 02:03:05 iman vmunix: stored scratcha: 0x31300
Feb 8 02:03:05 iman vmunix: scratch_lsp: 0x000000004c0bfc00
Feb 8 02:03:05 iman vmunix: c8xx_iocb [ffffffff87fdeb00]:
Feb 8 02:03:05 iman vmunix: 04005900 00001300 87fde288 9f033e80
Feb 8 02:03:05 iman vmunix: 00000001 000a58e0 00000006 000a58e8
Feb 8 02:03:05 iman vmunix: Pre-DSP script dump [ffffffff87fde250]:
Feb 8 02:03:05 iman vmunix: 1a000000 00000018 e27c0004 000a6000
Feb 8 02:03:05 iman vmunix: e2600004 000a58fc 7c36fb00 00000000
Feb 8 02:03:05 iman vmunix: Script dump [ffffffff87fde270]:
Feb 8 02:03:05 iman vmunix: 898b0000 000001e8 888b0000 000001e0
Feb 8 02:03:05 iman vmunix: 828a0000 ffffffc8 83830000 00000268
Feb 8 02:03:05 iman vmunix: NCR chip register dump for: 0x400200a
Feb 8 02:03:05 iman vmunix: 00: SCNTL3: 9f SCNTL2: 80 SCNTL1:
10 SCNTL0: da
Feb 8 02:03:05 iman vmunix: 04: GPREG: 0a SDID: 03 SXFER:
3e SCID: 47
Feb 8 02:03:05 iman vmunix: 08: SBCL: 22 SSID: 00 SOCL:
02 SFBR: 00
Feb 8 02:03:05 iman vmunix: 0c: SSTAT2: 00 SSTAT1: 0a SSTAT0:
01 DSTAT: 80
Feb 8 02:03:05 iman vmunix: 10: DSA: 87fdeb00
Feb 8 02:03:05 iman vmunix: 14: MBOX1: 00 MBOX0: 00 ISTAT1:
00 ISTAT: 08
Feb 8 02:03:05 iman vmunix: 2c: DSP: 87fde278
Feb 8 02:03:05 iman vmunix: 30: DSPS: 000001e8
Feb 8 02:03:05 iman vmunix: 34: SCRATCHA: 00031300
Feb 8 02:03:05 iman vmunix: 38: DCNTL: a1 DWT: 00 DIEN:
7f DMODE: 4c
Feb 8 02:03:05 iman vmunix: 3c: ADDER: 87fde460
Feb 8 02:03:05 iman vmunix: 40: SIST1: 00 SIST0: 00 SIEN1:
97 SIEN0: 8f
Feb 8 02:03:05 iman vmunix: 44: GPCNTL: 2f MACNTL: 00 SWIDE:
00 SLPAR: 00
Feb 8 02:03:05 iman vmunix: 48: RESPID1: 00 RESPID0: 80 STIME1:
00 STIME0: fc
Feb 8 02:03:05 iman vmunix: 4c: STEST3: 80 STEST2: 00 STEST1:
0c STEST0: 06
Feb 8 02:03:05 iman vmunix: 50: RESV50: 00 RESV51: c0 SIDL1:
00 SIDL0: 00
Feb 8 02:03:05 iman vmunix: 54: CCNTL1: 01 CCNTL0: 01 SODL1:
00 SODL0: 00
Feb 8 02:03:05 iman vmunix: 58: RESV58: 00 RESV59: 00 SBDL1:
00 SBDL0: 00
Feb 8 02:03:05 iman vmunix: 5c: SCRATCHB: 00030001
Feb 8 02:03:05 iman vmunix: 60: SCRATCHC: c0ffffff
Feb 8 02:03:05 iman vmunix: 64: SCRATCHD: 87fde288
Feb 8 02:03:05 iman vmunix: 68: SCRATCHE: 87fdec00
Feb 8 02:03:05 iman vmunix: 6c: SCRATCHF: 000a0300
Feb 8 02:03:05 iman vmunix: 70: SCRATCHG: 9f033e80
Feb 8 02:03:05 iman vmunix: 74: SCRATCHH: 000a560c
Feb 8 02:03:05 iman vmunix: 78: SCRATCHI: 09859f3e
Feb 8 02:03:05 iman vmunix: 7c: SCRATCHJ: 04005900
Feb 8 02:03:05 iman vmunix: bc: SCNTL4: 80
Feb 8 02:03:05 iman vmunix: PCI configuration register dump:
Feb 8 02:03:05 iman vmunix: Command: 0157
Feb 8 02:03:05 iman vmunix: Latency Timer: ff
Feb 8 02:03:05 iman vmunix: Cache Line Size: 10
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-07-2007 03:42 PM
02-07-2007 03:42 PM
Re: SCSI error in syslog
Please read the below thread.
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=745182
Regards,
Asif Sharif
Asif Sharif
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-07-2007 04:02 PM
02-07-2007 04:02 PM
Re: SCSI error in syslog
You could also check the same using cstm and infolog...
It could have been because of a disk, if there is a disk issue it may reset the full bus.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-07-2007 04:39 PM
02-07-2007 04:39 PM
Re: SCSI error in syslog
Event log
iman sent Event Monitor notification information:
/storage/events/tapes/SCSI_tape/0_3_0_0.3.0 is >= 1.
Its current value is INFORMATION(1).
Event data from monitor:
Event Time..........: Thu Feb 8 01:42:52 2007
Severity............: INFORMATION
Monitor.............: dm_stape
Event #.............: 100401
System..............: iman
Summary:
Disk at hardware path 0/3/0/0.3.0 : Successful completion of operation
Description of Error:
The device driver has successfully completed an I/O request.
Probable Cause / Recommended Action:
No action is necessary.
Additional Event Data:
System IP Address...: 10.1.1.28
Event Id............: 0x45ca32c400000000
Monitor Version.....: B.01.05
Event Class.........: I/O
Client Configuration File...........:
/var/stm/config/tools/monitor/default_dm_stape.clcfg
Client Configuration File Version...: A.01.00
Qualification criteria met.
Number of events..: 1
Associated OS error log entry id(s):
0x45ca32c300000000
Additional System Data:
System Model Number.............: 9000/800/L3000-8x
OS Version......................: B.11.11
System Firmware Version.........: 43.43
System Serial Number............: SGH4413BPJ
System Software ID..............: 1157404675
EMS Version.....................: A.04.00
STM Version.....................: A.43.00
System Current Product Number...: A6144B
System Original Product Number..: A6144B
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/scsi.htm#100401
v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v
Component Data:
Physical Device Path....: 0/3/0/0.3.0
Inquiry Vendor ID.......: HP
Inquiry Product ID......: Ultrium 2-SCSI
Firmware Version........: F48D
Serial Number...........: HUL4C05069
Product/Device Data:
Logger ID.........: stape
Product Identifier: SCSI Tape
Product Qualifier.: HPUltrium
SCSI Target ID....: (not available/applicable)
SCSI LUN..........: (not available/applicable)
I/O Log Event Data:
Driver Status Code..................: 0x00000005
Length of Logged Hardware Status....: 4 bytes.
Offset to Logged Manager Information: 8 bytes.
Length of Logged Manager Information: 30 bytes.
Hardware Status:
Raw H/W Status:
0x0000: 00 00 00 00
SCSI Status...: GOOD (0x00)
Indicates that the target has successfully completed the command.
SCSI Sense Data: (not present in log record)
SCSI Command Data Block: (not present in log record)
Manager-Specific Information:
Raw Manager Data:
0x0000: 07 0F 34 59 00 00 80 00 00 00 04 00 00 00 00 00
0x0010: 07 03 00 00 7E 00 00 06 0A 00 00 80 00 00
>---------- End Event Monitoring Service Event Notification ----------<
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-07-2007 04:52 PM
02-07-2007 04:52 PM