I have a two server set up in a high school using managed clients. One
server is the authenticaion server and the other hosts the home
directories and several common sharepoints. The home directory server
has two hard drives in it. One is partitioned into two parts, one for
the OS and the other for several sharepoints. The second hard drive is
for the user directories.
AFP services shut down on my home directory server this afternoon
(never has happened before). When I restarted the server it came up
very quickly but nobody was able to connect to their home directories.
I restarted the server a second time and this time it spent 20 minutes
starting hanging at a message that said something like "waiting for
local drives" I have had this happen before when the server shut down
due to power loss (bad UPS)
When it came up I was able to log at a client machine but my document
folder was empty. This was true for any user I tried. Logged in as
root on the server and checked my document folder and all documents
were there.
Logged back in on a client to an empty document folder. I saved a
document and then logged out and back in on a different machine and the
test document was there but no others. Went to the server and the new
document was not in my document folder.
Did some searching on the server and found out that in the OS
partition there is an invisible folder called Volumes. Inside of this
I found aliases to each of the two partitions (Mac OS , Disk 1), an
alias to the second hard drive (Disk 2) as well as a folder named Disk
2. Inside this Disk 2 folder I found home directories had been created
for any user I had tried to log in as. Inside one of these was the
test document I had saved.
This Disk 2 folder was a duplicate of my second hard drive where my
user directories are stored!
Didn't know what to do so I dragged this Disk 2 folder to the trash and
restarted the server. Went to a client machine and logged in and all
my documents are back.
My questions:
Have I fixed things? The remaining alias in the Volumes folder is now
named Disk 2 1 (instead of Disk 2) but seems to work. I was unable to
rename it back to what it should be as it was locked and wouldn't let
me unlock it.
Is there anything I should do before Monday morning to ensure a smooth
start to the week?
Thanks
Jim Cartlidge
Network Resources Dept Head
Brookswood Secondary School
20902 37A Ave
Langley, BC Canada
