Re: SYSTEM DISK FREEZES WITH HEAVY IO ON DISK



Why, I don't know, but I am going to offer my opinion.

First of all, as the others have said, when you do such a major step as
moving from AMD to Intel, you should expect incompatibilities. To use your
analogy of a car, would you expect to be able to take the engine (hard
drive) out of a Chevy and plop it into a Ford and have it work without major
changes to the Ford? I hope not.

OK, as to your problem, I had a similar problem (not identical) when moving
from PATA to SATA in my home office server with SBS 2003 SP1. I had a single
PATA drive, and installed a single SATA drive on the motherboard SATA
controller. The motherboard is a desktop board and does not have 2003
drivers. I used ShadowProtect IT Edition to copy the disk contents. Every so
often when under even moderate use, the server would freeze for about 90
seconds.

I had another SATA controller lying around, so I put that into the server,
installed the 2003 driver, and then moved the SATA drive to it. Problem
solved.

I now have an Adaptec RAID controller and two SATA drives, and the problem
is still gone.

Check your controller.

Gregg Hill





"Wouter Gotrade" <WouterKCS@xxxxxxxxxxx> wrote in message
news:48431dbb$2$4235$4c368faf@xxxxxxxxxxxxxxxxx
Hi,

If the life os an application server is 5 years you will have to change
hardware to keep up with obselence and efficiency. Many times with XP and
VIsta the only remedy to solve issues a restore or re-install.

With servers a re-install is a major task -- and I would assume Microsoft
designed their softwar so its life expentancy is at least 5 to 7 years
with multiple hardware changes during the seven years. To assume every
time you change hardware you need to re-install is redicoulous.

With a car, you don't expect to change engine every 2 years.

I know statements made that a re-install will fix your problems, but we
all know it is unrealistic with OS's. If it is Microsoft OS don't meet at
least mininum requirements, it's expens over it's life expentancy is
enormous.

In my casethe migration using Ghost was easy and un event full. No I have
a problem, an dno one can identify why?? It lasck expertise to this what
is so common.

We need to be smart enough to realize that upgard of hardware is normal,
and that OS needs to be able to meet that requirements.If not, because of
it complexity, we miss the boat completely.

May be we are not all that smart, and have Microsoft leads to very in -
efficent systems and very low expenctations.


Look, I have another post, asking for help wht SP3 server update fails.
Even with the log file displayed, no one knows why. Very disturbing.
Microsoft as whole is mssing it's mission. And its supports can only say
"we don't know why?", so re-install at a very high expense is the only
wise solution.Whoh!!!


"Leythos" <void@xxxxxxxxxxx> wrote in message
news:MPG.22ac6ad4f292065598988d@xxxxxxxxxxxxxxxxxxxx
In article <4842189e$2$4256$4c368faf@xxxxxxxxxxxxxx>,
WouterKCS@xxxxxxxxxxx says...
Still, I had no such problems on an AMD system. When I migrated (copied)
to
Intel, the problem started. I can not copy large files from or to the
drive - it freezes. I installed XP on this machineand it was fast!

Some how the drivers or setup are not compatible when I switched to
Intel
and SATA. Maybe I need to move back to an IDE drive?

Re-installing SBS is a lot of work. Maybe wait till the new SBS 2008
comes
out?

Thanks,

PS: Was surprised that the move from AMD to Intel was even possible. In
the
past and XP, this was not possible. Also, with 4GB of RAM, it uses
4GB --
not 3.1 with XP.

The simple fact remains that you may/will have problems as you change
platforms, it just happens. Yes, you can get away with it many times,
most in fact, but there is always some problem, some crappy driver that
loads an extra hidden task that runs improperly in the background,
waiting on you, like Jason with his hockey mask....

You can't just "Copy" and expect things to work properly, and with a
very limited system like yours you can't expect much performance either.

Find anything AMD or related to the old motherboard, remove it, make
sure that you've downloaded all the INTEL Drivers from the intel
website, install them, reboot, if it still works then you should be
better off, but you would have a sure fire solution if you just did a
swing migration.

--
- Igitur qui desiderat pacem, praeparet bellum.
- Calling an illegal alien an "undocumented worker" is like calling a
drug dealer an "unlicensed pharmacist"
spam999free@xxxxxxxxxx (remove 999 for proper email address)




.



Relevant Pages

  • Re: ????SATA or SCSI????
    ... it may have been perceived as a major failure if it had been SATA that you ... I haven't yet deployed a server ... Les Connor [SBS Community Member - SBS MVP] ... If the drives had been SATA and one had failed in a week, ...
    (microsoft.public.windows.server.sbs)
  • Re: SATA drives...
    ... as a subsitute for SCSI. ... for the investment of a new server, OS, backup system, etc. ... relative risk of the lower-cost SATA. ... > SCSI drives are designed for servers running 24*7. ...
    (microsoft.public.windows.server.sbs)
  • Re: Hotdesking and performance questions with SBS.
    ... I prefer SCSI based systems but some of the entry level Dells ... SATA drives are, for the most part, not designed for 24*7 ... SOME SATA drives are basically SCSI drives with SATA interfaces, ... It's a server, it also needs: ...
    (microsoft.public.windows.server.sbs)
  • RE: SCSI vs. SATA IDE
    ... I"ve been using the same SATA config in 15-16 servers now for about a year. ... This makes for a total of 7 drives running at a time. ... My personal server is setup like this. ...
    (microsoft.public.windows.server.sbs)
  • Help on IDE to SATA and SysPrep Required Please.
    ... I have not long done a re-install, so really don't want to be doing another ... but I've just been given a SATA drive to replace my IDE C ... Ghosting, and redumping to new drive, and using SysPrep to tell it to ... am I suppose to clone the drive, swap the drives and use SysPrep, or use ...
    (microsoft.public.windowsxp.general)