chipperMDW
Programmer
I have a system (inherited) acting as a file server; it is a NetStor WSS running Server 2003 attached via SCSI to a SecurStor XRS RAID. I have an ongoing issue where the OS locks up when it sees the RAID device.
If the RAID is powered on when the server boots, it usually just blinks the LEDs on the RAID a couple of times and then hangs on the loading screen forever with the gray bar scrolling past, or else it gets past the loading screen to a blank screen and hangs there; if the RAID is then powered off, or if it is not on during the boot, the server finishes booting.
Once the server is on, it works fine (though it can't see the RAID volumes, of course). Powering the RAID back on and rescanning the hardware causes the OS to recognize the volumes on the RAID, but attempting to do anything with them causes the OS to hang again until the RAID is powered off.
The frustrating part is that about 1 boot out of every 50, something clicks (not literally) and everything works fine. The OS sees the RAID, the LEDs begin flashing, and everything is well until I need to reboot.
I know the RAID itself works because I can always mount and access it using a Linux liveCD. (It also always shows up in the BIOS). So the issue lies somewhere with the Server 2003 installation. Since I inherited this system, I don't know whether or not it ever actually worked properly.
I'm normally a Unix admin, so I'm not entirely sure what to try on a Windows server at this point. To me, it sounds like a driver issue. Does that sound correct? Which drivers are the most likely culprits? Is there something else I should be looking at? Any other hints or ideas?
Thanks for any help.
If the RAID is powered on when the server boots, it usually just blinks the LEDs on the RAID a couple of times and then hangs on the loading screen forever with the gray bar scrolling past, or else it gets past the loading screen to a blank screen and hangs there; if the RAID is then powered off, or if it is not on during the boot, the server finishes booting.
Once the server is on, it works fine (though it can't see the RAID volumes, of course). Powering the RAID back on and rescanning the hardware causes the OS to recognize the volumes on the RAID, but attempting to do anything with them causes the OS to hang again until the RAID is powered off.
The frustrating part is that about 1 boot out of every 50, something clicks (not literally) and everything works fine. The OS sees the RAID, the LEDs begin flashing, and everything is well until I need to reboot.
I know the RAID itself works because I can always mount and access it using a Linux liveCD. (It also always shows up in the BIOS). So the issue lies somewhere with the Server 2003 installation. Since I inherited this system, I don't know whether or not it ever actually worked properly.
I'm normally a Unix admin, so I'm not entirely sure what to try on a Windows server at this point. To me, it sounds like a driver issue. Does that sound correct? Which drivers are the most likely culprits? Is there something else I should be looking at? Any other hints or ideas?
Thanks for any help.
