Previous 1 2 3 Next 30 Replies Latest reply: Mar 8, 2014 11:00 PM by Alvin Koh
Alvin Koh Level 1 Level 1 (45 points)

On the same day I upgraded to OS X 10.8, I started seeing frequent volume corruption on my Drobo. The corruption persists even after I have reset and reformatted the Drobo, and can happen at any time - after copying a bunch of files, or even after starting up the Drobo. For example, I can use diskutil to verify that the Drobo is fine before shutting it down, only to find the volume corrupted when I power it on. Several times I even saw corruption after leaving the Drobo idle for several hours.

 

Here are some of the errors I see with diskutil when there is corruption.

 

Started file system verification on disk5s2 Drobo

Checking file system

Checking Journaled HFS Plus volume

Checking extents overflow file

Checking catalog file

Checking multi-linked files

Checking catalog hierarchy

Checking extended attributes file

Checking volume bitmap

Checking volume information

Volume header needs minor repair

The volume Drobo was found corrupt and needs to be repaired

Error: -69845: File system verify or repair failed

Underlying error: 8: POSIX reports: Exec format error

 

Started file system verification on disk5s2 Drobo

Checking file system

Checking Journaled HFS Plus volume

Checking extents overflow file

Checking catalog file

Invalid sibling link

The volume Drobo was found corrupt and needs to be repaired

Error: -69845: File system verify or repair failed

Underlying error: 8: POSIX reports: Exec format error

 

Started file system verification on disk4s2 Drobo

Checking file system

Checking Journaled HFS Plus volume

Checking extents overflow file

Checking catalog file

Checking multi-linked files

Checking catalog hierarchy

Checking extended attributes file

Overlapped extent allocation (id = 275951, /Aperture Backups/Aperture Library 2008.aplibrary/Masters/2008/09/07/20080907-231132/DSC_2081.NEF)

Overlapped extent allocation (id = 275952, /Aperture Backups/Aperture Library 2008.aplibrary/Masters/2008/09/07/20080907-231132/DSC_2082.NEF)

Overlapped extent allocation (id = 275953, /Aperture Backups/Aperture Library 2008.aplibrary/Masters/2008/09/07/20080907-231132/DSC_2083.NEF)

Overlapped extent allocation (id = 275954, /Aperture Backups/Aperture Library 2008.aplibrary/Masters/2008/09/07/20080907-231132/DSC_2084.NEF)

Overlapped extent allocation (id = 275955, /Aperture Backups/Aperture Library 2008.aplibrary/Masters/2008/09/07/20080907-231132/DSC_2085.NEF)

Overlapped extent allocation (id = 275956, /Aperture Backups/Aperture Library 2008.aplibrary/Masters/2008/09/07/20080907-231132/DSC_2086.NEF)

Overlapped extent allocation (id = 275957, /Aperture Backups/Aperture Library 2008.aplibrary/Masters/2008/09/07/20080907-231132/DSC_2087.NEF)

Overlapped extent allocation (id = 275958, /Aperture Backups/Aperture Library 2008.aplibrary/Masters/2008/09/07/20080907-231132/DSC_2088.NEF)

Overlapped extent allocation (id = 275959, /Aperture Backups/Aperture Library 2008.aplibrary/Masters/2008/09/07/20080907-231132/DSC_2089.NEF)

Overlapped extent allocation (id = 275960, /Aperture Backups/Aperture Library 2008.aplibrary/Masters/2008/09/07/20080907-231132/DSC_2090.NEF)

Overlapped extent allocation (id = 600188, /Aperture Backups/Miscellaneous Library.aplibrary/Masters/2010/08/03/20100803-090117/DSCF9143.RAF)

Overlapped extent allocation (id = 600191, /Aperture Backups/Miscellaneous Library.aplibrary/Masters/2010/08/04/20100804-145503/DSC_6409.NEF)

Overlapped extent allocation (id = 600192, /Aperture Backups/Miscellaneous Library.aplibrary/Masters/2010/08/04/20100804-145503/DSC_6410.NEF)

Overlapped extent allocation (id = 600193, /Aperture Backups/Miscellaneous Library.aplibrary/Masters/2010/08/04/20100804-145503/DSC_6411.NEF)

Overlapped extent allocation (id = 600194, /Aperture Backups/Miscellaneous Library.aplibrary/Masters/2010/08/04/20100804-145503/DSC_6412.NEF)

Overlapped extent allocation (id = 600196, /Aperture Backups/Miscellaneous Library.aplibrary/Masters/2010/08/04/20100804-145617/DSCF9178.RAF)

Overlapped extent allocation (id = 600197, /Aperture Backups/Miscellaneous Library.aplibrary/Masters/2010/08/04/20100804-145617/DSCF9179.RAF)

Overlapped extent allocation (id = 600198, /Aperture Backups/Miscellaneous Library.aplibrary/Masters/2010/08/04/20100804-145617/DSCF9180.RAF)

Overlapped extent allocation (id = 601790, /Aperture Backups/Miscellaneous Library.aplibrary/Masters/2011/09/29/20110929-225140/IMG_0565.MOV)

Checking volume bitmap

Volume bitmap needs minor repair for under-allocation

Checking volume information

The volume Drobo was found corrupt and needs to be repaired

Error: -69845: File system verify or repair failed

Underlying error: 8: POSIX reports: Exec format error

 

Most times DiskWarrior can usually fix the problems in place, but there were times when the corruption was so severe DiskWarrior would instruct copying to a new disk.

 

I have been working with Drobo Support for the past 3 months and they have replaced the Drobo 3 times to no avail. I see this problem on 3 different Macs and on different interfaces (FW800, USB 3.0 and USB 2.0) and even with base OS installs of 10.7 and 10.8. At this point I have ruled out cables, drives and software conflicts. Drobo Support even had me try different versions of firmware. We are now out of ideas and I'm open to suggestions on tracking down the root cause.

 

Alvin

  • Sean_W Level 1 Level 1 (0 points)

    I have the same issue with my Drobo 2nd Gen right now.  I have 2 volumes on the Drobo and only the Time Machine volume keeps corrupting.  This is happening frequently when the machine wakes from sleep and starts a missed backup.  With sleep disable, the Drobo seems to be working ok, but I would like sleep to work.

     

    The second volume has basic file storage on it and never corrupts.  I just format the Time Machine volume and start over.  Luckly, I also use Crashplan so my data is backed up somewhere else also.  My issues seemed to start with 10.8.2.  10.8 and 10.8.1 ran without any issues.  If I turn off Time Machine, there are no issues with the Drobo.  Are you using sleep on the Mac and is the volume used for Time Machine?

  • Alvin Koh Level 1 Level 1 (45 points)

    I think there is an issue with Time Machine and Drobo. That was one of the questions Drobo Support kept asking me. But no, I don't use Time Machine with my Drobo, just a normal HFS+ Journaled filesystem. Sleep is also not enabled on my Mac. Drobo Support RMA'd my Drobo S twice and eventually replaced it with a Drobo 5D but to no avail. I have half a mind to revert to Snow Leopard and see if that helps.

  • Sean_W Level 1 Level 1 (0 points)

    I was thinking it was my Drobo also, but since it ran ok in 10.8 and 10.8.1, it seems to rule it out.  On the other hand, I can hook a cheap usb drive to the machine and run Time Machine without any issues so I may just go that route and move on.  Wish there was a fix for these issues.  I may try ZFS on the Drobo as a final test just to rule out HFS issues.  Of course both Apple and Drobo won't support this, but it is worth a try.

  • Alvin Koh Level 1 Level 1 (45 points)

    I'd be interested to know how ZFS works out for you on the Drobo. I guess we have nothing to lose even if Apple and Drobo don't support it.

  • Sean_W Level 1 Level 1 (0 points)

    ZFS did not seem to work well on the Drobo.  I decided to move to Carbon Copy for backups.  Seems to be working better.  Drobo still does not know what is going on yet.

  • Alvin Koh Level 1 Level 1 (45 points)

    Thanks for the update on ZFS. Drobo can't fingure out my issue too and asked me to follow up with Apple. I plan to revert one of my Macs to Snow Leopard and verify the corruption doesn't occur there before I log a case with Apple.

  • Sean_W Level 1 Level 1 (0 points)

    I think I finally found what was the problem with mine.  I found that Wacom had some issues with their tablet driver and 10.8.2 on another forum.  It was reported to cause issues with sleep in OSX.  I uninstalled it my issues seems to have cleared up.  I has been working for a few days now without any issues.

  • Alvin Koh Level 1 Level 1 (45 points)

    Hi Sean, I'm glad you managed to figure what was causing the problem. I'll need to find time to test with Snow Leopard to confirm it is the Lions causing the corruption.

  • Sean_W Level 1 Level 1 (0 points)

    After a week the issues came back.  I give up on this thing.  I don't trust it anymore.  Its not the 1st issue I have had with it anyway.  Since a standard USB drive works fine for me, I will be switching to them instead.

  • Alvin Koh Level 1 Level 1 (45 points)

    Sorry to hear that Sean. I guess it has to do with Lion and Mountain Lion and RAID/RAID-like devices.

  • Alfred.TV Level 1 Level 1 (0 points)

    Hi Alvin - did you every resolve your DROBO problem.  After several years of stability, I'm not getting frequent drive curruption under Mountain Lion. I'm using the latest dashboard and firmware, and I'm very close to tossing the device off of my 4th floor balcony.  Any insight would be helpful!

  • Alvin Koh Level 1 Level 1 (45 points)

    Hi Alfred.

     

    Unfortunately I did not get a resolution. Drobo Support worked with me to try several approaches to resolve the issue - different firmware and dashboard versions, swapping disks, different I/O interfaces, swapping Drobo units - but nothing worked.

     

    I have upgraded to Mavericks and just did a test and still see volume header corruption. Used Disk Utility to fix the problem. For now it's clean but I'll have to monitor.

     

    Alvin

  • Alfred.TV Level 1 Level 1 (0 points)

    Hi Alvin - thanks for the heads up. I did open a support ticket. They did say that MacMini's from 2011 and back do something funky with regard to Fireware data packets (whatever).  I'll post something here if I get any clear answers. I am running a MacMini4,1 cabled in to a Newertechnology MiniStack when then feeds the Drobos via FW800.

     

    Is your Drobo connected directly to your MacMini? What's your machine identifier? I am thinking of changing my cable config - going from the MacMini to the Drobo and THEN to the MiniStack.

     

    I will say, I go absolutely nuts when I see the reports of corruption after running a scan on these expensive devices.

     

    Alfred

  • Alvin Koh Level 1 Level 1 (45 points)

    Hi Alfred,

     

    I'm using a 2008 Mac Pro and was having issues with FW800 and USB 2.0. I even tested with a 2010 Macbook Pro (FW800 and USB 2.0) and a 2011 Macbook Air (USB 2.0). The Drobo was connected directly to the machines.

     

    I'm suspecting it's something they change at the core I/O level. If you seach this community you can find reports of corruption with RAID devices in general as well.

     

    Alvin

Previous 1 2 3 Next