- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- SCSI: Unexpected Disconnect -- lbolt: 2224237, dev...
Categories
Company
Local Language
Forums
Discussions
Knowledge Base
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Knowledge Base
Forums
Discussions
- Cloud Mentoring and Education
- Software - General
- HPE OneView
- HPE Ezmeral Software platform
- HPE OpsRamp
Knowledge Base
Discussions
Forums
Discussions
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
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
09-14-2005 02:11 AM
09-14-2005 02:11 AM
SCSI: Unexpected Disconnect -- lbolt: 2224237, dev: cb004000, io_id: 65
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-14-2005 02:25 AM
09-14-2005 02:25 AM
Solution1. Get the "dev:" entry from the lbolt:
# dmesg | grep lbolt | grep dev:
SCSI: Abort -- lbolt: 18346341, dev: e7015000, io_id: 122e9a3
SCSI: Request Timeout -- lbolt: 18351441, dev: e7015000
SCSI: Abort -- lbolt: 18351441, dev: e7015000, io_id: 122e9be
SCSI: Request Timeout -- lbolt: 18356641, dev: e7015000
SCSI: Abort -- lbolt: 18356641, dev: e7015000, io_id: 122e9cf
SCSI: Request Timeout -- lbolt: 18362141, dev: e7015000
SCSI: Abort -- lbolt: 18362141, dev: e7015000, io_id: 122e9e0
SCSI: Request Timeout -- lbolt: 74105435, dev: 1f000000
SCSI: Abort Tag -- lbolt: 74105435, dev: 1f000000, io_id: 4ead34
Here we have two:
1f
e7
2. This is the major number of the device in question. Convert the first
two digits of the device from hex to decimal:
# printf "%#d\n" 0x1f
31
3. find out what driver this major number is. It tells us the type of
device:
# lsdev 31
Character Block Driver Class
188 31 sdisk disk
So, this is probably a disk !
4. Find the device file entry from the remainder of the lbolt error:
SCSI: Abort Tag -- lbolt: 74105435, dev: 1f000000, io_id: 4ead34
This is the minor number for the device that is failing.
a. Block device:
# ll -R /dev/ | grep 31 | grep 0x000000
brw-r----- 1 bin sys 31 0x000000 Jul 15 16:25 c0t0d0
Or:
b. Character Device:
# ll -R /dev/ | grep 188 | grep 0x000000
crw-r----- 1 bin sys 188 0x000000 Oct 11 07:15 c0t0d0
5. Find the Hardware Address:
# lssf /dev/dsk/c0t0d0
sdisk card instance 0 SCSI target 0 SCSI LUN 0 section 0
at address 0/0/0.0.0 /dev/dsk/c0t0d0
6. Find the type of device:
# diskinfo /dev/rdsk/c0t0d0# diskinfo /dev/rdsk/c0t0d0
SCSI describe of /dev/rdsk/c0t0d0:
vendor: DGC
product id: C2300WDR1
type: direct access
size: 4102875 Kbytes
bytes per sector: 512
So, we have a Nike disk at hardware address 0/0/0.0.0, device file
/dev/dsk/c0t0d0
7. cX numbers break down as follows:
a. # cd /dev/dsk/
# ll
total 0
brw-r----- 1 bin sys 31 0x010000 Sep 13 2002 c1t0d0
brw-r----- 1 bin sys 31 0x012000 Sep 13 2002 c1t2d0
brw-r----- 1 bin sys 31 0x190000 Apr 30 13:02 c25t0d0
b. 0x 01 0 0 00
-- - - --
| | | |
| | | flags
| | lun
| target
ext_bus
c. ioscan -fnk | more
Class I H/W Path Driver S/W State H/W Type Description
=======================================================================
...
ext_bus 1 0/0/1/1 c720 CLAIMED INTERFACE SCSI C896 Ultra Wi
target 2 0/0/1/1.0 tgt CLAIMED DEVICE
disk 0 0/0/1/1.0.0 sdisk CLAIMED DEVICE HP 18.2GMAN3184MC
/dev/dsk/c1t0d0 /dev/rdsk/c1t0d0
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-14-2005 02:32 AM
09-14-2005 02:32 AM
Re: SCSI: Unexpected Disconnect -- lbolt: 2224237, dev: cb004000, io_id: 65
Another methoid is to fire up xstm,mstm,cstm and test your disks.
There may be one missing.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-14-2005 02:40 AM
09-14-2005 02:40 AM
Re: SCSI: Unexpected Disconnect -- lbolt: 2224237, dev: cb004000, io_id: 65
cb: 203
00: c0
4: t4
0: 0
check your disk as c0t4d0
you can use dd to check c0t4d0,
# dd if=/dev/dsk/c0t4d0 of=/dev/null bs=4096
if output as following, disk is fine
2222889+0 records in
2222889+0 records out
if dd hang, then you probably need to replace the disk. or maybe just disk too busy.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-14-2005 03:07 AM
09-14-2005 03:07 AM
Re: SCSI: Unexpected Disconnect -- lbolt: 2224237, dev: cb004000, io_id: 65
I suspect this is *not* a hard disk as that would be 1f (31).
Instead this is cb (203) and is most likely another device like a tape drive.
On my systems the tape device is cd (205).
Do you have a tape library hung off this server? This could be the library device itself.
HTH,
Jeff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-14-2005 03:09 AM
09-14-2005 03:09 AM
Re: SCSI: Unexpected Disconnect -- lbolt: 2224237, dev: cb004000, io_id: 65
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-14-2005 04:00 AM
09-14-2005 04:00 AM
Re: SCSI: Unexpected Disconnect -- lbolt: 2224237, dev: cb004000, io_id: 65
I agree with Jeff. I decode this to 203 (0xcb) which yields a SCSI controller.
Do:
# lsdev -e 203 # ...0xcb = 203
I'd check your cabling and /var/adm/syslog/syslog.log to see if this was just transient.
Regards!
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-14-2005 08:15 PM
09-14-2005 08:15 PM