HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- SCSI trouble...
Operating System - HP-UX
1838741
Members
3832
Online
110129
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
Forums
Discussions
Discussions
Discussions
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
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
07-06-2004 12:06 AM
07-06-2004 12:06 AM
SCSI trouble...
Hello,
On a D390 server with HPUX 10.20.
It seems I have a disk or a SCSI issue...
Extract of /var/adm/messages file :
SCSI: Request Timeout -- lbolt: 10331845, dev: 1f008000
lbp->state: 20
lbp->offset: ffffffff
lbp->uPhysScript: 180000
From most recent interrupt:
ISTAT: 22, SIST0: 00, SIST1: 04, DSTAT: 00, DSPS: 001803c0
NCR chip register access history (most recent last): 160349 accesses
15999787, ISTAT<-20
2894720, ISTAT<-20
105369, ISTAT<-20
4526796, ISTAT<-20
142, ISTAT<-20
3473009, ISTAT<-20
5543989, ISTAT<-20
302761, ISTAT: 22
4, SIST0: 00
2, SIST1: 04
2, DSTAT: 00
2, DSPS: 001803c0
1, SCRATCHA: ff00087d
5, CTEST3<-04
1, STEST3<-82
0, SCRATCHA1<-00
lsp: b1e5900
bp->b_dev: 1f008000
scb->io_id: 20f54
scb->cdb: 2a 00 00 7a a0 d0 00 00 08 00
lbolt_at_timeout: 10328715, lbolt_at_start: 10328715
lsp->state: 10d
lbp->owner: b1e5900
scratch_lsp: 0
Pre-DSP script dump [ac8b020]:
fbf44810 00180674 41080000 00180288
78347d00 0000000a 78350800 00000000
Script dump [ac8b040]:
0e000004 001803c0 80000000 00000000
9f0b0000 00000006 0a000000 001803c8
SCSI: Abort abandoned -- lbolt: 10331845, dev: 1f008000, io_id: 20f54, status: 200
LVM: VG 1 : PV 0 (device 0x1f008000) is POWERFAILED
# ioscan -fnCdisk
Class I H/W Path Driver S/W State H/W Type Description
=====================================================================
disk 0 8/4.5.0 sdisk CLAIMED DEVICE SEAGATE ST318275LC
/dev/dsk/c0t5d0 /dev/rdsk/c0t5d0
disk 1 8/4.8.0 sdisk CLAIMED DEVICE SEAGATE ST318436LC
/dev/dsk/c0t8d0 /dev/rdsk/c0t8d0
disk 2 8/4.9.0 sdisk CLAIMED DEVICE SEAGATE ST318436LC
/dev/dsk/c0t9d0 /dev/rdsk/c0t9d0
disk 3 8/16/5.2.0 sdisk CLAIMED DEVICE HP DVD-ROM 6x/32x
/dev/dsk/c1t2d0 /dev/rdsk/c1t2d0
Just before rebooting I had this HW issue:
# ioscan -fnCdisk
Class I H/W Path Driver S/W State H/W Type Description
=====================================================================
disk 0 8/4.5.0 sdisk CLAIMED DEVICE SEAGATE ST318275LC
/dev/dsk/c0t5d0 /dev/rdsk/c0t5d0
disk 1 8/4.8.0 sdisk NO_HW DEVICE SEAGATE ST318436LC
/dev/dsk/c0t8d0 /dev/rdsk/c0t8d0
disk 2 8/4.9.0 sdisk CLAIMED DEVICE SEAGATE ST318436LC
/dev/dsk/c0t9d0 /dev/rdsk/c0t9d0
disk 3 8/16/5.2.0 sdisk CLAIMED DEVICE HP DVD-ROM 6x/32x
/dev/dsk/c1t2d0 /dev/rdsk/c1t2d0
#
Someone can help me ? What is the issue ?
Now when I launch "dmesg" I have this message:
# dmesg
Jul 6 12:05
Can't get kernel namelist
#
???
Thanks,
On a D390 server with HPUX 10.20.
It seems I have a disk or a SCSI issue...
Extract of /var/adm/messages file :
SCSI: Request Timeout -- lbolt: 10331845, dev: 1f008000
lbp->state: 20
lbp->offset: ffffffff
lbp->uPhysScript: 180000
From most recent interrupt:
ISTAT: 22, SIST0: 00, SIST1: 04, DSTAT: 00, DSPS: 001803c0
NCR chip register access history (most recent last): 160349 accesses
15999787, ISTAT<-20
2894720, ISTAT<-20
105369, ISTAT<-20
4526796, ISTAT<-20
142, ISTAT<-20
3473009, ISTAT<-20
5543989, ISTAT<-20
302761, ISTAT: 22
4, SIST0: 00
2, SIST1: 04
2, DSTAT: 00
2, DSPS: 001803c0
1, SCRATCHA: ff00087d
5, CTEST3<-04
1, STEST3<-82
0, SCRATCHA1<-00
lsp: b1e5900
bp->b_dev: 1f008000
scb->io_id: 20f54
scb->cdb: 2a 00 00 7a a0 d0 00 00 08 00
lbolt_at_timeout: 10328715, lbolt_at_start: 10328715
lsp->state: 10d
lbp->owner: b1e5900
scratch_lsp: 0
Pre-DSP script dump [ac8b020]:
fbf44810 00180674 41080000 00180288
78347d00 0000000a 78350800 00000000
Script dump [ac8b040]:
0e000004 001803c0 80000000 00000000
9f0b0000 00000006 0a000000 001803c8
SCSI: Abort abandoned -- lbolt: 10331845, dev: 1f008000, io_id: 20f54, status: 200
LVM: VG 1 : PV 0 (device 0x1f008000) is POWERFAILED
# ioscan -fnCdisk
Class I H/W Path Driver S/W State H/W Type Description
=====================================================================
disk 0 8/4.5.0 sdisk CLAIMED DEVICE SEAGATE ST318275LC
/dev/dsk/c0t5d0 /dev/rdsk/c0t5d0
disk 1 8/4.8.0 sdisk CLAIMED DEVICE SEAGATE ST318436LC
/dev/dsk/c0t8d0 /dev/rdsk/c0t8d0
disk 2 8/4.9.0 sdisk CLAIMED DEVICE SEAGATE ST318436LC
/dev/dsk/c0t9d0 /dev/rdsk/c0t9d0
disk 3 8/16/5.2.0 sdisk CLAIMED DEVICE HP DVD-ROM 6x/32x
/dev/dsk/c1t2d0 /dev/rdsk/c1t2d0
Just before rebooting I had this HW issue:
# ioscan -fnCdisk
Class I H/W Path Driver S/W State H/W Type Description
=====================================================================
disk 0 8/4.5.0 sdisk CLAIMED DEVICE SEAGATE ST318275LC
/dev/dsk/c0t5d0 /dev/rdsk/c0t5d0
disk 1 8/4.8.0 sdisk NO_HW DEVICE SEAGATE ST318436LC
/dev/dsk/c0t8d0 /dev/rdsk/c0t8d0
disk 2 8/4.9.0 sdisk CLAIMED DEVICE SEAGATE ST318436LC
/dev/dsk/c0t9d0 /dev/rdsk/c0t9d0
disk 3 8/16/5.2.0 sdisk CLAIMED DEVICE HP DVD-ROM 6x/32x
/dev/dsk/c1t2d0 /dev/rdsk/c1t2d0
#
Someone can help me ? What is the issue ?
Now when I launch "dmesg" I have this message:
# dmesg
Jul 6 12:05
Can't get kernel namelist
#
???
Thanks,
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-06-2004 12:16 AM
07-06-2004 12:16 AM
Re: SCSI trouble...
"SCSI: Request Timeout" is caused by the kernel driver thinking that the request to the device did not complete.
Check the hardware connection/cabling. It could be more severe, and be a bad root disk as well.
The device is dev: 1f008000
# ll /dev/dsk |grep 008000
Check the hardware connection/cabling. It could be more severe, and be a bad root disk as well.
The device is dev: 1f008000
# ll /dev/dsk |grep 008000
"Downtime is a Crime."
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-06-2004 12:19 AM
07-06-2004 12:19 AM
Re: SCSI trouble...
hi,
device 0x1f008000 refers to c0t8d0 and i think you have a failing disk.
check it with dd
dd if=/dev/rdsk/c0t8d0 of=null bs=1024
do it three to four times and check the values of records in and records out..both should match..
If you have STM bundle installed, do a non destructive check with cstm or mstm
with best wishes
Naveej
device 0x1f008000 refers to c0t8d0 and i think you have a failing disk.
check it with dd
dd if=/dev/rdsk/c0t8d0 of=null bs=1024
do it three to four times and check the values of records in and records out..both should match..
If you have STM bundle installed, do a non destructive check with cstm or mstm
with best wishes
Naveej
practice makes a man perfect!!!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-06-2004 12:36 AM
07-06-2004 12:36 AM
Re: SCSI trouble...
The problem is c0t8d0.
Note that in the ioscan, it says "NO_HW". This means that you either have an old device file for a device that you meant to disconnect (and did) but its still in the kernel.
If this is the case then you need to use rmsf to get rid of the device file information.
OR it means that you have a broke disk drive at that location and need to open a HW call.
Best regards,
Kent M. Ostby
Note that in the ioscan, it says "NO_HW". This means that you either have an old device file for a device that you meant to disconnect (and did) but its still in the kernel.
If this is the case then you need to use rmsf to get rid of the device file information.
OR it means that you have a broke disk drive at that location and need to open a HW call.
Best regards,
Kent M. Ostby
"Well, actually, she is a rocket scientist" -- Steve Martin in "Roxanne"
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.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP