Windows Forum

Ask something
Discussion Locked

SWXCR Error on Mylex raid controller

0 helpful
7 replies

by choppit

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I'm getting the following error repeatedly in my system log after a rebuild on a RAID 1 array.

Event ID 7016 - The swxcrsrv service has reported an invalid current state 0.

I've checked for soft and parity errors and found none. I've found no clues as to the cause (or meaning) of this error from the documentation or from web searches. The array appears to be working correctly.

OS is NT4 SP5 on Alpha platform. Controllers are Storageworks 230.

Any assistance would be appreciated.

7 replies

by bfilmfan

If Service Control Manager is throwing that error, this may resolve your issue:

http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q320789&

Make sure you use the driver from HP here:
http://h18000.www1.hp.com/support/files/server/us/download/18619.html

I would call the vendor and see if the driver is complaint with Windows NT 4.0 on the controller card or is it only compliant with Windows 2000 and above, if you continue to have issues.

by choppit

The cause of this error was a badly seated drive. Oddly though, this was not picked up by the SWXCR utilities and was apparently working fine regardless. Thanks anyway.

by sgt_shultz

well, the array *would* appear to be working even if one failed drive, yes? maybe you are making assumptions about what to expect at drive failure. can you attempt similar array with set of spare drives. then pull power off a drive to simulate failure, see what you get. did this work before. new hd(s)? just how repeatedly is this error appearing. at regular interval? i would try sp6 and the old driver. i would try emailing mylex. i would tell mgmt might need new controller...

by choppit

I'm familiar with the normal failure/rebuild behaviour as I experience on average a drive failure every 3-4 months on this array (12 pairs over 4 controllers). The only difference this time was that I needed to replace drives on both sides of the mirror.(I posted about the circumstances of this occurence on TR a while back)

The error repeats every 10 minutes or so.

SP6 is not an option as the Alpha releases stopped at SP5.

The KBs in reply from BFilmFan seem to suggest that this may not be as critical as I feared and may be an NT 'feature'.

Thanks for your input anyway.

by sgt_shultz

you must know what you are doing, ignoring an hd controller error on your server. guess you understand the error and figure you don't need whatever it is doing? yikes!
you are welcome and good luck anyway...

by choppit

The cause of this error was a badly seated drive. Oddly though, this was not picked up by the SWXCR utilities and was apparently working fine regardless. Thanks anyway.

This discussion is closed to new replies.