I am so sick of incompetence

CletusJones said:
you should have watched the server to see what the cause of the reboot was before going to tell him. That way you could have given him all the facts.
My job is to answer the constantly ringing phone and attempt to inform all the employees that the server is down. I can't do that while I'm sitting in front of the server.
 
Here's the conversation we just had.

Me: So you saw the error about a bad sector on one of the system drives?
Him: No, I guess I missed that.
Me: It was in the event viewer. On the second page.
Him: Oh, I didn't bother looking back that far.

It's been an hour, what the fuck has he been doing?
 
Fat Burger said:
Here's the conversation we just had.

Me: So you saw the error about a bad sector on one of the system drives?
Him: No, I guess I missed that.
Me: It was in the event viewer. On the second page.
Him: Oh, I didn't bother looking back that far.

It's been an hour, what the fuck has he been doing?
getting paid more then you? :D
 
Fat Burger said:
Here's the conversation we just had.

Me: So you saw the error about a bad sector on one of the system drives?
Him: No, I guess I missed that.
Me: It was in the event viewer. On the second page.
Him: Oh, I didn't bother looking back that far.

It's been an hour, what the fuck has he been doing?


Is there a Krispy Kreme nearby or something? Seriously, what the hell?
 
Fat Burger said:
Here's the conversation we just had.

Me: So you saw the error about a bad sector on one of the system drives?
Him: No, I guess I missed that.
Me: It was in the event viewer. On the second page.
Him: Oh, I didn't bother looking back that far.

It's been an hour, what the fuck has he been doing?

A new intern.
 
Fat Burger said:
My job is to answer the constantly ringing phone and attempt to inform all the employees that the server is down. I can't do that while I'm sitting in front of the server.
What are you, new to IT? It takes 2 - 4 minutes for a server to boot. Common sense would dictate that you should watch it boot so that if it comes up successfully, you can just tell the admin that something caused it to reboot itself. Why inform the masses if there isn't really a problem?
 
Fat Burger said:
An intern would do a better job than this fuckwit.

Oh, did I mention it took him 3 weeks to figure out how to install server rails into our racks? He kept arguing with the vendor, saying they were the wrong type.

He was using his penis as a measuring guide. :fly:
 
Fat Burger said:
Here's the conversation we just had.

Me: So you saw the error about a bad sector on one of the system drives?
Him: No, I guess I missed that.
Me: It was in the event viewer. On the second page.
Him: Oh, I didn't bother looking back that far.

It's been an hour, what the fuck has he been doing?
OK so the guy's a tard, but it's just a bad sector. It should be able to continue running until you have the time during the off hours to deal with it without interrupting service. That's what RAID arrays are for.
 
CletusJones said:
What are you, new to IT? It takes 2 - 4 minutes for a server to boot. Common sense would dictate that you should watch it boot so that if it comes up successfully, you can just tell the admin that something caused it to reboot itself. Why inform the masses if there isn't really a problem?

Because if it keeps rebooting...then that's bad...?
 
Fat Burger said:
Here's the conversation we just had.

Me: So you saw the error about a bad sector on one of the system drives?
Him: No, I guess I missed that.
Me: It was in the event viewer. On the second page.
Him: Oh, I didn't bother looking back that far.

It's been an hour, what the fuck has he been doing?
He sounds like an a moron that I used to work with. :mad:
 
Fat Burger said:
Because that's what I've been told to do, and I get yelled at if I fix the problem before informing everybody?
You're not fixing anything. If you were to sit there and watch it, you would simply be making sure it was functioning properly. If you took the time to view the system log after the fact, why not just watch the thing in the first place?
 
CletusJones said:
OK so the guy's a tard, but it's just a bad sector. It should be able to continue running until you have the time during the off hours to deal with it without interrupting service. That's what RAID arrays are for.

I thought RAID arrays were for piliging small villages and kicking stray dogs?

My world is so topsy-turvey now. :(
 
CletusJones said:
OK so the guy's a tard, but it's just a bad sector. It should be able to continue running until you have the time during the off hours to deal with it without interrupting service. That's what RAID arrays are for.
Yes, and the system drive is a RAID 1 array.
The server still rebooted.

What's the point you're trying to make, I'm missing something here.