![]() The disk activity stops, and you can then run DiskWarrior. To kill it, type kill followed by the second number from the left, in this case: kill 67332 ![]() So opened Terminal and typed: ps -ef ' grep fsck_hfs and there was the culprit:Ġ 67332 18 0 6:26am ? 1:02.06 /System/Library/Filesystems/hfs.fs/Contents/Resources/././././././sbin/fsck_hfs -y /dev/disk5s2 Unfortunately that takes HOURS on this large volume full of time machine backups. I suspected that TimeMachine or something else on the mac is trying to fsck the file system in preparation for mounting. My disk isn't dead, it just has a sick filesystem, as proven by the fact that if I wait long enough, DiskWarrior can try to do something with it. Scratched my head over this for a while, so figured I would post the solution in case anyone has the same problem.Īll the forum posts are about dead disks. If I wait several hours until the DROBO is quiet, then DiskWarrior doesn't get the error, and I can try to recover it. ![]() When I connect the DROBO and try to run DiskWarrior, I get an error -36 "hardware failure". I have a DROBO which I am trying to recover with DiskWarrior.
0 Comments
Leave a Reply. |