07-11-2007
Quote:
Originally Posted by
akzin
could u guide me how to repair it?
The first step is "fsck", this tool does a filesystem check.
So run fsck /dev/...... on the device file for the volume that is failing and it should tell you what state the disk is in.
Can you see the man page for fsck on your system?
I suggest you start with something like....
/usr/sbin/fsck /dev/rrz0a
I am guessing at the device name, but there are two types of file for the data that underlies a file system, one is raw, one is block. I think you need the raw device.
10 More Discussions You Might Find Interesting
1. AIX
I understand that by putting in entries into the /etc/inittab file. We can actually call the our scripts during startup.
mkitab "start_server:2:once:sh /scripts/startserver.sh"
Would the system wait for startserver.sh finish executing before it goes to another entry? and how long would it... (1 Reply)
Discussion started by: vincente
1 Replies
2. Shell Programming and Scripting
I need to make a script to start the postfix service on a server when the machine starts up.
I have a script written below, which I think will work, but I am confused on how the rc2.d & rc3.d etc directories actually work.
If I enter the script below, and stick it in the rc3.d directory,... (1 Reply)
Discussion started by: BG_JrAdmin
1 Replies
3. Linux
I've created the following link in order to startup apache tomcat on startup, however, it does not seem to run. Am I missing something out?
:confused:
/etc/init.d
lrwxrwxrwx 1 root root 16 Sep 5 14:59 K73ypbind -> ../init.d/ypbind
lrwxrwxrwx 1 root root 16 Sep 11 13:09 S100tomcat ->... (5 Replies)
Discussion started by: jon80
5 Replies
4. HP-UX
Hi all
We have HP UX 11.23 installed on 4 RISC servers (2 oracle databases, 2 Oracle App Servers) , we are in a construction period , so the power failure may happen more than once a day.
I need to learn how to create an automatic startup services as in Windows, if we know that the services... (5 Replies)
Discussion started by: kafaween
5 Replies
5. AIX
Hi,
I am trying to start services on system reboot on AIX.
Have put the S* links under rd2.d & K* links under other rc*.d
At the moment, all scripts are getting called.
However, the services aren't coming up.
Where can i find the logs for these to check what failed. (8 Replies)
Discussion started by: vibhor_agarwali
8 Replies
6. UNIX for Dummies Questions & Answers
Hello,
I have to perform an audit of a system at work and I am looking at its /etc/rc3.d:
K01tog-pegasus K74nscd S08iptables S50openemm
K01yum K74ntpd S09isdn S55cups
K02NetworkManager K85mdmpd S09pcmcia S55sshd
K03rhnsd ... (8 Replies)
Discussion started by: mojoman
8 Replies
7. AIX
hi,
If we place Sxx (startup script) and Kxx(shutdown script) in /etc/rc.d/rc2.d,then it would start and stop automatically(assume they are linked to other script that actually starts/stops).
is there really a link needed here to /etc/rc.d/init.d? if not,what is the use of this directory..?... (1 Reply)
Discussion started by: to_bsr
1 Replies
8. UNIX for Advanced & Expert Users
Can someone please tell me how to run xsession startup scripts whenever I start or after I restart my X session? I'm not trying to do anything fancy I just want this to run. This makes life a lot easier when I use a dual monitor.
xrandr --output VGA1 --mode 1024x768 --rate 60 (7 Replies)
Discussion started by: cokedude
7 Replies
9. Solaris
Hi all,
I have a server in maintenance mode and need to boot it up. Its due to a broken service "RepX".
I need to stop the service from trying to start at boot up but i can't find where it is booting up from... it is not in any of the rcX.d directories and the two locations i have found it... (6 Replies)
Discussion started by: Tommyk
6 Replies
10. Shell Programming and Scripting
Edit: So sorry! I really didn't do a good job of clearly stating what I needed. Going to completely rewrite my post so everything is clearly stated.
I'm having trouble writing a shell startup script for a linux server. It uses the bash shell if I remember correctly. I'm trying to write it so... (9 Replies)
Discussion started by: Pyitoechito
9 Replies
esmd(1M) esmd(1M)
NAME
esmd - Essential Services Monitor (ESM) Daemon
SYNOPSIS
retry_seconds]
DESCRIPTION
The Essential Services Monitor (ESM) daemon, maintains the availability of essential system daemons by automatically restarting them if
they terminate. The ESM daemon monitors the Event Manager daemon, The ESM daemon is started by the init process when the system is ini-
tialized to run level 2 and continues to run until the system is shut down or returned to single user mode. Only one instance of can run
at a time.
Configuration information is sent to the ESM daemon by a control program, which is run at key points in the startup and shutdown proce-
dures. As startup or shutdown progresses, the control program updates the ESM state file, The control program then signals the daemon to
reconfigure itself.
On startup, state transitions occur after has started. On shutdown, transitions occur after each of these monitored daemons has termi-
nated. After each transition, the ESM daemon determines which of the monitored daemons should be running and adjusts its monitoring activ-
ities accordingly.
The ESM daemon reports all state change information, including notice of failures and restarts, through the system logging daemon, syslogd.
Messages are displayed on the system console during periods when syslogd is not running. See syslogd(1M) for more information.
If the ESM daemon fails to restart a monitored daemon, it reports the error by posting a high priority message through syslogd, and makes
no further restart attempts. The system administrator should investigate the problem and restart the failed daemon. The ESM daemon peri-
odically attempts to resume monitoring of the daemon, and posts an informational message when it succeeds. If the monitored daemon fails
again once monitoring has resumed, the ESM daemon again attempts to restart it.
The ESM daemon can be forced to restart a failed daemon by sending a SIGHUP signal to the process.
If there is a need to temporarily disable the ESM daemon for test purposes, in order to prevent the monitored daemons from being restarted
automatically, send a SIGSTOP signal to the process. To reactivate the ESM daemon, send a SIGCONT signal to the process. The ESM daemon
should never be disabled on a production system.
If the ESM daemon is terminated unexpectedly, it is restarted automatically by init.
Options
The command recognizes the following options:
Limit the priority of any syslog messages posted by the ESM daemon to "alert."
If this option is not specified, posts an "emergency" message if it cannot restart a failed daemon. A message may be sent to all
users currently logged in to the system. The option should only be used if the system administrator is actively monitoring syslogd
messages.
Specify the interval between attempts to begin monitoring a daemon
that has failed, and which has been unable to restart automatically. The default period is 30 seconds. Specifying a period of zero
disables retrying.
Notes
To use the start options, you must add them to the startup command in the file. The daemon reports any invalid start options with a single
generic message through syslogd.
Restrictions
The daemon terminates with an error message if it is started by any process other than init.
The /sbin/init.d/esm program is intended to be run by the system startup and shutdown process and should not be run from the command line.
Only one instance of can run at a time.
RETURN VALUE
The following exit values are returned:
0 (Zero) Successful completion.
not 0 An error occurred.
FILES
Executable file
Configuration control script
Initialization process control file
dispatched by boot init
Monitoring state file
Receives esmd status messages
AUTHOR
was developed by Hewlett Packard Company.
SEE ALSO
Commands
kill(1), evmd(1M), init(1M), syslogd(1M).
Files
inittab(4).
esmd(1M)