My "NAS" is a USB hard drive connected to an Airport Extreme.
I can see it through the nettwork, and I can mount it, and add it to the list of disks used by Time Machine for backups.
However, when I try to back up to it through the network, I get an error message in the System Preferences>Time Machine that says "The backup disk image could not be created."
Using Terminal, ls -lO shows me the user immutable flag on a root level file named tmbootpicker.efi
I tried
sudo chflags -R nouchg DriveName
but the process has been running for longer than seems reasonable to me.
The target volume also has a TM backup on it that is not a disk image, created when it was attached to the source machine locally.
FWIW, the MacBook Pro was recently repaired by Apple, but still crashes at times, despite having undergone a "nuke and pave" re-installation of OS X, with re-installation of latest versions of non-Apple programs.
Should I reattach the drive as a local drive, and try to use the command line to kill the file
drwxrwxrwx@ 1 username staff - 264 Jan 10 13:18 Backups.backupdb
and the file cited above, and try again through the network?
I can see it through the nettwork, and I can mount it, and add it to the list of disks used by Time Machine for backups.
However, when I try to back up to it through the network, I get an error message in the System Preferences>Time Machine that says "The backup disk image could not be created."
Using Terminal, ls -lO shows me the user immutable flag on a root level file named tmbootpicker.efi
I tried
sudo chflags -R nouchg DriveName
but the process has been running for longer than seems reasonable to me.
The target volume also has a TM backup on it that is not a disk image, created when it was attached to the source machine locally.
FWIW, the MacBook Pro was recently repaired by Apple, but still crashes at times, despite having undergone a "nuke and pave" re-installation of OS X, with re-installation of latest versions of non-Apple programs.
Should I reattach the drive as a local drive, and try to use the command line to kill the file
drwxrwxrwx@ 1 username staff - 264 Jan 10 13:18 Backups.backupdb
and the file cited above, and try again through the network?