Re: SBS 2003 Premium needs to be restarted every few days

RAID controller is indeed integrated on the MB and it's Silicon Image. Maybe
you are right since before complete rebuild it had only two 120 Gb in Mirror.
After the reinstalation I added two 250 Gb as a separate mirror array on the
same controller and it actualy now needs restart after 3 days instead of the
5 days as it was before reinstall. But one thing bothers me, that exact setup
worked for 1,5 years no prob and why the LSASS service consumes all memory
instead that for example server just runs out of memory and halts if the
problem is controller related?

"Charlie Russel - MVP" wrote:

What RAID controller are you using? There is a known problem with some
motherboard integrated RAID controller doing mirroing to SATA and/or IDE
drives. The RAID controller itself has a low level resource leak that is
happening at the hardware level and the behaviour is exactly as you
describe. I had this problem on one server and if I didn't schedule an
automatic reboot twice a week, I was out of luck. Put up with it for a
while, using an automatic script to schedule the reboot every Tuesday and
Saturday morning at 1 AM until I could replace the controller with a
standalone SATA controller. (A HighPoint, FWIW.) Since the replacement I
haven't seen a problem at all - it's been up for 4 weeks now.

I had to do a Swing Migration to do the rebuild, but the whole process was
fairly painless.

--
Charlie.
http://msmvps.com/xperts64
http://mvp.support.microsoft.com/profile/charlie.russel


"Aleksandar" <Aleksandar@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3424AAA3-5EE6-4DBC-8F81-61785F0FF95D@xxxxxxxxxxxxxxxx


"Leythos" wrote:

On Mon, 07 May 2007 04:33:00 -0700, Aleksandar wrote:
[snip]

OK, let me be more specific on the original instalation itself.
Originaly
SBS2003 Premium came witohout any SP for Server 2003 or SBS. It had SP1
for
Exchange and SP3a for SQL. After instalation I installed other SP's :
SP4 for
SQL, SP1 for Server 2003, SP1 for SBS and SP2 for Exchange. I didnt
installed
SP2 for server 2003 because of the issues it has with MS POP3 connector
for
Exchange and MMC 3.0. Other than that there is no 3rd party software
installed on the machine. I did that same installation (apart from SP2
for
exchange) exactly one year earlier and everything worked perfectly
until SP2
for Exchange is installed. Now compleatly deleted server software and
performed clean install and applied mentioned SP's and the problem is
the
same. Hope it helps

So you are not running any AV software on the server at all?

What event errors are you getting?

What errors after Sp2 are you getting that you were not getting before
SP2?

What server (model/vendor) are you loading this on?

--
Leythos
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)

Yes I tried different AV solutions but that is not problem for sure. I
removed all AV software for testing purpose but the problem persist. There
is
no errors in log at all until the mentioned slow down and eventual restart
happens. When server stops responding to client requests application log
is
overflowed by Exchange: Unable to open LDAP session on directory 'SERVER'
using port number 389. Directory returned the LDAP error:[0x1] Operations
Error. That error is because system resources are drained so the DC cannot
answer the request. In System Event Log there is an error: The server was
unable to allocate from the system nonpaged pool because the pool was
empty.
This is also because of the memory being drained by LSASS.

Before SP2 there were no errors and the server worked for couple of months
without need to be restarted (except for updates)

The server is OEM built Intel P4 3.0 Ghz, 2 x 120 Gb RAID 1, 2 x 250 Gb
Raid
1, 1.5 GB RAM. Tested same config on other machine but with same result.

.

Relevant Pages

  • Re: SBS 2003 Premium needs to be restarted every few days
    ... I saw one other instance where the poster said high lsass memory use was caused by users logging on to RWW with 'drives connected' and transferring large files. ... same controller and it actualy now needs restart after 3 days instead of the ... instead that for example server just runs out of memory and halts if the ... After instalation I installed other SP's ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 Premium needs to be restarted every few days
    ... Well, I switched to an inexpensive but real SATA RAID card and the problem went away. ... same controller and it actualy now needs restart after 3 days instead of the ... instead that for example server just runs out of memory and halts if the ... After instalation I installed other SP's ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 Premium needs to be restarted every few days
    ... instead that for example server just runs out of memory and halts if the ... problem is controller related? ... motherboard integrated RAID controller doing mirroing to SATA and/or IDE ... let me be more specific on the original instalation itself. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 Premium needs to be restarted every few days
    ... There is a known problem with some motherboard integrated RAID controller doing mirroing to SATA and/or IDE drives. ... I had this problem on one server and if I didn't schedule an automatic reboot twice a week, ... let me be more specific on the original instalation itself. ... > exchange) exactly one year earlier and everything worked perfectly> until SP2 ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 Premium needs to be restarted every few days
    ... let me be more specific on the original instalation itself. ... exchange) exactly one year earlier and everything worked perfectly until SP2 ... So you are not running any AV software on the server at all? ...
    (microsoft.public.windows.server.sbs)