C2k Help

Non-C2k Issues => Legacy Networks => Topic started by: Stephen on December 06, 2007, 04:52:58 PM

Title: Server Failure
Post by: Stephen on December 06, 2007, 04:52:58 PM
My primary server went down this morning. Either the Pentium II CPU finally bit the dust or something on the motherboard. I am thinking the CPU is dead. There is not even a beep when you turn it on although the SCSI lights are shinning.

However the CPU fan doesn't turn - so I thought dead machine - it is an old RX Systembase machine.

Unfortunately this meant certain things now dont work on my legacy system such as apple macs talking to the NAS. In order to try and resolve this I thought I would make server 2 into server 1 by removing the ScSi drives from 1 and putting them into 2. It nearly worked. Unfortunately the primary scsi has a spot of corruption on it and does want to boot up. (I get the blue screen of death with a stop error indicating unbootable drive).

So now I am going to have to put the server 2 disks back in (and I mixed up which disk is which) and see if I can change it over to the primary role.

My HoD isn't annoyed as they are both old machines and he now fancies his case for going to the Boss and asking for the money for an apple server - I'll see if I can get the SIMMS server back and stick a linux server onto it.

I know how the time team feel after a day digging, the amount of dust that was in the 2 servers was amazing.

Anyway I have tried booting with the server disk to get to the recovery console, unfortunately for some reason it isn't finding the scsi drives so I cant check them. I did boot up with a windows XP setup disk and run chkdsk /r to correct disk errors but I still can't get the machine to boot. I have tried to reboot with the windows XP disk but it keeps giving me errors on the CD that there are corrupted files, I'll give it another go and do the do or die fixmbr command, I have nothing to loose and I can always stick the disks in as extras when I have server2 back to it's old self.
Title: Re: Server Failure
Post by: bahhumbug on December 06, 2007, 08:54:07 PM
You really are a scary f****r ain't ya ?

lol      No offence      ;D 
Title: Re: Server Failure
Post by: Stephen on December 07, 2007, 08:53:43 AM
You want to see how many screws are sitting on me bench and the state of the servers, that is scary!!!
Title: Re: Server Failure
Post by: Stephen on December 07, 2007, 09:17:43 AM
Server 2 back up and running. What amazed me is that it worked first time - it was 50/50 on wether I had the drives in the right order.
Title: Re: Server Failure
Post by: Kev on December 07, 2007, 09:30:31 AM
stephen, as scared of u as I am, i might have some parts for that server if u need them.
although, im sure you'd prefer to go down the new server for christmas route.
Title: Re: Server Failure
Post by: Stephen on December 07, 2007, 09:42:48 AM
The primary server is dead, if it wasn't before I cant be bothered repairing it and to tell you the truth it wouldn't be worth fixing it is that old. (Slot 1 Pentium processor).

If I can get the secondary server to change to a primary then I can get the system up and running properly again. (We dont really use the servers for anything but giving out ip numbers).
Title: Re: Server Failure
Post by: Stephen on December 07, 2007, 10:28:41 AM
That was unbelievably simple, to change the server. Just went to server manager in the admin tools and made the server primary, waited a couple of mins while it did it's stuff, rebooted and everythings happy.

I spoke too soon. The macs running OS Tiger cannot find the proxy server, DHCP server, the NAS or basically anything on the network. The mac running OS Leopard can. This is quite irritating to say the least. It just looks like I am going to have to upgrade them all to leopard. I have been through the network settings and nothing appears to work. Macs just confuse me at times.
Title: Re: Server Failure
Post by: Stephen on December 12, 2007, 12:17:36 PM
I had to install the DHCP stuff on the secondary server after I made it the primary and set up the scope, router and dns server ip addresses to get it all up and running again.

Notes on this can be found at http://www.more.net/technical/unsupported/servers/nt4dhcp.pdf

Of course dont use their IP addresses use your own.