Live data from Hacker News

Here's why you should not buy a Drobo

jan.rychter.com

61–70 of 74 posts

Re: Here's why you should not buy a Drobo

#62
post #9

I'm not sure on how to reply, because experiences with a Drobo seem to be extremely hit or miss and it is all very anecdotal. My drobo with all WD green drives is as silent as my Mac minis and MBP are, while a friend of mine has one also with similar drives that's so loud it's very difficult to sleep in the same room with it (and yes, it rivals his Mac Pro in terms of noise). I've not had a single problem with my dro…

If the experience is so hit or miss that speaks against trying your luck, no?

Failure is inevitable and it is only a matter of time until it happens. You're going to be finding the same issues with any other nas/raid solution and with the drives you use in them. Maybe drobo is more likely to fail than the others or something by unfortunate design (and with droboshare, I could believe the fs corruption), but they all have the potential to fail in some way. (You're also talking to someone that's had more SSDs than hard drives die on her in the past six months...)

When I was shopping around for drobo alternatives (back when I couldn't stomach the price just yet to buy one and I was getting a bit sick of my hacked-together raid in one of my computers), product reviews and blog entries read exactly like what I see here with the drobo being hit or miss. There were people that were all "DO NOT BUY!!" because they lost all their data next to the people just gushing over how much they liked theirs cause it was working like a charm. This is a tough market, because people don't want to lose their data, and when (not if...) they do they get quite pissed.

It's really up to you to determine your needs and to find a device or twenty that meets them. I rather like the drobo because it's zero maintenance. I don't trust my data to it, I only trust it to keep working when a drive has failed. But that's about all I can expect from any such device. The whole market is pretty much hit or miss for people - it's a hit until it misses, then all you can think about is how it missed.

Re: Here's why you should not buy a Drobo

#63

Earlier quoted context omitted.

> I guess it's OK to use a Drobo if you get another one as backup for the first one — but then, what's the point? RAID is _not_ a backup. If you don't understand this, you'll never be satisfied with any RAIDish products.

It's true that RAID is not a backup, but backup strategies are rarely any good if they back up data "instantly", which is what redundancy provides. So you're stuck with a catch 22. If you back up instantly (without versioning), you may backup bad data. Boooo! If you backup, say, daily, you still stand to lose a days work when your array fails. Boooo! RAID should increase reliability, not decrease it. Any RAID solutio…

That's a catch 22 that can be minimized or even avoided altogether. My main drobo backup is automatically versioned and backed up every 12 hours (to a single external drive, since I don't need to back up everything on my drobo). I've got older backups dating from like a week (work-related) to half a year or more old (for the important docs that don't change that I should keep around regardless...like old accounting/tax stuff) stashed around my home, online, and in a safe deposit box at my bank. And of course occasionally I test whether or not my backup is actually backing up the things I want and that I can successfully restore from it.

If I back up bad data, I have older but good data to recover from. If my drobo catastrophically fails, at the worst I've lost data that is probably not going to be difficult to replicate/replace because of how new it is. I don't have to start ripping my hair out at the idea of having lost an incredible amount of data ranging from irreplaceable photos of my life to work and more.

In the ideal case, raid should increase reliability, and they do, only for one definition of reliability. But freak accidents and poor design happen, and it's silly to rely only on a raid for reliability.

Re: Here's why you should not buy a Drobo

#64
post #11
post #9

I'm not sure on how to reply, because experiences with a Drobo seem to be extremely hit or miss and it is all very anecdotal. My drobo with all WD green drives is as silent as my Mac minis and MBP are, while a friend of mine has one also with similar drives that's so loud it's very difficult to sleep in the same room with it (and yes, it rivals his Mac Pro in terms of noise). I've not had a single problem with my dro…

Well, in my case the failures are obvious and objectively present. You can't really discuss expectations if your device just lost all your data due to filesystem corruption. You don't discuss "infallibility" if your device tells you: Buffer I/O error on device sda1, logical block 422806282 scsi2 (0:0): rejecting I/O to dead device SCSI error : return code = 0x70000 end_request: I/O error, dev sda, sector 4533105544 H…

Oh, I'm not claiming they don't ever fail...they do. It happens. I can read your errors for myself. However, redundancy doesn't mean that you avoid fs corruption altogether.

If my drobo fails, so be it, drobo sucks etc., but my data is my responsibility. I have backups in place to deal with the data loss. I'm not asking my drobo to be perfect, I'm just asking it to keep on working in case a drive starts to fail, but there's clearly many possibilities where drobo itself fails. If there's fs corruption going on, it's my responsibility even if it's the fault of the hardware. If there's something I deleted off my drobo by accident, it's my responsibility.

Now, if you were going on about the bad design and hacky nature of droboshare and the software drobo runs on, and data robotics' bad customer support, then sure...you have a point. We could all learn from your experience not to use droboshare. That's about it.

Re: Here's why you should not buy a Drobo

#65
I've owned a 2nd-gen Drobo and now a DroboPro. My experience with it is very mixed. My opinion is that it's a good solution for someone who can't be bothered with mdadm anymore and needs a lot of storage, with some important caveats.

When it works, it's fantastic. When things start to go wrong, there's nothing you can do about it except experiment with switching drives or email support and hope they can diagnose it.

I loaded my first Drobo with Seagate 1.5tb drives. It constantly dropped drives out of the array and was very slow (I then upgraded to a DroboPro as I had outgrown the 4 drive version, which was painless. It was still slow, but not as much. The log is now ENCRYPTED(!!!) so there is absolutely nothing you can see for yourself other than whether a drive is "bad" or "good". If you suspect that one of the drives might be failing, you have to email your encrypted log to Drobo and wait for them to respond. Which is pretty frustrating when you're in another timezone and each exchange takes 24 hours.

Somewhere among switching around drives and upgrading firmware it became faster, and now to me seems acceptably fast. I think I must have just had a bad drive or three, but of course without access to any logs it's a tedious and expensive process of trial and error to figure out.

All was well, and then just shy of a year it stopped booting. I bought it in one country and then moved, so had to ship it back to the original distributor, which is annoying and expensive but understandable, but of course you can only access the drives with another Drobo, and means I'll be without access to my stuff for about a month (except for backups). I wasn't too impressed about what is marketed as a professional product designed to run 24/7 failing after less than a year of light use.

Pros:

* Very easy to use. Auto-expansion is fantastic and works as advertised. You literally only have to shove a new drive in the slot and wait a few minutes. * Don't have to rebuild when you add capacity * Don't lose all your data if you disconnect 2 drives at once, put them back in a different order, or any of the myriad interesting ways you can accidentally kill your entire array with RAID.

Cons:

* Somewhat pricey. But you get what you pay for - at least I did until it died. * Encrypting the log files is outrageous. This is probably the worst thing about it. * No transparency about what it's doing. It's quite literally a black box. * iSCSI on Mac doesn't reliably reconnect if you unmount it. I usually have to restart the device and/or my PC. * No way of accessing data (other than another Drobo) if the device fails. * Not particularly fast. Much slower than a bare drive. 40MB/sec if I'm lucky. No idea how they got VMware certification; trying to boot from it would be agonizing.

Other thoughts:

* Others have said it sounds like a jet engine. It's not quiet, but it's by no means loud. It's just two 80mm fans spinning at maybe 1200rpm or less. Drives always seem cool to the touch. You probably couldn't sleep with one next to your head but in the next room, no problem. * It takes days to rebuild 8TB when you switch out a bare drive. So does normal RAID though.

Re: Here's why you should not buy a Drobo

#66
post #56

I've read most of the comments here and I think people are missing the point. Forget the noise, that's just an inconvenience. More importantly: The "reliable" data storage device I bought corrupted and lost my data once, and right now is showing the symptoms of corrupting the filesystem again. I doesn't get any simpler and more objective than that. And to those people whose Drobos have been working fine so far: I wis…

[deleted]

Re: Here's why you should not buy a Drobo

#67

Why isn't Drobo in the comments here responding?

Why should they be? They have an official support channel--they aren't obligated to have some poor "evangelist" follow up on every reference to their product on the internet.

Some companies might do this, and you might be used to getting a semi-canned response on Twitter every time you mention a company's name, but that doesn't translate into any kind of obligation on their part.

Re: Here's why you should not buy a Drobo

#68

I've been very happy with FreeNAS running on a recycled PowerEdge 400SC. I boot it off a USB thumbdrive and it manages to spin up and down the six SATA drives I'm using with even even with a cheapie 4-port PCI SATA card. My workload is pretty light though as it hosts media and I only stream it from two devices max at a time. But it's hard to beat the price and comprehensive protocol support. FTP, Samba, NFS, AFP, Tim…

Are you using zfs? Have you anyone tries to use freenas as a time machine destination?

I've been using Time Machine on this setup. So far it hasn't complained. But I also haven't had need to restore yet.

As for power consumption, I unfortunately haven't kept tabs on the electricity nor have a Kill-a-Watt.

But I have told FreeNAS to pretty aggressively spin down unused drives.

Re: Here's why you should not buy a Drobo

#69
post #50

First off, I never trust reviews saying that something is extremely loud. Just look at every single fan or video card on newegg and you'll see people complaining that they are the loudest thing they've ever heard and other people claiming they are virtually silent. Secondly, what does the author (or you guys) recommend as an alternative to the Drobo? Just creating your own file server/NAS? Do you need a hardware RAID…

Generally, hardware RAID is good and software RAID is decent. Mobo-integrated and "software hardware RAID" suck.

Re: Here's why you should not buy a Drobo

#70

Earlier quoted context omitted.

> I guess it's OK to use a Drobo if you get another one as backup for the first one — but then, what's the point? RAID is _not_ a backup. If you don't understand this, you'll never be satisfied with any RAIDish products.

It's true that RAID is not a backup, but backup strategies are rarely any good if they back up data "instantly", which is what redundancy provides. So you're stuck with a catch 22. If you back up instantly (without versioning), you may backup bad data. Boooo! If you backup, say, daily, you still stand to lose a days work when your array fails. Boooo! RAID should increase reliability, not decrease it. Any RAID solutio…

That's not a catch-22... You can do both backups and RAID.
Post reply on HN