Sponsored Content
Operating Systems Linux Red Hat How to monitor HP server hard disk failure ? Post 302480207 by mtomar on Tuesday 14th of December 2010 08:31:59 AM
Old 12-14-2010
simplest solution is to check "dmesg"
Smilie
 

9 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. HP-UX

Disk Failure

I am new to being a Unix admin and have a question about replacing some hardware. I have a K class box using HP-UX 10.20 with three disks. Two of the drives are in one logical volume. Every 3 or 4 days, the syslog is showing that one of these drives is experiencing "POWERFAILED" and then recovering... (6 Replies)
Discussion started by: SemiOfCol
6 Replies

3. Shell Programming and Scripting

IInd Hard Disk Mounting Problem on 1st HDD On SCO UNIX Open Server

Hi Engg. ! :mad: I have a harddisk on which SCO UNIX Open Server was installed. There was some data (in .dbf format) on it. Present condition of HDD is that it is not booting. Now I want to mount this HDD through other HDD on which SCO UNIX Open Server is installed by attaching... (0 Replies)
Discussion started by: Niraj Gopal Sha
0 Replies

4. Solaris

Add new hard disk to sun sparc server?

A sparc server has a new SCSI hard disk added and labeled by the engineer, but they need to be formatted identically to an existing disk (c4t0d0). You decide to script the process and run from the command line without interaction. I know that the following command line must be achieve this. #... (3 Replies)
Discussion started by: kingsan
3 Replies

5. Shell Programming and Scripting

Need help on Linux script to monitor hard drive space

I'm new to Linux and have very limited experience with shell scripts in general. I am taking a class and I have to research online and come up with a shell script that monitors disk space. I also have to be able to explain it line by line. I've researched various sites and came across this shell... (3 Replies)
Discussion started by: wgreg23
3 Replies

6. SCO

declare disk driver for IDE hard disk

hi I've a fresh installation of SCO 5.0.7 on the IDE hard disk. For SCSI hard disk I can declare, for example blc disk driver using: # mkdev hd 0 SCSI-0 0 blc 0but it works for IDE hard disk? (3 Replies)
Discussion started by: ccc
3 Replies

7. Linux

C++ Code to Access Linux Hard Disk Sectors (with a LoopBack Virtual Hard Disk)

Hi all, I'm kind of new to programming in Linux & c/c++. I'm currently writing a FileManager using Ubuntu Linux(10.10) for Learning Purposes. I've got started on this project by creating a loopback device to be used as my virtual hard disk. After creating the loop back hard disk and mounting it... (23 Replies)
Discussion started by: shen747
23 Replies

8. AIX

Clone 1 Hard disk fromIBM Intellipoint server with AIX 5.x

Hello to all, Im having a new task in a new world (AIX - IBM Servers) I have an IBM Server (Type - 9111-285 very old one) with one Hard disk (73 GB 10 K) with AIX 5.x, and I need to clone the existing disk to another with the same specifications. Could you please give me some advice in order... (7 Replies)
Discussion started by: trevian3969
7 Replies

9. 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
DMESG(1)							   User Commands							  DMESG(1)

NAME
dmesg - print or control the kernel ring buffer SYNOPSIS
dmesg [options] dmesg --clear dmesg --read-clear [options] dmesg --console-level level dmesg --console-on dmesg --console-off DESCRIPTION
dmesg is used to examine or control the kernel ring buffer. The default action is to display all messages from the kernel ring buffer. OPTIONS
The --clear, --read-clear, --console-on, --console-off, and --console-level options are mutually exclusive. -C, --clear Clear the ring buffer. -c, --read-clear Clear the ring buffer after first printing its contents. -D, --console-off Disable the printing of messages to the console. -d, --show-delta Display the timestamp and the time delta spent between messages. If used together with --notime then only the time delta without the timestamp is printed. -E, --console-on Enable printing messages to the console. -e, --reltime Display the local time and the delta in human-readable format. Be aware that conversion to the local time could be inaccurate (see -T for more details). -F, --file file Read the syslog messages from the given file. Note that -F does not support messages in kmsg format. The old syslog format is sup- ported only. -f, --facility list Restrict output to the given (comma-separated) list of facilities. For example: dmesg --facility=daemon will print messages from system daemons only. For all supported facilities see the --help output. -H, --human Enable human-readable output. See also --color, --reltime and --nopager. -k, --kernel Print kernel messages. -L, --color[=when] Colorize the output. The optional argument when can be auto, never or always. If the when argument is omitted, it defaults to auto. The colors can be disabled; for the current built-in default see the --help output. See also the COLORS section below. -l, --level list Restrict output to the given (comma-separated) list of levels. For example: dmesg --level=err,warn will print error and warning messages only. For all supported levels see the --help output. -n, --console-level level Set the level at which printing of messages is done to the console. The level is a level number or abbreviation of the level name. For all supported levels see the --help output. For example, -n 1 or -n alert prevents all messages, except emergency (panic) messages, from appearing on the console. All levels of messages are still written to /proc/kmsg, so syslogd(8) can still be used to control exactly where kernel messages appear. When the -n option is used, dmesg will not print or clear the kernel ring buffer. -P, --nopager Do not pipe output into a pager. A pager is enabled by default for --human output. -r, --raw Print the raw message buffer, i.e. do not strip the log-level prefixes. Note that the real raw format depends on the method how dmesg(1) reads kernel messages. The /dev/kmsg device uses a different for- mat than syslog(2). For backward compatibility, dmesg(1) returns data always in the syslog(2) format. It is possible to read the real raw data from /dev/kmsg by, for example, the command 'dd if=/dev/kmsg iflag=nonblock'. -S, --syslog Force dmesg to use the syslog(2) kernel interface to read kernel messages. The default is to use /dev/kmsg rather than syslog(2) since kernel 3.5.0. -s, --buffer-size size Use a buffer of size to query the kernel ring buffer. This is 16392 by default. (The default kernel syslog buffer size was 4096 at first, 8192 since 1.3.54, 16384 since 2.1.113.) If you have set the kernel buffer to be larger than the default, then this option can be used to view the entire buffer. -T, --ctime Print human-readable timestamps. Be aware that the timestamp could be inaccurate! The time source used for the logs is not updated after system SUSPEND/RESUME. -t, --notime Do not print kernel's timestamps. --time-format format Print timestamps using the given format, which can be ctime, reltime, delta or iso. The first three formats are aliases of the time-format-specific options. The iso format is a dmesg implementation of the ISO-8601 timestamp format. The purpose of this for- mat is to make the comparing of timestamps between two systems, and any other parsing, easy. The definition of the iso timestamp is: YYYY-MM-DD<T>HH:MM:SS,<microseconds><-+><timezone offset from UTC>. The iso format has the same issue as ctime: the time may be inaccurate when a system is suspended and resumed. -u, --userspace Print userspace messages. -w, --follow Wait for new messages. This feature is supported only on systems with a readable /dev/kmsg (since kernel 3.5.0). -x, --decode Decode facility and level (priority) numbers to human-readable prefixes. -V, --version Display version information and exit. -h, --help Display help text and exit. COLORS
Implicit coloring can be disabled by an empty file /etc/terminal-colors.d/dmesg.disable. See terminal-colors.d(5) for more details about colorization configuration. The logical color names supported by dmesg are: subsys The message sub-system prefix (e.g. "ACPI:"). time The message timestamp. timebreak The message timestamp in short ctime format in --reltime or --human output. alert The text of the message with the alert log priority. crit The text of the message with the critical log priority. err The text of the message with the error log priority. warn The text of the message with the warning log priority. segfault The text of the message that inform about segmentation fault. SEE ALSO
terminal-colors.d(5), syslogd(8) AUTHORS
Karel Zak <kzak@redhat.com> dmesg was originally written by Theodore Ts'o <tytso@athena.mit.edu> AVAILABILITY
The dmesg command is part of the util-linux package and is available from Linux Kernel Archive <https://www.kernel.org/pub/linux/utils /util-linux/>. util-linux July 2012 DMESG(1)
All times are GMT -4. The time now is 09:52 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy