Sponsored Content
Full Discussion: Disk Failure
Operating Systems HP-UX Disk Failure Post 74055 by Perderabo on Tuesday 7th of June 2005 01:52:32 PM
Old 06-07-2005
Post the exact text of the error message. I would not immediately suspect a bad drive although it is possible. Does your manager have a good reason for suspecting a bad drive? A bad drive should be diagnosed from the hardware logs. Use the script command to record your session. Then as root, use the command: "cstm". From the cstm prompt, type "runutil logtool". Do a "sl" and pay attention to the output. It will tell you what the current log was renamed to. Type "sr", and when prompted, type in the name of that log. You will get a summary of the errors. Type "fr" to format the raw log. Now type "fl" to finally view the log.

Each logtool command is two letters and you type return after the two letters. If the commands wants more info, it will ask for it. To summarize the logtool commands:

sl [switch log]
sr [select raw]
fr [format raw]
fl [formatted log]

Then "quit" to get out of logtool. And "quit" to get out of cstm.


By the way, "powerfailed" sounds like a disk driver or a lvm driver thought an operation took too long. You might have an overloaded bus or an unreasonable timeout value. This is what I would be checking first.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Disk failure

is there anu way by which i can find out if all the disks on the system are working ? Milind Shauche. (2 Replies)
Discussion started by: shauche
2 Replies

2. Filesystems, Disks and Memory

Looking for a solution to disk failure!

Hi people, I have been using my disk for quite a long time but the other day I heard the drive making some noise and had to restart the system again. But when I did that the disk would not boot and I fear that the data might be deleted or lost. So, if you people have any know about the ways to get... (1 Reply)
Discussion started by: adam466
1 Replies

3. Filesystems, Disks and Memory

Looking for a solution to disk failure!

Hi people, I have been using my disk for quite a long time but the other day I heard the drive making some noise and had to restart the system again. But when I did that the disk would not boot and I fear that the data might be deleted or lost. So, if you people have any know about the ways to... (2 Replies)
Discussion started by: christopher4
2 Replies

4. Solaris

SAN disk failure

hi all, have a solaris 9 OS and a SAN disk which used to work fine is not getting picked up by my machine. can anyone point out things to check in order to troubleshoot this ?? thanks in advance. (3 Replies)
Discussion started by: cesarNZ
3 Replies

5. Red Hat

How to monitor HP server hard disk failure ?

in red hat 4, 5 any one know any commands or any scritps to monitor HP DL 380 G5/6 server and trigger alarm when hard disk failed. thanks for all support ---------- Post updated at 02:45 PM ---------- Previous update was at 12:00 PM ---------- does HP ProLiant Support Pack support is... (4 Replies)
Discussion started by: maxlee24
4 Replies

6. Solaris

Poor disk performance however no sign of failure

Hello guys, I have two servers performing the same disk operations. I believe one server is having a disk's impending failure however I have no hard evidence to prove it. This is a pair of Netra 210's with 2 drives in a hardware raid mirror (LSI raid controller). While performing intensive... (4 Replies)
Discussion started by: s ladd
4 Replies

7. UNIX for Advanced & Expert Users

RAID5 multi disk failure

Hi there, Don't know if my title is relevant but I'm dealing with dangerous materials that I don't really know and I'm very afraid to mess anything up. I have a Debian 5.0.4 server with 4 x 1TB hard drives. I have the following mdstat Personalities : md1 : active raid1 sda1 sdd1... (3 Replies)
Discussion started by: chebarbudo
3 Replies

8. Linux

Disk is predictive failure but LED is showing green.

Hi Linux Team we use hpacucli ctrl all show config command find out the failure disk. Here command output is showing predictive failure but The Datacenter team are unable to find the correct failure disk. From Datacenter all LEDs are showing green. Datacenter asks us to blink the LED. How... (2 Replies)
Discussion started by: Naveen.6025
2 Replies

9. Linux

0: Failure: (138) Device does not have a disk-config

Hi guys, Any idea why I am getting the below error ? # drbdsetup disk-options 0 --resync-rate=500M 0: Failure: (138) Device does not have a disk-config Some info is; # fdisk -l Disk /dev/sda: 64.4 GB, 64424509440 bytes 64 heads, 32 sectors/track, 61440 cylinders Units =... (0 Replies)
Discussion started by: Junaid Subhani
0 Replies

10. AIX

AIX hard disk failure

Hi all, I have encountered the issue with the hard disk, the disk is failed and need to replace by the new one. As my understanding, this is just to take out the failed disk and insert the new ones, and that's all. But the third party hardware vendor said, there should be another procedure... (9 Replies)
Discussion started by: Phat
9 Replies
xfs_logprint(8) 					      System Manager's Manual						   xfs_logprint(8)

NAME
xfs_logprint - print the log of an XFS filesystem SYNOPSIS
xfs_logprint [ options ] device DESCRIPTION
xfs_logprint prints the log of an XFS filesystem (see xfs(5)). The device argument is the pathname of the partition or logical volume con- taining the filesystem. The device can be a regular file if the -f option is used. The contents of the filesystem remain undisturbed. There are two major modes of operation in xfs_logprint. One mode is better for filesystem operation debugging. It is called the transactional view and is enabled through the -t option. The transactional view prints only the portion of the log that pertains to recovery. In other words, it prints out complete transactions between the tail and the head. This view tries to display each transaction without regard to how they are split across log records. The second mode starts printing out information from the beginning of the log. Some error blocks might print out in the beginning because the last log record usually overlaps the oldest log record. A message is printed when the physical end of the log is reached and when the logical end of the log is reached. A log record view is displayed one record at a time. Transactions that span log records may not be decoded fully. OPTIONS
-b Extract and print buffer information. Only used in transactional view. -c Attempt to continue when an error is detected. -C filename Copy the log from the filesystem to the file filename. The log itself is not printed. -d Dump the log from front to end, printing where each log record is located on disk. -D Do not decode anything; just print data. -e Exit when an error is found in the log. Normally, xfs_logprint tries to continue and unwind from bad logs. However, sometimes it just dies in bad ways. Using this option prevents core dumps. -f Specifies that the filesystem image to be processed is stored in a regular file at device (see the mkfs.xfs(8) -d file option). This might happen if an image copy of a filesystem has been made into an ordinary file with xfs_copy(8). -l logdev External log device. Only for those filesystems which use an external log. -i Extract and print inode information. Only used in transactional view. -q Extract and print quota information. Only used in transactional view. -n Do not try and interpret log data; just interpret log header information. -o Also print buffer data in hex. Normally, buffer data is just decoded, so better information can be printed. -s start-block Override any notion of where to start printing. -t Print out the transactional view. SEE ALSO
mkfs.xfs(8), mount(8). xfs_logprint(8)
All times are GMT -4. The time now is 12:55 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy