Everybody Staze...

Nobody leavz...

  • Home
  • About Me
    • LinkedIn
    • Lab
  • Contact
  • Links
  • Reviews
  • Sitemap
  • Weather

Drobo 5D Review

2015/01/13 By staze

Drobo 5DFor the last year I’ve had a Drobo 5D on my desk hooked to my Mac Pro. I’ve loved the unit as it’s fast, and so far, extremely reliable. I have it connected to the Mac Pro via Thunderbolt, on bus 1 ((Don’t get me started on the Thunderbolt buses on the Mac Pro. I had to move stuff around several times to get one of my monitors to NOT randomly go black now and then)). When I initially purchased the unit, I didn’t have the SSD cache installed, and had 4 2TB Western Digital (WD) Black drives in it (giving me 6TB of usable storage). The only problem I had with it was the 7200RPM drives caused a bit of vibration, so occasionally it would make noise, or anytime something was touching the body of the Drobo, it would cause a rattling. But the performance was excellent (significantly faster than my Drobo 4-bay 2nd Generation at home).

Since buying it, however, I’ve done two things. First, I purchased a Crucial 128GB mSATA SSD for it’s cache, which boosted the performance another 25% or so, and just yesterday, I upgraded to 3x WD 4TB Red drives. The biggest advantage of that being TLER support, as well as drive speed/balance. The Drobo is now “silent”, and there is no physical vibration to the enclosure at all (gotta say, I love the “Red” drives). While the spindle speed is slower ((WD doesn’t actually advertise their speed, but it has been deduced to be 5,400RPM)), the platter density is higher. This should largely even out transfer speed changes with larger files, which was evident in my data restore once I had swapped all the drives ((Tidbit: The 5D is “smart” in that if you are replacing all the drives at once, it will come up in an error state if you pull all the old hard drives out, and put in new HD’s. You have to then “reset” it to get it to recognize the new drives. This is interesting because my 2nd generation 4-bay never did this)). If you’re upgrading drives, doing a backup/restore is going to be significantly faster than swapping one drive at a time (which the Drobo will let you do, but each rebuild will probably take 24 hours to complete if you have a significantly sized volume).

Actual read/write performance on the unit is pretty good. With sequential read/writes at 145MB/sec both ways. My 4-bay 2nd generation scored about 25MB/sec each way. Random access is not based on throughput so much as IOPs. Sadly, it scores only about 100/sec in that space, but that’s not bad for a Drobo, since my old 2nd generation only scored 50/sec.

All and all, I’m very happy with the 5D. While the price point is a bit high, it really is a great external storage device. If you can afford it, I’d highly recommend it.

[xrr rating=5/5]

Update: I contacted Drobo a few days ago asking about a review unit of the new 4-bay, and sadly, heard nothing back. As “luck” would have it, though, Adorama had a sale for one for about $70 off street price, so I purchased one to upgrade my home 2nd generation Drobo. I’ll be posting a review of that new unit once I have it, and move my drives over. =)

Filed Under: Reviews Tagged With: 5D, Drobo, SSD

fail2ban WordPress and Cloudflare

2015/01/12 By staze

Fail2ban_logoLike most people that run a WordPress site, or any CMS, I’ve struggled with brute force attacks on my site. Having just installed fail2ban on a mail server, this seemed like an obvious. Thankfully, as well, someone had already written a plugin for WordPress to drop a message in the system log saying a login failed (by default, Apache doesn’t do this, it just shows someone hit the login page). At first, I had set up an iptables/pf rule to block the bad user, but for some reason, this wasn’t happening. My test browser kept hitting the page successfully.

After a break, I realized that I use Cloudflare, and of course blocking the offending IP wouldn’t work… it never actually connects to my host. Thankfully, Cloudflare has an API, and there was already a starting point for a fail2ban action, albeit, out of date (Cloudflare forces json now). Below is that action. You should be able to just call this like any other action, after you fill out the appropriate “token” and “email”. ((Note: I had to disable “always online” with Cloudflare to have the block take effect within 5-10 seconds. With “always online” enabled, it took about 2-3 minutes to block the attack, all the while the “bot” was able to keep hitting my server.))

Good luck!


# Fail2Ban cloudflare action
#
# Author: Ryan Stasel
#
# $Revision$
#

[Definition]

# Option: actionstart
# Notes.: command executed once at the start of Fail2Ban.
# Values: CMD
#
actionstart =

# Option: actionstop
# Notes.: command executed once at the end of Fail2Ban
# Values: CMD
#
actionstop =

# Option: actioncheck
# Notes.: command executed once before each actionban command
# Values: CMD
#
actioncheck =

# Option: actionban
# Notes.: command executed when banning an IP. Take care that the
# command is executed with Fail2Ban user rights.
# Tags: <ip> IP address
# <failures> number of failures
# <time> unix timestamp of the ban time
# Values: CMD
#
actionban = curl -s https://www.cloudflare.com/api_json.html -d ‘a=ban’ -d ‘key=‘ -d ’email=‘ -d ‘tkn=‘

# Option: actionunban
# Notes.: command executed when unbanning an IP. Take care that the
# command is executed with Fail2Ban user rights.
# Tags: <ip> IP address
# <failures> number of failures
# <time> unix timestamp of the ban time
# Values: CMD
#
actionunban = curl -s https://www.cloudflare.com/api_json.html -d ‘a=nul’ -d ‘key=‘ -d ’email=‘ -d ‘tkn=‘

[Init]

account = YOUR_CLOUDFLARE_EMAIL

token = YOUR_CLOUDFLARE_TOKEN

Filed Under: Sys Admin Tagged With: Cloudflare, fail2ban, Wordpress

Quick repair of Fluke 87 (Faded Digits)

2015/01/09 By staze

Fluke 87 Faded DigitsAt my suggestion, a coworker purchased a Fluke 87 (Series 1) off eBay, with the faded digit problem, for $70 a week ago. A very good deal. I assured him I could repair it.

The meter arrived, and really, there was very little fading, but it still needed “repair”. Rather than bring it home, I pulled it apart here and showed him what to do (should it happen again). Mr. Modemhead has a great article on this, but also there is a video from Fluke themselves on the issue, even though they’re incorrect on some facts with regards to the original 87 (they say there’s only one zebra strip, when there are two). Anyway, I’ve done the modemhead way, but I thought I’d try Fluke’s suggestion, and just clean the PCB side of the connection. I used some cotton swabs and 99% IPA, and after a couple minutes of scrubbing until clean, I put everything back together, and bingo! It works great. =)

Interestingly, this meter also had a slight issue with the buzzer/beeper. Turns out the speaker (Piezo) uses two rubber “nipples” to make contact with contact points on the back of the PCB. One of these nipples had been squashed/distorted over time and if you screwed the back of the meter on fully/snuggly, the nipple would distort enough to lose contact with the PCB. Simple solution was to leave the middle back screw loose, and place a piece of tape over the screw. Problem solved. =)

Filed Under: Electronics Tagged With: Faded Digits, Fluke 87, Multimeter, repair

« Previous Page
Next Page »

Weather

Categories / Archives

  • Apple
  • Coding
  • Electronics
  • Energy
  • Home Ownership
  • Miscellany
  • Politics
  • Prius
  • Sys Admin
  • Travel
  • Uncategorized
  • Work
  • June 2026
  • April 2026
  • August 2025
  • April 2025
  • January 2024
  • February 2021
  • July 2020
  • January 2020
  • April 2019
  • March 2018
  • February 2018
  • June 2017

Copyright © 2026 · Staze On Genesis Framework · WordPress · Log in