NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

jluros's avatar
jluros
Aspirant
May 18, 2017

Can't delete Time Machine .inprogress folder

I'm a new ReadyNAS user.

 

I migrated two sparsebundles over from an external drive attached to our AirPort Extreme Base Station. After turning Time Machine back on and pointing it to the new share, Time Machine gets stuck on "preparing backup." The instructions on several sites say to remove the ".inProgress" file, which I'd love to do, but can't. Locally (when logged into the ReadyNAS through SSH), the sparsebundle is stored as a proprietary format that the system can't read properly (only Macs can read sparsebundles properly).

 

When I've mounted the sparsebundle on the ReadyNAS as Time Machine Backups and browsed to Backups.backupsdb/SYSTEMNAME in Finder, I can't delete the .inProgress file/folder. No matter what user/password combination I use, it rejects it (readynas, admin, or root). I didn't think admin would work, but I thought the Time Machine user (readynas) or root should have worked, but they don't. Any knowledable Mac ReadyNAS users out there?

6 Replies

Replies have been turned off for this discussion
  • Amidala's avatar
    Amidala
    NETGEAR Expert

    When logged into the ReadyNAS through SSH, in /data/.timemachine, you can see all files from Mac. Then you can delete any files.

    • jluros's avatar
      jluros
      Aspirant

      That's not correct. It says, "Operation Not Permitted." Did you try that?

    • capaz's avatar
      capaz
      Tutor

      Amidala wrote:

      When logged into the ReadyNAS through SSH, in /data/.timemachine, you can see all files from Mac. Then you can delete any files.


      Not sure exactly what you mean by "through SSH" together with "see all the files from the Mac", so I'm assuming that you just mean using SSH client on the Mac to get a linux shell on the ReadyNAS.  While it's true that you can then see the component files of the sparsebundle(s) in /data/.timemachine, that doesn't help.  Taken all together the sparsebundle folder/file tree represents an image of a HFS+-formatted virtual disk.  The file that the OP is referring to is inside that virtual HFS+ filesystem, not one of the component files of the sparsebundle itself.

       

      I'm not aware of any reliable way on linux to access the sparsebundle's virtual disk/filesystem.  Apologies if I misunderstood your suggestion.

       

      jluros, what do you mean by "No matter what user/password combination I use, it rejects it (readynas, admin, or root)."?  If I understand what you're saying, you've already mounted the ReadyNAS Time Machine share *and* the virtual disk (on /Volumes/Time Machine Backups), so I don't see where the ReadyNAS user accounts come in after that.  At this point, /Volumes/Time Machine Backups is effectively a local disk on the Mac client, so the permissions on its HFS+ filesystem are *local* to the Mac, and independent of the ReadyNAS user accounts.  You should be able to use the root user on the Mac to do whatever you need to do.

       

      • capaz's avatar
        capaz
        Tutor

        capaz wrote:
        jluros, what do you mean by "No matter what user/password combination I use, it rejects it (readynas, admin, or root)."?  If I understand what you're saying, you've already mounted the ReadyNAS Time Machine share *and* the virtual disk (on /Volumes/Time Machine Backups), so I don't see where the ReadyNAS user accounts come in after that.  At this point, /Volumes/Time Machine Backups is effectively a local disk on the Mac client, so the permissions on its HFS+ filesystem are *local* to the Mac, and independent of the ReadyNAS user accounts.  You should be able to use the root user on the Mac to do whatever you need to do.

        Ah, just occurred to me...  I totally missed that you said "browsed to... in Finder"!  When you then get prompted for a username/password, that is your local Mac asking for admin permission.  You need to authenticate using the same username/password that you normally use for admin rights on the Mac.

         

        BTW, you could avoid that stuff by using sudo in Terminal.  If you're not comfortable with that, I think Finder should work if you authenticate correctly.

NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology! 

Join Us!

ProSupport for Business

Comprehensive support plans for maximum network uptime and business peace of mind.

 

Learn More