Skip to main content

SATA disk shelf research

I'll compile it here for my reference really.

We use the Perc 5/e card in two servers - we'll use one to attach to our current MD1000 - I'm checking around for a better alternative to another MD1000 - the lowest price I've seen for an MD1000 is $1200 on Dell's Outlet site. Needless to say, it disappeared quite quickly. Now that we have a US address to ship to, that site can be used!

The current MD1000 will be filled with our existing 300GB 15k SAS disks, and probably set up for RAID10 or 50. It'll house our ESXi test environments in two arrays I would guess. We need another one for other purposes.

The purpose of the second unit: mass storage array for temp files, archives, miscelaneous files, and backup-to-disk. The more space and spindles, the better, however, price does factor into things. Another option would be to run openFiler alongside it. Have to explore that.

Here are the current options:

Used Dell MD1000 (single EMM is fine, dual gives us more SAS ports to play with, and the option for two hosts hooked up properly) with 15 1TB ES.2 drives (quoted $235 per drive).


Came across this:

A nice SATAII enclosure, 12 disks, max of 12TB raw. It is compatible with the Seagate .250-1TB ES.2 series drives, and our Perc 5/e cards (which are actually re-flashed/branded LSI MegaRAID SAS 8480E cards). Nice. But 12TB isn't much in the grand scale of things...would be nice to have more.

For reference, here is the RSC5ED5R-SA1C-0: $1585.00 (RSC5ED5R-SS2 is for SATA, that price is for SAS)

So, $1500 or more for the chassis. We got quoted $235+tax for a 1TB ES.2 drive, so that gives us: $6000 for the drives, $1500 for the chassis, plus whatever we put into it. Sheesh!!


Enhance-Tech also produces a slick looking unit, albeit running u320 SCSI:

The R16 unit may fit the bill, although lack of RAID10 or RAID50 is kind of a deal killer. They also look expensive (update: and how!).


RAD-Direct has some fun names: SATAboy, SATAbeast, SASboy, SASbeast. Someone creative in marketing. Unfortunately, 'from $980/TB' is a deal killer for us.
SATAboy link:


More to come...

Here's a fun technical article on SATA arrays:


Popular posts from this blog

DFSR - eventid 4312 - replication just won't work

This warning isn't documented that well on the googles, so here's some google fodder:

You are trying to set up replication for a DFS folder (no existing replication)Source server is 2008R2, 'branch office' server is 2012R2 (I'm moving all our infra to 2012R2)You have no issues getting replication configuredYou see the DFSR folders get created on the other end, but nothing stagesFinally you get EventID 4312:
The DFS Replication service failed to get folder information when walking the file system on a journal wrap or loss recovery due to repeated sharing violations encountered on a folder. The service cannot replicate the folder and files in that folder until the sharing violation is resolved.  Additional Information:  Folder: F:\Users$\\Desktop\Random Folder Name\  Replicated Folder Root: F:\Users$  File ID: {00000000-0000-0000-0000-000000000000}-v0  Replicated Folder Name: Users  Replicated Folder ID: 33F0449D-5E67-4DA1-99AC-681B5BACC7E5  Replication Group…

Fixing duplicate SPNs (service principal name)

This is a pretty handy thing to know:

SPNs are used when a specific service/daemon uses Kerberos to authenticate against AD. They map a specific service, port, and object together with this convention: class/host:port/name

If you use a computer object to auth (such as local service):

If you use a user object to auth (such as a service account, or admin account):

Why do we care about duplicate SPNs? If you have two entries trying to auth using the same Kerberos ticket (I think that's right...), they will conflict, and cause errors and service failures.

To check for duplicate SPNs:
The command "setspn.exe -X

C:\Windows\system32>setspn -X
Processing entry 7
MSSQLSvc/ is registered on these accounts:
CN=SQL Admin,OU=service accounts,OU=resources,DC=company,DC=local

found 1 groups of duplicate SPNs. (truncated/sanitized)

Note that y…

Logstash to Nagios - alerting based on Windows Event ID

This took way longer than it should have to get here's a config and brain dump...

You want to have a central place to analyze Windows Event/IIS/local application logs, alert off specific events, alert off specific situations.  You don't have the budget for a boxed solution.  You want pretty graphs.  You don't particularly care about individual server states.  (see rationale below - although you certainly have all the tools here to care, I haven't provided that configuration)

ELK stack, OMD, NXlog agent, and Rsyslog.  The premise here is as follows:

Event generated on server into EventLogNXlog ships to Logstash inputLogstash filter adds fields and tags to specified eventsLogstash output sends to a passive Nagios service via the Nagios NSCA outputThe passive service on Nagios (Check_MK c/o OMD) does its thing w. alerting
Open Monitoring Distribution, but the real point here is Check_MK (IIRC Icinga uses this...).  It makes Nagios easy to use and main…