10-05-2009
looks like memory errors... but the AFSR and AFAR output needs to be decrypted to be sure where the problem comes from...
10 More Discussions You Might Find Interesting
1. Solaris
Got an curious issue.
I applied 109147-39 to, oh 15 or so various systems all running Jumpstarted Solaris 8. When I hit the first two V440s, they both failed with Return code 139. All non shell commands segfaulted from then on.
The patch modified mainly the linker libraries and commands.
... (2 Replies)
Discussion started by: BOFH
2 Replies
2. Solaris
Hello,
I hope you can help me. I am new to Sun servers and we have a Sun Fire v440 server in which one power supply failed, we are waiting for new one. But now our server is shutting down constantly. Is there any setting with which we can prevent this behaviour? (1 Reply)
Discussion started by: Tibor
1 Replies
3. Solaris
Hi Guyz,
I recently downloaded sol-10-u6-ga1-sparc-dvd.iso from Sun. I burned the disk as cd .iso.
When trying to boot at the ok> boot cdrom
i get the following error:
-----------------------------------------------------------------------
Boot device:... (2 Replies)
Discussion started by: Mwamba
2 Replies
4. Solaris
First of all it's shut down 60 second after power on and write on console :
SC Alert: Correct SCC not replaced - shutting managed system down!
This is cured by moving out battery from ALOM card.
Now server start to loop during the testing.
That's on the console:
>@(#) Sun Fire V440,Netra... (14 Replies)
Discussion started by: Alisher
14 Replies
5. Solaris
Hi,
I was asked to connect a KVM screen to a Sun Fire V440 last night so I connected it up but no joy and nothing on the KVM screen. I was told that a reboot may fix the problem so connected to the ALOM and rebooted. On the plus side, the KVM screen now works but I lost the ALOM connection.
... (0 Replies)
Discussion started by: jimmy54321
0 Replies
6. Solaris
Hi:
I bougth an used Sun Fire v440, and It have a firmware password. When I turn on the server, it ask for firmware password. (I don 't know what is the correct password). I can access to SC, but when I want to access to OBP, Firmware Password appears again. I remove the battery for two hours,... (1 Reply)
Discussion started by: mguazzardo
1 Replies
7. Solaris
Dear Team,
I need some expert advice to my problem.
We have a Sun Fire v440 in our customer Place. Server is working fine and no hardware deviations are found except one problem that processors generating too much heat. I have verified and found that the room temperature was 26-27 degree.... (5 Replies)
Discussion started by: sudhansu
5 Replies
8. Solaris
Hi,
I have Sun Fire V440. Boot disks are mirrored. system crashed and it's not coming up. Error message is
Insufficient metadevice database replicas located. Use Metadb to delete databases which are broken.
Boot disks are mirrored and other disks are ZFS configuration. Please... (2 Replies)
Discussion started by: samnyc
2 Replies
9. Solaris
Hi,
I have a SUN Fire V440 server running Solaris 8. One of the 4 disks do not appear when issued the format command. The "ready to remove" LED is not on either.
Metastat command warns that this disk "Needs maintenace". Can I just shutdown and power off the machine and then insert an... (5 Replies)
Discussion started by: Echo68
5 Replies
10. Solaris
Hi,
I have a Sun Fire V440 server that fails to boot up correctly. A lot of services are not started and the sytems acts really slow to commands. During boot I can see the following Error:
WARNING: /pci@1f,700000/scsi@2/sd@0,0 (sd1):
SCSI transport failed: reason 'reset': retrying... (15 Replies)
Discussion started by: oliwei
15 Replies
LEARN ABOUT OSF1
filterlog
filterlog(8) System Manager's Manual filterlog(8)
NAME
filterlog - Logs and reports system Correctable Read Data (CRD) memory errors on specific systems.
SYNOPSIS
/usr/sbin/filterlog [-l] [-d crdlog] [-d crdlifetime] [-s crdlength #] [-s crdcount #] [-h]
OPTIONS
Logs or filters an entry from stdin. This option is used by the binary event-log daemon, binlogd. Dumps the contents of the CRD log file
in text format. Errors shown in the file are those recorded by the system since the last boot. Dumps the CRD lifetime log information in
text format. Used to set the CRD interval time in minutes. The default is 24 hours. Used to set the CRD interval count. The default is
50. Prints a list of the command option options defined in this reference page.
DESCRIPTION
This utility ensures that only genuine memory errors are reported to system log files on certain system types. The command filterlog is
called directly by the binary event-log daemon, binlogd to filter system CRD (memory hardware) errors. CRD errors are logged according to
user-definable parameters. If it is determined that a genuine memory problem exists, an entry is passed to binlogd. The error will then
be written to the system's error log file and can be notified to the user through DECevent.
The filterlog utility uses two variables to determine if a CRD error signifies a genuine memory hardware problem -- crdlength and crdcount.
If crdcount number of errors occur during crdlength minutes, an entry is passed to binlogd. The default settings are 50 errors in 24 hours
(1440 minutes).
The filterlog utility reads the /etc/binlog.conf file to determine what log file should be used to record any events. The default log file
is /usr/adm/binary.crdlog.
SEE ALSO
Commands: binlogd(8), dia(8) (DECevent)
filterlog(8)