sparsebundle – Unable to change permission on a mounted volume

I can not change the permissions on mounted sparseimage, I have tried the command like chflags, vsdbutil and others but nothing has happened.
enter the description of the image here

I tried to delete the access control list, but I return "unauthorized operation"
enter the description of the image here

I need to change the permissions because I have to put RSA keys, and ssh does not allow me to use keys if they have too open permissions.

sparsebundle – Check the backup of the time machine

After this problem, I restored the entire shared folder from my NAS version manager. However, perhaps because of the size of the image (more than 600 GB), the version manager confirms neither failure nor success. Since the restored image is almost the same size, I guess I can use it.

To check the image, I launched an fsck and it is successful. Then I started to use it normally and Time Machine does not seem to indicate that the image is corrupted.

However, I wonder if it is possible that some of the tapes are not recovered correctly and fsck does not recognize them. fsck_hfs is only responsible for analyzing metadata, not data, and time machine works primarily with metadata in terms of drift comparison.

It is true that fsck_hfs can scan the entire drive (-S). Through hdiutil, -verbose and -debug, it will display information about reading / writing tapes, but there is no documentation on how to read it, or fsck_hfs fails if a group is not find.

I need a way to check my back up machine backup.

mojave – Requirements for restoring a Time Machine backup from a sparsebundle?

I have a sparsebundle backup of Time Machine on an NTFS volume on a USB stick. When I wanted to restore from it, I had it connected and the volume was mounted read-only, but I could not mount sparsebundle and the migration wizard did not offer it as a source of restoration.

After copying the sparsebundle to a read-write HFS + volume (on a USB stick), the restore option was offered to me, which led to my question.

What are the requirements to be able to restore from a sparsebundle? Is the containing volume in writing or something else?


I do my backups on SMB, so I want a file system logged in Linux (I can not use HFS +) and I can restore using it as a USB key (so far not NTFS). I know paid drivers for NTFS under macOS, but I'm looking for a free solution for Mojave.

The ntfs-3g project seemed completely dead, judging by its website, and the installation / compilation instructions seemed missing and out of date (2015 bundles compared to the latest version in 2017).

macos – Mounting a sparsebundle file generates a blank ContainerToInvert file

I have a system backup locked in a .sparsebundle file on my desktop (it was extracted from the SSD drive of my broken laptop). When I try to ride the .sparsebundle file, it mounts properly as a disk image, but it contains only a blank text file (size 0 KB) titled ContainerToInvert. the .sparsebundle However, the file far exceeds 100 GB – the correct size of the backup. Any suggestions regarding this problem or how to proceed? Until now, I have tried to use the afps_invert command in a Unix shell to no avail …

security – MacOS: password-protected sparsebundle mount does not require a password

I have an encrypted and password protected sparsebundle that I mount and unmount from time to time from the terminal. I want the system to ask for the password every time I mount it, but for whatever reason, it always remembers.

Here is how I mount it: hdiutil attach ~ / path / to / my / package -mountpoint ~ / my / mount point

Here are some examples of attempts to disassemble it:

hdiutil detach -force ~ / path / to / my / bundle
hdiutil detach -force / Users / me / path / to / my / bundle
hdiutil eject -force ~ / path / to / my / bundle
diskutil eject ~ / path / to / my / bundle
diskutil unmounts the force ~ / path / to / my / package

(I've read here that hdiutil disassemble is not enough for the system to forget the password.)

However, no matter what I try, the system "usefully" uses the password every time.

The system forgets the password only when I use the eject button in the Finder.

In addition, my keychain does not contain any entries suggesting that the password has been cached. (At least, I can not find it, there is no kind password disk image.)

I even created a new sparsebundle, with a new name and a different password, but the problem persists.

What do I forget here? How can I make sure that the system always asks for the password each time I mount the sparsebundle?