| Vince Zamora 2004-02-12, 3:35 am |
| Has anyone seen this error message when booting up? Any ideas in how
to correct it?
This is not a server I take care of, it's in one of our remote
offices, so I am not intimately familiar with it, that's why I come to
the experts for help.
Here's some background in what happened to the people in charge of it:
*** BEGIN QUOTE ***
I ran a script (as root) that included a line similar to
rm -f $TMP_HOME/*
Unfortunately, the $TMP_HOME was not defined, so, rm /*
The box is fairly clean, so I do not think may files were lost and it
did not have the -R option so the directories are still in place. Of
note that are missing were /bin and /dev. I am guessing they were
symbolic links, but not sure. Other stuff may be out of whack, but
those are the ones I have noticed so far.
What I have done so far:
ln -s /usr/bin /bin
ln -s /device /dev
ln -s /cluster/???0/dev/null /dev/null
This seemed to get it functional and responsive to most commands, but
I am guessing is incorrect. The biggest problem at this point is
there are no tty* entries in /dev, so I cannot open any additional
sessions.
** END QUOTE **
After which I suggested testing functionality and then figuring out
whether there was a way to reboot the server and reconfigure the
/dev/tty entries (something like the touch /reconfigure, which I am
not sure exists in Tru64)
But after they tried to reboot, this is what happened"
Advanced File System was not in use and no documented options like
that on the reboot or shutdown. The /cluster directory seemed to have
a mirror of the dev directory, so I copied that back to /dev and after
fixing a couple of links, everything seemed to be working. However,
afterwards I rebooted to make sure any startup sanity checks ran, and
the boot is failing.
console is showing a "slot context is not valid" message and then
bails out.
Still have not been able to locate the documents/disks that came with
the server.
Any ideas in how to fix this are most welcomed.
Thanks,
V Zamora
Hightstown, NJ
|