Permissions issues on backup volume

I just finished a complete reformat and reinstall of 10.3 with the intent to just restore certain data from TM. I ended up creating trouble for myself by creating my new user account with a different name than the old one. While I could retrieve data through TM it wasn't optimal since the previous user didn't exist on the drive.
I created a new account with the same name as the TM backup and most things are fine, but... certain folders throughout the backup (Desktop, Library, and the like) seem to have set their permissions to the now deleted account - which means I can't read them from TM. I'm able to change the permissions on a file by file basis in the finder, but would love to be able to propagate these changes across all instances of the folders in the backup volume. Anybody have any ideas?

Open /Applications/Utilities/Terminal, copy the blue text in, and press enter.
You'll be asked for your admin password, which you won't see.
sudo chown -R `id -un`:`id -gn` ~
That will change the owner of ALL files in your home directory to you. (Which is how it should be)
The get info pane in Leopard is buggy for changing permissions.
To fix any damage it caused, use these steps:
1. Open /Applications/Utilities/Terminal from the affected account.
IMPORTANT NOTE: copy the blue text in. Don't attempt to retype it, as a mistake could cause more issues.
2. Copy the blue text in, and press enter. chmod -R -N ~
That command removes all ACL entries from your home folder. The next commands put them back where they should be.
3. (Press enter after copying and pasting this command in). chmod +a "everyone deny delete" ~/ ~/Desktop ~/Documents ~/Downloads ~/Library ~/Movies ~/Music ~/Pictures ~/Public ~/Sites
4. (Press enter after copying and pasting this command in). chmod +a "`id -un` allow list,addfile,search,delete,add_subdirectory,delete_child,readattr,writeattr,readextattr, writeextattr,readsecurity,writesecurity,chown,file_inherit,directoryinherit" ~/Public/Drop\ Box
After running those commands, your home folder permissions should be fine. (NOTE: You may get a response:
chmod: Failed to clear ACL on file Commands: Invalid argument
chmod: Failed to clear ACL on file Notification: Invalid argument
That is safe to ignore. The rest of the commands will still work fine.)
In future, do NOT use the "Apply to enclosed items" option in the get info window.
Good luck!
Message was edited by: joshz
Message was edited by: joshz

Similar Messages

  • Permissions issues with multiple volumes

    I'm currently running one boot volume with Snow Leopard and one with Mountain Lion on my Mac Pro.  Due to current software compatibility-related issues, I need to be able to use both volumes regularly as part of my workflow for now, though I plan to transition fully to 10.8 in the next couple months.  Right now, I'm running into a permissions issue that is impeding my workflow.  When I first set up the 10.8 volume, I had access to all the folders in my main user account on the 10.6 volume.  However, yesterday I used the process described in the link below to change name of my home folder, which includes creating a new user account.  With this new user account, I find that I do not have access to user content on my 10.6 volume.
    http://support.apple.com/kb/HT1428
    I know how to change permissions in the "Get Info" window, but I'm wondering if there's a way to globally give this account the same permissions the original one had.  (Actually, I thought that was what the process in that support article was supposed to do, so perhaps I've done something wrong...)  As it is right now, if I've granted myself read and write permissions to the Documents folder, but those permissions seem to have "cascaded" inconsistently--some files and folders are still blocked, others are accessible.  Can anyone help me out with this?  For now, I'm just going to copy the files I need over, but I need a better solution.

    Anyone have any ideas?

  • Permissions issue with Time Machine backup store

    I am struggling with a Time Machine permissions issue on an iMac running OS X 10.10.2 + OS X Server 4.0.3, and backing itself up to an external USB disk.
    Backups complete successfully, but I am unable to carry out any user-level operations such as accessing the "time travel" interface via Enter Time Machine from the menu bar. Invoking Enter Time Machine fails with the error Can't connect to a current Time Machine backup disk. Likewise, although tmutil will correctly list the backup destination, tmutil listbackups produces an error:
    $ tmutil listbackups
    2015-02-05 16:53:19.413 tmutil[29181:2324148] Error enumerating (null): The file “Backups.backupdb” couldn’t be opened because you don’t have permission to view it.
    No machine directory found for host.
    My system logs are full of similar error messages from Finder.
    On the back volume, the permisisons to the store are set to owner root and group wheel, and there is an access control list applied to the directory and Backups.backupdb:
    $ ls -lae
    total 2688
    drwxrwxr-x  12 root  wheel      476 Feb  4 22:29 .
    drwxrwxrwt@  9 root  admin      306 Feb  4 11:57 ..
    0: group:everyone deny add_file,add_subdirectory,directory_inherit,only_inherit
    drwxrwx---+  6 root  wheel      204 Jan 30 13:49 Backups.backupdb
    0: group:everyone deny add_file,delete,add_subdirectory,delete_child,writeattr,writeextattr,chown
    -rwxr-xr-x@  1 root  wheel   115716 Nov 13 02:43 tmbootpicker.ef
    The problem is clearly the drwxrwx--- permissions applied to the store. I can temporarily revert these with chmod, after which all the user-level operations described above work correctly. But on the next backup, backupd will revert the permissions to give wheel write access and remove rx privileges for everyone else. It doesn't leave anything in the system log to suggest why it is making this change.
    I have a MacBook also running OS X 10.10.2, without the Server pack. This also backs up to a (different) external volume. On this volume the owner, group and access control list for the store are set as above, but the permissions are (and remain) what I would have expected, drwxr-xr-x.
    Is there any obvious reason why backupd should be modifying the permissions in this way — and is there any way to stop it?

    Thanks - I was seeing exact same problem on one of my client's machines (10.10.2 with OS X Server). I could see wrong group of "wheel" but wasn't certain that just changing to "staff" would be enough - but seems to have sorted things out

  • Time machine problems on clean-install, doesn't recognize old backups as such/permissions issues

    My iMac had been pretty slow, and never received a clean install since I'd gotten it. With the security that I'd just restore whatever I wanted from Time Machine afterward, I used the recovery partition to format the hard drive and install Lion.
    Everything's fast now! It's remarkably like it was when it was brand new with Tiger, which is pretty good for a nearly-six-year-old computer running today's OS. I'm having problems with the Time Machine part, though. Even after ensuring that my username is the same as it was before and making all the permissions my own in both Finder and with chmod, it throws me permissions errors when restoring some, but not all files, with no pattern about it. This isn't a big deal for restoration because I've just used sudo cp to put everything back where I wanted it, but now I have issues with backups. Even though TM sees my old backups and can restore the ones that don't give permissions errors, it still wants to take new backups of things I've manually restored, such as my iTunes folder of about 50GB. That's the big conflict now; I don't want to take up all that space for files that are already backed up. Can anyone offer a fix? Thanks!

    coldcaption wrote:
    Yes, the other drive was backed up before. If it was previously associated then perhaps something was messed up trying to re-associate.
    As long as you pointed it to the backups of that disk, it should be fine.  If not, or if in doubt, just run the command again.
    It changes whether or not I have the previously-backed up external drive added to the things to back up (unless it's supposed to do delete the old ones in this case?),
    I don't quite follow that.  The Estimated size of full backup is just the total data on the drives that are included (unfortunately, there's no display of them), less any exclusions of files/folders on them.
    Finally, though, the size of a backup if I were to take one right now would be 363 GB;
    How do you know that?  The only way to tell what Time Machine thinks is new or changed is to actually start a backup, and see what the display ("xxx GB of yyy GB") and/or log messages (". . . xxx MB/GB requested (including padding), yyy MB/GB available.") say.  See #A1 in Time Machine - Troubleshooting for a handy widget to display the log messages.

  • TimeMachine refuses to make backups (backup volume could not be found)

    Let me start by saying that I'm new to Macs, so if you're going to make suggestions involving strange and arcane steps in Terminal (which I'm completely open to trying), please try to be as clear as possible
    When I set up my new iMac, everthing worked beautifully for a few weeks, and then inexplicably, TimeMachine started failing to make backups. I have a 200g external Maxtor HD that I was using as my backup drive. TimeMachine had no problems backing up to it for a few weeks, and then suddenly it stopped. I don't know why.
    I have searched these forums for a solution to my problem, and none of the suggestions work. Here's what I've tried:
    -- Going into preferences, unselecting the volume, then reselecting it.
    -- Turning off TM, unplugging the EHD, restarting the iMac, plugging in the EHD, and following the wizard prompts to enable TM.
    -- I have verified the EHD. It reports no errors. I have tried repairing the EHD. No errors reported.
    -- I have erased, formatted, partitioned, formatted again. TM still fails.
    -- Following the suggestions in this thread: http://discussions.apple.com/thread.jspa?threadID=1480141 I have done the following:
    1. Quit all applications, open /Applications/Utilities/Terminal.app and type in the following commands:
    # sudo mv /Library/Preferences /Library/Preferences.old
    # sudo mv /Library/Caches /Library/Caches.old
    # sudo reboot
    Time Machine still failed.
    2. Deleted: com.apple.TimeMachine.plist, then went through all the steps above again. Time Machine still failed.
    I have tried every single solution on this forum I could find, and TimeMachine simply will not work. I would prefer to not have to spend an additional $300 on a TimeCapsule when I already have a wireless router and an EHD that TimeMachine previously had no problem making backups to.
    Here's what I find in Console:
    5/29/08 7:06:11 AM /System/Library/CoreServices/backupd[160] Starting standard backup
    5/29/08 7:06:11 AM /System/Library/CoreServices/backupd[160] Volume at path /Volumes/Untitled does not appear to be the correct backup volume for this computer. (Cookies do not match)
    5/29/08 7:06:16 AM /System/Library/CoreServices/backupd[160] Backup failed with error: 18
    Untitled is the name of my drive after all the formatting, partitioning, erasing rigamarole. I'm incredibly frustrated right now, because it USED TO WORK. Now it doesn't. There's no reason for it not to work for what I can tell. What else is there left for me to try?

    I believe I have isolated the problem as a permissions issue which I have logged as bug 5990628:
    Summary:
    Unable to backup over network after upgrading to 10.5.3.
    Steps to Reproduce:
    Configure Time Machine to back up Leopard machine over AirPort to another Leopard machine (with external drive and .Mac account configured in this case)
    Expected Results:
    Backups complete as usual.
    Actual Results:
    Backups are 'Delayed' with errors like this in the console:
    6/6/08 4:25:57 AM /System/Library/CoreServices/backupd[2334] Volume at path /Volumes/Time Machine-1 does not appear to be the correct backup volume for this computer. (Cookies do not match)
    Regression:
    Yes
    Notes:
    There are many threads on the subject:
    http://discussions.apple.com/thread.jspa?threadID=1538633
    http://discussions.apple.com/thread.jspa?threadID=1543033
    http://discussions.apple.com/thread.jspa?threadID=1547134
    http://discussions.apple.com/thread.jspa?threadID=1546079
    The problem appears to relate to being unable to read the cookie:
    6/6/08 4:20:23 AM System Preferences[2315] Failed to create remote cookie file at path: /Volumes/Time Machine/.001b63abcdef
    And this appears to be because the cookie was owned by a different user (likely due to it wanting to connect using a .Mac username instead of a local one), per my explanation below:
    I only ever used Time Machine after upgrading to 10.5.3 so my first experience with it has been fairly ordinary, as the backups were constantly being 'Delayed' with this error in the Console:
    6/6/08 4:25:57 AM /System/Library/CoreServices/backupd[2334] Volume at path /Volumes/Time Machine-1 does not appear to be the correct backup volume for this computer. (Cookies do not match)
    The first thing I discovered from a blog post was that my .Mac 60 day trial was causing it to connect using my .mac username (which appeared in the username field in the UI as a string of hex characters); disconnecting and reconnecting using a local user seemed to work but the issue remained.
    I then spotted this in the console:
    6/6/08 4:20:23 AM System Preferences[2315] Failed to create remote cookie file at path: /Volumes/Time Machine/.001b63abcdef
    The 'random' characters are your MAC address and the binary inside is likely this 'cookie' - a random value used to transparently and reliably link backups to machines. Curiously I couldn't modify this file over the network despite apparently owning it (in Terminal):
    $ cd /Volumes/Time\ Machine
    $ ls -la .00*
    -r-------- 1 samj staff 16 Jun 6 04:33 .001b63abcdef
    But when looking at it on the Mac Mini 'server' I saw that the owner was in fact another user:
    -r-------- 1 otheruser staff 16 Jun 6 04:33 .001b63abcdef
    So I ran these commands:
    sudo chown samj .001b63abcdef
    sudo chgrp staff .001b63abcdef
    And sure enough I was able to configure Time Machine as expected and it is as we speak backing up my MacBook over Airport to a USB drive attached to my Mac Mini.
    Cheers,
    Sam
    Sam Johnston
    Australian Online Solutions
    http://www.aos.net.au/

  • "screen shot can't be saved" and other permissions issues

    After having my iMac at the Apple Store for four days solving a problem with "quit unexpectedly" issues with all Apple built-in Apps on OS X Yosemite, I got the machine back with those problems solved.  It involved re-installing OS X and restore files from backup.  I thought all was well; the Genius Bar dude showed me that it's fixed. He said it took so long because of bizarre permissions issues he'd never seen before.
    Now that I've lugged this 40lb machine back home (after verifying the fixes in the store) I now find that several (other) functions don't work.  When I try to do a screenshot, I get this message:"Your screen shot can't be saved.  You don't have permission to save this file in the location where screen shots are stored."  Message could have been more helpful; the "location" is the desktop.  Pretty descriptive, though.  Seems I can't save anything to the desktop.
    I tried creatng a folder on the desktop.  Got this message: "Finder wants to make changes. Type your password to allow this".  Type password and new folder appears.  Drag the new folder to the trash, get same message..
    I tried copying a file from a network drive to the desktop. I get this dialog: "Modifying Desktop requires and administrator name and password.  I clicked "authenticate" and after a 3 minute delay (with "Preparing.." ) I get this dialog; "Finder wants to make changes.  Type your password to allow this".  I type the password and the file appeared on the desktop.  Before the work at the Apple Store, this never happened.  BTW I have only one user account and it's marked "Allow user to administer this computer".  Thinking something might be goofy with the pw, I changed it (took 3 minutes to do, oddly) and rebooted. No joy. Same thing happens when I try to drag something from the desktop to the trash.  Long time "moving" message followed by having to provide and admin pw.
    I tried to save a Safari attachment to the Downloads folder and got this message: "Safari could not download the file xxxxx because there is not enough free disk space".  Since I have more than 600GB of available space, I think the message is wrong and that it's really a permission issue with the Downloads folder.
    Tried to reset the password again.  Click to unlock the Users & Groups panel, get "System Preferences is trying to unlock Users & Groups preferences.  Type your password to allow this".
    All this tells me that somehow Yosemite is in "nag" mode (reminiscent of Windows Vista.
    Any ideas?
    Chaz

    Back up all data before proceeding.
    This procedure will unlock all your user files (not system files) and reset their ownership, permissions, and access controls to the default. If you've intentionally set special values for those attributes on any of your files, they will be reverted. In that case, either stop here, or be prepared to recreate the settings if necessary. Do so only after verifying that those settings didn't cause the problem. If none of this is meaningful to you, you don't need to worry about it, but you do need to follow the instructions below.
    Step 1
    If you have more than one user, and the one in question is not an administrator, then go to Step 2.
    Triple-click anywhere in the following line on this page to select it:
    sudo find ~ $TMPDIR.. -exec chflags -h nouchg,nouappnd,noschg,nosappnd {} + -exec chown -h $UID {} + -exec chmod +rw {} + -exec chmod -h -N {} + -type d -exec chmod -h +x {} + 2>&-
    Copy the selected text to the Clipboard by pressing the key combination command-C.
    Launch the built-in Terminal application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
    Paste into the Terminal window by pressing command-V. I've tested these instructions only with the Safari web browser. If you use another browser, you may have to press the return key after pasting.
    You'll be prompted for your login password, which won't be displayed when you type it. Type carefully and then press return. You may get a one-time warning to be careful. If you don’t have a login password, you’ll need to set one before you can run the command. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.
    The command may take several minutes to run, depending on how many files you have. Wait for a new line ending in a dollar sign ($) to appear, then quit Terminal.
    Step 2 (optional)
    Take this step only if you have trouble with Step 1, if you prefer not to take it, or if it doesn't solve the problem.
    Start up in Recovery mode. When the OS X Utilities screen appears, select
              Utilities ▹ Terminal
    from the menu bar. A Terminal window will open. In that window, type this:
    res
    Press the tab key. The partial command you typed will automatically be completed to this:
    resetpassword
    Press return. A Reset Password window will open. You’re not going to reset a password.
    Select your startup volume ("Macintosh HD," unless you gave it a different name) if not already selected.
    Select your username from the menu labeled Select the user account if not already selected.
    Under Reset Home Directory Permissions and ACLs, click the Reset button.
    Select
               ▹ Restart
    from the menu bar.

  • Time Machine Contradiction: "The backup volume could not be mounted"

    (This is only one wireless issue I've had this year, but I'm trying to keep this brief -- hoping clarity will instigate some help.)
    Recently I bought a Western Digital 500GB drive to go with my AEBS. I was intent upon using the drive as an Airdisk for Time Machine backups, but it isn't working. (I also have the WD drive partitioned in halves, but there is no reason to believe that is an issue.) When wired, the disk backs-up quickly and easily. After the initial backup, and attempting to do so wirelessly, however, it doesn't work. I get the message: "The backup volume could not be mounted."
    And there's the contradiction: the disk is mounted, I'm looking at the mounted disk as I type -- I even have no problems reading and writing from the Airdisks independent of Time Machine. I have all the latest software updates and am running Leopard. I've been going at this for hours, but I would really appreciate some help.
    Here are some of the things I've tried:
    -checking all connections
    -erasing the Airdisk and starting from scratch
    -repairing disk permissions(on my internal harddrive, the one I boot on, not the WD)
    -attempting to "Connect to Server" in the Finder, only to get this:
    And if you look, you can see that while the Airdisks are there, they are grey and can't be selected. It
    never becomes possible to select them, and "Connecting to Server" never connects.
    -I've toggled every Airport Utility setting to no avail(I will admit I might have missed something though).
    -I've done everything I can think of
    -banged my head into walls...
    -and pulled my hair out, but nothing.
    I really would like to get this working. This is my worst Apple experience yet, and it is literally making me sick. You will be my God if you can help me with this. Let me know if you need anymore information. Thanks in advance.
    <Edited by Moderator>

    Okay, so it seems you need to do initial Time-Machine-ing over WiFi if you intend to use it that way. Why nobody at Apple mentioned this baffles me; why this is even a problem, makes me wonder if Time Machine went through adequate testing.
    So my problem is solved! I am my own God!
    <Edited by Moderator>

  • Everything was OK - now have "The backup volume could not be found" error

    Setup:
    * MacBook Air
    * MacBook 10.5.5
    * Mac Mini with external hard drive with 2 partitions, one of which is called "Time Machine", 10.5.5
    What was working:
    MacBook Air and MacBook would backup with Time Machine over wireless connection to .sparseimage files on the "Time Machine" volume connected to the Mac Mini.
    Change:
    Had to give the MacBook Air back to my old employer, so I "merged" the MacBook Air onto the MacBook (the merge was somewhat convoluted, and unrelated to my issue I think: I used SuperDuper to copy the MacBook Air hard drive onto a new SATA notebook drive. Then I installed that drive in the MacBook. Then I used Migration Assistant to copy the user from the original MacBook SATA drive onto the new drive in the MacBook. Now I have two users on the MacBook, whereas before I had one use on each of two computers).
    Symptom:
    Now I cannot use Time Machine to backup the MacBook to the "Time Machine" volume. Everything I've tried causes Time Machine to briefly "prepare" the backup, then return the error "The backup volume could not be found". Things I've tried:
    * Mounting the volume "Time Machine" on the MacBook, under either user, works fine - I can write, read, and delete from the volume.
    * Deleting the old .sparseimage backup files from the "Time Machine" volume.
    * Erasing the "Time Machine" volume with Disk Utility on the Mac Mini.
    * Using "Change Disk..." in Time Machine to re-select the volume "Time Machine"
    * Using "Change Disk..." in Time Machine to select None, then restarting, then re-selecting the volume "Time Machine"
    * Making the volume "Time Machine" read/write by guests, then connecting to it from the MacBook as a guest instead of as an admin user.
    * Repairing permissions and/or repairing disks using Disk Utility on all applicable volumes.
    * Tried all of the above under both users on the MacBook (both of whom are Admin users)
    None of these things have worked, they all exhibit the same symptom when I manually start a time machine, or when I wait for Time Machine to automatically start the backup.
    Any ideas of what I can try next?

    Consider these reasons for this error...
    *_"Backup Volume Could Not Be Found"_*
    First, it is important to distinguish this error message from another, similar Time Machine error that states, “The backup volume could not be mounted”. This is important as the causes and cures for these two errors can be very different.
    *Reselect Your Time Machine Disk*
    (http://support.apple.com/kb/TS1329)
    In the Finder, go up to the "Go" menu and select "Connect to Server".
    Click the "Browse" button at the dialogue box.
    In the Network window that opens, do you see your TM drive?
    Double click it to mount the drive.
    Now let's try to reselect it for Time Machine use.
    Go to System Preferences --> Time Machine.
    Click the "Change Disk..." button.
    Select "None" and click "Stop Backing Up".
    Now click "Choose Backup Disk" and reselect your drive again.
    Close System Preferences and try backing-up again.
    On the other hand, does your Time Machine drive NOT appear at all? Is it appearing on your desktop? If it is still connected try disconnecting the cable, waiting a few seconds and then reconnecting the cable. Does the drive mount on the desktop? Try initiating a backup now.
    *Disk Fails to Wake From Sleep*
    “If your external HD has a sleep function that does not wake for Time Machine backups.  Time Machine will alert you that "The backup volume could not be found", and backups will not be made.” (http://support.apple.com/kb/TS1337)
    *3rd-Party Disk Utilities* #
    Many external hard disks come with software for maintaining/monitoring hard disk activities. It may have come on a separate CD or been installed on the drive itself. If these programs have been installed they may interfere with Time Machine backups, generate erratic behavior, or cause the drive to ‘disappear’ altogether.
    You may never know these applications are there as they may be running in the background. Go to System preferences --> Accounts. Select your account in the pane on the left. Click “Login Items”. Are there any items listed there that might refer to hard disk utilities. If so remove them using the “-” button at the bottom.
    *Time Capsule Has a Long Name*
    “When using your Time Capsule for Time Machine backups in Mac OS X 10.5 Leopard or later, the Time Capsule backup volume may not mount and Time Machine may not be able to back up to it. This alert may appear: "Backup volume cannot be found". This can happen if the Time Capsule disk has a long name. [http://support.apple.com/kb/HT1170]
    Open AirPort Utility (in /Applications/Utilities).
    Click your Time Capsule's icon.
    Click "Manual Setup".  
    Enter the password for the Time Capsule if prompted.
    Click the Disks icon.
    Highlight the volume name that appears under "Time Capsule Disk".
    In the Name field, enter a name for the volume that is less than 27 characters long.
    Click Update.
    After Time Capsule restarts, on the Mac(s)using Time Machine, open Time Machine preferences and reselect the Time Capsule volume.”
    Let us know if any of these suggestions help.
    Cheers!
    Message was edited by: Glenn Carter

  • TM Backup Volume after restoring with Migration Assistant

    Hi there,
    I recently restored my system from a time machine volume via migration assistant (NOT while first boot, because it hangs on caluculating amount of space there) to be able to use Boot Camp (my partition seemed to be too much fragmented). There are a whole bunch of files in older backups I still need. Therefor I need to know for sure if I can choose the external HDD with the old Backups as the new TM Backup Volume WITHOUT loosing my old backups.
    I haven't found satisfying information about it in this forum but of course it is possible that I've overlooked it.
    What do you think about it?
    Thanks a lot!

    ragob66,
    Welcome to the Apple discussions!
    Try this:
    *Accessing Time Machine Backups From Another User Account or Computer*
    Yes, you can do this using the Time Machine interface.
    Attach the drive containing the TM backups to your computer.
    Control-click the TM icon in the dock and select "Browse Other Time Machine Disks...".
    Highlight the desired disk and click “Use Selected Disk”. This will now allow you to browse those TM backups via the ‘time travel’ window. From here you can restore what files you need access to. Bear in mind that any files moved will have the permissions of that previous user account. Thus you may be prompted for the user name and password of that previous account. However, once verified you should be able to adjust “Sharing & Permissions” in the files “Get Info” window.
    Let us know if this resolved your issue.
    Glenn

  • "No such file or directory" errors on Time Machine backup volume

    I remotely mounted the Time Machine backup volume onto another Mac and was looking around it in a Terminal window and discovered what appeared to be a funny problem. If I "cd" into some folders (but not all) and do a "ls -la" command, I get a lot of "No such file or directory" errors for all the subfolders, but all the files look fine. Yet if I go log onto the Mac that has the backup volume mounted as a local volume, these errors never appear for the exact same location. Even more weird is that if I do "ls -a" everything appears normal on both systems (no error messages anyway).
    It appears to be the case that the folders that have the problem are folders that Time Machine has created as "hard links" to other folders which is something that Time Machine does and is only available as of Mac OS X 10.5 and is the secret behind how it avoids using up disk space for files that are the same in the different backups.
    I moved the Time Machine disk to the second Mac and mounted the volume locally onto it (the second Mac that was showing the problems), so that now the volume is local to it instead of a remote mounted volume via AFP and the problem goes away, and if I do a remote mount on the first Mac of the Time Machine volume the problem appears on the first Mac system that was OK - so basically by switching the volume the problem switches also on who shows the "no such file or directory" errors.
    Because of the way the problem occurs, ie only when the volume is remote mounted, it would appear to be an issue with AFP mounted volumes that contain these "hard links" to folders.
    There is utility program written by Amit Singh, the fella who wrote the "Mac OS X Internals" book, called hfsdebug (you can get it from his website if you want - just do a web search for "Mac OS X Internals hfsdebug" if you want to find it ). If you use it to get a little bit more info on what's going on, it shows a lot of details about one of the problematic folders. Here is what things look like on the first Mac (mac1) with the Time Machine locally mounted:
    mac1:xxx me$ pwd
    /Volumes/MyBackups/yyy/xxx
    mac1:xxx me$ ls -a
    . .DS_Store D2
    .. Documents D3
    mac1:xxx me$ ls -lai
    total 48
    280678 drwxr-xr-x 5 me staff 204 Jan 20 01:23 .
    282780 drwxr-xr-x 12 me staff 442 Jan 17 14:03 ..
    286678 -rw-r--r--@ 1 me staff 21508 Jan 19 10:43 .DS_Store
    135 drwxrwxrwx 91 me staff 3944 Jan 7 02:53 Documents
    729750 drwx------ 104 me staff 7378 Jan 15 14:17 D2
    728506 drwx------ 19 me staff 850 Jan 14 09:19 D3
    mac1:xxx me$ hfsdebug Documents/ | head
    <Catalog B-Tree node = 12589 (sector 0x18837)>
    path = MyBackups:/yyy/xxx/Documents
    # Catalog File Record
    type = file (alias, directory hard link)
    indirect folder = MyBackups:/.HFS+ Private Directory Data%000d/dir_135
    file ID = 728505
    flags = 0000000000100010
    . File has a thread record in the catalog.
    . File has hardlink chain.
    reserved1 = 0 (first link ID)
    mac1:xxx me$ cd Documents
    mac1:xxx me$ ls -a | head
    .DS_Store
    .localized
    .parallels-vm-directory
    .promptCache
    ACPI
    ActivityMonitor2010-12-1710p32.txt
    ActivityMonitor2010-12-179pxx.txt
    mac1:Documents me$ ls -lai | head
    total 17720
    135 drwxrwxrwx 91 me staff 3944 Jan 7 02:53 .
    280678 drwxr-xr-x 5 me staff 204 Jan 20 01:23 ..
    144 -rw-------@ 1 me staff 39940 Jan 15 14:27 .DS_Store
    145 -rw-r--r-- 1 me staff 0 Oct 20 2008 .localized
    146 drwxr-xr-x 2 me staff 68 Feb 17 2009 .parallels-vm-directory
    147 -rwxr-xr-x 1 me staff 8 Mar 20 2010 .promptCache
    148 drwxr-xr-x 2 me staff 136 Aug 28 2009 ACPI
    151 -rw-r--r-- 1 me staff 6893 Dec 17 10:36 A.txt
    152 -rw-r--r--@ 1 me staff 7717 Dec 17 10:54 A9.txt
    So you can see from the first few lines of the "ls -a" command, it shows some file/folders but you can't tell which yet. The next "ls -la" command shows which names are files and folders - that there are some folders (like ACPI) and some files (like A.txt and A9.txt) and all looks normal. And the "hfsdebug" info shows some details of what is really happening in the "Documents" folder, but more about that in a bit.
    And here are what a "ls -a" and "ls -al" look like for the same locations on the second Mac (mac2) where the Time Machine volume is remote mounted:
    mac2:xxx me$ pwd
    /Volumes/MyBackups/yyy/xxx
    mac2:xxx me$ ls -a
    . .DS_Store D2
    .. Documents D3
    mac2:xxx me$ ls -lai
    total 56
    280678 drwxr-xr-x 6 me staff 264 Jan 20 01:23 .
    282780 drwxr-xr-x 13 me staff 398 Jan 17 14:03 ..
    286678 -rw-r--r--@ 1 me staff 21508 Jan 19 10:43 .DS_Store
    728505 drwxrwxrwx 116 me staff 3900 Jan 7 02:53 Documents
    729750 drwx------ 217 me staff 7334 Jan 15 14:17 D2
    728506 drwx------ 25 me staff 806 Jan 14 09:19 D3
    mac2:xxx me$ cd Documents
    mac2:Documents me$ ls -a | head
    .DS_Store
    .localized
    .parallels-vm-directory
    .promptCache
    ACPI
    ActivityMonitor2010-12-1710p32.txt
    ActivityMonitor2010-12-179pxx.txt
    mac2:Documents me$ ls -lai | head
    ls: .parallels-vm-directory: No such file or directory
    ls: ACPI: No such file or directory
    ... many more "ls: ddd: No such file or directory" error messages appear - there is a one-to-one
    correspondence between the "ddd" folders and the "no such file or directory" error messages
    total 17912
    728505 drwxrwxrwx 116 me staff 3900 Jan 7 02:53 .
    280678 drwxr-xr-x 6 me staff 264 Jan 20 01:23 ..
    144 -rw-------@ 1 me staff 39940 Jan 15 14:27 .DS_Store
    145 -rw-r--r-- 1 me staff 0 Oct 20 2008 .localized
    147 -rwxr-xr-x 1 me staff 8 Mar 20 2010 .promptCache
    151 -rw-r--r-- 1 me staff 6893 Dec 17 10:36 A.txt
    152 -rw-r--r--@ 1 me staff 7717 Dec 17 10:54 A9.txt
    If you look very close a hint as to what is going on is obvious - the inode for the Documents folder is 152 on the local mounted case (the first set of code above for mac1), and it's 728505 in the remote mounted case for mac2. So it appears that these "hard links" to folders have an extra level of folder that is hidden from you and that AFP fails to take into account, and that is what the "hfsdebug" shows even better as you can clearly see the REAL location of the Documents folder is in something called "/.HFS+ Private Directory Data%000d/dir_135" that is not even visible to the shell. And if you look closely in the remote mac2 case, when I did the "cd Documents" I don't go into the inode 135, but into the inode 728505 (look close at the "." entry for the "ls -la" commands on both mac1 and mac2) which is the REAL problem, but have no idea how to get AFP to follow the extra level of indirection.
    Anyone have any ideas how to fix this so that "ls -l" commands don't generate these "no such file or folder" messages?
    I am guessing that the issue is really something to do with AFP (Apple File Protocol) mounted remote volumes. The TimeMachine example is something that I used as an example that anyone could verify the problem. The real problem for me has nothing to do with Time Machine, but has to do with some hard links to folders that I created on another file system totally separate from the Time Machine volume. They exhibit the same problem as these Time Machine created folders, so am pretty sure the problem has nothing to do with how I created hard links to folders which is not doable normally without writing a super simple little 10 line program using the link() system call - do a "man 2 link" if you are curious how it works.
    I'm well aware of the issues and the conditions when they can and can't be used and the potential hazards. I have an issue in which they are the best way to solve a problem. And after the problem was solved, is when I noticed this issue that appears to be a by-product of using them.
    Do not try these hard links to folders on your own without knowing what they're for and how to use them and not use them. They can cause real problems if not used correctly. So if you decide to try them out and you loose some files or your entire drive, don't say I didn't warn you first.
    Thanks ...
    -Bob

    The problem is Mac to Mac - the volume that I'm having the issue with is not related in any way to Time Machine or to TimeCapsule. The reference to TIme Machine is just to illustrate the problem exists outside of my own personal work with hard links to folders on HFS Extended volumes (case-sensitive in this particular case in case that matters).
    I'm not too excited about the idea of snooping AFP protocol to discover anything that might be learned there.
    The most significant clue that I've seen so far has to do with the inode numbers for the two folders shown in the Terminal window snippets in the original post. The local mounted case uses the inode=728505 of the problematic folder which is in turn linked to the hidden original inode of 135 via the super-secret /.HFS+... folder that you can't see unless using something like the "hfsdebug" program I mentioned.
    The remote mounted case uses the inode=728505 but does not make the additional jump to the inode=135 which is where lower level folders appear to be physically stored.
    Hence the behavior that is seen - the local mounted case is happy and shows what would be expected and the remote mounted case shows only files contained in the problem folder but not lower-level folders or their contents.
    From my little knowledge of how these inode entries really work, I think that they are some sort of linked list chain of values, so that you have to follow the entire chain to get at what you're looking for. If the chain is broken somewhere along the line or not followed correctly, things like this can happen. I think this is a case of things not being followed correctly, as if it were a broken chain problem then the local mounted case would have problems also.
    But the information for this link in the chain is there (from 728505 to the magic-135) but for some reason AFP doesn't make this extra jump.
    Yesterday I heard back from Apple tech support and they have confirmed this problem and say that it is a "implementation limitation" with the AFP client. I think it's a bug, but that will have to be up to Apple to decide now that it's been reported. I just finished reporting this as a bug via the Apple Bug Reporter web site -- it's bug id 8926401 if you want to keep track it.
    Thanks for the insights...
    -Bob

  • Unable to restore from Time Machine after an erase and reinstall - MacbookPro cannot access my old Time Machine backup volume. Desperate for help please?

    My MacbookPro would not move past the Apple logo and spinning wheel for a number of hours.  After trying the numerous suggestions to solve the issue I eventually opted to erase and reinstall feeling confident my Time Machine backups would come to the rescue.  After a successful erase and reinstall I tried to restore all my data from my TIme Capsule using Command-R during start up and by using the Migration Assistant.  Neither worked and I have received messages to the effect that the backup volumes on my Time Capsule cannot be access because I have entered a wrong password or because the backup volume is damaged.
    When I open my Time Capsule in Finder and click on my sparsebundle I get an eror message saying that the disk image could not be opened and that the resource is temporarily unavailable.
    Desperate for some help and comfort that many years of personal data have not been lost.
    Thank you.
    M

    When I try to Verify option it says Unable to Verify - Resource temporarily unavailable.
    Here is the past of the log screen:
    2013-06-09 15:00:00 -0500: Disk Utility started.
    2013-06-09 15:09:01 -0500: Disk Utility started.
    2013-06-09 15:19:53 -0500: [DUDiskController viewablePartitions] expecting DUDisk, but got nil
    2013-06-09 15:19:53 -0500:
    2013-06-09 15:20:00 -0500: [DUDiskController viewablePartitions] expecting DUDisk, but got nil
    2013-06-09 15:20:00 -0500:
    2013-06-09 15:20:05 -0500: [DUDiskController viewablePartitions] expecting DUDisk, but got nil
    2013-06-09 15:20:05 -0500:
    2013-06-09 15:20:13 -0500: Verifying Image “Macajee’s MacBook Pro”
    2013-06-09 15:20:14 -0500: Unable to verify “Macajee’s MacBook Pro.” (Resource temporarily unavailable)
    2013-06-09 15:20:14 -0500:
    2013-06-09 15:25:21 -0500: Verifying Image “Macajee’s MacBook Pro”
    2013-06-09 15:25:23 -0500: Unable to verify “Macajee’s MacBook Pro.” (Resource temporarily unavailable)
    2013-06-09 15:25:23 -0500:
    2013-06-09 15:25:27 -0500: Attach Image “Macajee’s MacBook Pro”
    2013-06-09 15:25:27 -0500: Initializing…
    2013-06-09 15:25:31 -0500: Attaching…
    2013-06-09 15:25:31 -0500: Finishing…
    2013-06-09 15:25:32 -0500: Unable to attach “Macajee’s MacBook Pro.” (Resource temporarily unavailable)
    2013-06-09 15:25:32 -0500:
    2013-06-09 20:02:06 -0500: Disk Utility started.
    2013-06-09 20:05:22 -0500: Disk Utility started.
    2013-06-09 20:07:11 -0500: Disk Utility started.
    2013-06-09 20:18:34 -0500: [DUDiskController viewablePartitions] expecting DUDisk, but got nil
    2013-06-09 20:18:34 -0500:
    2013-06-09 20:19:34 -0500: [DUDiskController viewablePartitions] expecting DUDisk, but got nil
    2013-06-09 20:19:34 -0500:
    2013-06-09 20:19:36 -0500: [DUDiskController viewablePartitions] expecting DUDisk, but got nil
    2013-06-09 20:19:36 -0500:
    2013-06-09 20:22:29 -0500: [DUDiskController viewablePartitions] expecting DUDisk, but got nil
    2013-06-09 20:22:29 -0500:
    2013-06-09 20:22:33 -0500: [DUDiskController viewablePartitions] expecting DUDisk, but got nil
    2013-06-09 20:22:33 -0500:
    2013-06-09 20:22:45 -0500: Verifying Image “Macajee’s MacBook Pro”
    2013-06-09 20:22:45 -0500: Unable to verify “Macajee’s MacBook Pro.” (Resource temporarily unavailable)
    2013-06-09 20:22:45 -0500:
    2013-06-09 20:34:53 -0500: [DUDiskController viewablePartitions] expecting DUDisk, but got nil
    2013-06-09 20:34:53 -0500:
    2013-06-09 20:34:56 -0500: [DUDiskController viewablePartitions] expecting DUDisk, but got nil
    2013-06-09 20:34:56 -0500:
    2013-06-09 20:38:17 -0500: Verifying Image “Macajee’s MacBook Pro”
    2013-06-09 20:38:17 -0500: Unable to verify “Macajee’s MacBook Pro.” (Resource temporarily unavailable)
    2013-06-09 20:38:17 -0500:
    2013-06-09 20:47:35 -0500: Disk Utility started.
    2013-06-09 20:53:06 -0500: Disk Utility started.
    2013-06-09 20:55:30 -0500: Disk Utility started.
    2013-06-09 20:56:40 -0500: Disk Utility started.
    2013-06-09 21:06:32 -0500: Verifying Image “macajee’s MacBook Pro”
    2013-06-09 21:06:32 -0500: Unable to verify “macajee’s MacBook Pro.” (Resource temporarily unavailable)
    2013-06-09 21:06:32 -0500:
    2013-06-09 21:07:08 -0500: Verifying Image “macajee’s MacBook Pro”
    2013-06-09 21:07:08 -0500: Unable to verify “macajee’s MacBook Pro.” (Resource temporarily unavailable)
    2013-06-09 21:07:08 -0500:

  • Permissions Issue, Colour Wheel, Hard Drive Issue??

    Hi!
    I have had issues with my mid 2009 MBP recently and I'm wondering what the best way to fix them would be. 
    First off, I have some major permissions issues with my accounts.  I am using 3 different users regualrly on the same machine and needed to access files from the home folder so I changed them a long time ago, and am not sure how to fix that.  I have repaired the permissions countless times in the disk utility and it seems like there's always loads more to do each time.  When I varify the disk, it says its all okay.
    Secondly, I have had the machine freeze on me several times while doing very little on it.  This happened awhile ago, and thought that it was just the permisions thing and so I did that again, and it started working better, for awhile.  It would go a few days or weeks before doing the same thing, sometimes not even getting past the apple logo on startup before freezing.  This makes me think it may be a hard drive issue???????
    This morning, I tried dozens of times to boot, with no success at all.....  until about the 25th time when it miraculasly booted.  I have run permissions repair a few more times and it seems to be working okay at the moment, but the problem seems to be happening more often over time. 
    To complicate matters, I am traveling at the moment and will not be home for several months.  I purchased an external harddrive last night and was able to successfully back up my data. 
    Question 1: Is it the permissions that are causing these problems, or is it related to something else.  The computer seems to work fine when its working, and then once in awhile, decides its not going to do anything. 
    Question 2:  Would upgrading to Lion (currently running 10.6.8) fix the permissions issues or just carry them forward?  I would like to consolidate the 3 users into one, if that would solve it.  Does the migration utility preserve permissions or does it give you a brand new start?
    Question 3:  If neither solving the permissions or the OS upgrade would fix the problem and it does need a new harddrive, is it possible to buy one and install it myself?  I do not have apple care left on this machine and am on a very tight budget.  I am used to taking things apart and all that as part of my job and it seems simple enough.  Where can you buy a replacement?? 
    Hopefully someone out there will be able to help me out on this one. 
    Cheers!!!!
    Brian

    bgroot422 wrote:
    First off, I have some major permissions issues with my accounts.  I am using 3 different users regularly on the same machine and needed to access files from the home folder so I changed them a long time ago, and am not sure how to fix that.  I have repaired the permissions countless times in the disk utility and it seems like there's always loads more to do each time.  When I verify the disk, it says its all okay.
    Disk Utility permissions are separate from User account permissions.
    This link is how to fix them
    https://discussions.apple.com/thread/2181549?start=0&tstart=0
    Disk Utility will always show something to be needing repair, but that's ok
    Apple supoort doc.
    https://support.apple.com/kb/TS1448?locale=da_DK
    Verify Disk is good, that's a good thing.
    To complicate matters, I am traveling at the moment and will not be home for several months.  I purchased an external hard drive last night and was able to successfully back up my data. 
    Your data is backed up, hopefully not with TimeMachine alone, but if you did, then get another drive and backup data manually to that as well. If the TM drive gets messed up, it's a pain to get your data off of it.
    Question 1: Is it the permissions that are causing these problems, or is it related to something else.  The computer seems to work fine when its working, and then once in awhile, decides its not going to do anything.
    Well you could call Apple for replacement 10.6.x disks, and just reinstall 10.6 and bundled programs, but this can kick out kext files out of the /System/Library/Extensions folder installed by some third party software.
    This method fixes OS X, but doesn't touch your files or most programs.
    Nor will this method fix your Users accounts if the issue is in there.
    A creation of a new user, then deletion of the others, return files from backup (set permissions) will fix User folder issues if the above user permissions fix doesn't work.
    (Of course you could wipe the drive from the 10.6 disk, but you have to install all software again)
    Would upgrading to Lion (currently running 10.6.8) fix the permissions issues or just carry them forward?
    No, you don't want to install Lion, it won't fix those issues in User folders, not only that Lion has it's own issues and doesn't work with a lot of older software etc.   No use clusterfscking a already bad situtation when it's seems it's only localized to the User accounts.
    I would like to consolidate the 3 users into one, if that would solve it.
    Yes that could very nicely and tidy up things in the process.
    What you do is transfer all files to one regular powered storage hard drive.
    (Don't use/disconnect the TimeMachine drive for this as it preserves the users seperated and you don't want all those users back restoring  with Migration Assistant)
    Create the New User on the machine as Admin, log into it and delete all the other Users, transfer all your files back from the regular storage drive, changing all the permissions to yourself before placing them into their respective folders as they will have three different permissions.
    Notes:
    If you have a extensive iTunes playlists on one User (say #1), then create the new user with that same name (will require some work, create User 4, delete Users 1-3, reboot, create User 1, delete User 4) then transfer your iTunes folder to Music of that User 1 (same name as before). This will preserve the pathnames of your song locations and your playlists will be preserved.
    (before you ask, no you can't combine playlists)
    Also if you have photo's in iPhoto Library, you have to right click on it and "show package contents" inside is a folder called Originals, copy them out and import into the iPhoto of the User #1.
    Does the migration utility preserve permissions or does it give you a brand new start?
    Yes it preserves user permissions, no it doesn't give you a brand new start. Only a fresh install, creation of new users and then just transferring of files does that.
    Nothing about TimeMachine or Migration Assistant gives one a "fresh start", it's if hosed, so is your restore.
    If you want that sort of pristine protection, you need to clone your ideal boot partition/drive using Carbon Copy Cloner (free/donationware) occasionally as a hold the option key bootable drive, then you can erase and reverse clone the pristine saved clone.
    One can also update the clone on occasion, this way keeping the clone pristine.
    I maintain 3 clones time dated, even have my boot drive partitioned 50/50 and auto-cloned, this way I have two boot partitions on the road and two externals at home.
    I never use TimeMachine, it's not bootable (well it is on 10.7.2 only to restore though)

  • "This backup is too large for the backup volume" - Info

    Hi there. I had a problem with my time machine and got an error stating "This backup is too large for the backup volume". I did noticed after logging in that TM was indexing in the upper right corner [magnifier with a flashing dot(spotlight)] for a few seconds. So then I went on to "back up now" and it was preparing and then I got the Error message described above. So I uninstalled my anti-virus (you must disable auto protection/or exclude timemachine.app and its plist file (location below)from Anti-virus preferences in the case you have a anti-virus app, otherwise it will take forever to back up.) though that was not my issue. I then turn off time machine and deleted this .plist file in Macintosh HD > Library > Preferences > com.apple.TimeMachine.plist....STOP here if this fixed your problem after restarting. Time machine External Drive in Disk Utility **THESE STEPS WILL ERASE YOUR ENTIRE BACKUPS** ( "Erase" and rename or "partition" to make more that one partition on the External Drive if you wish, and Rename) (Disk utility> Partition tab> "option" you must - guid=intel / apple partition map=PowerPC)...sorry alot of newbie out there...by deleting the "com.apple.TimeMachine.plist" = when you plug in you TM it will ask you if you want to use the drive as a TM back up automatically. This did the trick. But to let you guys know I also used Cocktail (app) and used a feature it has to erase my computers spotlight index and rebuild it. Also in Cocktail, when you have your time machine plugged in you can erase its index and disable it all together. I recommend you first disable spotlight (before the first initial TM backup) in system preferences > spotlight> Privacy (tab) and plus to add time machine ...which has to be mounted (plugged in) to add from window under "Devices".

    http://www.macfixit.com/article.php?story=20090403093528353

  • Can't Customize, Change Settings, or Move Files -- Permissions Issue?

    Hey all:
    Just got a new MBP w/ 10.5.2. Successfully migrated most of my user settings and applications from the old Tiger HDD (old laptop died a horrible death).
    The problem is that aside from everything appearing to be the same, I'm finding that I don't have the access to do a whole lot with my own files. Several different problems that "seem" like they're stemming from the same accessiblity/permissions issue include:
    Intermittent trouble downloading files with Firefox's default download tool.
    Complete inability to change desktop background.
    Programs fail to remember setting changes after quit and re-launch.
    System Preferences do not remember changes to settings.
    Certain files can not be moved, renamed, opened, or deleted w/o admin authorization, or in some cases, at all.
    The problems started after I migrated the old system over after having an interim user account running for a few days prior. After migrating, I attempted to reconcile the two together and that's when things got hairy.
    In the past couple days, I have tried:
    1.) Archive and Install (preserving User settings - now down to just one admin).
    2.) Changing permissions to system read/write, admin read/write, everyone read only for the entire /User directory, applied to all enclosed items.
    3.) Repairing Permissions (which took about 10 minutes!)
    I'm at the end of my rope here. I'm stuck with my OS acting the way it wants to, which is the exact way it was after being archived and reinstalled, no matter what changes I try to apply in the Finder, Preferences, or in any programs.
    I'm thinking maybe a clean install and then migrating over the backup I just made on my external HD will get me my stuff without whatever troublesome thing is freezing me out, but I'm not really sure, and I don't really understand much about command lines in Terminal.
    Does anyone have any ideas? Many thanks.

    Oddly enough I just had a spastic moment with a mouse click and put my Drop Box in the Trash (I keep the Delete thing in my window toolbar, which is handy, but can lead to accidents)... Since I was playing with it I noticed its absence immediately. Realized what I had done after a moment's reflection, and put it back. Which just goes to confirm something I ALWAYS do before I empty the Trash: open it and see what's in there first, then click empty.
    As to whether removing ACLs is for advanced users only: well, up until Leopard that's the way it always was, there were, until now, NO ACLs on the users folders. So should everyone have been an advanced user until now? Did you ever delete a folder in Jaquar or Panther or Tiger and empty your Trash without checking? Indeed, if you use Time Machine, available in Leopard but not before, you are already protected from such goofs, since you can recover things accidently deleted using Time Machine, so actually you are in better shape with Leopard than ever before, WITHOUT the ACLs if you use Time Machine. Until Leopard there was neither belt nor suspenders to automatically protect you from losing data. Leopard supplies both.
    The situation reminds me of the continuing debate about virus protection on the Mac. Personally, I have seen various anti-virus programs cause all sorts of problems, and it has yet to protect any Mac system from anything (since as yet there are no Mac system viruses). Anti-virus software may have saved some users of Microsoft Office who share files with Windows users from getting a macro virus in their Word docs, and it might have kept a Mac user from passing on some email virus to some Windows users by forwarding stuff from the Internet. But still.... if you don't use MS Office or forward email junk, you get no benefit and may get some problems.
    Same seems to me to be true of ACLs: it is possible to get a benefit (you can't accidently toss your Movies folder and lose data, assuming you mindlessly empty your Trash and don't have a backup), but an awful lot of people are having an awful lot of problems.
    Francine
    Francine
    Schwieder

  • Backup Volume cannot be mounted

    Time machine stopped working for me back in July. I've looked at every post and tried nearly everything, and I cannot get it working again. The error through the Time Machine pref pane is "The Backup volume cannot be mounted." The errors in the console are the following:
    Sep 4 23:19:25 tesla /System/Library/CoreServices/backupd[50182]: Backup requested by user
    Sep 4 23:19:25 tesla /System/Library/CoreServices/backupd[50182]: Starting standard backup
    Sep 4 23:19:25 tesla /System/Library/CoreServices/backupd[50182]: Network mountpoint /Volumes/Backup not owned by backupd... remounting
    Sep 4 23:19:26 tesla /System/Library/CoreServices/backupd[50182]: Failed to remount network volume.
    Sep 4 23:19:31 tesla /System/Library/CoreServices/backupd[50182]: Backup failed with error: 19
    This is a network volume. It's a 750GB firewire drive, formatted HFS+ with a GUID partition table connected to an iMac. The iMac can back up just fine to it. My MBP cannot. It worked before.
    It appears it is failing to remount the drive as root rather than myself, as backupd runs as root. Others are having the same problem, and I've seen no resolution for this particular issue. Is Apple even aware of it? Do they even read the discussion forums?

    Paul,
    Give these ideas some condsideration:
    First, it is important to distinguish this error message from another, similar Time Machine error that states “The backup volume could not be found”. This is important as the causes and cures for these two errors can be very different.
    Give each topic separate consideration. If one does not resolve your issue, move on the next one.
    *Time Machine Has Lost Its’ Backup Disk*
    If Time Machine was NOT setup to recognize a hard disk for backup, and “Back up now” was selected from the Time Machine Dock icon, an error would report “No backup volume has been selected. To select a backup volume, open . . “ The Console log would report:
    +Backup failed with error: 17+
    But if Time Machine HAD BEEN setup to use a specific disk for backups, but if had lost its’ connection to the drive, it would report “The backup volume could not be mounted”. The Console log would say:
    +FSMatchAliasBulk returned -35 while resolving alias to backup target+
    +Backup failed with error: 19+
    When you check the Time Machine preferences you may see the name of your backup disk greyed-out and a generic hard drive icon beside it. More than likely this means Time Machine has lost is physical connection to the drive. Either the drive is not plugged in, it’s not turned ON, the drives’ cable is bad, the drives internal controller has failed, or the drive has a sleep function that is preventing it from waking when a backup is called for.
    *Airport Has Been Turned Off* (For Time Capsule / AirDisk Users) #
    Look and the Airport menu at the top of the screen. Does it no longer display the radiating bands of wireless signal strength? The Airport has been turned off on this computer.
    Go to System Preferences.
    Select Network.
    Click “Turn Airport On”
    Now try backing up.
    *File Sharing Has Been Disabled* (For Time Capsule / AirDisk Users) #
    Launch Airport Utility.
    Click "Manual Setup".
    Select "Disks" in the tool bar at top of window.
    Click "File Sharing".
    Verify that "Enable file sharing" is checked.
    If not, check it, click “Update”.
    Once the Time Capsule has finished restarting, close Airport Utility and try backing up again.
    *Password Has Changed/Become Corrupted* (For Time Capsule / AirDisk Users) #
    [Mac OS X 10.5.3 or later: Time Machine - "Backup volume could not be mounted" after changing network volume's password]
    *Proper Computer Name* #
    Make sure your computer has a proper name. Go to System Preferences --> Sharing. Time Machine needs to differentiate your computer from others on your network (i.e. "Bills MacBook" or "Office iMac"). If the "Computer Name" field is blank, create a name. Realize that if this step is necessary, you will likely have to start the Time Machine backup process over again and do another full initial backup.
    According to THIS article [http://support.apple.com/kb/TS1760], Time Machine may experience problems if your computer name includes certain characters. Make sure the computer name only includes ASCII characters from the following set.
    (0123456789abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ)
    Once a change in the computer name occurs, you should stop and restart Sharing on the affected computer. Uncheck and then recheck Sharing in the Services list on the left.
    Also, if the name of your backup devise contains any special characters (like an apostrophe) consider removing them and trying a backup again.
    Let is know if any of the ideas above helped.
    Cheers!

Maybe you are looking for

  • 6 month on.. My observations on Data Services vs SSIS

    Hi all, I'd like to share some observations on my first six months working with Data Services.  I have previously worked with SSIS for several years and have some minor experiense with Datastage also. Firstly, let me say that I am largely happy with

  • Sony DSR PD-170 Non-Drop Frame Footage

    I recorded footage on my PD-170 in non-drop frame (NDR) and went to capture my footage into Final Cut Pro. I changed my sequence settings to NDR and I went to Batch Capture some clips and after each one it told me that my PD-170 was in drop-frame mod

  • Airport Extreme can't connect to MacBook Pro running Windows XP

    I have a new Airport Extreme Base Station and an intel MacBook pro that is 6 months old and dual boot. The AEBS is set up with WPA2 and AEs. All works well for both MacOS (Leopard) and WindowsXP in wired mode and wireless works fine for the Mac side.

  • How to use HttpServletResponse() ?

    Dear sirs... consider the following code: public class DataPage1Action extends DataForwardAction public void onAa(DataActionContext ctx) ctx.getHttpServletResponse().setContentType("text/txt"); try ctx.getHttpServletResponse().getWriter().write("this

  • How to display fonts on my system?

    Working in Windows 7,  I have so many fonts installed.  Is there a way to easily create some kind of key or master list showing the font and how it looks?