Sponsored Content
Operating Systems Solaris Hardware faulty, but which hardware? Post 302577742 by dehetoxic on Tuesday 29th of November 2011 08:48:44 PM
Old 11-29-2011
by the way, I run the fmadm repaired all i got is this

Code:
fmadm: failed to record repair to 60dfafdd29-5456-4c21-eeda-8afafd6f61b8: specified resource is not known to be faulty

 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Hardware

Hi I have a problem to start up my Solaris Ultra 5. When it boots up I get a strange clicking sound, sounds like the hard drive that is "thinking" very hard. On the screen I get these messages: Boot device: Files and Args: Please check cable and try again Network link setup fail Time out... (8 Replies)
Discussion started by: Orange
8 Replies

2. UNIX Desktop Questions & Answers

hardware 3d

How do I check my system to see if the graphics are using hardware 3d suport or not. I have a TNT2 on RH 7.1 kernel 2.4.9-?(can't remember off top of my head)I'm running all the latest updates from RH. Also I now have a dvd drive and I am trying to find a player that will play all movies and not... (1 Reply)
Discussion started by: MaxCat
1 Replies

3. UNIX for Dummies Questions & Answers

Per and Hardware

Is it possible to use Perl to work with hardware? Or is it strictly for text processing. (1 Reply)
Discussion started by: Luftwaffe
1 Replies

4. Programming

C and hardware !

Hello ! I have a friend , in one day he tell me this : some guy made a cool program in C , for some sort or hardware control . I say : wow ! Maybe someone , can give me an example , how can C control hardware so good ( as I hear ) , and maybe some cool information , where to learn the idea ,... (1 Reply)
Discussion started by: !_30
1 Replies

5. Solaris

Hardware

Hi, I'm looking to run Sun Solaris 8 or 9, but have been running windows :mad: .can anyone give me advice about the hardware needed for solaris and possably any software i may need, the type of model and where i may be able to buy these within the uk. :confused: ... (3 Replies)
Discussion started by: franz
3 Replies

6. Solaris

hardware problem?

Can someone tell me what the following means? We have a v440 running Solaris 9. What do the patterns actually mean? May 17 12:12:03 ibasdb02 cediag: Revision: 1.78 @ 2005/02/11 15:5 :29 UTC May 17 12:12:03 ibasdb02 cediag: Analysed System: SunOS 5.9 with UP 117171-17 (MPR active) May 17... (5 Replies)
Discussion started by: hshapiro
5 Replies

7. AIX

New Hardware

Can someone help me with what I am guessing is a simple job for an AIX admin. However I am 100% HP-UX and not touched AIX before the start of this week. I am trying to connect an IBM Blade (JS22) to our HP Enterprise Tape Library. I have done all the SAN zoning and this appears to be happy... (5 Replies)
Discussion started by: Andyp2704
5 Replies

8. Virtualization and Cloud Computing

Hardware virtualization

Hello to all In my organization we want to pass to move the systems to an virtualized environment, nevertheless, considering the absence of resources, the idea is to acquire the versers and that the department (I) do the facilities, tests, etc. Wearing out the possible minimal cost in... (1 Reply)
Discussion started by: aalvarez77
1 Replies

9. Solaris

Porting to new hardware - best way?

Same version of Solaris etc. Moving to new hardware. The application that runs on this server is easy enough to re-install but Im concerned about things like:- 1. Users/passwords/home directories 2. Cron jobs 3. Static routes Is there ANY way to either export this sort of thing so that I... (6 Replies)
Discussion started by: psychocandy
6 Replies

10. Solaris

[solved] How to blink faulty disk in Solaris hardware?

Hi Guys, One of two disks in my solaris machine has failed, the name is disk0, this is SUN physical sparc machine But I work remotely, so people working near that physical server are not that technical, so from OS command prompt can run some command to bink faulty disk at front panel of Server.... (9 Replies)
Discussion started by: manalisharmabe
9 Replies
fmadm(1M)						  System Administration Commands						 fmadm(1M)

NAME
fmadm - fault management configuration tool SYNOPSIS
fmadm [-q] [subcommand [arguments]] DESCRIPTION
The fmadm utility can be used by administrators and service personnel to view and modify system configuration parameters maintained by the Solaris Fault Manager, fmd(1M). fmd receives telemetry information relating to problems detected by the system software, diagnoses these problems, and initiates proactive self-healing activities such as disabling faulty components. fmadm can be used to: o view the set of diagnosis engines and agents that are currently participating in fault management, o view the list of system components that have been diagnosed as faulty, and o perform administrative tasks related to these entities. The Fault Manager attempts to automate as many activities as possible, so use of fmadm is typically not required. When the Fault Manager needs help from a human administrator, service repair technician, or Sun, it produces a message indicating its needs. It also refers you to a knowledge article on Sun's web site, http://www.sun.com/msg/. The web site might ask you to use fmadm or one of the other fault manage- ment utilities to gather more information or perform additional tasks. The documentation for fmd(1M), fmdump(1M), and fmstat(1M) describe more about tools to observe fault management activities. The fmadm utility requires the user to possess the SYS_CONFIG privilege. Refer to the for more information about how to configure Solaris privileges. The fmadm load subcommand requires that the user possess all privileges. SUBCOMMANDS fmadm accepts the following subcommands. Some of the subcommands accept or require additional options and operands: fmadm acquit fmri | label [uuid] Notify the Fault Manager that the specified resource is not to be considered to be a suspect in the fault event identified by uuid, or if no UUID is specified, then in any fault or faults that have been detected. The fmadm acquit subcommand should be used only at the direction of a documented Sun repair procedure. Administrators might need to apply additional commands to re-enable a previously faulted resource. fmadm acquit uuid Notify the Fault Manager that the fault event identified by uuid can be safely ignored. The fmadm acquit subcommand should be used only at the direction of a documented Sun repair procedure. Administrators might need to apply additional commands to re-enable any previ- ously faulted resources. fmadm config Display the configuration of the Fault Manager itself, including the module name, version, and description of each component module. Fault Manager modules provide services such as automated diagnosis, self-healing, and messaging for hardware and software present on the system. fmadm faulty [-afgiprsv] [-n max] [-u uid] Display status information for resources that the Fault Manager currently believes to be faulty. The following options are supported: -a Display all faults. By default, the fmadm faulty command only lists output for resources that are currently present and faulty. If you specify the -a option, all resource information cached by the Fault Manager is listed, including faults which have been automatically corrected or where no recovery action is needed. The listing includes information for resources that might no longer be present in the system. -f Display faulty fru's (Field replaceable units). -g Group together faults which have the same fru, class and fault message. -i Display persistent cache identifier for each resource in the Fault Manager. -n max If faults or resources are grouped together with the -a or -g options, limit the output to max entries. -p Pipe output through pager with form feed between each fault. -r Display Fault Management Resource with their Identifier (FMRI) and their fault management state. -s Display 1 line fault summary for each fault event. -u uid Only display fault with given uid. -v Display full output. The percentage certainty is displayed if a fault has multiple suspects, either of different classes or on different fru's. If more than one resource is on the same fru and it is not 100% certain that the fault is associated with the fru, the maximum percentage certainty of the possible suspects on the fru is displayed. The Fault Manager associates the following states with every resource for which telemetry information has been received: ok The resource is present and in use and has no known problems so far as the Fault Manager is concerned. unknown The resource is not present or not usable but has no known problems. This might indicate the resource has been disabled or deconfigured by an administrator. Consult appropriate management tools for more information. faulted The resource is present but is not usable because one or more problems have been diagnosed by the Fault Manager. The resource has been disabled to prevent further damage to the system. degraded The resource is present and usable, but one or more problems have been diagnosed in the resource by the Fault Manager. If all affected resources are in the same state, this is reflected in the message at the end of the list. Otherwise the state is given after each affected resource. fmadm flush fmri Flush the information cached by the Fault Manager for the specified resource, named by its FMRI. This subcommand should only be used when indicated by a documented Sun repair procedure. Typically, the use of this command is not necessary as the Fault Manager keeps its cache up-to-date automatically. If a faulty resource is flushed from the cache, administrators might need to apply additional commands to enable the specified resource. fmadm load path Load the specified Fault Manager module. path must be an absolute path and must refer to a module present in one of the defined direc- tories for modules. Typically, the use of this command is not necessary as the Fault Manager loads modules automatically when Solaris initially boots or as needed. fmadm unload module Unload the specified Fault Manager module. Specify module using the basename listed in the fmadm config output. Typically, the use of this command is not necessary as the Fault Manager loads and unloads modules automatically based on the system configuration fmadm repaired fmri | label Notify the Fault Manager that a repair procedure has been carried out on the specified resource. The fmadm repaired subcommand should be used only at the direction of a documented Sun repair procedure. Administrators might need to apply additional commands to re-enable a previously faulted resource. fmadm replaced fmri | label Notify the Fault Manager that the specified resource has been replaced. This command should be used in those cases where the Fault Man- ager is unable to automatically detect the replacement. The fmadm replaced subcommand should be used only at the direction of a docu- mented Sun repair procedure. Administrators might need to apply additional commands to re-enable a previously faulted resource. fmadm reset [-s serd] module Reset the specified Fault Manager module or module subcomponent. If the -s option is present, the specified Soft Error Rate Discrimina- tion (SERD) engine is reset within the module. If the -s option is not present, the entire module is reset and all persistent state associated with the module is deleted. The fmadm reset subcommand should only be used at the direction of a documented Sun repair pro- cedure. The use of this command is typically not necessary as the Fault Manager manages its modules automatically. fmadm rotate errlog | fltlog The rotate subcommand is a helper command for logadm(1M), so that logadm can rotate live log files correctly. It is not intended to be invoked directly. Use one of the following commands to cause the appropriate logfile to be rotated, if the current one is not zero in size: # logadm -p now -s 1b /var/fm/fmd/errlog # logadm -p now -s 1b /var/fm/fmd/fltlog OPTIONS
The following options are supported: -q Set quiet mode. fmadm does not produce messages indicating the result of successful operations to standard output. OPERANDS
The following operands are supported: cmd The name of a subcommand listed in SUBCOMMANDS. args One or more options or arguments appropriate for the selected subcommand, as described in SUBCOMMANDS. EXIT STATUS
The following exit values are returned: 0 Successful completion. 1 An error occurred. Errors include a failure to communicate with fmd or insufficient privileges to perform the requested operation. 2 Invalid command-line options were specified. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWfmd | +-----------------------------+-----------------------------+ |Interface Stability |See below. | +-----------------------------+-----------------------------+ The command-line options are Committed. The human-readable output is not-an-interface. SEE ALSO
fmd(1M), fmdump(1M), fmstat(1M), logadm(1M), syslogd(1M), attributes(5) http://www.sun.com/msg/ SunOS 5.11 22 Oct 2008 fmadm(1M)
All times are GMT -4. The time now is 09:02 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy