Re: SBS 2003 hanging

Sorry Preben

Just a quick note for your own sense of well being. I don't think that you
will have any problems with your new hardware as I have many servers running
SBS 2003 on SCSI RAID and have never had an issue. I don't think I will ever
go down the SATA route again after the endless headaches this has caused me.

All the best

"Preben Nyeng" wrote:

Hi Mark,
I am sorry to hear about your problems, and even more sorry to tell you that
I cannot be of any help to you...
We never solved the problem. Instead we replaced the server with one using
SCSI disks on a hardware SCSI RAID controller (using RAID 1). We have not
had any problems with this server yet, but on the other hand the old one ran
for more than half a year before the problem started so we are still holding
our breath, hoping for the best...
Of course with 6 servers, replacing the hardware may not be an option, but
we simply could not afford to waste more time and decided that we had to do
something radical.
My best regards,
Preben Nyeng

"Mark van den Hoek" <Mark van den Hoek@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:E73850E8-0F0B-4969-B9B3-E5E610F0DBCE@xxxxxxxxxxxxxxxx
Hi Lanwench,

I am having the exact same problem as Preben. I have at least 6 of these
Intel servers out there (the same motherboard as Preben) and it first
started
to happen to one. Not long after that the same thing started to happen to
another one and just recently it has started to happen to another. I was
wandering if Preben or yourself had fixed the problem and what method was
used to overcome it.

Any help would be much appreciated.


Regards

"Lanwench [MVP - Exchange]" wrote:



In news:usKGNo3OGHA.344@xxxxxxxxxxxxxxxxxxxx,
Preben Nyeng <pny@xxxxxxxx> typed:
Have already checked for driver updates for the hardware. Also
checked for BIOS updates from Intel for the motherboard. We are using
an SE7210 from Intel with its built-in SATA Raid 1 support. I did
some googling on SBS problems and found some people having problems
with SATA Raid when running SBS.
So our next step may be a complete reinstall with the BIOS Raid
disabled, using a mirrored volume in Windows to provide fault
tolerance. Any comments on this procedure?

Better than nothing, but I don't like software RAID - I always go for
SCSI
hardware RAID.

Regards,
Preben

"Lanwench [MVP - Exchange]"
<lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:%23sKWS0WOGHA.2888@xxxxxxxxxxxxxxxxxxxxxxx


In news:OtWVflUOGHA.1192@xxxxxxxxxxxxxxxxxxxx,
Preben Nyeng <pny@xxxxxxxx> typed:
Hi,
we have a problem with our SBS 2003. Occasionally it will
hang/freeze/stop responding. The entire server locks up, it does not
repond to network connections or user input. The screen saver also
freezes. Disabling the Exchange services in safe-mode makes it
possible to
restart the server in normal mode. After that, the Exchange services
may be started, but only after the mailbox and public folder folder
stores have both been marked with "Do not mount this store at
start-up". With this in order the Exchange services can start and
stop and the
server may also be re-booted. But if an attempt to mount any of the
stores is made, the server hangs again.
It is a little different from incident to incident how we move on.
Restoring a previous off-line copy of the databases (.edb + .stm
files) according to MS article 296788 followed by eseutil /r usually
solves the problem and the databases can be mounted. But sometimes
it will only last 10-15 minutes and the server hangs again. In these
cases we delete all log files and the chk file after
restore+recovery and thereby restarts the log sequence numbering.
This seems to have a positive effect. However the server will
eventually hang again, it can run for days or
weeks, but sooner or later it hangs. There is no pattern regarding
the time of day. It can happen while we are working or in the middle
of the night. No suspicious event logs are generated up to the
incident, but the event logging stops when the server hangs.
Any help will be appreciated!

Regards,
Preben Nyeng

If you aren't even getting a blue screen of death, this is usually a
hardware issue. I'd make sure all drivers are up to date - try
swapping out memory, etc.






.

Loading