- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Disk diagnostics and problem solving
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
07-11-2003 08:43 AM
07-11-2003 08:43 AM
I see nothing in syslog/dmesg. Also, when I run STM I see only 'non-medium errors' on three of the disks. I was unable to see what this meant in the STM help files.
The question is what is the best way to determine the disk error, type, etc. The db vendor wanted me to run dd, but I have never done that as a diagnostic tool. The disks were created as raw. Ideas on running either fsck or stm's built in diagnostic tools?
Thanks in advance,
Doug
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-11-2003 08:49 AM
07-11-2003 08:49 AM
Solution# dd if=/dev/rdsk/c?t?d? of=/dev/null bs=2048k
If dd terminates abnormally then you have a disk problem.
DO NOT use fsck if these are raw volumes. fsck is designed for filesystem use only and may screw them up.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-11-2003 08:51 AM
07-11-2003 08:51 AM
Re: Disk diagnostics and problem solving
DD is actually a good tool for this.
There are two levels of I/O that need to be examined. If you are using LVM then it is possible that a single LVOL might span multiple disks.
dd if=/dev/vg02/rlvol1 bs=256k of=/dev/null
OR (to access a disk directly)
dd if=/dev/rdsk/c2t5d0 bs=256k of=/dev/null
I would choose the one that matches your backup scheme.
Man dd for details.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-11-2003 09:32 AM
07-11-2003 09:32 AM
Re: Disk diagnostics and problem solving
Check the disk with
dd if=/dev/rdsk/cXtXdX of=/dev/null bs=1024k
see if all the block readed.
Also check the disk with diskinfo if you
will get the info about the disk.
This way you will see if any hardware problems
You can use the sar to check the I/O of disk.
Caesar
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-30-2009 01:39 PM
04-30-2009 01:39 PM