11-05-2009
Quote:
Originally Posted by
vettec3
Did the server actually panic I cant see any panic string.
The problems I see could have made the server sluggish or hang it.
The first messages has to do with veritas volumemanager/filesystem
and you are having problems with the fibre connection to the SUN3510 raid.
I would update HBA card driver (sun would probably tell you to ugrade tha SAN "package" its varios patches) ,firmware in the 3510 array and check
fibre cables and "GBICS"
Actually yes, the server crash, and under /var/crash I have unix.0, vmcore.0 , and bounds files.
3510 FC firmware is latest.
I agree regarding the driver, I found the server patch level is kind of old, so my colleague installed the latest patches and upgraded drivers. He kept it under observation.
9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I still haven't got an answer to this question...
Excerpt from My SysAd Blog
A colleague of mine is having a problem with a Sun Fire v1280 server crashing. He tried Googling for the error message in red but hasn't found anything yet. Your insights would be greatly appreciated.
"cannot... (2 Replies)
Discussion started by: esofthub
2 Replies
2. UNIX for Dummies Questions & Answers
Hello all,
I'm lost and can't figure this problem out.
I have a Sun fire 280R running Solaris 8. Everything was working great. I have one drive in bay 1(not 0). But when I reboot the system it trys to open files in /dev/rdsk/c1t1d0s0. Should it have been opeing /dev/rdsk/c1t0d0s0, the... (4 Replies)
Discussion started by: larryase
4 Replies
3. Solaris
Hello, I'm trying to fix this server System Board (CPU/Memory Unit). The error indicates that its missing 3.3VDC. So far all the fuses and caps have been checked. I new at this type of machine, need help for idea on this system. Thank you in advance.
Vu (0 Replies)
Discussion started by: vhtran
0 Replies
4. Solaris
During system startup the following warnings are appear.
Warning: /pci@8, 700000/scsi@6, 1 (g1m1)
Connected command timeout for target 9.0
Warning: /pci@8, 700000/scsi@6, 1 (g1m1)
Target 9 reducing sync, transfer rate
Warning: /pci@8, 700000/scsi@6, 1... (5 Replies)
Discussion started by: tabreaz
5 Replies
5. Solaris
I am new to Sun.
I brought Sun Fire 280R to practice UNIX. What are the requirements for the monitor/CRT? Will it burn out old non-Sun CRTs? Does it need LCD monitor?
Thanks. (3 Replies)
Discussion started by: bramptonmt
3 Replies
6. Solaris
Hi men,
Have you ever meet this error ?
I install full Sun MC 4.0 packages (+ Add ons) exception of Sun Midrange Platform Administration because i don't know how to configure it
Then all other servers are ok, only E2900 servers have Config reader module error: Data Acquisition error
I... (12 Replies)
Discussion started by: tien86
12 Replies
7. Solaris
I am running Sun Explorer to collect data, but /proc is very big in size so it is takin time to get completed. (Running from past 3 hours). I ran -->
/opt/SUNWexplo/bin/explorer -w all,zones
root@tsrim03:/# ps -ef | grep -i explo
root 27623 6539 0 06:28:59 pts/1 0:03 ksh -p... (1 Reply)
Discussion started by: solaris_1977
1 Replies
8. Solaris
several newbie questions:
> how-to find serialnumber for Sun E2900
prtdiag -v does not show chassis serial number
> LOM is not connectable .
Are there any tools to get automatically Serial numbers for HW.
Thanks ! (7 Replies)
Discussion started by: magedfawzy
7 Replies
9. Solaris
Hello,
I have purchaced an old SUn fire x2270 server .
I wanted to make ILOM upgrade to the latest version of software :
ILOM 3.0.9.18.a r126592
BIOS vers. 2.09
Server 2.2.3
(10-Aug-2018)
Because my version is very outdated.
But i can't download the updatebecause it's require... (4 Replies)
Discussion started by: LouisLakoute
4 Replies
crashdc(8) System Manager's Manual crashdc(8)
NAME
crashdc - Diagnostic data collection for a running or crashed system
SYNOPSIS
/usr/bin/crashdc [system-kernel] [core-image]
DESCRIPTION
The crashdc utility examines the core image of the operating system to extract critical diagnostic data. This utility is a shell script
that invokes several tools and commands that extract selected parameters of a running or a crashed system (for example, system configura-
tion, running processes, and panic messages).
The arguments to the crashdc utility are the system kernel and the core image. The default values are /vmunix and /dev/mem, respectively.
If you specify no arguments, the crashdc utility examines the running system.
The system usually invokes the crashdc utility during system startup. If the most recent core dump has been saved by the savecore command,
both the core image and the system kernel (respectively vmcore.n and vmunix.n, where the variable n is the crash number) are saved in the
crash directory (by default, /var/adm/crash). Also, the crashdc utility saves the output as the file crash-data.n (where the variable n is
the crash number) in the crash directory. The crashdc utility is invoked only if crash-data.n output in the crash directory does not exist
or is not from the most recent crash.
FILES
Default core image Default system image Output from crashdc
SEE ALSO
Commands: dbx(1), kdbx(8), savecore(8)
crashdc(8)