i tried running diskwarrior on my drobopro (latest software/firmware as of halloween 2010). my drives were basically healthy (no observed problems) – so this was mostly a “good hygiene” kind of operation.
disk warrior ran successfully on several other disks attached to the same machine (connected via firewire and SATA and including a drobo2G), but failed on the drobopro connected via iscsi. diskwarrior first issued some warnings about slow performance, then indicated that the operation failed when trying to write the new directory to the volume. the dialog said something to the effect of “the disk is failing and you should copy all content to another volume” .
i disconnected the iscsi connection and connected the (same) unit via firewire to the same server, then ran diskwarrior again. it completed successfully.
it seems that diskwarrior there is a specific bug or incompatibility between diskwarrior and the drobopro connected via iscsi. perhaps dw’s threshold for thinking that an operation has timed out is set too low for drobopro over iscsi?
and/or possibly i have a drive in my drobopro that is somehow marginal and generating some low-level errors or retries which the drobopro is “managing” (but not generating anything in the logs) and which is causing timeout errors on some i/o ops, but is not bad enough (yet) to cause the drobopro to turn on the red light. it would be nice if i could get more detailed reporting from the drobo.
and/or perhaps it was just a “fluke” that dw failed (twice) over iscsi then succeeded over firewire – i.e., it may be that just the shutdown/restart of the drobopro played a role in making the problem go away.
anyone have any ideas? it is very inconvenient to have to disconnect and reconnect to run “routine” utilities. i’m sure there must be others out there with experience with diskwarrior+drobopro… anyone seen this problem? diskwarrior is even recommended by drobo inc. as a tool for maintaining/troubleshooting drobos, no?
mac os x server v.10.6.4
diskwarrior v. 4.2.
drobopro with latest firmware, 8 drives, dual redundancy, 26% capacity