some advice needed - rebuild of scsi server

[news.microsoft.com]

Hi

i have a server that i need advice with

Windows 2000 SP4 + patched to date
SQL Server 2000 SP3a
SCSI raid 5 setup with 2 raid packs

on rebooting the server i found that i am having problems with the MUP.SYS
file it causes the server to reboot.

my question is that if i rebuild windows will i lose the information on the
other drives?

Many thanks
Simon Whale

 

[Guest]

what is a raid pack?

You don't describe wheither this is hardware or software raid. Nor do you
state your partitioning across the array.

Blanket answer is if software raid you will lose access to the other
partitions. If hardware raid you will not.

 

[news.microsoft.com]

Sorry Joshua,

i have 2 raid 5 packs and it is a hardware based raid setup


Simon

 

[Colon Terminus]

Hi

i have a server that i need advice with

Windows 2000 SP4 + patched to date
SQL Server 2000 SP3a
SCSI raid 5 setup with 2 raid packs

on rebooting the server i found that i am having problems with the MUP.SYS
file it causes the server to reboot.

my question is that if i rebuild windows will i lose the information on the
other drives?

Many thanks
Simon Whale

I thnk you'll find that MUP.SYS is not the problem, it's just the last thing
that successfully loaded. You need to find out what is happening subsequent
to MUP.SYS loading.

Start your server with boot logging enabled then when it fails you can
examine the contents of ntbtlog.txt to determine the failing process. That
should go a long way toward solving your problem. Donig a complete rebuild
of the server is a rather drastic measure and you should exhaust all other
avenues before making such a decision.

 

[news.microsoft.com]

Colon,

before i took this stage i did enable boot logging and on all occassions on
loading it would get as far as the mup.sys file and then blue screen.

i even tried replacing the mup.sys from the service pack uninstalls too to
no avail

Simon

 

[Colon Terminus]

Yes, but what does the boot log say?
Look at %systemroot%\ntbtlog.txt.

Looking at a recent boot log On the 25th line I can see that MUP.SYS was
loaded.
The next line loads the driver for ACPI Multiprocessor PC
The next is the beginning of loadinc audio stuff, etx.
The boot log goes on for 356 lines.

The boot log is NOT displayed on your screen, it is recorded to your hard
disk as a text file. Examine it. Your solution is in there.

I'd wager precious parts of my anatomy that MUP.SYS is NOT the cause of your
BSOD.