- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Determing device from error message
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-06-2003 10:23 AM
02-06-2003 10:23 AM
Determing device from error message
Feb 4 21:52:53 ds1-nhdr vmunix: SCSI: Request Timeout -- lbolt:
> 46931652, dev: cd030000
> Feb 4 21:52:53 ds1-nhdr vmunix: lbolt_at_timeout:
> 46871552, lbolt_at_start: 46871552
> Feb 4 21:52:53 ds1-nhdr vmunix: SCSI: Abort -- lbolt: 46931652, dev:
> cd030000, io_id: 31600b5
In looking around on our system we came up with two possible culprits. /dev/rmt/0m and /dev/dsk/c0t3d0
How can we distinguish:
ds1-nhdr:brianm:16$ ls -l /dev/rmt/0m
crw-rw-rw- 2 bin bin 205 0x030000 Feb 4 07:23 /dev/rmt/0m
from:
ds1-nhdr:root:/->#ls -l /dev/dsk/c0t3d0
brw-r----- 1 bin sys 31 0x003000 Jun 2 1998 /dev/dsk/c0t3d0
to determine which device is failing?
Thank you,
Randy Brown
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-06-2003 10:32 AM
02-06-2003 10:32 AM
Re: Determing device from error message
The first two digits of the device are the major number. Hence, device 'cd030000' would be a major number 0xcd or decimal 205. That's tape.
Regards!
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-06-2003 10:33 AM
02-06-2003 10:33 AM
Re: Determing device from error message
205 is decimal value of hex cd , from your lbolt output cd.
-USA..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-06-2003 10:34 AM
02-06-2003 10:34 AM
Re: Determing device from error message
-USA..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-06-2003 11:24 AM
02-06-2003 11:24 AM
Re: Determing device from error message
Randy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-06-2003 11:26 AM
02-06-2003 11:26 AM
Re: Determing device from error message
If it currently works, it won't for long. Either cabling or termination, or the device will have to be replaced. Make arrangements.
Exception. If you recently did an equipment swap like a hot swap of a drive, you will get an lbolt until next boot.
Doesn't look from the earlier info thats what happened.
P
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com