I replaced a 250GB drive with a 4TB drive to increase my storage capacity in my Drobo 5N. At first all the drive lights were blinking green to yellow and everything seemed happy. I returned about an hour later to find it cycling though this sequence:
It reboots itself.
Immediately after the reboot the drive lights flash green to yellow.
20 seconds later all the drive lights turn solid yellow and the capacity lights all come on
All light turn off and it reboots (back to step one).
Stuff I’ve tried already.
Swapping the power supply with another 5N. No change
Rebooting the device.
Turn off, remove all the drives and turn back on. This finally allowed me to see it in dashboard, but didn’t change the behavior when I put the drives back in.
I can’t get any help from Drobo support because the device is older than a year.
i was looking at the steps of things you tried already, and for your step 3, can i check if the drobo was on when you put your drives back inside, or after seeing it in dashboard, did you power off and then put the drives back in?
from what you mentioned though, it seems that the main unit is ok (as usually an empty unit should be found and recognised in dashboard), though looks like 1 or more drives are encounting problems. (it may possibly be that another drive/drives started to encounter problems during the necessary part of the work that takes place during a rebuild, but i think hopefully there are a few ways forward to try)
in some cases, 1 or more drives may need blockcloning and a certain process, though it is worth trying the above first as it has fixed things for some other users too.
you might already be aware, though just to mention that i believe there is still a way to raise a ticket with the support team (as a pay-per-incident) if you would wish, even if out of support, and they may be able to help also ascertain which actual drive or drives need the cloning, for example as mentioned here: https://myproducts.drobo.com/article/AA-01864
Thanks Paul. I did have the unit on when I put the drives back in and as soon as all five were back it disappeared from dashboard and started the same behaviors.
I tried the read only mode, with no luck.
Everything on the drive is a backup, so I think I’m going to put in all the 3 new drives I was planning on and start fresh. No data loss, and probably not much time lost vs. waiting for the Drobo to bring 3 drives in. Thanks
thanks for the clarification and for trying that,
if you do end up starting fresh, it may be worth updating the firmware as well, if applicable (plus rebooting the drobo once after the update process is complete, just to make sure the new version is showing in dashboard), before putting any data back onto it, though please feel free to let us know how things go.
This thread is two years old but I am now facing this same issue and am hoping that someone can help.
I have a Drobo 5N that now goes into a continuous boot loop when all hard drives are in the Drobo. I am able to see the Drobo in the Dashboard and see it start to attempt a repair process, but only after a few minutes of being up it reboots and starts the process over again. After powering down the Drobo, removing the drives and powering up the Drobo, I am able to see the Drobo in the Dashboard and it does not reboot.
I have a total of five 4 TB drives in the Drobo. I received an alert today via the Dashboard that a drive had been removed, thought it hadn’t been physically, and the data protection process had started. Shortly after that, I noticed the Drobo boot loop had started and here I am.
It was mentioned by @Paul that a read-only mode might make the data available. I have tried to search the Web for such a solution and can’t find anything. At this point, I’m only concerned about recovering the data for now and replacing drives later. Would this be a good option for me? If so, can anyone provide instructions on how I go about putting the Drobo in the read-only mode?
It was also mentioned that block cloning the bad drive might need to be done to fully recover the data. Considering that I can’t get the Drobo to stay on for very long before it reboots, is there an easy way to identify the drive that might be causing the issue? Are there any pointers that someone can give me on block cloning?