Drobo

Drobo Gen3 recurring unmount on macOS

I have a Gen3 Drobo that has been doing odd things.

It will unmount and remount a short time later. Sometimes it doesn’t remount, then goes into standby. If I pull the USB and plug it in again, it will mount.

If I catch it when it unmounts, it will show a red light on one of the drives, then the red light goes away and it remounts.

The OS has many unsafe unmount warnings:

After I turned on critical situation alert emails, I get an email most of the time that this event happens.

I got the diagnostics files and it looks like these issues line up with the following TMDiags log messages:
TM: 0x700002bae000 07\21 07:31:51 Error - SCSISession::execute - Unknown problems from calling user client: 0xE00002C2
TM: 0x700002bae000 07\21 07:31:51 Error - ESABlockDevice::doPollESAUpdate() - Error fetching ESA system settings
TM: 0x700002bae000 07\21 07:31:51 Error - ESABlockDevice::doPollESAUdate() - Failed
TM: 0x700002bae000 07\21 07:31:51 Error - ESABlockDevice::doPoll polling failed. cached info is used to send up to Dashboard
TM: 0x700002bae000 07\21 07:31:51 Error - ESABlockDevice::PopulateESAUpdate - Error occurred during this polling interval for dra150401d01875
TM: 0x700002bae000 07\21 07:32:39 Error - SCSISession::execute - Unknown problems from calling user client: 0xE00002BC
TM: 0x700002bae000 07\21 07:32:39 Error - ESABlockDevice::doPollESAUpdate the new feature table we got is invalid, all 0 out. Let’s disgard it and use previous value -1871843841
TM: 0x700002bae000 07\21 07:32:39 Error - SCSISession::execute - Unknown problems from calling user client: 0x10000003
TM: 0x700002bae000 07\21 07:32:39 Error - ESABlockDevice::doPollESAUpdate() - Error fetching ESA system settings
TM: 0x700002bae000 07\21 07:32:39 Error - ESABlockDevice::doPollESAUdate() - Failed
TM: 0x700002bae000 07\21 07:32:39 Error - ESABlockDevice::doPoll polling failed. cached info is used to send up to Dashboard
TM: 0x700002bae000 07\21 07:32:39 Error - ESABlockDevice::PopulateESAUpdate - Error occurred during this polling interval for dra150401d01875
TM: 0x70000335b000 07\21 07:32:40 Information - iocscsi::close - ***** IOServiceClose( 0xa4f ) with status 0x10000003
TM: 0x70000335b000 07\21 07:32:40 Error - IOServiceClose returned 0x10000003
TM: 0x700002dba000 07\21 07:33:27 Information - PNPManager::enumESAs - ***** IOServiceOpen returned ( 0x5623 ) and status 0x0
TM: 0x700002bae000 07\21 07:33:58 Error - PNPManager::GetFSVolumeRefNum - No volume reference numbers found for disk2s
TM: 0x700002bae000 07\21 07:33:58 Error - PNPManager::GetFSVolumeRefNum - No volume reference numbers found for disk2s
TM: 0x700002bae000 07\21 07:33:58 Error - PNPManager::GetFSVolumeRefNum - No volume reference numbers found for disk2s
TM: 0x700002bae000 07\21 07:33:58 Information - ESAAlertHistory::Update - ESA status change for ID dra150401d01875 - 0x0 to 0x2
TM: 0x700003255000 07\21 07:34:03 Information - AlertMailer - Send alert: 0x2, severity: 0

It’s always disk2s. I’ve swapped drives and it continues to be disk2s. Is there anything I can do to resolve this, or is it simply a hardware failure?