Sponsored Content
Full Discussion: Prediction of failures
Operating Systems Solaris Prediction of failures Post 302341282 by incredible on Wednesday 5th of August 2009 12:05:57 PM
Old 08-05-2009
Prediction of failures

Any diagnostic tool to do predictive check on all the SUN hard disks before it fails, as a preventive measure? Meaning, is there any tool that can really check for hdd which are failing/or "will fail soon" for Sun servers?
 

4 More Discussions You Might Find Interesting

1. HP-UX

Communication Failures

HI ALL, I have been trying to install a particular software using remote linux server. some thing like this: rsh <host ID> /usr/sbin/swinstall -x autoreboot=true -s /tmp/<software> <Product name>. The problem is whenever I try to install the product through a shell script the installation... (1 Reply)
Discussion started by: barun agarwal
1 Replies

2. Post Here to Contact Site Administrators and Moderators

Event Prediction - New Sports Events

Hi, Some sports predictions suggestions. Although the Celtics are still playing the Heat. Just being optimistic that they will win. Otherwise, please change to Heat. (9 Replies)
Discussion started by: ni2
9 Replies

3. Post Here to Contact Site Administrators and Moderators

Event Prediction - Euro 2012

Please add this new "event". (10 Replies)
Discussion started by: ni2
10 Replies

4. Solaris

11.0 to 11.2 update failures

Attempting to update an 11.0 server with many non-global zones installed. pkg publisher is pkg.oracle.com/solaris/support. FMRI = pkg://solaris/entire@0.5.11,5.11-0.175.1.15.0.4.0:20131230T203500Z When we run pkg update --accept the server contacts oracle, checks packages, finds about 700... (4 Replies)
Discussion started by: CptCarrot
4 Replies
note(4) 							   File Formats 							   note(4)

NAME
note - specify legal annotations SYNOPSIS
/usr/lib/note DESCRIPTION
Each file in this directory contains the NOTE (also _NOTE) annotations legal for a single tool. The name of the file, by convention, should be the tool vendor's stock name, followed by a hyphen, followed by the tool name. For example, for Sun's lock_lint tool the filename should be SUNW-lock_lint. The file should contain the names of the annotations understood by the tool, one per line. For example, if a tool understands the follow- ing annotations: NOTE(NOT_REACHED) NOTE(MUTEX_PROTECTS_DATA(list_lock, list_head)) then its file in /usr/lib/note should contain the entries: NOT_REACHED MUTEX_PROTECTS_DATA Blank lines, and lines beginning with a pound (#), are ignored. While /usr/lib/note is the default directory tools search for such files, they can be made to search other directories instead simply by setting environment variable NOTEPATH to contain the paths, separated by colons, of directories to be searched, e.g., /usr/mytool/note:/usr/lib/note. USAGE
These files are used by such tools whenever they encounter NOTEs they do not understand. If a file in /usr/lib/note contains the annota- tion, then it is valid. If no such file contains the annotation, then the tool should issue a warning complaining that it might be invalid. ENVIRONMENT VARIABLES
NOTEPATH specify paths to be searched for annotation files. Paths are separated by colons (":"). SEE ALSO
NOTE(3EXT) SunOS 5.11 17 Jan 1995 note(4)
All times are GMT -4. The time now is 05:17 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy