Hello, I’ve been using my drobo for about 6 months or so now and love it. Recently, the performance has been poor though, and I’m wondering if it’s a bad drive. My main purpose of the drobo is for network storage and using with plex. Lately, I can’t get through a movie without it constantly buffering. This was never a problem in the past. I’ve reset everything and the network is good. While I was on the dashboard the other day, the drive in bay 0 went to a red/critical state and now it’s sitting at a yellow/warning state, but the overall condition is greed/good.
Disk space is getting up there, but still have 2TB available of space according to the Capacity in the dashboard. This is my largest drive. This one is a 3tb, I also have 3x2TB and 1x1.5TB.
Does the fact that it went to critical then to warning indicate the drive is bad and needs replacement?
If the lights are flashing red at you then your drive has failed and needs to be replaced. If it’s just a solid yellow light then you’re running out of space on the Drobo.
If you are running out of space, what you should do is replace the smallest drive you have with a 2 or 3TB drive. I would recommend a 3TB drive so that you gain more space. If you get below 80% capacity the Drobo will begin to slow down just like any other storage system would.
Okay, thanks. So, is that normal, that it would go into a critical state prior to a warning state? Currently, the lights are all green, but the warning label (green outline with yellow warning) remains on the 3TB drive. All other drives have a green good, except the 3tb.
Yes, it’s normal. It’s not a critical state (that’s red).
When free capacity gets low and write speed is at risk of being seriously degraded (ie due to needing to rewrite slack sector space etc…) then the status light of Drive Bay 0 will go yellow. This is not a fault with Drive Bay 0, but a sign that you need to increase capacity.
The best way to do this, would be to swap your 1.5TB drive for the best capacity drive you can get (they do nice 4TB WD Reds now I think).
No, there’s something else going on here. This is not a complete failure state (red light) or a low capacity issue (yellow light). I’m seeing the exact same thing, and all physical lights are green, all drives in the Dashboard are drawn as green, and I have 2TB free on a 10TB array. The drive in Bay 0 shows the same status - green light, no action needed, but a yellow warning label in Dashboard if I inspect the individual drives.
However, like the original poster I’ve also been getting poor to impossible performance from my 5N (two tickets opened so far with support and no resolution: 140102-000057 and 140204-000153). When using my 5N transfers either slow or fail completely, and if I’m SSH’ed in at the time I can see CPU load skyrocketing while actual CPU usage remains non-existent. I’ve applied to replace my top drive (4TB Seagate) under warranty, but now I wonder if this isn’t a fault in the 5N itself.
[quote=“diamondsw, post:5, topic:139415”]
No, there’s something else going on here. This is not a complete failure state (red light) or a low capacity issue (yellow light). I’m seeing the exact same thing, and all physical lights are green, all drives in the Dashboard are drawn as green, and I have 2TB free on a 10TB array. The drive in Bay 0 shows the same status - green light, no action needed, but a yellow warning label in Dashboard if I inspect the individual drives.[/quote]
My bad - sorry I missed the particular detail about the discrepancy between the Dashboard report and the actual lights.
Wonder if this has any relation to the recent firmware update? Diamondsw, please keep me posted and feel free to attach me to those tickets if I can help.
In my case it started well before the updates - I first noticed the odd drive label in November/December. I’m able to write to the Drobo again (not sure why, but I can), but Drobo Inc hasn’t so much as looked at my ticket.
I haven’t had a response from them either. I submitted the same info with details under ticket 140206-000043. I’m thinking of just getting another hard drive and swapping it out with this one in warning in bay 0 to see if that solves the issue. I need more space anyways…