- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Scsi Errors in syslog.log
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
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
12-29-2003 08:32 PM
12-29-2003 08:32 PM
Scsi Errors in syslog.log
We are getting the folowing erros in syslog.log. Any thought?
Best regards,
Kaleem
Dec 26 22:12:50 lib-04 vmunix:
Dec 26 22:12:50 lib-04 vmunix: SCSI: First party detected bus hang -- lbolt: 1951848311, bus: 0
Dec 26 22:12:50 lib-04 vmunix: lbp->state: 1060
Dec 26 22:12:50 lib-04 vmunix: lbp->offset: 40
Dec 26 22:12:50 lib-04 vmunix: lbp->uPhysScript: f87fe000
Dec 26 22:12:50 lib-04 vmunix: From most recent interrupt:
Dec 26 22:12:50 lib-04 vmunix: ISTAT: 29, SIST0: 00, SIST1: 00, DSTAT: 84, DSPS: 0000000a
Dec 26 22:12:50 lib-04 vmunix: lsp: 0
Dec 26 22:12:50 lib-04 vmunix: lbp->owner: 42e80100
Dec 26 22:12:50 lib-04 vmunix: bp->b_dev: cb000000
Dec 26 22:12:50 lib-04 vmunix: scb->io_id: 8f0800
Dec 26 22:12:50 lib-04 vmunix: scb->cdb: 12 00 00 00 80 00
Dec 26 22:12:50 lib-04 vmunix: lbolt_at_timeout: 1951848211, lbolt_at_start: 1951847711
Dec 26 22:12:50 lib-04 vmunix: lsp->state: 5
Dec 26 22:12:50 lib-04 vmunix: scratch_lsp: 42e80100
Dec 26 22:12:50 lib-04 vmunix: Pre-DSP script dump [f87fe030]:
Dec 26 22:12:50 lib-04 vmunix: 78340000 0000000a 78351000 00000000
Dec 26 22:12:50 lib-04 vmunix: 0e000006 f87fe500 e0100004 f87fe7b8
Dec 26 22:12:50 lib-04 vmunix: Script dump [f87fe050]:
Dec 26 22:12:50 lib-04 vmunix: 9f0b0000 00000006 98080000 00000005
Dec 26 22:12:50 lib-04 vmunix: 721a0000 00000000 98080000 00000001
Dec 26 22:12:50 lib-04 vmunix: NCR chip register dump for: 0x1002002
Dec 26 22:12:50 lib-04 vmunix: 00: SCNTL3: 57 SCNTL2: 80 SCNTL1: 10 SCNTL0: d8
Dec 26 22:12:50 lib-04 vmunix: 04: GPREG: 0f SDID: 00 SXFER: 1f SCID: 47
Dec 26 22:12:50 lib-04 vmunix: 08: SBCL: 26 SSID: 80 SOCL: 06 SFBR: 00
Dec 26 22:12:50 lib-04 vmunix: 0c: SSTAT2: 00 SSTAT1: 0e SSTAT0: 00 DSTAT: 80
Dec 26 22:12:50 lib-04 vmunix: 10: DSA: c0ffffff
Dec 26 22:12:50 lib-04 vmunix: 14: MBOX1: 00 MBOX0: 00 ISTAT1: 02 ISTAT: 28
Dec 26 22:12:50 lib-04 vmunix: 18: CTEST3: 71 CTEST2: 75 CTEST1: 00 CTEST0: ff
Dec 26 22:12:50 lib-04 vmunix: 1c: TEMP: 00740000
Dec 26 22:12:50 lib-04 vmunix: 20: CTEST6: c0 CTEST5: 24 CTEST4: 00 DFIFO: 00
Dec 26 22:12:50 lib-04 vmunix: 24: DCMDDBC: 9f0b0000
Dec 26 22:12:50 lib-04 vmunix: 28: DNAD: f87fe050
Dec 26 22:12:50 lib-04 vmunix: 2c: DSP: f87fe058
Dec 26 22:12:50 lib-04 vmunix: 30: DSPS: 00000006
Dec 26 22:12:50 lib-04 vmunix: 34: SCRATCHA: ff001000
Dec 26 22:12:50 lib-04 vmunix: 38: DCNTL: a1 DWT: 00 DIEN: 7f DMODE: 4c
Dec 26 22:12:50 lib-04 vmunix: 3c: ADDER: f87fe05e
Dec 26 22:12:50 lib-04 vmunix: 40: SIST1: 00 SIST0: 40 SIEN1: 87 SIEN0: 8f
Dec 26 22:12:50 lib-04 vmunix: 44: GPCNTL: 0f MACNTL: f0 SWIDE: 00 SLPAR: 5b
Dec 26 22:12:50 lib-04 vmunix: 48: RESPID1: 00 RESPID0: 80 STIME1: 00 STIME0: 0c
Dec 26 22:12:50 lib-04 vmunix: 4c: STEST3: 80 STEST2: 00 STEST1: 0c STEST0: 76
Dec 26 22:12:50 lib-04 vmunix: 50: RESV50: 80 RESV51: a0 SIDL1: 00 SIDL0: 00
Dec 26 22:12:50 lib-04 vmunix: 54: CCNTL1: 00 CCNTL0: 00 SODL1: 00 SODL0: 1f
Dec 26 22:12:50 lib-04 vmunix: 58: RESV58: 00 RESV59: 00 SBDL1: 00 SBDL0: 00
Dec 26 22:12:50 lib-04 vmunix: 5c: SCRATCHB: 00000000
Dec 26 22:12:50 lib-04 vmunix: 60: SCRATCHC: 00000000
Dec 26 22:12:50 lib-04 vmunix: 64: SCRATCHD: 00000000
Dec 26 22:12:50 lib-04 vmunix: 68: SCRATCHE: 00000000
Dec 26 22:12:50 lib-04 vmunix: 6c: SCRATCHF: 00000000
Dec 26 22:12:50 lib-04 vmunix: 70: SCRATCHG: 00000000
Dec 26 22:12:50 lib-04 vmunix: 74: SCRATCHH: 00000000
Dec 26 22:12:50 lib-04 vmunix: 78: SCRATCHI: 00000000
Dec 26 22:12:50 lib-04 vmunix: 7c: SCRATCHJ: 00000000
Dec 26 22:12:50 lib-04 vmunix: PCI configuration register dump:
Dec 26 22:12:50 lib-04 vmunix: Command: 0157
Dec 26 22:12:50 lib-04 vmunix: Latency Timer: ff
Dec 26 22:12:50 lib-04 vmunix: Cache Line Size: 10
Dec 26 22:12:51 lib-04 vmunix:
Dec 26 22:12:51 lib-04 vmunix: SCSI: Resetting SCSI -- lbolt: 1951848411, bus: 0
Dec 26 22:12:51 lib-04 vmunix: SCSI: Reset detected -- lbolt: 1951848411, bus: 0
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-29-2003 08:42 PM
12-29-2003 08:42 PM
Re: Scsi Errors in syslog.log
it does not look good. your disk may crash or about to.
do this:
# lvdisplay -v /dev/vgXX/lvolXX|grep -i stale
if any output is shown, that is bad news.
keep me updated.
regards.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-29-2003 08:59 PM
12-29-2003 08:59 PM
Re: Scsi Errors in syslog.log
BR/MK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-29-2003 09:07 PM
12-29-2003 09:07 PM
Re: Scsi Errors in syslog.log
0xCB=203dec
Just do a lsdev
I think it should point to sctl.
the device is 0x000000
I am not sure whether this points to a media changer.
SCSI resets can occur
1.When the SCSI termination is not OK.It can also happen when you reset your device or remove the cables.
2.check with proper SCSI patches for your OS
3.Also check whether the device is responding.
REvert
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-29-2003 09:31 PM
12-29-2003 09:31 PM
Re: Scsi Errors in syslog.log
sorry for the false alarm. did not go through your syslog thoroughly. Manikandra is right, it should be the media device
# lsdev -C ctl
to check if the character is 203 which is cb000000 in hexdecimal.
regards.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-01-2004 01:16 AM
01-01-2004 01:16 AM
Re: Scsi Errors in syslog.log
This is a symptom of SCSI RESET. It may occur due to termination problem in any of your hard disks or scsi devices( external or Internal )