[OmniOS-discuss] Fault Manager component could not load

[Matthew Lagoe]

Is there anything I can do then to work around this issue on the Seagate
drives?

At the moment the only reason it is working is because it broke fmd, if I
enable fmd it causes my whole storage to go out of commission :(

Any assistance is greatly apreaciated.

-----Original Message-----
From: OmniOS-discuss [mailto:omnios-discuss-bounces at lists.omniti.com] On
Behalf Of Ian Kaufman
Sent: Monday, September 22, 2014 06:17 PM
To: omnios-discuss
Subject: Re: [OmniOS-discuss] Fault Manager component could not load

AFAIK, this has not been implemented yet in the Open Source community.

Ian

On Mon, Sep 22, 2014 at 5:44 PM, Matthew Lagoe <matthew.lagoe at subrigo.net>
wrote:
> I tried to add "setprop temp-multiple 0" to 
> /usr/lib/fm/fmd/plugins/disk-transport.conf due to a bug in Seagate 
> drives, however when I start up the machine with that configuration in 
> it I get the following error, if anyone has any ideas what the cause could
be.
>
> Thanks
>
> --------------- ------------------------------------  --------------
> ---------
> TIME            EVENT-ID                              MSG-ID
> SEVERITY
> --------------- ------------------------------------  --------------
> ---------
> Sep 22 17:10:10 e0719be1-fe87-6a27-cb4c-aaf2f8902a13  FMD-8000-3F    Minor
>
>
> Host        : stor10
> Platform    : PowerEdge-R720    Chassis_id  : FCNH3W1
> Product_sn  :
>
> Fault class : defect.sunos.fmd.config
> Affects     : fmd:///module/disk-transport
>                   faulted and taken out of service
> FRU         : None
>                   faulty
>
> Description : A Solaris Fault Manager component could not load due to an
>               erroroneous configuration file.  Refer to
>               http://illumos.org/msg/FMD-8000-3F for more information.
>
> Response    : The module has been disabled.  Events destined for the
module
>               will be saved for manual diagnosis.
>
> Impact      : Automated diagnosis and response for subsequent events
> associated
>               with this module will not occur.
>
> Action      : Use fmdump -v -u  to locate the module.  Use fmadm load
>                to load the module after repairing its configuration.
>
>
>
>
>
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss



--
Ian Kaufman
Research Systems Administrator
UC San Diego, Jacobs School of Engineering ikaufman AT ucsd DOT edu
_______________________________________________
OmniOS-discuss mailing list
OmniOS-discuss at lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss