Re: P4 Xeon compatibility with 5.0.5

From: Brian K. White (brian_at_aljex.com)
Date: 02/24/04


Date: Tue, 24 Feb 2004 01:26:47 -0500

Jeff Davis wrote:
> I am looking to upgrade our current Pentium II 300 Mhz. server. I need
> to be able to do this in a couple of stages as I can't afford to
> upgrade the server and the OS at the same time. We are currently
> running SCO
> 5.0.5 and I was looking at the HP ML350 which has a P4 Xeon running at
> 2.2 Ghz. Will 5.0.5 run on this computer or should I look at getting
> something a bit older like a Pentium III 700? What kind of troubles
> would I run into trying to install an older OS on such a new model
> computer? I am almost thinking to get the upgraded OS first and then
> upgrade the server later, but I need to make a move soon as my current
> hardware is aging. Any and all suggestions would be appreciated.
>
> Thanks,
>
> Jeff

You need at least 5.0.6 WITH rs506a in order to be able to run on any
p4 without risking torching your cpu.

It'll run, it just may or may not keep running. Also remember to
disable hyperthreading in the bios even for current 5.0.7

You can safely use whatever is the fastest p3 you can find with your
current 5.0.5. including xeon as long as it's a p3-xeon and including over
1ghz.

Maybe you can find an old P3 desktop and transfer the special hardware
(multi-port serial, scsi/raid, tapes etc... which will tide you over,
Assuming you know what specific hardware is going bad and can avoid
bringing that over.

The hardware is the immediate concern and you don't want to upgrade
the os on failing hardware, hope it makes it through that, then sit
there and hope it continues to live while they recover from buying the
OS before they can buy new hardware. You need to get on better
hardware 1st, but you can't get on current hardware without upgrading
the OS. So you better find a good old box, or a cheap new box and move
on to that temporarily, and try to offset the overhead by not paying
much for the temp box. (IE: grab an old desktop and use as much of the
old server as possible in the form of nic,serial,scsi etc...) Probably
what's mostly going bad on the old box are the hard drives and the
power supply and possibly the motherboard due to drying out
capacitors. probably the nic/serial/scsi cards are all fine. I've done
this a few times and it's worked out well. moving those pci cards also
made it easy to get the kernel to run on the new temp box since the
drivers are all already in and generally all you need to do is re-run
netconfig to tell the nic driver what irq/bus/function to find the nic
at.

if the hd's are failing and new hd's would run on the old scsi card
(even if grossly underspeed) Then that is a safe investment. Get new drives
that you will use in the (final) new server, use them in the temp box
and don't worry that it's a ultra320 drive running at 20mhz. If the
new server will have raid and the old one doesn't, no problem, just
get one of whatever will be in the raid array. You will wipe it during
install anyways. (unless the new machine will have 80-pin sca2 hot-swap
connectors and the old one doesn't and you don't have a drive bay to use in
the temp box...)

-- 
Brian K. White  --  brian@aljex.com  --  http://www.aljex.com/bkw/
+++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
filePro BBx  Linux SCO  Prosper/FACTS AutoCAD  #callahans Satriani


Relevant Pages

  • Re: Upgrading server motherboard
    ... I used Paragon Drive Copy in the end for the image but I took many drivers ... I found the server board I was supplied had a fault and the customer in the ... relevant drives on your existing server, then restore the images to the new ... can effectively migrate hardware and restore onto the RAID of the new mobo. ...
    (microsoft.public.windows.server.sbs)
  • Re: Upgrading to SBS 2003
    ... My idea was to upgrade the hardware and install a proper server OS. ... SBS is a server O/S, ...
    (microsoft.public.windows.server.sbs)
  • Re: Upgrading server motherboard
    ... I found the server board I was supplied had a fault and the customer in the ... relevant drives on your existing server, then restore the images to the new ... can effectively migrate hardware and restore onto the RAID of the new mobo. ...
    (microsoft.public.windows.server.sbs)
  • Re: A difficult migration (2000 -> 2003)
    ... > I'm in the process of migrating a Windows 2000 domain whose old servers ... > due to lots of misconfigurations, hardware problems and a dead Exchange ... > server, so we tought it was better to create a completely new one instead ... > only to get a blue screen after rebooting; I never ran a direct upgrade (I ...
    (microsoft.public.windows.server.general)
  • Re: A difficult migration (2000 -> 2003)
    ... > I'm in the process of migrating a Windows 2000 domain whose old servers ... > due to lots of misconfigurations, hardware problems and a dead Exchange ... > server, so we tought it was better to create a completely new one instead ... > only to get a blue screen after rebooting; I never ran a direct upgrade (I ...
    (microsoft.public.windows.server.active_directory)