On Nov 7, 2005, at 6:39 PM, Josh Wisenbaker wrote:
On Nov 7, 2005, at 5:16 PM, Jerry J wrote:
From: Ken Garland <email@hidden>
Subject: Re: Re : Xserve boot issue - lock related
that is strange. i was a bit frustrated to say the least when i was
first 'locked out' by the front locking mechanism, but now i'm more
thankful for it. it would be nice to have the option to set what it
locks exactly as having it be strictly for hardware (drive removal
and
enclosure removal) would be cool. currently i have to leave it
unlocked
so i can use my kvm on the systems.
That sure would be nice. I have one client way out in the sticks with
an XServe G4 dual 1.33 that has a stack of FW800 drives (and one
FW400) plugged into the back for backups. OSXS 10.3.9. They don't
mounht at boot when its locked.
I keep seeing this about mount on boot thing. It makes sense, but why
all the reboots?
Really, I'm not trying to be snarky here. What's with all the
rebooting?
Josh
No snarkification taken. I have learned to take your words very
seriously, and have learned much from you. Thanks!
That XServe has been _extremely_ reliable. Here are the last three
reboots that I can remember:
1) Yesterday, (Sunday afternoon) I got a call from the ranch manager in
a panic. He's got "12 hours of work" to do before he catches an early
morning plane to Atlanta. Every time he touches the Finder he gets a
"Connect to Server XServe1" dialog with a username of one of his
lieutenants (Brent) and empty password. No matter what he does (he
knows Brent's password), he gets the Spinning PIzza Of Death forever.
Many client restarts, other tactics and anything else bizarre I can
think of don't fix it quickly. Since its Sunday afternoon, he can
verify that nobody else is there. I stopped AFP via ARD. He still has
the problem. His computer insists upon (re-)connecting to the XServe as
Brent, which it apparently cannot, and I need to fix this NOW. Nobody
else is in the building. I restarted the XServe via ARD and sent the
boss upstairs to the server room to do the twist-o on the lock.
Suddenly, all is well. This building is a 2 hour drive away for me, and
this was the fastest way I could think of to solve the problem and get
the manager back to work. He is not particularly technical, and his
descriptions over the phone were not very clear, to say the least.
Taking the time to figure out exactly what was wrong would have been
inappropriate. Any advice from anybody about a better solution is
welcome.
2) A bad power outage exceeded the UPS. I talked a secretary through
doing the twist-o over the phone.
3) When I upgraded to OSXS 10.3.9, I was present. I had to learn about
re-connecting to directory services, which I did from saved advice from
this list. Thanks to whoever, maybe you, Josh. Before I learned that
lesson, I had to re-clone from a backup in a hurry, late... and drive
again another day.
Before that, I don't remember any specific pain.
Thats whats up with all the rebooting! Not that often, or avoidable,
really...
