carrsa

Q: hfs_clonefile: cluster_read failed: -34

Hello, ever since updating to El Capitan, I'm getting a ton of these "hfs_clonefile: cluster_read failed: -34" errors in my Console logs. I have a Late 2009 27" 2.8 GHz iMac booting off of a new 4 TB Seagate SSHD external firewire drive in a NewerTech miniStack Max enclosure. I have 32 GB memory and I'm running OS X 10.11.5.

 

Other than an occasional kernel panic, I haven't been able to pinpoint any noticeable performance issues, though any disk errors are always a little disconcerting. I'm mainly curious as to what would be causing this behavior, as there appears to be very little information out there on -34 errors. I do wonder if this is somehow associated with permissions errors and/or Spotlight indexing, but it's hard to tell from the logs.

 

This is a brand new drive, and I've already had both the drive and enclosure replaced. I've also tried replacing the Firewire cable, and there's only one FW800 port on this machine. I do need the speed of this connection since I'm using the drive as an external boot. I get this error, regardless of whether there are any other devices connected to the FW800 chain or USB, i.e. the error appears if the disk is the only thing connected. I've tried many other strategies without results, including resetting PRAM, NVRAM, booting into Safe Mode, Recovery Mode, reinstalling OS multiple times, erasing and reformatting drive, Disk Utility repairs, etc. At one point, I rebuilt some caches related to an lsd folder. That seemed to help with some other errors that were being generated, but not with the hfs_clonefile errors.

 

Finally, I'd also note that this is a hybrid drive, so I doubt TRIM is an issue. And I'm only getting -34 errors, not the more common -5 errors or i/o errors that seem to accompany a failing disk drive.

 

Any insight or help would be greatly appreciated. Again, I'm mainly curious as to what a -34 error means, and whether I should be worried about the integrity of the external drive.

iMac, OS X El Capitan (10.11.5)

Posted on May 21, 2016 6:42 AM

Close

Q: hfs_clonefile: cluster_read failed: -34

  • All replies
  • Helpful answers

  • by carrsa,

    carrsa carrsa Jun 15, 2016 1:35 PM in response to carrsa
    Level 1 (5 points)
    Desktops
    Jun 15, 2016 1:35 PM in response to carrsa

    After researching this issue for a year, I finally narrowed down the culprit to LaunchAgents of programs I thought I already had uninstalled, AVG and LaCie Desktop Manager. Once I deleted these two files and ran Disk First Aid on an external drive, the hfs_clonefile errors appear to be gone, at least for now.

     

    254      Jun 14 22:24:55 com.apple.xpc.launchd.domain.user.235: Could not read path: path = /Library/LaunchAgents/com.avg.LinkScannerAgent.plist, error = 2: No such file or directory

    255      Jun 14 22:24:55 com.apple.xpc.launchd.domain.user.235: Service plist does not specify a label.

    256      Jun 14 22:24:55 com.apple.xpc.launchd.domain.user.235: Could not import service from caller: path = /Library/LaunchAgents/com.lacie.LaCieDesktopManagerAgent.plist, caller = mds.66, error = 110: Invalid or missing service identifier

    257      Jun 14 22:24:55 com.apple.xpc.launchd.domain.user.235: Failed to bootstrap path: path = /Library/LaunchAgents/com.lacie.LaCieDesktopManagerAgent.plist, error = 110: Invalid or missing service identifier

    258      Jun 14 22:24:55 com.apple.xpc.launchd.domain.user.235: Failed to bootstrap path: path = /Library/LaunchAgents/com.avg.LinkScannerAgent.plist, error = 2: No such file or directory

  • by Arjen Hiemstra,

    Arjen Hiemstra Arjen Hiemstra Sep 20, 2016 8:28 AM in response to carrsa
    Level 1 (21 points)
    Desktops
    Sep 20, 2016 8:28 AM in response to carrsa

    Hi,

     

    After being on Yosemite since El Capitan came out, I thought let's give this a try again. But the errors are still happening.

     

    Have you seen my thread about this?

     

    El Capitan: Kernel: hfs_clonefile: cluster_read failed - 34

     

    Are you 100% sure you fixed this?

     

    It is interesting you mention this. On my iMac this seems to be related to 2 external LaCie drives.

     

    Do you still have LaCie drives attached to your system?