Sponsored Content
Operating Systems Solaris Solaris 11 - a retired device Post 302560771 by RychnD on Saturday 1st of October 2011 04:09:10 AM
Old 10-01-2011
I tried the
Code:
fmadm faulty

command but was not able to deduce the actual device from its output. I include the output below - would you be able to recognize the faulty device based on the information?

Thank you
Dusan

Code:
--------------- ------------------------------------  -------------- ---------
TIME            EVENT-ID                              MSG-ID         SEVERITY
--------------- ------------------------------------  -------------- ---------
Jul 06 11:31:07 6c7d5714-f4e9-ee90-ea2e-fe9cb600e069  PCIEX-8000-G2  Major

Host        : nas1
Platform    : X58A-UD5  Chassis_id  :
Product_sn  :

Fault class : fault.io.pciex.device-interr max 33%
              fault.io.pciex.device-noresp 17%
              fault.io.pciex.device-invreq 17%
              fault.io.pciex.bus-noresp 17%
Affects     : dev:////pci@0,0/pci8086,3408/pci-ide@0
              dev:////pci@0,0/pci8086,3408@1
                  faulted and taken out of service
FRU         : "MB" (hc://:product-id=X58A-UD5:server-id=nas1/motherboard=0) max 33%
                  faulty

Description : A problem has been detected on one of the specified devices or on
              one of the specified connecting buses.
              Refer to http://sun.com/msg/PCIEX-8000-G2 for more information.

Response    : One or more device instances may be disabled

Impact      : Loss of services provided by the device instances associated with
              this fault

Action      : Ensure that the latest drivers and patches are installed.
              Otherwise schedule a repair procedure to replace the affected
              device(s).  Use fmadm faulty to identify the devices or contact
              Sun for support.

 

2 More Discussions You Might Find Interesting

1. SCO

*retired*

I have a user with the value *RETIRED* on the password field (shadow file), what does it meands? is it block?, is it erased? Please i need the answer ASAP thanks (1 Reply)
Discussion started by: VLP
1 Replies

2. Solaris

How to get Device id information on solaris 8

Hi friends am writing a script to get the device id of i/o devices on solaris. The command iostat -iE works well on Solaris 5.9 and 5.10 but fails on solaris 5.8 as there is no 'i' switch with iostat command on this os Can anyone suggest me an alternate way to find device id information on... (3 Replies)
Discussion started by: vikashtulsiyan
3 Replies
fmd(1M)                                                   System Administration Commands                                                   fmd(1M)

NAME
fmd - fault manager daemon SYNOPSIS
/usr/lib/fm/fmd/fmd [-V] [-f file] [-o opt=val] [-R dir] DESCRIPTION
fmd is a daemon that runs in the background on each Solaris system. 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. When appropriate, the fault manager also sends a message to the syslogd(1M) service to notify an administrator that a problem has been detected. The message directs administrators to a knowledge article on Sun's web site, http://www.sun.com/msg/, which explains more about the problem impact and appropriate responses. Each problem diagnosed by the fault manager is assigned a Universal Unique Identifier (UUID). The UUID uniquely identifes this particular problem across any set of systems. The fmdump(1M) utility can be used to view the list of problems diagnosed by the fault manager, along with their UUIDs and knowledge article message identifiers. The fmadm(1M) utility can be used to view the resources on the system believed to be faulty. The fmstat(1M) utility can be used to report statistics kept by the fault manager. The fault manager is started automatically when Solaris boots, so it is not necessary to use the fmd command directly. Sun's web site explains more about what capabilities are cur- rently available for the fault manager on Solaris. OPTIONS
The following options are supported -f file Read the specified configuration file prior to searching for any of the default fault manager configuration files. -o opt=value Set the specified fault manager option to the specified value. Fault manager options are currently a Private inter- face; see attributes(5) for information about Private interfaces. -R dir Use the specified root directory for all pathnames evaluated by the fault manager, instead of the default root (/). -V Print the fault manager's version to stdout and exit. EXIT STATUS
The following exit values are returned: 0 Successful completion 1 An error occurred which prevented the fault manager from initializing, such as failure to open the telemetry trans- port. 2 Invalid command-line options were specified. FILES
/etc/fm/fmd Fault manager configuration directory /usr/lib/fm/fmd Fault manager library directory /var/fm/fmd Fault manager log directory ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWfmd | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
svcs(1), fmadm(1M), fmdump(1M), fmstat(1M), syslogd(1M), attributes(5), smf(5) http://www.sun.com/msg/ NOTES
The Fault Manager is managed by the service management facility, smf(5), under the service identifier: svc:/system/fmd:default The service's status can be queried using the svcs(1) command. Administrators should not disable the Fault Manager service. SunOS 5.10 17 Nov 2004 fmd(1M)
All times are GMT -4. The time now is 12:48 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy