runtime corruption on backup volume

Forum History Drobo
1

Hi,

I have a Drobo 5D and since yesterday I’ve been having a problem with corruption on my time machine/backup volume.

Yesterday Time Machine reported that a verification of my backup has failed and would need to start a new backup. I started new backups but each time I would get the same verification error message again. So I tried deleting and recreating the backup volume from the Drobo Dashboard. This again, failed several times during formatting, but eventually it was able to pass. When I tried to backup again with Time Machine, it again reported this error.

I checked the console logs on mac os x and I see this message:
12/5/14 10:46:09.000 AM kernel[0]: hfs: node=3 fileID=4 volume=TimeMachine device=/dev/disk4s2
12/5/14 10:46:09.000 AM kernel[0]: hfs_mark_inconsistent: Runtime corruption detected on TimeMachine, fsck will be forced on next mount.
12/5/14 10:46:09.000 AM kernel[0]: hfs_swap_BTNode: record #-1 invalid offset (0x0000)

I also see messages like this:
12/5/14 10:46:51.000 AM kernel[0]: 0xffffff804bcd9748 : 1861713647428 ns - com_drobo_SCSI_ThunderBoltController::InitializeController() 0xffffff8063cf3c00 - BAR remap interrupt not processed yet
12/5/14 10:48:02.000 AM kernel[0]: 0xffffff804846dbf0 : 1932015092397 ns - com_drobo_SCSIChannel::ProcessCompleteRequests() 0xffffff8063cf3c00 - 0xffffff8044722000 request failed with result 1.
12/5/14 10:48:03.000 AM kernel[0]: 0xffffff804846dbf0 : 1933018074107 ns - com_drobo_SCSIChannel::ProcessCompleteRequests() 0xffffff8063cf3c00 - 0xffffff8044722000 actualTransferSize (0x1C) != transferSize (0x20) transID: 0x0
12/5/14 10:48:03.000 AM kernel[0]: 0xffffff804846dbf0 : 1933018612070 ns - com_drobo_SCSIChannel::ProcessCompleteRequests() 0xffffff8063cf3c00 - 0xffffff8044722000 actualTransferSize (0x1C) != transferSize (0x820) transID: 0x0

The Drobo dashboard reports that all my disks and my devices are green and functioning correctly. I also seem to have no problems with my primary Drobo storage volume as of yet.

Any ideas on what might be going on? Do I have a broken drobo volume set or broken drobo?

2

This morning I ran into a similar issue. I have a iMac 5k (OS X 10.10.1 - Drobo Dashboard 2.6.3[70504]) connected to a Drobo 5D via Apple 2m Lightning cable. The Drobo has 5 6TB WD RED drives and a 128 GB mSATA SSD. I was untar’ing a 3 Gb tar file and the iMac just hung with the following in dmesg:

[font=Courier]0xffffff804c904338 : 48644400367109 ns - com_drobo_SCSIChannel::ProcessCompleteRequests() 0xffffff806be94800 - 0xffffff80593bf000 actualTransferSize (0x1C) != transferSize (0x40) transID: 0x0
0xffffff804c904338 : 48644404049145 ns - com_drobo_SCSIChannel::ProcessCompleteRequests() 0xffffff806be94800 - 0xffffff80593bf000 actualTransferSize (0x1C) != transferSize (0x40) transID: 0x0
0xffffff804c904338 : 48644757007406 ns - com_drobo_SCSIChannel::ProcessCompleteRequests() 0xffffff806be94800 - 0xffffff80593bf000 actualTransferSize (0x1C) != transferSize (0x40) transID: 0x0
0xffffff804c904338 : 48644785028814 ns - com_drobo_SCSIChannel::ProcessCompleteRequests() 0xffffff806be94800 - 0xffffff80593bf000 actualTransferSize (0x1C) != transferSize (0x40) transID: 0x0[/font]

I ended up having to unplug and replug the Drobo to get things to work. I am going to have to guess that the OS X drivers have at least some error handling issues. I have the Drobo Diagnostic zip file it anyone knows how to decrypt it…