- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: understand error in syslog file
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
10-27-2005 04:23 AM
10-27-2005 04:23 AM
I had SCSI error in the syslog :
SCSI: io_id: 178d4ae8
Oct 27 01:06:28 hpux188 vmunix: lbolt: 4219261
Oct 27 01:06:28 hpux188 vmunix: bp: 00000000497cf400
Oct 27 01:06:28 hpux188 vmunix: dev: bc172600 (1/0/2/1/0.1.4.0.0.2.6)
Oct 27 01:06:28 hpux188 vmunix: tag: fe (untagged)
Oct 27 01:06:28 hpux188 vmunix: cdb: 15 10 00 00 20 00
Oct 27 01:06:28 hpux188 vmunix: addr: 0000000050d95e00
Oct 27 01:06:28 hpux188 vmunix: retry_cnt: 1
Oct 27 01:06:28 hpux188 vmunix: data out: 00 00 00 08 00 7f cb b2 00 00 02 00 08 12 00 00
Oct 27 01:06:28 hpux188 vmunix: status: (400) None -- Incomplete
Oct 27 01:06:28 hpux188 vmunix: Retry count exceeded!
Can you explain what's wrong? Also can you tell me what lbolt means and the status of "incomplete" means.
Thanks,
Shirley
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-27-2005 04:33 AM
10-27-2005 04:33 AM
Re: understand error in syslog file
You need to test the device at (1/0/2/1/0.1.4.0.0.2.6)
try diskinfo as well as a dd:
dd if=/dev/dsk/
Rgds...Geoff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-27-2005 04:42 AM
10-27-2005 04:42 AM
Re: understand error in syslog file
Thanks,
Shirley
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-27-2005 04:46 AM
10-27-2005 04:46 AM
Re: understand error in syslog file
Check your terminators and cable connections for snugness.
Looking at the message again you have ONE device reporting lbolt error
the dev bc172600
You can be confident that lbolt errors (parity errors, etc) are definitely
hardware,not software. Note that bad tapes and dirty heads will cause these errors
too.DDS3 is an older technology so replacement drives are cheap and if the drive
is used daily, about 2 years is all you can expect for reliable operation.
Hanwant
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-27-2005 04:49 AM
10-27-2005 04:49 AM
Re: understand error in syslog file
Well bc=188 & 188 is the character major number for a SCSI disk.
Now you can decode just what disk from 172600
where c=17 (hex) so c23 (decimal)
t=2 and
d=6
So it should be /dev/rdsk/c23t2d6 that reported the problem.
I'd advise you check that disk with a diskinfo command
diskinfo /dev/rdsk/c23t2d6
If it reports accurate info check it with a dd command or even the STM diags.
HTH,
Jeff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-27-2005 04:50 AM
10-27-2005 04:50 AM
Solutionhttp://forums1.itrc.hp.com/service/forums/questionanswer.do?admit=716493758+1093012932131+28353475&threadId=219110
And this doc:
http://docs.hp.com/en/5991-1236/When_Good_Disks_Go_Bad.pdf
Rgds...Geoff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-27-2005 05:08 AM
10-27-2005 05:08 AM
Re: understand error in syslog file
lbolt is just the number of ticks (or 10msec) that passed since system was booted. It is another type of timestamp used sometimes internally.
Marie.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-27-2005 05:18 AM
10-27-2005 05:18 AM
Re: understand error in syslog file
Can anybody tell me the entry: stataus: (400)None-Incomplete and Retry count exceeded mean?
Shirley
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-27-2005 05:41 AM
10-27-2005 05:41 AM
Re: understand error in syslog file
Rgds,
Jeff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-27-2005 05:54 AM
10-27-2005 05:54 AM
Re: understand error in syslog file
You mention the max_retry, how many times is the default maximum? Cause sometimes I see retry_cnt is 1, sometimes it's 45, sometimes it's 72.
Shirley