Thanks to Dr. Tom Blinn once again for his speedy response. He
suggested that either osf_boot of vmunix could be corrupted, and it
turned out that the root domain was corrupted as were many files
thereof. This is probably related to the second disk malfunctioning.
For anyone who doesn't konw the relationship between osf_boot and
vmunix (from Dr. Blinn):
"osf_boot is the "secondary bootstrap" program. It's read in from the
root directory by the primary bootstrap (in the disk boot blocks), and
then it loads the vmunix kernel."
I still don't know what the meaning of the "Internal limit reached"
message is supposed to be though.
Thanks again.
Original message:
----------------------------------------------------------------------
Has anyone seen this error:
Internal limit reached in OSF_BOOT: Out of space for pass2 segments
I have a 600au that currently will not boot, and gives the above
message early in the boot process, after the "New PAL Revision..."
line, and then fails. It is at 4.0D bl11.
Is this an OS variable that can somehow be reset, is it an OS
parameter that I would need to reinstall the OS in order to reset, or
does it refer to some hardware level error that cannot be reset?
As a brief history, this system has two disks. The second disk, of
user data, registers occasional SCSI errors. The first (boot) disk
does not have such errors. The system failed to boot two days ago, at
the same point in the boot process but without the pass2 error
message. At that time I could boot it from the OS disk, and then
remove disk 2 and boot it. I ended up changing termination on the
second disk (it had not been explicitly terminated, and it is at the
end on the SCSI chain), and it booted normally. I had thought that the
second disk was causing the problem, but today the system cannot boot
with the second disk removed either.
Thanks in advance.
----------------------------------------------------------------------
Received on Thu May 06 1999 - 18:09:18 NZST