sglee
asked on
Adaptec Controller 2130S PCI - Windows 2003 Server Running Slow
Hi,
I had this windows 2003 Server on Adaptec 2130 SCSI PCI Controller (three 147GB SCSI 15K HD on RAID 5) that has been running fine for about 4 years. All of sudden it became very SLOW any command whether it is to open My Computer, running an existing programs ... etc.
So I moved all the programs to another server and decided to find out what is going on with this box.
I installed Windows 2003 Server from the scratch after reformatting existing partition and it ran like a sick puppy ... same as before.
So I hooked up a SATA HD to the Motherboard (disconnected the controller cable from the 2130S) and loded Windows 7. It runs like a charm. So I concluded that there is nothing wrong with the computer,CPU, RAM or Motherboard.
It has to be either Controller or SCSI Hard Drives or RAID 5 Build itself. When I can go into Adaptec BIOS screen and it says each HD is optimal.
I could delete existing RAID and recreate a RAID, but since I have loaded Windows 2003 Server already, if that is not the problem, I wil l be wasting my time.
So what do you think I should do next?
Thanks.
I had this windows 2003 Server on Adaptec 2130 SCSI PCI Controller (three 147GB SCSI 15K HD on RAID 5) that has been running fine for about 4 years. All of sudden it became very SLOW any command whether it is to open My Computer, running an existing programs ... etc.
So I moved all the programs to another server and decided to find out what is going on with this box.
I installed Windows 2003 Server from the scratch after reformatting existing partition and it ran like a sick puppy ... same as before.
So I hooked up a SATA HD to the Motherboard (disconnected the controller cable from the 2130S) and loded Windows 7. It runs like a charm. So I concluded that there is nothing wrong with the computer,CPU, RAM or Motherboard.
It has to be either Controller or SCSI Hard Drives or RAID 5 Build itself. When I can go into Adaptec BIOS screen and it says each HD is optimal.
I could delete existing RAID and recreate a RAID, but since I have loaded Windows 2003 Server already, if that is not the problem, I wil l be wasting my time.
So what do you think I should do next?
Thanks.
There is a possibility the RAM on the card could have gone bad.
ASKER
Is there a way to check the integrity of the ram on the card?
Does the controller say whether the RAID array is in a degraded state? (check in the card's BIOS) If it is, your RAID array has a bad drive and will run slow until you replace the drive and the array is rebuilt.
ASKER
jq1801:, Callandor:
----------------
Array Status says "Optimal".
What I am going to do is to delete an existing array and recrate one. Then I will load OS to see if it loads any faster. Last time loading Windows 2003 Server took so long, I just went home.
I should be able to tell right away. I will keep you posted within an hour.
----------------
Array Status says "Optimal".
What I am going to do is to delete an existing array and recrate one. Then I will load OS to see if it loads any faster. Last time loading Windows 2003 Server took so long, I just went home.
I should be able to tell right away. I will keep you posted within an hour.
ASKER
jq1801:, Callandor:
----------------
I recreated RAID 5 array and loaded Windows 2003 Server. After more than two hours, it was still running. What I going to do is to connect 3 HDs to Adaptec 29160 controller to see if the problem reisdes on the 2130S controller. I will report back.
----------------
I recreated RAID 5 array and loaded Windows 2003 Server. After more than two hours, it was still running. What I going to do is to connect 3 HDs to Adaptec 29160 controller to see if the problem reisdes on the 2130S controller. I will report back.
Certainly sounds like a problem with the controller, but I would also check the cables and termination on the controller and drives.
ASKER
Callandor:
This is what I tried since my last post.
I inserted two separate 2130S Low Profile Cards (Brand New that I bought as backup when I set up this server 4 years ago), but none of them wouldeven respond to Control-A.I thought that was very strange. So I gave up on those 2130S and tried a good old 29160 Host Controller. The 29160 showed, at the startup, three HDs - HD1 and 3 as 160, but HD2 as 40. (I think these numbers are speed of transfer in MB).
Anyway I added SATA with WIN7 OS and used it as bootup HD. After loading the driver for 29160 on Win7, CompMgmt.msc showed three SCSI HDs. I formatted them and copied "C:\Program Files" folder to each HD and they worked great. I also ran SeaTools and performed a Short Test on HDs and they all passed the test.
Then I put back my origianl 2130S in tthe server, re-created RAID 5 and now in the process of installing W2003 OS. In my opinion it is taking way too long, but let me reserve my judgement until it is complete. I will continue to post.
This is what I tried since my last post.
I inserted two separate 2130S Low Profile Cards (Brand New that I bought as backup when I set up this server 4 years ago), but none of them wouldeven respond to Control-A.I thought that was very strange. So I gave up on those 2130S and tried a good old 29160 Host Controller. The 29160 showed, at the startup, three HDs - HD1 and 3 as 160, but HD2 as 40. (I think these numbers are speed of transfer in MB).
Anyway I added SATA with WIN7 OS and used it as bootup HD. After loading the driver for 29160 on Win7, CompMgmt.msc showed three SCSI HDs. I formatted them and copied "C:\Program Files" folder to each HD and they worked great. I also ran SeaTools and performed a Short Test on HDs and they all passed the test.
Then I put back my origianl 2130S in tthe server, re-created RAID 5 and now in the process of installing W2003 OS. In my opinion it is taking way too long, but let me reserve my judgement until it is complete. I will continue to post.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Callandor:
-------------------
I found the problem. It was the second hard drive that showed 40 when connected to 29160 while 1st & 3rd HDs showed 160.
I took 2nd hard drive out of 2130S controller, created RAID 1, and started loading Windows 2003 from the CD. WOW the difference it makes ...
The frustrating part was that 2130 Controller did not show/display any sign of error or error message about failing hard drive where 29160 did. Even when I ran SeaTools on Windows 2003 server off RAID 5 on 2130S controller, it ran Basic Test successfully. Strange ...
Anyway I need to replace this HD and all will be good.
Thanks for you help.
-------------------
I found the problem. It was the second hard drive that showed 40 when connected to 29160 while 1st & 3rd HDs showed 160.
I took 2nd hard drive out of 2130S controller, created RAID 1, and started loading Windows 2003 from the CD. WOW the difference it makes ...
The frustrating part was that 2130 Controller did not show/display any sign of error or error message about failing hard drive where 29160 did. Even when I ran SeaTools on Windows 2003 server off RAID 5 on 2130S controller, it ran Basic Test successfully. Strange ...
Anyway I need to replace this HD and all will be good.
Thanks for you help.