- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- dmesg errors and disks
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-15-2002 07:58 AM
02-15-2002 07:58 AM
dmesg errors and disks
HP-UX 10.20
I was doing a bdf, very, very slow, I actually killed the process as it took too long...... So I did a quick dmesg and got the below mesage. I am not sure of the disk setup, if it's mirrored, etc, just took over the system. It seems like the disks are not set using lvm....... Any things I can start to check to investigate a possible bad disk?
Thanks
DIAGNOSTIC SYSTEM WARNING:
The diagnostic logging facility has started receiving excessive
errors from the I/O subsystem. I/O error entries will be lost
until the cause of the excessive I/O logging is corrected.
If the DEMLOG daemon is not active, use the DIAGSYSTEM command
in SYSDIAG to start it.
If the DEMLOG daemon is active, use the LOGTOOL utility in SYSDIAG
to determine which I/O subsystem is logging excessive errors.
SCSI: Async write error -- dev: b 31 0x022000, errno: 16, resid: 8192,
blkno: 32, sectno: 64, offset: 32768, bcount: 8192.
SCSI: Async write error -- dev: b 31 0x022000, errno: 16, resid: 8192,
blkno: 32, sectno: 64, offset: 32768, bcount: 8192.
4/0/3.2 tgt
4/0/3.2.0 sdis
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-15-2002 08:02 AM
02-15-2002 08:02 AM
Re: dmesg errors and disks
Check /var/adm/syslog/syslog.log, see if any specific errors are appearing there as well as 'dmesg'.
if so, look for possible 'lbolt' errors, which can be resolved to a Disk Device Name /dev/dsk/c1t2d3. Resolve this device to a SCSI address using 'ioscan -fn'.
Multiple failures can indicate a bad SCSI Card (as I just found out today).
Share and Enjoy! Ian Dennison
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-15-2002 08:09 AM
02-15-2002 08:09 AM
Re: dmesg errors and disks
There are some hardware errors. Use STM for checking all your hardwares.
See this for help:
http://www.docs.hp.com/hpux/onlinedocs/diag/stm/stm_qik.pdf
HTH,
Shiju
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-15-2002 08:12 AM
02-15-2002 08:12 AM
Re: dmesg errors and disks
Check your disk at /dev/dsk/c2t2d0. Seems like this might be giving problem.
hope this helps.
Regds
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-15-2002 08:20 AM
02-15-2002 08:20 AM
Re: dmesg errors and disks
Usually /dev/dsk/c2t2d0 is the cdrom, do you think that could cause a slow bdf? Possibly if it was mounted at the time...
C
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-15-2002 08:21 AM
02-15-2002 08:21 AM
Re: dmesg errors and disks
Sanjay has it -- you have a disk with problems.
Paula
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-15-2002 09:59 AM
02-15-2002 09:59 AM
Re: dmesg errors and disks
I just decoded the device that is giving problem,
SCSI: Async write error -- dev: b 31 0x022000, errno: 16, resid: 8192,
0x -> Major No.
02 -> Controller / bus
2 --> Target device
0 --> Lun No.
00 -> Flags
Hope this helps.
Regds
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-15-2002 10:07 AM
02-15-2002 10:07 AM
Re: dmesg errors and disks
I know how you decoded it, I am just bring up the issue of a possible cdrom and will it cause the same problems as a hard disk. Seeing as most disks are on different controllers and buses than a cdrom, what would the implications be?
C
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-15-2002 10:12 AM
02-15-2002 10:12 AM
Re: dmesg errors and disks
I cannot say anything about cdrom being at that address. I have a system where my cdrom is at c7t2d0. We can say anything about cdrom being at that place with certainity only after looking at the ioscan output.
Regards
Sanjay
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-15-2002 10:14 AM
02-15-2002 10:14 AM
Re: dmesg errors and disks
I'm sorry i didn't answer your question fully. I don't see any reason why a cdrom mounted should interfere with the bdf command. I have not seen something like that.
Regds
Sanjay