04-26-2015
The first thing to try, in case it's simply a poor contact problem, is to take out each memory module and plug it back in. Then test again to see if the problem has gone.
Next, divide the memory into two and remove one half completely and test. Then insert the other half and test. See which half has the fault.
You can then swap individual modules around until you identify the faulty one.
Be sure to adhere to the memory configuration rules for your hardware. Read the manual section about memory configuration.
Also, take precautions not to let static electricity damage the electronics.
10 More Discussions You Might Find Interesting
1. Debian
Hi All,
I am running my application on a dual cpu debian linux 3.0 (2.4.19 kernel).
For my application:
<sar -U ALL>
CPU %user %nice %system %idle
...
10:58:04 0 153.10 0.00 38.76 0.00
10:58:04 1 3.88 0.00 4.26 ... (0 Replies)
Discussion started by: jaduks
0 Replies
2. Solaris
Hi,
I found devices errors in #ioscan -En.
it is showing that soft errors = 0 and hard errors= 5.
what should i do for hard errors=0.
Thanks. (4 Replies)
Discussion started by: arjunreddy3
4 Replies
3. Shell Programming and Scripting
Hi,
I have line in input file as below:
3G_CENTRAL;INDONESIA_(M)_TELKOMSEL;SPECIAL_WORLD_GRP_7_FA_2_TELKOMSEL
My expected output for line in the file must be :
"1-Radon1-cMOC_deg"|"LDIndex"|"3G_CENTRAL|INDONESIA_(M)_TELKOMSEL"|LAST|"SPECIAL_WORLD_GRP_7_FA_2_TELKOMSEL"
Can someone... (7 Replies)
Discussion started by: shis100
7 Replies
4. UNIX for Advanced & Expert Users
Hi Experts,
I am executing "svn" checkout command through my java code on a freeBSD machine. SVN checkout gets started , but when I run "top" command on my freebsd machine, I have observed that "svn" processes are stuck in "pipewr" state.
Any pointer for this problem?
Thanks,
akash (0 Replies)
Discussion started by: akash.mahakode
0 Replies
5. BSD
Hi Experts,
I am executing "svn" checkout command through my java code on a freeBSD machine. SVN checkout gets started , but when I run "top" command on my freebsd machine, I have observed that "svn" processes are stuck in "pipewr" state.
Any pointer for this problem?
Thanks,
akash (0 Replies)
Discussion started by: akash.mahakode
0 Replies
6. Shell Programming and Scripting
I am just trying to read the password from command prompt that user should type with in 10 seconds,
I am getting "read: Illegal option -t"
#!/bin/bash ... (1 Reply)
Discussion started by: KarthikPS
1 Replies
7. Solaris
I keep getting "Too many open files" in /var/adm/messages that I do not know how to fix.
I've searched for solution on this forum and have increased the file descriptors limit but the problem persists.
The problem is happening in a solaris zone....
/var/adm/messages log example
May... (8 Replies)
Discussion started by: JT-KGY
8 Replies
8. Solaris
Hi Forum
please help me to fix M5000 Server which we were not using. now i logged to serve and foung that everything is showing as Deconfigured.
XSCF> showhardconf
SPARC Enterprise M5000;
+ Serial:BDF1051F30; Operator_Panel_Switch:Locked;
+ Power_Supply_System:Single;... (4 Replies)
Discussion started by: bentech4u
4 Replies
9. Solaris
Hi all, I have a LUN that is in "Online Busy" when I issue the dev_gestate subcommand of luxadm:
root@es088wb6:~# luxadm -v -e dev_getstate /dev/rdsk/c21t50050763090887FEd4s2
phys path = "/devices/pci@6c0/pci@1/pci@0/pci@4/SUNW,qlc@0/fp@0,0/ssd@w50050763090887fe,4:c,raw"
... (5 Replies)
Discussion started by: ludiegu
5 Replies
10. Shell Programming and Scripting
Hello.
System : opensuse leap 42.3
I have a bash script that build a text file.
I would like the last command doing :
print_cmd -o page-left=43 -o page-right=22 -o page-top=28 -o page-bottom=43 -o font=LatinModernMono12:regular:9 some_file.txt
where :
print_cmd ::= some printing... (1 Reply)
Discussion started by: jcdole
1 Replies
LEARN ABOUT OPENSOLARIS
fmd
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 appro-
priate, 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 interface; 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 transport.
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.11 17 Nov 2004 fmd(1M)