Benches macOS

10

Time Machine Read-Only Error

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

Just today I am getting a Time Machine error that it cannot backup, stating that the given volume is Read Only. I have been using Time Machine for a while now (some months), with only minor issues (occasional backup failure without specified cause) but never consecutive backup failures before.

Now, the volume is Read Only, just checked its Information - in-fact both of my Time Machine disks are (I have two separate drives that I switch over once a day to keep a Time Machine copy in two places - redundancy).

Anyways, I don't know what the problem or solution is, I have tried to Sleep the Mac, and unplug the drives' power cables. None of that has helped.

Any ideas?

10 replies

Sign in or join Beachball Help to reply.

  1. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    If you have tried changing the permissions on the drives through the normal means and have been unsuccessful, then the following may help:

    What to do if Time Machine reports you don't have permission

    This was posted in the Apple Discussions by V.K. I have only modified it slightly to be more generic.

    The problem seems to be that 10.5.6 changes permissions on a file so that even the root user doesn't have write peivileges. I have no idea why they did this. The workaround suggested in [an]other post will probably work, too, but i did something less drastic. Instead of deleting the file I changed permissions on it, and it worked just fine. An added benefit is that the permission change seems to stick, so you don't have to delete the file every time you change a drive.

    [Open the Terminal application in your Utilities folder. At the prompt [enter] the following command:

    sudo chmod 644 /volumes/"TM drive name"/.xxxxxxxxxxxx

    The name of the file .xxxxxxxxxxxx is based on the MAC address of your computer and will be different for every computer. Put the name of the TM drive in the above and keep the quotes.

    You'll have to enter your admin password (which you won't see) which is normal.

    This was edited by Kappy just for cleanup.

    Enable Finder to Show Invisible Files and Folders

    Open the Terminal application in your Utilities folder. At the prompt enter or paste the following command line then press RETURN.

    defaults write com.apple.finder AppleShowAllFiles TRUE

    To turn off the display of invisible files and folders enter or paste the following command line and press RETURN.

    defaults write com.apple.finder AppleShowAllFiles FALSE

    Alternatively you can use one of the numerous third-party utilities such as TinkerTool or ShowHideInvisibleFiles - VersionTracker or MacUpdate.

  2. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I can't remember how local disks are handled but remote disks use a sparsebundle. You can check the backup sparsebundle to see if it is damaged because this also causes the read only error.
    To check the backup:
    1/ Mount the disk that you backup to
    2/ Find the backup file - normally named "yourmachinename_hexnumber.sparsebundle"
    3/ Launch Disk Utility
    4/ Drag the backup file into the Disk Utility disk list on the left handside of its window
    5/ Select the file and click "Verify disk" button

    If the sparsebundle is ok then it may be your physical backup disk that is the problem. If the sparsebundle is damaged then that is likely the issue.

    My experience is that Time Machine on my mac pro consistently destroys its airdisk archive every couple of months. Other macs backing up over the same network to the same disk do not have this problem and the physical disk does not have a problem. Although I haven't lost any data it's beginning to get annoying having to restart backups

    Message was edited by: foldedSoul

  3. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Thanks for all your help - very truly.

    A run of DiskWarrior fixed all issues. I had not been in the habit of DiskWarrioring the TM drives - emphasis on had not.

  4. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I have a similar problem whit my time machine but when i try to change the permisions on terminal it says that it’s a Read-only file system
    I have some files that i rely need so i can’t format te disk the files are not backup but they are in a folder in the disk.
    when i try to copy or move it says that an unexpected error has occurred (error code -1426.)
    Can anyone help me please

  5. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I get this problem on a regular basis. The simple fix is to delete your backup file on the TC and start a new backup. You lose all of your previous backups, but it works. Apple really needs to improve TC and TM. Great idea but, it dosen't really work great on a regular basis

  6. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Hi all,

    thanks for your contributios to this problem. I have the problem about "read only" too.
    When I get info about my external drive (LaCie 250 Gb attached with FW400) i can see :
    maison (me) read & write
    (unknown) read only
    everyone read only

    So I don't have sparsebundle file with hexadecimal name (may because my external drive isn't attached with network) so i can't use the chmod 644 command.

    Somedy have an Idea ?
    I've tried to chmod 777 (with root) on entire disk but I receive "read only filesystem" and "operation not permitted"

    Thanks in advande
    Seb

  7. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Hi Kappy,

    thanks for your help !

    I follow your instructions :
    1) display invisible files ok I see a .0016cbc95868 file on my external drive
    2) use terminal with command "sudo chmod 644 /Volumes/"La Cie"/.0016cbc95868
    but system return "No such file or directory"

    Can you see if I make a mistake ?

    Thanks in advance
    Seb

    Message was edited by: Sebastien Rousseau

  8. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I didn't find this in time before, in frustration, I wiped the hard drive... again... and am going to go through the all-night task of getting the backup started up fresh again. 1 1/2 months of backup down the .... drain.
    This happened before. (1 1/2 months ago).
    I have an iMac and a MacBook Pro both connected to the Time Machine'd HD which is connected to an Airport Extreme basestation.
    Both issues started with the iMac... which at some point started saying "The backup volume is read only."
    Very, very frustrating.
    I disconnected the computers from the HD... then connected the HD directly to my MacBook Pro... used disk utility to try and fix the disk...
    This did not work.

    If this happens again down the road I am going to scream.
    This is supposed to be easy... and, I admit, it is... until it scr_ws up. Then the errors are so "easy" looking that you just want to scream.

    If / when it happens again... I will let you know if this process worked.
    I only hope that I don't have to return here.

  9. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I, too, have experienced the notice of my drive mysteriously becoming "read only" by TIME MACHINE. I have been looking for a fix for about a week and a half. I have restarted the computer with and without the drive attached, ... I have ejected and re-connected the drive on several occasions, ... and was ready, today to just throw in the towel and reformat the drive and start fresh. Not happy about it, but had no other choices.

    Then, today, I checked the TIME MACHINE LOG on the external HD (1TB MyBook, USB) and was ready to start over ... and wha-la, I am backed up. VErY sTrANgE.

    Come on APPLE give us some help with answers.

    Could it be that a recent update contained a fix?

  10. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I used Time Machine without incident for many months, backing up one Macbook to an Airdisk. Two weeks ago I bought a Drobo to replace my single-drive Airdisk, and at the same time set up a second Macbook and an iMac to also Time Machine into the newer, larger drive.

    Naturally I didn't attempt to keep my old sparsebundle: all three computers started their backups from scratch.

    My Macbook didn't even complete its first backup before experiencing the "read-only" error described in this thread, followed by corruption of the sparsebundle (Invalid node, according to Disk Utility). The iMac completed its first backup and worked for about a week before experiencing the same failure. At this point, the second Macbook is still Time Machining properly, for no reason I can fathom.

    Changing the chmod permissions of the invisible files whose names correspond to the MAC addresses of the three computers accomplished nothing.

    I have now switched to Chronosync until Apple fixes this bug. I updated to 10.5.6 as soon as it came out, and Time Machine worked after that--until I changed hardware and added more computers to the mix.