- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- HPE 9000 and HPE e3000 Servers
- >
- Re: K380 Crashed
HPE 9000 and HPE e3000 Servers
1753947
Members
7656
Online
108811
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
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
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- 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
тАО04-23-2002 12:05 PM
тАО04-23-2002 12:05 PM
Had a K380 with an AutoRaid 12H crash this morning. This is what the syslog contained at the time of the crash, any insight as to what happened would be appreciated.
Apr 23 11:38:27 uesc2 vmunix: SCSI: Request Timeout -- lbolt: 568723935, dev: 1f
014000
Apr 23 11:38:27 uesc2 vmunix: lbp->state: 20
Apr 23 11:38:27 uesc2 vmunix: lbp->offset: ffffffff
Apr 23 11:38:27 uesc2 vmunix: lbp->uPhysScript: 700000
Apr 23 11:38:27 uesc2 vmunix: From most recent interrupt:
Apr 23 11:38:27 uesc2 vmunix: ISTAT: 22, SIST0: 00, SIST1: 04, DSTAT:
00, DSPS: 007003c0
Apr 23 11:38:27 uesc2 vmunix: NCR chip register access history (most recent la
st): 31183445 accesses
Apr 23 11:38:27 uesc2 vmunix: 953, ISTAT<-20
Apr 23 11:38:27 uesc2 vmunix: 181, ISTAT<-20
Apr 23 11:38:27 uesc2 vmunix: 132, ISTAT<-20
Apr 23 11:38:27 uesc2 vmunix: 113, ISTAT<-20
Apr 23 11:38:27 uesc2 vmunix: 113, ISTAT<-20
Apr 23 11:38:27 uesc2 vmunix: 14289, ISTAT<-20
Apr 23 11:38:27 uesc2 vmunix: 0, ISTAT<-20
Apr 23 11:38:27 uesc2 vmunix: 1138001, ISTAT: 22
Apr 23 11:38:27 uesc2 vmunix: 6, SIST0: 00
Apr 23 11:38:27 uesc2 vmunix: 3, SIST1: 04
Apr 23 11:38:27 uesc2 vmunix: 3, DSTAT: 00
Apr 23 11:38:27 uesc2 vmunix: 1, DSPS: 007003c0
Apr 23 11:38:27 uesc2 vmunix: 1, SCRATCHA: ff000861
Apr 23 11:38:27 uesc2 vmunix: 6, CTEST3<-04
Apr 23 11:38:27 uesc2 vmunix: 1, STEST3<-82
Apr 23 11:38:27 uesc2 vmunix: 1, SCRATCHA1<-00
Apr 23 11:38:27 uesc2 vmunix: lsp: b802800
Apr 23 11:38:27 uesc2 vmunix: bp->b_dev: 1f014000
Apr 23 11:38:27 uesc2 vmunix: scb->io_id: 171406e
Apr 23 11:38:27 uesc2 vmunix: scb->cdb: 2a 00 00 00 06 40 00 00 02 00
Apr 23 11:38:27 uesc2 vmunix: lbolt_at_timeout: 568720805, lbolt_at_st
art: 568720805
Apr 23 11:38:27 uesc2 vmunix: lsp->state: 10d
Apr 23 11:38:27 uesc2 vmunix: lbp->owner: b802800
Apr 23 11:38:27 uesc2 vmunix: scratch_lsp: 0
Apr 23 11:38:27 uesc2 vmunix: Pre-DSP script dump [b64f020]:
Apr 23 11:38:27 uesc2 vmunix: ffb00810 00700604 41040000 00700288
Apr 23 11:38:27 uesc2 vmunix: 78346100 0000000a 78350800 00000000
Apr 23 11:38:27 uesc2 vmunix: Script dump [b64f040]:
Apr 23 11:38:27 uesc2 vmunix: 0e000004 007003c0 80000000 00000000
Apr 23 11:38:27 uesc2 vmunix: 9f0b0000 00000006 0a000000 007003c8
Apr 23 11:38:27 uesc2 vmunix:
Apr 23 11:38:27 uesc2 vmunix: SCSI: Abort abandoned -- lbolt: 568723935, dev: 1f
014000, io_id: 171406e, status: 200
Apr 23 11:38:27 uesc2 vmunix: LVM: vg[2]: pvnum=0 (dev_t=0x1f014000) is POWERFAI
LED
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-23-2002 12:18 PM
тАО04-23-2002 12:18 PM
Solution
It appears that /dev/dsk/c1t4d0 failed. This can be determined by the device node 1f014000.
1f (Decimal 31) is sdisk block device major number
014000 (minor device) decodes as c1t4d0.
Looks as though its time to replace a disk. This could be an AutoRAID LUN. There is no enough data here for me to determine that.
1f (Decimal 31) is sdisk block device major number
014000 (minor device) decodes as c1t4d0.
Looks as though its time to replace a disk. This could be an AutoRAID LUN. There is no enough data here for me to determine that.
If it ain't broke, I can fix that.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-23-2002 12:24 PM
тАО04-23-2002 12:24 PM
Re: K380 Crashed
Everything seems to point to c1t4d0 which is in vg02. A quick status check is in order ..
# /etc/diskinfo /dev/rdsk/c1t4d0
==> does it respond ?
# pvdisplay -v /dev/rdsk/c1t4d0 | more
==> any stale PEs ?
# arraydsp -a | more
==> what's the status of the disk in the LUN.
Post the outcome/results ..
# /etc/diskinfo /dev/rdsk/c1t4d0
==> does it respond ?
# pvdisplay -v /dev/rdsk/c1t4d0 | more
==> any stale PEs ?
# arraydsp -a
==> what's the status of the disk in the LUN.
Post the outcome/results ..
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP