New User - Added Drives, rebuild process keeps rebooting device

Hi there - have a Drobo 3rd Gen. I started with three drives (750GB, 2TB, 3TB) and last night I removed the 750GB and then added two 1 TB drives.

The Drobo did it’s thing and then said was rebuilding and would take seven hours.

This morning, when I looked at the computer, the Drobo had been “unsafely” unmounted once but was back rebuilding (no time estimate this time).

Since then, it keeps unmounting and appearing to reboot (all lights go off then it powers up again), and then re-mounting.

It’s done that a few times. I moved some of the files from my backup to another hard drive in the mean time so I don’t have to access them on the Drobo (even though it says I can access them safely right now, I was afraid that was causing an issue).

At this moment, all the lights on the Drobo appear correct (solid green across the board) and some lower blue indicating file space usage … but the device is not mounted on my machine and does not appear in Drobo Dashboard. But the lights seem to say it is okay.

Oh wait. Just rebooted again.

Couple things:

  1. Is there a way to rebuild without it being connected to the computer ?
  2. How do I get the rebuild proccess started correctly because it’s in some weird loop right now. I know it can take a long time to rebuild and I’m happy to leave it alone … but it would be better if it weren’t connected.

Thanks,
Damon

Hi

My Drobo S is exactly in the same situation. One of may drives died, I replaced it and it started the rebuild process. After a while it started to do frequent reboots and starting the rebuild process again. For a while I was able to backup some data out of it, but now it’s in a constant rebooting loop being mounted on the computer only for a minute or so :frowning:

Sent an email to Drob Support but they said they wouldn’t help because the Drobo is no longer in the garantee - what the hell is this? No help from the manufacturer because Drobo has 4 years and they still had the guts to suggest I replaced my Drobo with a new one!!! I probably would if I trusted this brand, but with this behaviour my trust in datarobotics has all gone away.

Tried removing the drives and booting Drobo as proposed on the Knowledge Database. Without the drives it didn’t reboot, but it solved nothing because as soon as I added the drives back the constant rebooting returned :frowning:

This problem started only in this February, before that it stayed 4 years without a hiccup, even when I needed to replace a drive last year. New firmware problem?

Anyone has suggestions?

Thanks
Carlos Muralhas

So, after contacting Drobo support, it turned out that one of the drives I had inserted had bad sectors on it which was causing it too fail so miserably. I wish the error handling were a little smoother and more informative. I haven’t looked through my own log files to see if I can find how they identified it … I also am not sure if it is even recoverable if the data is already being moved around before the bad sector is identified.

So, I fixed it by removing the bad drive; buying new drive; reformatting the Drobo and then restoring my backup. Been fine since then. I’m going to be sure I have my backup ready though the next time I do any disk swapping!

Damon

If you replace a drive in Drobo the Drobo goes into rebuild, and during the rebuild the Drobo reboots - this is an indication that a drive is failing. In this scenario it is very possible a drive needs to be block level cloned. Since you have a Drobo Gen 3 it must be under Standard Warranty, would you follow up with our Support team. TY

[quote=“DroboMod, post:4, topic:140529”]If you replace a drive in Drobo the Drobo goes into rebuild, and during the rebuild the Drobo reboots - this is an indication that a drive is failing. In this scenario it is very possible a drive needs to be block level cloned. Since you have a Drobo Gen 3 it must be under Standard Warranty, would you follow up with our Support team. TY
[/quote]

That was indeed the recommendation from the Support Team!

However, it was much easier to replace the faulty drive, format the Drobo, and restore a backup than do a block level clone (with the available hardware I had, anyway).