11-27-2009
What Solaris release are you using (cat /etc/release) ?
Were these crashes kernel panics ?
Are crash dumps enabled (coreadm) ? If true, is there a crash dump to analyse (/var/crash/<hostname>/unix.x & vmcore.x) ?
While supported, booting off a USB stick is AFAIK not a usual practice. I would recommend to create instead a mirror with two of you disks and install Solaris on it.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I have a TV and a monitor hooked up to my box. Right now the system is displaying all the information on the TV instead of the monitor, obviously I want to switch this, as the TV is very impracticle for everything other than watching movies.
I thought I remembered a command I used to use that... (2 Replies)
Discussion started by: Synbios
2 Replies
2. HP-UX
Hello All!
Where I work we have C3600's that have a video cards that have both DVI and Regular RBG type monitor ports on them. My question is: is it possible to spread my desktop across two monitors that are plugged into the one card much like you can do with NVIDIA software like NVIEW for... (0 Replies)
Discussion started by: giftedone
0 Replies
3. Linux
hiii,
in many of the linux machines i have tried this but the result is the same everywhere.
if there are double letters in a hostname then that is displayed as single letter.
e.g. if hostname is set to nepttune then login into the shell will display :
NEPTUNE(admin)@/
$ hostname... (15 Replies)
Discussion started by: shamik
15 Replies
4. AIX
Hello. I have an AIX machine at 6100-00.
We had some strange activity since filling up /tmp. One symptom is that who -r displays no output. It doesn't hang just no output is displayed.
We are going to boot the machine, but prior to that I'd like to dig a bit to see what may be causing the... (0 Replies)
Discussion started by: maficdan
0 Replies
5. Solaris
A new x86 server was installed with 16G of memory. The swap space assigned in the prtvtoc is also 16G. But after the installation of the OS and verifying, noticed df -k output for swap shows as 30G. Other systems do not have this characteristic. Whats wrong in here?:eek: (4 Replies)
Discussion started by: incredible
4 Replies
6. Filesystems, Disks and Memory
My ZFS on debian media server just died in a power outage, the zpool status shows this:
NAME STATE READ WRITE CKSUM
tank UNAVAIL 0 0 0 insufficient replicas
raidz1 UNAVAIL 0 0 0 corrupted data
sda ONLINE 0 0 0
sdb ONLINE 0 0 0
sdf ONLINE 0 0 0
sdh ONLINE 0 0 0
sdi ONLINE 0 0 0
sdk ONLINE 0... (2 Replies)
Discussion started by: mastersarg
2 Replies
7. UNIX for Dummies Questions & Answers
Hi,
ls -l displays the long listing of a file in 8 fields.
Query:
------
Does ls -l display the filename size in KB or MB or GB?
-rwxrwxr-x 1 xx dba 655 May 22 06:27 time
Here 655 is KB or MB or GB?
Many thanks. (2 Replies)
Discussion started by: venkatesht
2 Replies
8. Solaris
Hi,
I have a very frustrating issue! I hope you guys can assist
When a disk is presented out the iSCSI target display a lower disk capacity
SOLARIS VERSION is SOLARIS 10 05/09 Kernel Patch 139555-31
ISCSI Patch 119090-31, 141878-11
Unix Commands To discover Target
bash-3.00# i... (0 Replies)
Discussion started by: capitalexall
0 Replies
9. Solaris
when i use ls command it works normal but when i using additional parameter with ls like ls -l , ls -a... it shows a error followed by the output.
# ls -l
./hgfs: Operation not applicable
total 12861
-rw-r--r-- 1 root root 0 Jun 1 21:12 1
drwxr-xr-x 2 root root ... (4 Replies)
Discussion started by: chidori
4 Replies
10. Shell Programming and Scripting
I need to print out text from a file in the console up, you know someone like that? (8 Replies)
Discussion started by: gizmo16
8 Replies
LEARN ABOUT MINIX
savecore
savecore(1M) System Administration Commands savecore(1M)
NAME
savecore - save a crash dump of the operating system
SYNOPSIS
/usr/bin/savecore [-Lvd] [-f dumpfile] [directory]
DESCRIPTION
The savecore utility saves a crash dump of the kernel (assuming that one was made) and writes a reboot message in the shutdown log. It is
invoked by the dumpadm service each time the system boots.
savecore saves the crash dump data in the file directory/vmcore.n and the kernel's namelist in directory/unix.n. The trailing .n in the
pathnames is replaced by a number which grows every time savecore is run in that directory.
Before writing out a crash dump, savecore reads a number from the file directory/minfree. This is the minimum number of kilobytes that must
remain free on the file system containing directory. If after saving the crash dump the file system containing directory would have less
free space the number of kilobytes specified in minfree, the crash dump is not saved. if the minfree file does not exist, savecore assumes
a minfree value of 1 megabyte.
The savecore utility also logs a reboot message using facility LOG_AUTH (see syslog(3C)). If the system crashed as a result of a panic,
savecore logs the panic string too.
OPTIONS
The following options are supported:
-d Disregard dump header valid flag. Force savecore to attempt to save a crash dump even if the header information stored on
the dump device indicates the dump has already been saved.
-f dumpfile Attempt to save a crash dump from the specified file instead of from the system's current dump device. This option may be
useful if the information stored on the dump device has been copied to an on-disk file by means of the dd(1M) command.
-L Save a crash dump of the live running Solaris system, without actually rebooting or altering the system in any way. This
option forces savecore to save a live snapshot of the system to the dump device, and then immediately to retrieve the data
and to write it out to a new set of crash dump files in the specified directory. Live system crash dumps can only be per-
formed if you have configured your system to have a dedicated dump device using dumpadm(1M).
savecore -L does not suspend the system, so the contents of memory continue to change while the dump is saved. This means
that live crash dumps are not fully self-consistent.
-v Verbose. Enables verbose error messages from savecore.
OPERANDS
The following operands are supported:
directory Save the crash dump files to the specified directory. If directory is not specified, savecore saves the crash dump
files to the default savecore directory, configured by dumpadm(1M).
FILES
directory/vmcore.n
directory/unix.n
directory/bounds
directory/minfree
/var/crash/'uname -n' default crash dump directory
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO
adb(1), mdb(1), svcs(1), dd(1M), dumpadm(1M), svcadm(1M), syslog(3C), attributes(5), smf(5)
NOTES
The system crash dump service is managed by the service management facility, smf(5), under the service identifier:
svc:/system/dumpadm:default
Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). The ser-
vice's status can be queried using the svcs(1) command.
If the dump device is also being used as a swap device, you must run savecore very soon after booting, before the swap space containing the
crash dump is overwritten by programs currently running.
SunOS 5.10 25 Sep 2004 savecore(1M)