- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- dmesg output
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
Discussions
Discussions
Forums
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
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-17-2006 04:29 AM
тАО02-17-2006 04:29 AM
dmesg output
What do u guys think about it
SCSI: bp: 0d288000
dev: cd023000 (8/16/5.3.0)
cdb: 01 00 00 00 00 00
status: (02) Check Condition
sense data: 71 00 04 00 00 00 00 0e 00
00 15 00 00 00 00
sense key: (04) Hardware Error
additional sense code: (44)
additional sense code qualifier: (00)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-17-2006 04:39 AM
тАО02-17-2006 04:39 AM
Re: dmesg output
The 'dmesg' buffer doesn't record *when* an event occured, so this message could be hundreds of days old!
You should have STM installed and EMS too. See if these have revealed any alerts and if they are current and on-going.
You might also find some limited information in '/var/adm/syslog/syslog.log'.
Regards!
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-17-2006 07:34 AM
тАО02-17-2006 07:34 AM
Re: dmesg output
Regards,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-17-2006 09:56 AM
тАО02-17-2006 09:56 AM
Re: dmesg output
The first two hex digits "cd" (dec 205) indicate the major device number. Do an lsdev and look for character driver 205 -- probably "stape". The next two hex digit "02" indicates the controller instance number "2". The next hex digit "3" is the SCSI ID and the hex hex digit "0" is the LUN. The last two hex digits "00" are driver dependent.
The problem occurred on /dev/rmt/c2t3d0BEST and was a hardware problem.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-17-2006 06:14 PM
тАО02-17-2006 06:14 PM
Re: dmesg output
ioscan -fknC disk
can help identify any disk problems.
STM will allow you to further drill down.
kind regards
yogeeraj