Drobo 5C stops responding for 90 seconds every 20 to 30 minutes. This happens no matter what I am doing or what media I am streaming from it.
I first noticed this through my media player software (Plex) which has ben running without issues for years. I tried playing a movie directly from my 5C and also tried playing music, same issue. I then tried transferring files either to or from the DAS and it demonstrated the same behavior.
Once the 90 seconds is up (I was counting in my head so that may not be exact but it is within 4 seconds every time) everything resumes without issue until it happens again.
All my software (Drobo and Windows) is up to date.
Any ideas would be greatly appreciated.
Looking through the logs I find this…
TM: 00003b3c 01\27 11:07:01 Error - ESADevice::IsZombieDevice - ESA dra164802100113 is a zombie. currTime = 84828375, lastUpdate = 84755687
TM: 00005438 01\27 11:07:06 Error - UThread::EndThread() - Timed out waiting for thread 26e8 to exit
TM: 00005438 01\27 11:07:06 Error - UThread::EndThread(tESABlockDevice_dra164802100113) - Terminating thread 26e8
TM: 00003b3c 01\27 11:22:02 Error - ESADevice::IsZombieDevice - ESA dra164802100113 is a zombie. currTime = 85728859, lastUpdate = 85655718
TM: 00002a90 01\27 11:22:07 Error - UThread::EndThread() - Timed out waiting for thread 6288 to exit
TM: 00002a90 01\27 11:22:07 Error - UThread::EndThread(tESABlockDevice_dra164802100113) - Terminating thread 6288
TM: 00003b40 01\27 11:34:27 Error - FTPClient::GetFile failed to connect to server, error A connection with the server could not be established
TM: 00003b40 01\27 11:34:27 Error - FTPFileManager::DownloadFile - Failed to download file droboapps/2.1/droboapps_listing_2.5.2.xml
TM: 00003b3c 01\27 11:37:02 Error - ESADevice::IsZombieDevice - ESA dra164802100113 is a zombie. currTime = 86629359, lastUpdate = 86555890
TM: 000024a4 01\27 11:37:07 Error - UThread::EndThread() - Timed out waiting for thread 4130 to exit
TM: 000024a4 01\27 11:37:07 Error - UThread::EndThread(tESABlockDevice_dra164802100113) - Terminating thread 4130
TM: 00003b3c 01\27 11:52:03 Error - ESADevice::IsZombieDevice - ESA dra164802100113 is a zombie. currTime = 87529781, lastUpdate = 87455859
TM: 00001e70 01\27 11:52:08 Error - UThread::EndThread() - Timed out waiting for thread 2ee8 to exit
TM: 00001e70 01\27 11:52:08 Error - UThread::EndThread(tESABlockDevice_dra164802100113) - Terminating thread 2ee8
TM: 00003b3c 01\27 12:07:03 Error - ESADevice::IsZombieDevice - ESA dra164802100113 is a zombie. currTime = 88430281, lastUpdate = 88356171
TM: 00001fe4 01\27 12:07:08 Error - UThread::EndThread() - Timed out waiting for thread 4950 to exit
TM: 00001fe4 01\27 12:07:08 Error - UThread::EndThread(tESABlockDevice_dra164802100113) - Terminating thread 4950
TM: 00003b3c 01\27 12:22:04 Error - ESADevice::IsZombieDevice - ESA dra164802100113 is a zombie. currTime = 89330781, lastUpdate = 89256328
TM: 000061ec 01\27 12:22:09 Error - UThread::EndThread() - Timed out waiting for thread 4d64 to exit
TM: 000061ec 01\27 12:22:09 Error - UThread::EndThread(tESABlockDevice_dra164802100113) - Terminating thread 4d64
TM: 00003b3c 01\27 12:37:04 Error - ESADevice::IsZombieDevice - ESA dra164802100113 is a zombie. currTime = 90231281, lastUpdate = 90156625
TM: 00001d5c 01\27 12:37:09 Error - UThread::EndThread() - Timed out waiting for thread 5fb4 to exit
TM: 00001d5c 01\27 12:37:09 Error - UThread::EndThread(tESABlockDevice_dra164802100113) - Terminating thread 5fb4
TM: 00003b3c 01\27 12:51:50 Error - ESADevice::IsZombieDevice - ESA dra164802100113 is a zombie. currTime = 91116796, lastUpdate = 91056453
TM: 000059a4 01\27 12:51:55 Error - UThread::EndThread() - Timed out waiting for thread 33c4 to exit
TM: 000059a4 01\27 12:51:55 Error - UThread::EndThread(tESABlockDevice_dra164802100113) - Terminating thread 33c4
mmmm not sure but all I call tell you is when my 5D started doing that, in a couple of days, drives started failing and eventually had to buy another drobo to get data out. make sure you got a good backup or start backing up most important stuff
Just in case anyone was interested, I removed Drobo Dashboard and the problem seems to have vanished. I will continue to test but I believe their software to be the root of the issue.