04-14-2005
Well you can't use another server emergency boot diskette becos the kernel is different from the server you intend to rescue. However, since you can enter with other users you can then try using the authck command to repair the file corrupted. After you have done that use the fixmog and the integrity command and reboot your system. Try this and let see the outcome.
8 More Discussions You Might Find Interesting
1. SCO
I know how to create the bootable tape image by using emergency_rec, but I could not find any document to instruct me on how to boot off the tape, and detail steps I should go through, for instance, at what point the booting sequency would prompt me to enter bootable path, and what the path is...... (0 Replies)
Discussion started by: vkky2k
0 Replies
2. Shell Programming and Scripting
I'm trying to write a script to push out to all our servers some Veritas add-ons. I want the script to push to all servers and if there server hardware matches the uname -i statement, it will install a additional add-on.. The script keeps giving me a error on line 29. Here is the script.... (3 Replies)
Discussion started by: soupbone38
3 Replies
3. Ubuntu
Hi guys
i have some question about ubuntu(10.10)
1.what time scheduling & page replacement algorithm have been used in ubuntu
2.how to create a process
3.how to kill a process
4.how to send information to a process
5.how to see a process
6.how to increase priority of a process
7.how to... (1 Reply)
Discussion started by: mortez28
1 Replies
4. Solaris
Hi Guru's,
I am unable to mount NFS share on unix system (DG/UX) which is nfs client.
Error:
mount: /nfsshare: Invalid argument
mount: giving up on:
/mountpoint
i tried following commands
mount -t nfs remotehost:/nfsshare /mountpoint
Error:
mount: /nfsshare: Invalid... (1 Reply)
Discussion started by: Justin John
1 Replies
5. Shell Programming and Scripting
can anyone please tell me that how can i boot unix from a cd? full procedure.
it's an emergency. reply asap (1 Reply)
Discussion started by: niket agarwal
1 Replies
6. SCO
We have old SCO Openserver 5.0.5. and its was running out of disk space on root disk - error 142 /2. I tried to move some files to another partition with space, but I ran into issue as I moved /opt/K and /opt/P. Now when the servers boots it fails and goes into debug mode.
I don't have a... (4 Replies)
Discussion started by: grips03
4 Replies
7. SCO
OS = Openserver 5.0.5
Ran 'mkdev fd' and made emergency boot floppy (boot and root). Choose custom kernel, not generic.
However kernel on the 1.44 floppy did not see both hard disks, it only saw the first one (SCSI id 0), and not SCSI id 1 (second disk)
Q. Is this a limitation of emergency... (5 Replies)
Discussion started by: grips03
5 Replies
8. SCO
In my previous thread post (which is also the most recent on this SCO forum), I mentioned that we have an HP DL380G5 server running SCO Unixware 7.11
which has unable to boot with error “FATAL BOOT ERROR: Can't load stage 3”.
..
Unfortunately no media is available for the machine and I think the... (1 Reply)
Discussion started by: BernP
1 Replies
LEARN ABOUT CENTOS
systemd-readahead-done.service
SYSTEMD-READAHEAD-REPLAY.SERVICE(8) systemd-readahead-replay.service SYSTEMD-READAHEAD-REPLAY.SERVICE(8)
NAME
systemd-readahead-replay.service, systemd-readahead-collect.service, systemd-readahead-done.service, systemd-readahead-done.timer, systemd-
readahead - Disk read ahead logic
SYNOPSIS
systemd-readahead-replay.service
systemd-readahead-collect.service
systemd-readahead-done.service
systemd-readahead-done.timer
/usr/lib/systemd/systemd-readahead/systemd-readahead [OPTIONS...] COMMAND [DIRECTORY | FILE]
DESCRIPTION
systemd-readahead-collect.service is a service that collects disk usage patterns at boot time. systemd-readahead-replay.service is a
service that replays this access data collected at the subsequent boot. Since disks tend to be magnitudes slower than RAM, this is intended
to improve boot speeds by pre-loading early at boot all data on disk that is known to be read for the complete boot process.
systemd-readahead-done.service is executed a short while after boot completed and signals systemd-readahead-collect.service to end data
collection. On this signal, this service will then sort the collected disk accesses and store information about them in /.readahead.
Normally, both systemd-readahead-collect.service and systemd-readahead-replay.service are activated at boot so that access patterns from
the preceding boot are replayed and new data collected for the subsequent boot. However, on read-only media where the collected data cannot
be stored, it might be a good idea to disable systemd-readahead-collect.service.
On rotating media, when replaying disk accesses at early boot, systemd-readahead-replay.service will order read requests by their location
on disk. On non-rotating media, they will be ordered by their original access timestamp. If the file system supports it,
systemd-readahead-collect.service will also defragment and rearrange files on disk to optimize subsequent boot times.
OPTIONS
systemd-readahead understands the following options:
-h, --help
Prints a short help text and exits.
--max-files=
Maximum number of files to read ahead. Only valid for thes collect command.
--file-size-max=
Maximum size of files in bytes to read ahead. Only valid for the collect and replay commands.
--timeout=
Maximum time in microseconds to spend collecting data. Only valid for the collect command.
COMMANDS
The following commands are understood by systemd-readahead:
collect [DIRECTORY]
Collect read-ahead data on early boot. When terminating, it will write out a pack file to the indicated directory containing the
read-ahead data.
replay [DIRECTORY]
Perform read-ahead on the specified directory tree.
analyze [FILE]
Dumps the content of the read-ahead pack file to the terminal. For each file, the output lists approximately how much will be read
ahead by the replay command.
SEE ALSO
systemd(1)
systemd 208 SYSTEMD-READAHEAD-REPLAY.SERVICE(8)