• On CHOW: Is it OK to sneak popcorn into a movie?
advertisement
December 23, 2008 6:50 AM PST

Time Machine permissions problems after Mac OS X 10.5.6

by CNET staff
  • Font size
  • Print
  • 22 comments

After updating to Mac OS X 10.5.6, many users are experiencing problems with Time Machine backups, wherein the system will show an error stating the users does not have sufficient privileges on required files for the backups.

Apple Discussions poster GreggSymington writes:

"After the 10.5.6 update today my backup is no longer recognized, and when trying to reselect the drive i get this error: You do not have appropriate access privileges to save the files '.001b6397c156' in folder 'Backup'."

Time Machine associates backups to the computer based on the computer's MAC address, which is a unique identifier number associated with the ethernet card. The computer stores this information in an invisible file that has the computer's MAC address as it's name. This file is stored at the root of the Time Machine drive, enabling the drive to be used with multiple computers. For some reason, the latest OS update has altered either the file or how permissions are read from the file. Basically, this file has become corrupted, and users should be able to manually reset ownership and permissions on the file with the terminal.

Fix: Change ownership and permissions on the file In the "Terminal" application, perform the following steps to figure out what the file is called, and then change the permissions on it accordingly.

1. Type "cd" followed by a single space, and then drag the Time Machine drive to the Terminal window. The command should then look something like this:

  • cd /Volumes/Backup

2. Press enter to submit that command, and then enter the following command:

  • ls -la

3. Note the name of the file that begins with a period and has 12 characters in the name, such as ".001b6397c156" mentioned in the quote above.

4. Now enter the following commands, substituting "FILENAME" in the commands with the file name exactly as it's shown both in the error as well as in the output of the command in step 2, including the period before it (ie: ".001b6397c156"):

  • sudo chown `id -un` FILENAME
  • sudo chmod 400 FILENAME

After each of these commands are entered, users will need to supply their passwords (which will not be shown) and the Time Machine backups should work again.

Resources

  • GreggSymington
  • More from Late-Breakers
  • Recent posts from MacFixIt
    Manage iCal's automatic e-mail generation for invitations
    CNET TV Apple Byte: Apple faces critics
    Weekly Utilities Update: Net Monitor, MiniUsage, TimeMachineEditor, more...
    Odds and Ends: Essential video codec packs for OS X
    Address Book: Unable to add, view contacts
    Persistent 'Faster Browser Search' overtaking Safari's default search
    Quick tip: Faster Time Machine backups
    MacFixIt Answers
    Add a Comment (Log in or register) Showing 1 of 2 pages (22 Comments)
    by Jan P. Andrews/NPR December 23, 2008 4:50 AM PST
    I was pleased to find this explanation and fix since I have been receiving the Time Machine error with two drives, neither of which were connected at time of upgrade. I've followed the instructions to the letter, but Terminal rejects chown 'id -un' .001ff3d3d20e with chown: id -un: INVALID ARGUMENT (or chown: id: INVALID ARGUMENT if I eliminate the single quotes surrounding id -un). I'm a UNIX idiot, however, and may be doing something obviously wrong.
    Reply to this comment
    by Dave Hill--2008 December 23, 2008 4:50 AM PST
    >
    This is a reply to a previous comment by Jan P. Andrews/NPR


    Those quotes should be *backquotes*, not normal quotes.

    On the UK keyboard it's the key to the left of the Z key, dunno
    about the US keyboard.
    Reply to this comment
    by Fingal December 23, 2008 4:50 AM PST
    >
    This is a reply to a previous comment by Jan P. Andrews/NPR


    On a typical Apple US keyboard the backquote is just under the esc key.

    What this part of the command is actually doing is figuring out your username and then providing it to the chown command. You can just substitute your short username for the `id -un` part.

    Since my short username is fingal it would be the following for me:

    sudo chown fingal FILENAME
    Reply to this comment
    by traumatiziert December 23, 2008 4:50 AM PST
    >
    This is a reply to a previous comment by Jan P. Andrews/NPR


    I tried this but it doesn't work. I typed cd and a space in Terminal and tried moving Time Machine to the Terminal window, but when I try to do that nothing happens.
    Reply to this comment
    by Rick Chin December 23, 2008 9:50 AM PST
    I was able to make this change by using Path Finder, Show Invisibles, clicking the file and using Get Info to change the permissions.
    Reply to this comment
    by grayw December 23, 2008 9:50 AM PST
    >
    This is a reply to a previous comment by Rick Chin


    Andrew,

    Did you use backquotes ` ` or forward ones ' ' ?
    Reply to this comment
    by grayw December 23, 2008 12:18 PM PST
    This worked for me! Many thanks.
    Reply to this comment
    by John Albergo December 23, 2008 1:11 PM PST
    Terrible form, Apple! C'mon!
    Reply to this comment
    by gbdoc December 23, 2008 5:13 PM PST
    I'm always intrigued by these things, why a given update messes up some systems but not others. This particular problem (nor any other problem, for that matter - no partial DL, no "Mail" problem) didn't happen on either of our two main Macs. Both are plain vanilla, no haxies, and well-maintained. In fact, before the update I had an occasional failed TM backup, but not once since.

    ---
    1.25 GHz 15" G4 PB, 2GB RAM, newest OS X

    2.2 GHz Intel MB, newest OS X

    1 TB FW HD

    AP Extreme & Express, cable broadband

    Reply to this comment
    by galambo December 23, 2008 5:13 PM PST
    >
    This is a reply to a previous comment by gbdoc


    having the same issue. permission on external usb drive are marked 'custom' and can not be changed. tried doing the above mentioned fix this and got the message 'permission denied' can not run 'repair pernission' its grayed out

    have another usb drive and no issues

    help!!!!!
    Reply to this comment
    by grayw December 24, 2008 6:46 AM PST
    Well I am batting 50/50 on this. I have a PowerBook Pro with a Buffalo Drive for backup at work and another one at home. This trick worked like a charm on the one at work. But not at home. The home one goes into eternal "preparing" mode and will keep on "preparing" for as long as I let it (hours), but will never actually back up this drive.

    Any ideas anyone?

    Both Buffalo Drives are the Duo with 2 500 gb discs. The work one is configured so that disc 1 mirrors disc 2. The home one is configured as one 1,000 gb drive. I don't know if that can explain my variance, but maybe. Any ideas?
    Reply to this comment
    by grayw December 24, 2008 6:46 AM PST
    >
    This is a reply to a previous comment by grayw


    Oops. Guess 3rd times the charm here. After "preparing" for the last 30 min my home TimeMachine is now backing up. I don't think I did anything different this time than I did the first two times.
    Reply to this comment
    by lcpguy December 24, 2008 7:32 PM PST
    Well, as you all know, I am the guy that never has problems with Apple updates.

    Not this time around! This 10.5.6 update has to be from Hell itself!

    Time Machine is "honked".

    I can no longer burn a DL DVD without getting the error that my laser can't be calibrated to the media.

    Various AppleMail messages won't open.

    The MDS process now takes a constant 68% of the CPU.

    Here's what I did before installing. I verified the HD with Disk Util. I repaired Disk permissions.

    I downloaded the Combo-updater and ran it. Upon re-boot my external speakers popped at me, loudly enough to make me jump.

    Anyway, problem after problem.

    I then did an Archive and install. Then ran the combo updater again. No luck, all these problems still exist.

    I went back to my CCC3 backup of 10.5.5 and restored it. I am now "Fat, Dumb and Happy" once again. Everything just works again.

    In my opinion, this 10.5.6 upgrade is the upgrade from HELL!!!

    Oh yes: Time Machine? I tried to restore from it and just got an error message that some files were corrupted and it couldn't continue. Thank God for the likes of CCC and/or SuperDuper: They JUST WORK.

    In my opinion, Time Machine, in its current state, is a piece of you know what!!! As is the 10.5.6 update.

    Shame on Apple for releasing such "CRAP"!

    Aiyeeeeeee!!!!!!!

    And yes, I am an Apple fanboy!!!
    Reply to this comment
    by lcpguy December 24, 2008 7:32 PM PST
    >
    This is a reply to a previous comment by lcpguy


    Funny thing happened. I ran the combo updater again. Same "bad" results. I then decided to do things my old way and use Software Update instead of the downloaded stand alone installer. It worked like a charm and I'm now back in business with 10.5.6, except the external speakers still pop on startup. All other problems have disappeared.

    I think I'll just stick with Software Update like I always have, as it just works. For me anyway.

    Go figure???

    John
    Reply to this comment
    by lcpguy December 24, 2008 7:32 PM PST
    >>
    This is a reply to a previous comment by lcpguy


    Sorry, I spoke too soon. Time Machine is now useless as it says it can't process link files. Keyboard and mouse are not recognized after boot until I unplug and replug-in the USB cable. Apple Mail has lost all my user folders and quits every time I click the mouse, anywhere in it!!! Printing to Epson printer, I get message that it can't communicate with printer. Unplug and replug its USB cable solves that problem.

    These anomalies and errors have never occurred before 10.5.6 and did not occur when I posted the above message, but developed over time.

    Needless to say I am now CCC restored back to 10.5.5 and will stay there. I should have never installed 10.5.6 as 10.5.5 was working perfectly, all the time. I guess from now on I'll follow that old adage: If it ain't broke, don't fix it.

    John
    Reply to this comment
    by J.-Ph. Peçon December 24, 2008 7:32 PM PST
    >
    This is a reply to a previous comment by lcpguy


    Must say I do not face these problems maybe because I'm using as backup Time Capsule ????
    Reply to this comment
    by Jimperrin December 27, 2008 10:22 AM PST
    I've tried solving the problem with Terminal, as suggested, using the back quote and following the directions very carefully, but with no result -- my Time Machine is still Read-Only.

    I also tried changing permissions with Pathfinder, but that didn't work either.

    I'm now ready to erase the entire Time Machine volume and start fresh. BUT, of course, Disk Utility can't unmount the volume to erase it.

    I've got a couple of utilities that will delete files, but I don't want to go that route if someone can give me a safer way to erase the volume!
    Reply to this comment
    by Jimperrin December 27, 2008 10:22 AM PST
    >
    This is a reply to a previous comment by Jimperrin


    The minute I posted this, I realized that using Disk Utility on the System Install disk would do the trick, and it did.

    So I'm now starting over on Time Machine -- until the next system update, anyway!
    Reply to this comment
    by January 4, 2009 5:21 PM PST
    I Googled "Mac OS X hidden files" and offer the following links:

    http://www.mactricksandtips.com/2008/04/show-hidden-files.html (Brief discussion of system files and methods of displaying them)

    http://secrets.blacktree.com/?search=hidden+file (Links to a Preference Pane download file to control "Secret" functions much like Onyx)

    In my case, the Time Machine dialog reported I didn't have permissions to access ".001b63a22e2d" Indeed, when I finally exposed the referenced file (via the Secrets Preference Pane--I don't do Terminal), permissions were "Read Only" and "No Access." A quick unlock of the padlock and change to "Read and Write" and Time Machine is grinding away, as I type.

    I'm happy again.
    Reply to this comment
    by halteach January 19, 2009 5:42 AM PST
    Worked for me. Guess they need better regression testing. :-)

    hal
    Reply to this comment
    Showing 1 of 2 pages (22 Comments)
    advertisement

    About MacFixIt

    MacFixIt is CNET's troubleshooting resource for all things Mac. The information here helps you navigate the ins-and-outs of Mac ownership with how-tos, troubleshooting information, news, reviews, and more.

    Add this feed to your online news reader