Posts Related to Use of Drobo FS in my Personal Context

  • : Function ereg() is deprecated in /home/terry/public_html/includes/file.inc on line 647.
  • : Function ereg() is deprecated in /home/terry/public_html/includes/file.inc on line 647.
  • : Function ereg() is deprecated in /home/terry/public_html/includes/file.inc on line 647.
  • : Function ereg() is deprecated in /home/terry/public_html/includes/file.inc on line 647.
  • : Function ereg() is deprecated in /home/terry/public_html/includes/file.inc on line 647.
  • : Function ereg() is deprecated in /home/terry/public_html/includes/file.inc on line 647.
  • : Function ereg() is deprecated in /home/terry/public_html/includes/file.inc on line 647.
  • : Function ereg() is deprecated in /home/terry/public_html/includes/file.inc on line 647.
  • : Function ereg() is deprecated in /home/terry/public_html/includes/file.inc on line 647.
  • : Function ereg() is deprecated in /home/terry/public_html/includes/file.inc on line 647.
  • warning: Parameter 1 to theme_field() expected to be a reference, value given in /home/terry/public_html/includes/theme.inc on line 170.
  • warning: Parameter 1 to theme_field() expected to be a reference, value given in /home/terry/public_html/includes/theme.inc on line 170.
  • warning: Parameter 1 to theme_field() expected to be a reference, value given in /home/terry/public_html/includes/theme.inc on line 170.
  • warning: Parameter 1 to theme_field() expected to be a reference, value given in /home/terry/public_html/includes/theme.inc on line 170.
  • warning: Parameter 1 to theme_field() expected to be a reference, value given in /home/terry/public_html/includes/theme.inc on line 170.
  • warning: Parameter 1 to theme_field() expected to be a reference, value given in /home/terry/public_html/includes/theme.inc on line 170.
  • warning: Parameter 1 to theme_field() expected to be a reference, value given in /home/terry/public_html/includes/theme.inc on line 170.
  • warning: Parameter 1 to theme_field() expected to be a reference, value given in /home/terry/public_html/includes/theme.inc on line 170.
  • warning: Parameter 1 to theme_field() expected to be a reference, value given in /home/terry/public_html/includes/theme.inc on line 170.
  • warning: Parameter 1 to theme_field() expected to be a reference, value given in /home/terry/public_html/includes/theme.inc on line 170.

01/26/2011 01:18 AM

As there is clearly still an issue I invoked the diagnostics option again in Drobo Dashboard. This represents the situation leading up to me stopping the backup. I hope that the enclosed file helps.

(File not enclosed here for security reasons)


01/26/2011 02:15 AM

I have discontinued the backup process on the Drobo for the Power Mac and I await further assistance from Drobo Support.

For security I have now reverted to my former backup process to a 5 bay Sonnet system.

I have to admit that I am now feeling rather pessimistic and loss of 10s of hours of time in trying to get this system to work is dispiriting.


01/27/2011 01:55 AM

Auto upgrade took place this morning to:

Drobo Dashboard 1.7.3 [1.7.30095]
Drobo Firmware 1.1.1 [4.24.34540]


01/29/2011 09:05 AM

Since the vendor seemed to be taking some time to replace the 2TB Seagate drive I purchased an additional one from Amazon. It arrived this morning. Unfortunately it was dead on arrival. The Drobo classed it as faulty/defective. I have sent it back to Amazon and I should have a replacement for that on Monday. I replaced the 250GB in slot 1 and Drobo has gone through the restoration process again.

Some help would be gratefully received as I need to know if I have a faulty Drobo. I am beginning to think that the Drobo may have to be sent back.

Best wishes

(Note: 1 defective Seagate drive out of 5 from one vendor then a another dead on arrival from another vendor - is there a question about the quality of these drives?)


02/01/2011 03:58 AM

Tuesday. I received the replacement Seagate Barracuda Low Power Hard Drive, 2 TB, SATA, 5900 RPM, 32MB Cache from Amazon. I fitted it into bay 1 (top bay) and as before it registered as defective (red) - then the red light went out as if there was no drive in that bay. Having already had two apparent drive failures in that bay I felt that I should try the replacement drive in another bay.

With all drives removed I inserted the replacement into bay 5 and the Drobo started also indicating that a 2TB drive unit was inserted. That drive unit thus appeared not to be faulty after all - as I expected.

I then went back to the original configuration with the replacement drive in bay 1 but with all the other drives in place. Again the Drobo rejected it.

At that point I re-inserted the 0.25GB drive into bay 1 with all other drives in place. The Drobo accepted the 0.25GB unit as expected and it is now in the process of protecting the data again.

Conclusion: There is some issue with bay 1 or the software associated with the Drobo.

Clearly I am causing the vendors of the drive units considerable inconvenience sending back units which I suspect are not faulty and I need help. If possible may I please have some technical assistance now. Last contact from you was 7 days ago.

Best wishes


02/01/2011 06:45 AM

After a phone call it was concluded that there might be an issue with the power supply unit and possibly the Drobo. I was advised that replacements would be sent . This was done quickly and efficiently.


02/03/2011 05:48 AM

Thank you for a most helpful and courteous response to my phone call. I received the replacement Drobo and power supply late this morning.

I have installed all discs including the new 2TB Seagate. The new disc in bay 1 was recognised without any difficulty. The existing information transferred across and so existing backups can continue.

The Drobo is currently engaged with the Power Mac Time Machine backup. I suspect that this will take 24 hours before I can see whether or not the new system is slow in data transfer.

I will update this support ticket as soon as I have any further information. Meanwhile I will package and arrange to return the Drobo which is being replaced minus the original power supply as directed - it was suspected of being faulty.

Best wishes


02/04/2011 02:03 AM

The backup started yesterday has faltered. Screen shot of 3rd Feb shows the status of the Time Machine backup (TimeMachineStuckAgain3rdFeb.jpg). I stopped the backup - progress had halted.

I will also supply diagnostics.

I am going to phone Drobo support this morning.

The only alternative next action is to delete the TimeMachine share which has taken days to produce just in case there is a problem with the .sparseburdle file - and then start again.


02/04/2011 02:08 AM

Sorry it seems as though I have reached the limit of attachments for this ticket. The 'choose file' is not available to me - it is 'grayed-out'. I can provide diagnostics by email if requested. It doesn't seem to make sense to me to create a new ticket when the whole story of the event is in this discussion.

I will phone this morning.

Npte: This problem recurred several times as the story of the evolved. ie I had to open up new tickets as the support system had either a limit on aggregate attachment size or number of attachments.


02/04/2011 02:47 AM

I'm just gathering my thoughts prior to phoning Drobo support. Issues which may be important.

The TimeMachine share which seems to be the problem runs under the root user. Could this be the problem?

The latest diagnostic file which I cannot attach is showing lots of TimeOut Events. I have cut and pasted from the diagnostics file below.

Thu Feb 3 19:10:49 2011: HandleTimeoutEvent: Calling IOCTL
Thu Feb 3 20:14:40 2011: HandleTimeoutEvent: Got TIME VALID! Seconds Since Epoch: 1296764080
Thu Feb 3 20:14:40 2011: HandleTimeoutEvent: Calling IOCTL
Thu Feb 3 21:18:32 2011: HandleTimeoutEvent: Got TIME VALID! Seconds Since Epoch: 1296767912
Thu Feb 3 21:18:32 2011: HandleTimeoutEvent: Calling IOCTL
Thu Feb 3 22:22:26 2011: HandleTimeoutEvent: Got TIME VALID! Seconds Since Epoch: 1296771746
Thu Feb 3 22:22:26 2011: HandleTimeoutEvent: Calling IOCTL
Thu Feb 3 23:26:17 2011: HandleTimeoutEvent: Got TIME VALID! Seconds Since Epoch: 1296775577
Thu Feb 3 23:26:17 2011: setTimeIfLooksValid: Ignoring time from Vx Kernel since our time lookscorrect: Vx secs: 1296775577, Local secs: 1296804377
Thu Feb 3 23:26:17 2011: HandleTimeoutEvent: Calling IOCTL
Fri Feb 4 00:30:08 2011: HandleTimeoutEvent: Got TIME VALID! Seconds Since Epoch: 1296779408
Fri Feb 4 00:30:08 2011: HandleTimeoutEvent: Calling IOCTL
Fri Feb 4 01:33:59 2011: HandleTimeoutEvent: Got TIME VALID! Seconds Since Epoch: 1296783239
Fri Feb 4 01:33:59 2011: HandleTimeoutEvent: Calling IOCTL
forkProcessAndWaitForResult: /bin/sh exited with a 0 value
forkProcessAndWaitForResult: /bin/sh exited with a 0 value
forkProcessAndWaitForResult: /bin/sh exited with a 0 value
forkProcessAndWaitForResult: /bin/sh exited with a 0 value
Fri Feb 4 01:53:01 2011: SledCommandThread::HandleTimeoutEvent: GetNASAdminConfig: Received command
Fri Feb 4 01:53:02 2011: SledCommandThread::HandleTimeoutEvent: GetNASSharesConfig: Received command
Fri Feb 4 01:53:28 2011: Got LX SHUTDOWN!
stopping smbd ...

Best wishes