I’m wary of the Drobo now until I can clear up the bugs. (Feel free to advise if you have any experience doing this or if you know: does the Drobo data protection routine itself weed out bad blocks?)īottom line is I still haven’t been able to complete my original project: clone internal HD to disk image on Drobo. Figure the worst might be having to endure the 4-day-long Drobo automatic data protection routine again.
I’m also considering pulling each drive out of the Drobo, putting it into a Voyager Q external enclosure and running the block check on each disk separately, eventually putting all four drives back into the Drobo.ĭon’t know if this interferes with the Drobo’s built-in housekeeping.
Maybe if I can at least rebuild the directory I can resume running a program to check for bad blocks. I am going to attempt this in a little while and see what happens. I think it had only gone through 0.7% of the Drobo space after running for over 24 hours.Īfter that, remembered having recently read a Drobo FAQ webpage that suggested booting off the Disk Warrior DVD and having the Drobo plugged in directly to the computer via USB to get around the non-rebuilding index issue. I thought maybe Drive Genius 3’s block check might work it was way slower than Disk Tools Pro (I think it has a more extensive routine than Disk Tools Pro), and I had to reboot my laptop because of a software update and abort the Disk Tools Pro run. I’ve tried to run several disk utilities to check for bad blocks on the Drobo drives.ĭisk Tools Pro (the fastest) will inadvertently lock up after running for 24 hours or so (and this only covers about 7% of the Drobo, which is loaded with four 2TB drives). No more warnings from Drive Genius, though I would expect this because I wasn’t writing massive GBs of data to the Drobo. After four days of data protection rebuilding (orange flashing lights), again no red light on a Drobo hard drive. I powered the Drobo down again, reordered the hard drives (just for chuckles) and powered it on. When Drobo came back up, there was no red drive warning light! I tried to run Disk Warrior but got errors similar to what’s reported here. I powered the Drobo down to do some cable reconfiguring so I could work on some other projects via external HDs on FW800 while trying to run a block repair utility on the Drobo. One of the Drobo’s drives also started giving me the red light warning. Again, the routine failed, and this last time Drive Genius 3’s Drive Pulse menu item reported a number of bad blocks on the Drobo. So I removed GB of unneeded data on the Drobo and tried the clone drive to disk image on the Drobo again. This persisted after multiple attempts over several days. Apparently as the Drobo neared its maximum capacity, the app I was using to create the backup disk image on the Drobo slowed to a crawl, or the Drobo itself slowed to a crawl trying to find spaces for the data. I have been trying to back up my ailing MacBook Pro HD to a disk image on my Drobo. Long story here, but a direct response to your suggestion at the end-take a deep breath! Thus, you could simply leave DiskWarrior as is, and re-launch the software if you need to rebuild another drive.'įor further coverage of this issue, see our DiskWarrior product page.Just for sanity’s sake, I would try using a different port and cable. "However, the actual DiskWarrior rebuild process is completed and the crash will do no harm to your data. We will have to work around this in a future version of DiskWarrior. "We're disappointed that the issue wasn't fixed with the update to QuickTime 7.1. Rename the "Complete.aiff" sound file "Alert Complete.aiff" - then close ALL windows"Īn Alsoft technical support representative states:.Locate the "Complete.aiff" sound file - the path is: - DiskWarrior 3.0.3.app -> Contents -> Resources -> Complete.aiff.Control click on DiskWarrior 3.0.3 and from the contextual menu select "Show Package Contents".In the meantime, this issue can still be resolved via our previously published workaround, as follows: This issue was created with the installation of QuickTime 7.0.4 and continues with QuickTime 7.1 and 7.1.1. A bug that causes DiskWarrior to unexpectedly quit at step 10 in the rebuild process due to the presence of QuickTime has yet to be resolved with the latest QuickTime releases or an update from Alsoft (DiskWarrior's developer).
0 kommentar(er)
