Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

240218

January 4th, 2016 19:00

SSD Compatibility w/PERC S300 RAID?

We have an older PE T110 first generation with a PERC S300 RAID controller and 4x250GB drives. However, because the controller is older, there is not much in terms of documentation on SSD compatibility. Has anyone had any success upgrading any server/workstation using a PERC S300 with an SSD of any kind in RAID 10 configuration?

Lastly, I don't recall what kind of connector is on the existing drives and am a little confused about the difference between SATA and SAS. What normally comes stock with this system and what would I need if I moved to SSD's? New cables? Anything else I would need to know?

9 Legend

 • 

16.3K Posts

January 24th, 2016 08:00

would it be safe to assume that I could just as easily swap out each drive of the array, one at a time, with an SSD?

You cannot mix SAS and SATA in the same array. You also cannot mix HDD and SSD. If the S300 doesn't support SSD, then it may not know the difference between a SATA SSD and a SATA HDD, so it may work, but 1) I wouldn't count on it, and 2) just know that on real RAID controllers, it can't be done.

In the end, I'm not sure if it will accomplish your goals. The reason I asked is because you may have been able to just add the SSD's as a new VD, then move database files, etc. to it to improve speed, but this all sounds like a lot of work for little return. I'd just invest in a good backup, recovery solution. Can this run in a virtual environment?

9 Legend

 • 

16.3K Posts

January 4th, 2016 20:00

"Stock"? Eh, that's buyer's choice, BUT hardly anyone would pay the price of SAS drives and put them in a T110.

SAS cables/connectors and controllers will take SAS or SATA drives. SATA cables/connectors and controllers will only take SATA. See the comparison here:

They make SAS SSD's, but they are very expensive, so assuming you go with SATA SSD's, you can use your existing cables (because the drives you have - 250GB - are SATA too).

Honestly, I would remove the S300 altogether and connect them to the onboard SATA ports.

125 Posts

January 21st, 2016 18:00

Thank you so much for clarifying that. I was a little confused on the compatibility and that clears it up much better. Because this is a production machine and little available in terms of failover, having some RAID is better than no RAID. Or are you referring to using the onboard controller in RAID mode?

9 Legend

 • 

16.3K Posts

January 21st, 2016 19:00

are you referring to using the onboard controller in RAID mode?

No. that is the worst possible scenario. The S100 controller is even worst than the S300. Put them on the onboard SATA ports in non-RAID (AHCI) mode and do OS-managed RAID instead.

9 Legend

 • 

16.3K Posts

January 21st, 2016 23:00

Not "supported", but that doesn't mean they don't work on it anyway. S-series reliability and performance is the real disservice and the reason I suggested just removing it altogether (not intending he use the onboard RAID).

January 21st, 2016 23:00

"Honestly, I would remove the S300 altogether and connect them to the onboard SATA ports."

Well, since the S300 doesn't support SSD drives, that would be a good choice.

125 Posts

January 22nd, 2016 15:00

That clarifies it so well, thank you. Because of the proprietary nature of software we run, I do not have any 64 bit migration pathway, so can only squeeze performance through hardware means only, even though it seems marginal. I found a set of Seagate Pulsar's that I can install and was wondering about a couple details.

I plan on using Terabyte Image to clone the existing RAID array. But are the RAID configuration details stored on the controller, the drives, or both? If I were to create an image, restore it to the new SSD array, but find it not working, would it be as simple as putting the old drives back in and booting back to normal?

9 Legend

 • 

16.3K Posts

January 22nd, 2016 18:00

Both. You can always put the drive back in, but because the SSD will have a different configuration, you will have to IMPORT the foreign configuration found on the drives if you put the originals back in.

125 Posts

January 23rd, 2016 00:00

I have never actually tried this before. Is it relatively straight forward in Windows 2003 Server x86? And given the age of the OS, wouldn't I be better off just trying to piece-meal this server using the SSD's on the PERC S300?  

And as for "chicken or the egg," given my setup, how would I let the OS configure the array if I want to clone the OS to that same array ...? Or is it not possible w/o a clean install?  Very interesting discussion, thank you!

9 Legend

 • 

16.3K Posts

January 23rd, 2016 10:00

For sake of simplicity, if you are cloning, I would create a VD with the SSD's, then clone directly from one VD to the other, BECAUSE cloning isn't designed to move between different hardware.

If you were doing a backup/restore using good backup software, then you could inject the onboard AHCI drivers into the restore, moving from the current S300 array to a standalone SATA SSD disk on the chipset controller THEN configure a software RAID.

So, it is also horrible that you are using Server 2003. 2003 doesn't support SSD's and won't know how to use them properly, although it will still run better on them. 2003 is also obsolete and past end-of-life. That said, let's look at why you are wanting to use SSD's in the first place. Something isn't running as fast as you'd like? If you are running a database or file shares or something like QuickBooks on the server, you can create a second/separate VD with the SSD's and move the data/services that need the extra speed to the SSD array.

125 Posts

January 23rd, 2016 15:00

Thanks for laying that all out. I think doing a backup/restore as you've mentioned will work out best but would it be safe to assume that I could just as easily swap out each drive of the array, one at a time, with an SSD? The PERC S300 should be able to rebuild itself from what I recall. This will take more time, granted, but I feel would take the guess work out of whether or not my backup file is good to go (I've had lots of bad luck using backup files for some reason - been cloning or swapping drives where possible).

The server itself is the backbone of our financial reporting as well as PoS function for our market. It controls 4 checkout lanes and 6 deli scales as well as a variety of other miscellaneous network server functions. It was purchased some six years ago when NCR's independent retailer unit was still going strong with its current offering. Then about a year ago, Microsoft pulled the rug under NCR regarding legacy software support and NCR subsequently pulled its rug from under retailers using legacy hardware/software. We are in the position that we cannot even buy a replacement server if this one died. If we are lucky, we can rebuild the software if the hardware fails, but the hardware is pretty much on its last leg. Otherwise, we are in the position that we must upgrade the entire market, which is an expense we are not willing to take on given our uncertainty about our return on investment. But seriously, we're running Windows 2003 x86 with SQL Express 2005 ... geez.

Currently, the server runs quite well, but has had several components replaced in hopes of extending its operational life by maintaining RAID health and motherboard longevity. I was hoping to replace the HDD's with SSD's to reduce wear on the PSU since these would be lower power, and also reduce wear on the system as a whole due to temperature. The CDROM was recently removed and replaced with a 2 bay high fan. An SSD is currently connected to the onboard controller for pagefile/temp file use.

125 Posts

February 2nd, 2016 20:00

After a lot of reading, I am leaning toward a virtualized environment. I will have to confirm this with our hardware vendor but am pretty sure it should work assuming I'm virtualizing the same system. Moving the system over will surely cause our license on the PoS software to go ... but thank you for the idea. This will be something for me to look into further!

125 Posts

October 11th, 2016 15:00

Old thread, but wanted to confirm our setup for future reference. Due to an OS failure, we went ahead and just upgraded all our add-on cards and HDD's. Amazingly, it works. Stability is unclear as we have not fully resolved our BSOD issues but it works, mostly. 

Dell T110 Win2K3 Standard 32 bit
PERC S300 supports OCZ Deneva 3.5" SSD in RAID 10
Win2K3 Will Work with ATI Fire Pro 2270 (ATI XP Driver)
Sound Blaster Live SB 1040 (XP Driver)
US Robotics PCIe Soft Modem (XP Driver)

The only thing we noticed that performance with SSD on this card in RAID10 is marginal at best. I think RAID10 with 4 drives already saturates the port. However, it almost feels like I can passively cool this server. It's so quiet, and absolutely vibration free!

May finally get to upgrade to 2008 or 2012 soon ... If the price is right, we'll be keeping our fingers crossed!

9 Legend

 • 

16.3K Posts

October 11th, 2016 16:00

Blue-screen, poor performance ... not sure it "works" very well at all. The issues I see:

  • Running 2003
  • With XP drivers
  • Using an S300 controller
  • In a RAID 10 (S300 is horrible, but other than RAID 1 is worse)
  • Using unsupported drives (at least they are enterprise class drives, but even that doesn't guarantee compatibility)
  • Using non-validated hardware in the server
  • A modem?! Who uses a modem anymore?!

Just some friendly observations :) The more of these you correct, the more reliable it is likely to be, and the better performance you will likely see.

125 Posts

October 11th, 2016 16:00

Yep, the only real way to correct this is to go to a modern OS. But for those of us who are really really stuck (and there are many of us in the local trading area), this is one way to go. Currently haggling with our local NCR dealer to see what they can do. It's funny because they refused to load Server 2008 onto our server because it was incompatible with our PoS software. The salesman was just here today telling me that the new hardware will come with 2008 or 2012 Server but still use the older PoS software. Essentially trying to force a software+hardware upgrade at the same time.

No Events found!

Top