 |
» |
|
|
|
It is now possible to recover from "Out of Disk Space"
during an Update. UPDATE will skip
any file if it cannot be added to LDEV 1. You will see error and status messages on the console at the
point the file is skipped and at the end of UPDATE.
At the end of the UPDATE, when
the system normally boots, the system will stop. The operator must
boot the machine manually. Messages will stay on the console including
a form of the following message. ERROR.
This UPDATE did not restore all files from the tape.(UPDERR
1001)
There were # files not restored because of out of disk space.
There were # files not restored for other than disk space
reasons.
There is more information about the error conditions in previous
messages.
START the system, create more free disk space and run this
UPDATE again.
Correct the problems and run this UPDATE again.
Correct the problems, START the system, create more free disk
space and run this UPDATE again.
END of LOAD(update). |
What You Should Do | |
Follow these steps to correct the problem: Determine the
reason the files were skipped. Start the system. Correct the problem. Shut the system down. Do the UPDATE again.
Files Skipped because Out of Disk SpaceIf there were files skipped because of an "Out of
Disk Space" error, look at the messages on the console
to determine which files were skipped. Confirm that
these three files have been restored to disk: ISL.MPEXL.SYS, MMSAVE.MPEXL.SYS, START.MPEXL.SYS |
Boot the system. Free some disk space on LDEV 1. Shut the system down. Redo the UPDATE
from the same tape.
(The files ISL.MPEXL.SYS
and MMSAVE.MPEXL.SYS are small
so there should not be a problem restoring them. The file START.MPEXL.SYS
is large, but under reasonable conditions instead of just skipping
it, the file DUMPAREA.MPEXL.SYS
is purged by UPDATE to make room
for START.MPEXL.SYS. If DUMPAREA.MPEXL.SYS
is purged, it will be replaced by UPDATE
when enough disk space is available.) Files Skipped Because of Other ReasonsIf files were skipped for other than disk space reasons, determine
the cause. There will be error and status messages on the console.
When a call to HPFOPEN returns an error status, that status is always
displayed on the console. This is the key to the cause of the problem.
Whatever the problem, it must be corrected. Correct the problems
that have been found. If there are still problems to correct, start the
system and correct them. If you started the system, shut the system down. UPDATE again from
the same tape.
If error messages have scrolled off the screen and you need
the information, try the UPDATE
again. The same conditions should exist and the same messages should
be generated. If a system experiences a problem and files have been skipped,
the system on disk is complete except for the skipped file or files.
It is safe to start the operating system. The system will not be
a mixed system on disk. The process of replacing files consists
of first purging the old file and then creating the new file. Any
errors that occur are found between the point where the old file
is purged and the new file is created. If the steps above do not resolve the problem, contact your
support representative. Trained Hewlett-Packard Response Center
engineers can recover some systems. When to Continue | |
If you have experienced problems during an Update, you can
continue when the following conditions are met: UPDATE
has completed successfully. All files from the SLT have been restored to disk. The system is up and running. There is some free space on LDEV 1.
|
