On Wed, 19 Jun 1996, Andrew Mickish wrote:
> I get the impression from this group that a lot of people are running AFS
> on Solaris 2.5. Did anyone else have an unusual install problem?
>
> Thanks,
>
> --Andrew Mickish
>
When installing from the manual under Solaris 2.4 and 2.5 -- at the point in
the install where you replicate your root.afs and root.cell volumes by doing
a vos release the system will panic and fry the whole nine yards when you
do the "fs checkvolumes".
I have hit it a few times. I finally got smart and wrote it in the book.
The fix is to release the root.cell and root.afs and then do a bos
shutdown and reboot the box. When you come back up you can then drive on
with the install.
I figured after 3 releases this would have been fixed, so I just shot
myself in the foot about 10 minutes ago. In big letters in my install
manual I wrote. REBOOT THE MACHINE BEFORE RUNNING "fs checkvolumes". Of
course I figured it was fixed by now. It wasn't. After lunch I get to
start over.
When this happens, it trashes the BosConfig file, and screws up the /afs
mount point. Then when it reboots the salvager runs to salvage the file
systems. This would be allright, except that it salvages forever. Seems
to be stuck in some kind of salvage loop. Until it salvages the
fileserver won't come up blah blah blah blah.
When AFS works it works great. It has been a real uphill battle getting
it that way. This is the 3rd time we have rebuilt the cell. At different
points in the install when have been able to panic the system. When it
happens it usually cooks things.
About 2 weeks ago we finally go the cell up and couldn't log into the
console, because the bosserver would not let go of the system console on
boot up. If you have this problem contact TransArc, they have a fix.
Unfortunately I don't have the manual in front of me to give you the page
numbers where the panic above occurs. Just remember that it is at the
point where you release root.afs and root.cell for the first time. What
ever you do, dont run the "fs checkvolumes" command that follows, or
you'll have to start over.
I'm not impressed :-(
Rick
