11-24-2008
whats the status now? did you perform any fsck on the filesystem in single user?
Worse come to worst, you will need to do a reinstallation. Are u using the same jumpstart config for other systems running this solaris 10 update?
Last edited by incredible; 11-24-2008 at 11:27 AM..
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
help, what is the difference between core dump and panic dump? (1 Reply)
Discussion started by: aileen
1 Replies
2. UNIX for Advanced & Expert Users
I am importing data into a new database using bcp (ASE 11.0) on Solaris 5.7. I keep getting a core dump error when my ksh script attempts to load one table. All other tables load fine. If I load the table directly from the command line without a script the table loads fine.
Does anybody know... (1 Reply)
Discussion started by: gerald_agoi
1 Replies
3. UNIX for Dummies Questions & Answers
does any one have read a core dump?
is there any reader for that? or may i know what is the use of that core which takes sometimes memory in GBs?
:) (6 Replies)
Discussion started by: sskb
6 Replies
4. Programming
MY friends:
my program under sco unix have a problem?
it create a core dump file on the path when execute program ,
but i can't find the error of the C program ,i don't know how to
see the error about my program use core, please help me
or give me some suggest and what tools can use... (1 Reply)
Discussion started by: zhaohaizhou
1 Replies
5. Solaris
anybody know abt Segmentation Fault - core dumped in solaris 5.10..wats this error?? (4 Replies)
Discussion started by: sanjana
4 Replies
6. AIX
My application gives core dump. When i am debugging with dbx getting instructions below:
pthdb_session.c, 818: 695445 PTHDB_INTERNAL (internal error)
pthreaded.c, 1941: PTHDB_INTERNAL (internal error)
Illegal instruction (illegal opcode) in . at 0x0
warning: Unable to access address 0x0... (1 Reply)
Discussion started by: bapi
1 Replies
7. Programming
how to view core dumped file using gdb and how to extract information from the coredumped file.can we get similar information from the other utilites like strace or ptrace. (2 Replies)
Discussion started by: Manabhanjan
2 Replies
8. Solaris
Hi guys,
just want to know which core file pattern is best to set for core dumps:
1) per-process file name pattern
or
2) global file name pattern.
I will really appreciate an explanation why the chosen one is better.
Thanks a lot guys. (2 Replies)
Discussion started by: cjashu
2 Replies
9. Solaris
I have compiled GhostPDL that provides a shell script pcl2pdf that calls the executable pcl6.
pcl6 compiled with no errors using gmake and gcc. Running pcl2pdf generates a core dump when trying to convert a pcl file to pdf.
I have installed the Ghost fonts. Does anyone have GhostPDL compiled... (1 Reply)
Discussion started by: gduncan
1 Replies
10. Shell Programming and Scripting
Hi All,
I am doing Solaris packaging. I got core dump error while doing it. I have identified particular folder causing it but not sure about the reason. Without
that folder i can able to do the package. I have attached the proto file and other related files for your reference. Pls... (1 Reply)
Discussion started by: kamal_456
1 Replies
FSCK(1) General Commands Manual FSCK(1)
NAME
fsck, fsck1 - perform file system consistency check
SYNOPSIS
fsck [-aclmrs] [device] ...
OPTIONS
-a Automatically repair inconsistencies
-c Check and list only the specified i-nodes
-l List the files and directories in the filesytem
-r Prompt user for repairs if inconsistencies are found
-s List the superblock of the file system
EXAMPLES
fsck /dev/hd4 # Check file system on /dev/hd4
fsck -a /dev/at0 # Automatically fix errors on /dev/at0
fsck -l /dev/fd0 # List the contents of /dev/fd0
fsck -c 2 3 /dev/hd3
# Check and list /dev/hd3 i-nodes 2 & 3
DESCRIPTION
Fsck performs consistency checks on the file systems which reside on the specified devices. Fsck1 is an alternate version for use on obso-
lete V1 file systems. When either the -a or -r flags are given, the file system will be repaired if errors are found. Before running fsck
on a mounted file system, it must first be unmounted. Trying to repair a mounted file system is dangerous and should not be attempted.
To repair the root file system (which cannot be unmounted), first type CTRL-F9 at the console to kill any and all processes. Log back in
as root, type sync to force any buffered changes to disk, run fsck on the root file system and immediately reboot the computer by typing
reboot.
It is necessary to kill all processes before repairing the root file system to prevent them from modifying any disk blocks while fsck is
running. This is only necessary for the root file system, any other file system can simply be unmounted before it is checked.
SEE ALSO
mkfs(1), mount(1).
FSCK(1)