Hal 0.5.13-3 breaks volume mounting

I -Syu'd today and hal got upgraded to 0.5.13-3 and I found that hal no longer wanted to mount my drives. PCManFM just gave me a long and weird error message. I built the 0.5.13-2 package, and it worked fine again.
Then I see:
upgpkg: hal 0.5.13-3
Disable ACL management
Disable consolekit support
Disable policykit suport
Switch to at_console rules instead of using policykit
Add some patched from fedora
revert ssb removal, new versions of networkmanager have fixes for this
A quite large change in the hal package. What is this at_console? I can see the benefit of moving away from the horrid PolicyKit. How to make at_console work well?

skipio wrote:
no problems here with slim and openbox. i just added 'exec ck-launch-session openbox-session' in my ~/.xinitrc, so '/var/run/console/my_username' is created and everything works as expected.
no need to "hack", i guess you can do the same with any login manager.
for console login:
after logging, 'ck-launch-session' will start a new consolekit instance, so automounting, etc should work there.
Adding ck-launch-session to my .xinitrc does not work for me. I.e.,
exec ck-launch-session openbox-session
For the record, I've tried rebooting as well as restarting dbus and hal.
Still results in the following error message:
Rejected send message, 1 matched rules; type="method_call", sender=":1.34" (uid=1000 pid=4159 comm="exo-mount) interface="org.freedesktop.Hal.Device.Volume" member="Mount" error name="(unset)" requested_reply=0 destination="org.freedesktop.Hal" (uid=0 pid=3519 comm="/usr/sbin/hald)).
Please advise. It's all well and good for a developer to lecture people not to "hack" temporary solutions, but if an upgrade of hal breaks mounting, then it would be nice to have a developer chime in here with the "correct" solution.
Last edited by madalu (2009-11-14 17:14:23)

Similar Messages

Rhythmbox breaks auto mounting.

For a few days I have struggeled with making gnome-volume-manager automount removable storage devices. Some times it woked and sometimes it did not. I had enabled hal and dbus I was sure gnome-volume-manager was running. Eventualy I even loggeg into Gnome as root and everything workes perfectly, so my system is configured correctly. So maybe it was a permission issue, was what first come to my mind, but eventualy it turned out to be Rhythmbox(Rb) who was the trubblemaker. Rb does not autostart as root, as it does on my regular user account, thats way it worked as root.
Now, after some more testing, the situation is this: Automounting works perfektly until i start rhythmbox, then it just stop woking. Even if i stops Rhythmbox, automounting still is broken, even a "pkill gnome-volume-manager && gnome-volume-manager" does not fix it, but logging out and inn again does fix it! No other programs breaks auto mounting!!
I have tried to recompile Rb without both the --with-ipod and --with-dbus flags, but it did not help? Otherwise I have a standard Arch-install.

This is my rc.conf, so if you don't see anything wrong with it I can file a bug!
# /etc/rc.conf - Main Configuration for Arch Linux
# Localization
# HARDWARECLOCK: set to "UTC" or "localtime"
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/unimaps
# USECOLOR: use ANSI color sequences in startup messages
HARDWARECLOCK="UTC"
TIMEZONE=Europe/Oslo
KEYMAP=no-latin1
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# Networking
HOSTNAME="arch"
# Module to load at boot-up (in this order)
# (prefix a module with a ! to disable it)
MODULES=(usblp fuse snd-bt-sco)
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# Note: to use DHCP, set your interface to be "dhcp" (eth0="dhcp")
lo="lo 127.0.0.1"
eth0="dhcp"
ra0="dhcp"
INTERFACES=(lo ra0)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network-profiles
#NET_PROFILES=(main)
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
DAEMONS=(syslog-ng hotplug sshd network netfs crond dbus portmap fam hal alsa cups uptimed sensors hcid)
# End of file

HT201372 I am trying to create a bootable USB drive for Yosemite and the terminal is telling me /Volumes/Untitled is not a valid volume mount point. HELP!!!

I erased the USB drive and partitioned it as directed in order to create a bootable drive. When I type in the sudo command in the terminal, it is telling me that /Volumes/Untitled is not a valid volume mount point. HELP!!!

FYI
my process just completed: here is what I see when it is done... (the first you saw in my earlier post. It took about 15-20 minutes.
To continue we need to erase the disk at /Volumes/Recovery.
If you wish to continue type (Y) then press return: y
Erasing Disk: 0%... 10%... 20%... 30%...100%...
Copying installer files to disk...
Copy complete.
Making disk bootable...
Copying boot files...
Copy complete.
Done.

How to make Launchd/LaunchAgents wait for volume mount?

I've been trying off and on for months to resolve a problem I have starting up named on my OS X 10.5 Mac Mini, which acts as a home server. Actually, I've been trying since 10.4 came out.
All my configuration files are located on a volume located on an external pair of RAIDed drives. At system startup the volume mounts automatically, and I have soft links pointed to the remote directories, in this case /usr/local/etc/. The problem is that system startup doesn't wait for this volume to come online before starting to run items in LaunchAgents. Therefore, using the StartAtLoad option, I'll see messages in the system log from bind saying that it tried to start, but the config file /usr/local/etc/named/named.conf wasn't available, so it died.
I've experimented with WatchPaths - that doesn't seem to work reliably because by the time it gets going, the path is available; since it doesn't actually check availability, but only status change, it doesn't work. (If I log in and touch the file afterwards, named starts right up.)
I can figure out some hack to run a script and check the status regularly and launch/re-launch, but I'd rather figure out how to do this the "right" way with launchd. Current (still broken) script is below. Thanks for suggestions!
KeS
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Label</key>
<string>org.bind</string>
<key>ProgramArguments</key>
<array>
<string>/usr/sbin/named</string>
<string>-f</string>
<string>-c</string>
<string>/usr/local/etc/named/named.conf</string>
</array>
<key>WatchPaths</key>
<array>
<string>/usr/local/etc/named/named.conf</string>
</array>
<key>Sockets</key>
<dict>
<key>Listeners</key>
<dict>
<key>SockServiceName</key>
<string>domain</string>
</dict>
</dict>
</dict>
</plist>

Umm, ok. Are you suggesting that there's more likelihood of getting an answer there, or that it's in the wrong place here? I hate to bother developers with a user question. I'm not asking for new features.
Tx.
KeS

Bigtime Problems With Volume Mounts

Dear kind, helpful, charitable, community of Apple users,
I'm been spinning my wheels on this for a week now and I'm totally stuck. I'm sufficiently desperate that I thought about offering a cash bounty via PayPal. (But I can't figure out an equitable way to do that so anyone who can help with this will win a virtual $1 "admin buck" and my undying gratitude.)
Here's what I'm trying to do: I have a Mac Mini running 10.6 server. I also have a 1T external USB hard drive. I want to permanently mount this external hard drive at /Users, so all user accounts will live on the external drive. I've been a sysadmin for 20 years, dabbling in Unix the whole time, and this seems to me like it should be a no-brainer.
Here's what I've tried: I added this line to /etc/fstab using vifs:
UUID=BDFE6D09-7483-3479-B37F-0BE15F9CBFBB /Users hfs rw
I've also tried a couple of variations, using different options (like LABEL and the volume label instead of the UUID, as well as explicit numeric values for fs_freq and fs_passno in the fifth and sixth fields. Regardless, when I run 'mount -av' I get:
GetMasterBlock: Error 2 opening UUID=BDFE6D09-7483-3479-B37F-0BE15F9CBFBB
GetMasterBlock: Error 2 opening UUID=BDFE6D09-7483-3479-B37F-0BE15F9CBFBB
mount_hfs: No such file or directory
mount: exec /System/Library/Filesystems/url.fs/Contents/Resources/mount_url for
/Network/Servers: No such file or directory
This is nonsense because the drive itself is formatted and partitioned and attached and on and visible in Disk Utility (though not mounted), and the /Users directory exists on the root. In fact, if I execute the following:
mount_hfs /dev/disk2s3 /Users
The volume mounts perfectly! Everything is peachy. Except, as soon as I log off twice, the volume unmounts for no explicable reason. Rebooting the system never automounts the volume like it's supposed to. Anytime automount (or mount, for that matter) fails, this is posted in the console error log:
10/9/09 6:38:59 PM com.apple.autofsd[91] automount: Mount for UUID=BDFE6D09-7483-3479-B37F-0BE15F9CBFBB has no path for the directory to mount
Oh, and yes, autodiskmount.plist is correct and exists in /Library/Preferences/SystemConfiguration.
So my questions are these:
1. Why does the darn think keep unmounting whenever someone logs off the server?
2. Why does mount -a fail, while mount_hfs works fine
3. What the heck am I supposed to do to get this thing to mount and stay mounted at /Users?
Thanks for taking the time to ever read this!

Hi Strontium90,
Thanks for the reply!
That is because Firewire and USB drives do not mount until the Finder is active. This is the default behavior, meaning that server, booting to the login screen, will not mount "transitory bus" devices. However, this can be overcome. You need to run this command to alter the default behavior (note this is all one line):
sudo defaults write /Library/Preferences/SystemConfiguration/autodiskmount AutomountDisksWithoutUserLogin -bool YES
Well, unfortunately, that's what I meant in my original post when I said that, yes, the file /Library/Preferences/SystemConfiguration/autodiskmount.plist already exists. I have already executed the command you indicated, which creates the .plist file. And while this does seem to mount the drive right after a reboot, as I stated, the act of logging on and then off causes the drive to be unmounted. In fact, the as far as I can tell, no matter how the drive gets mounted, it is automatically unmounted at every logoff.
But unless I am misreading what you are trying to do, that will allow the drive to mount automatically during startup and be available to the system without a user session.
And it does... but it doesn't stay mounted. And it doesn't explain why mount -a fails with the errors I listed.
As for a remap of the Users folder... If this is for network homes, then simply define the share point and define it to go to your external drive.
It is indeed for network homes. Unfortunately, all of the defaults in server when creating accounts want to use /Users. I know I can change these defaults, but my experience with Apple is that successive operating system upgrades never respect or protect changes to defaults. Since all of the admin tools (and applications, and etc.) want to use /Users, I want to simply mount a larger partition at that point.
Which, unfortunately, brings me back to my original three questions...

Windows machine on local network can see all volumes mounted on my MBP

I have a Macbook Pro running 10.6.4 with 4 volumes mounted (Macintosh HD, Scratch Drive, Files, & Media). On this same network I have a Windows 7 machine. I just noticed today that in the Windows File Explorer I can see all 4 of the volumes that I have mounted on my Mac. Not only can I see the volumes, I can drill down into folders on my Mac, open files, and even make changes to and save those files.
I've checked all the Sharing options on my Mac and everything is turned off and my firewall is turned on. I know that in the past I wasn't able to see these volumes from the Windows machine. I recently upgraded to 10.6.4 but don't know if that has anything to do with this as I rarely do anything with that Windows machine so I'm not really sure when this started.
Any advice would be greatly appreciated.
Cheers!

Check this
Go to system preferences--------->
Sharing -------------->
File Sharing ---------------> ( you said this is not selected )
then
go to the options ------------->
and See if SMB sharing on or not .
this is the only place which is sharing with windows .......
hope it helps
 csp 10.5/10.6

I get /Volumes/Untitled is not a valid volume mount point when I try to use teminal to make bootable usb stick

I get /Volumes/Untitled is not a valid volume mount point when I try to use teminal to make bootable usb stick. Why and what do I do to fix this. Very frustrating. Thanks for any help. Btw, I went through all the steps properly more than once to fomat and partition etc.
John

FYI
my process just completed: here is what I see when it is done... (the first you saw in my earlier post. It took about 15-20 minutes.
To continue we need to erase the disk at /Volumes/Recovery.
If you wish to continue type (Y) then press return: y
Erasing Disk: 0%... 10%... 20%... 30%...100%...
Copying installer files to disk...
Copy complete.
Making disk bootable...
Copying boot files...
Copy complete.
Done.

XSAN volumes mount RW, but ROOT is locked out.

I am mounting several clients to the XSAN, and the volumes mount as RW through the admin, and the get info shows them as RW mounts, but additional info says 'you can only read' and there is a small lock illustration on the drive icon after mounting. Using terminal ADMIN, I can not write to the root of the drive, but previously created folders work as RW. Using one of the volumes as the FCP scratch disk, and it will not work, but use the folder inside the volume works. Have tried resetting permissions, restarting the volume(s) and the controller. Nothing has helped. I did have one client with possibly corrupted data (bad HDD) that was crashing at the time of this beginning. Any thought will be appriciated, as I have not been able to find anything on it yet.

I would say that read only access at the root level of your XSan volume would be preferable, at least it is in the environment that we are working. This prevents anyone but an administrator from placing folders at the root level, meaning that you can control affinity assignment, whereas any local user that would create a folder on the root level would have no affinity assignment. In our environment, where we're working with multiple shows at a time and 52 TB of total storage, affinity assignments become absolutely crucial for file management.

Hal 0.5.14-1 does not mount some usb drives correctly

Hi folks
When I try to mount a USB hard disk (with KDE 4.3.4), it tries to mount it at some wrong path used by another USB hard disk. Or I have to mount it as root, or even as root it still doesn't work right... pfff I'm really disappointed by this showstopper...
For example, I own a LaCie hard disk (/media/disk), a Iomega one (/media/IOMEGA) and a LaCie mobile disk (no power cable, /media/MobileDisk):
- When I try to mount the Iomega one, it works fine, as normal user;
- When I try to mount the LaCie one, it fails, independently of the fact that the Iomega drive is mounted or not, with the following message:
Unable to run the command specified. The file or folder file:///media/IOMEGA does not exist.
Looks like it wants to mount the LaCie one where the Iomega one is/should be mounted...
- When I connect the LaCie hard disk, the directory /media/MobileDisk
is created, instead of /media/disk
, and when as root I try to manually mount the hard disk, it says:
ntfs-3g: Failed to access volume '/dev/sdb1': No such file or directory
Maybe there's some erroneous entry in some cache or data used by hal/dbus? I don't know how they work and how to activate their logging systems and then where to find the logs...
Maybe there's a way to simply completely wipe out hal/dbus/consolekit/policykit/... configuration data without having to reinstall the complete system?
I have:
hal 0.5.14-1
dbus-core 1.2.16-1
dbus 1.2.16-1
dbus-glib 0.82-2
dbus-python 0.83.0-2
I start KDM using /etc/inittab, as described in the wiki. I've put "/usr/sbin/console-kit-daemon" in /etc/rc.local and have modified /etc/inittab so that it starts kdm with: "x:5:respawn:/usr/bin/ck-launch-session /usr/bin/kdm -nodaemon"!
Is this the right setup, equivalent to the one with xinitrc?
The same setup works fine on my laptop.
I've got the impression that hal/dbus/... confounds my drives and does not know where to mount them...
Downgrading to hal 0.5.13-idontrememberwhatcifer does not solve the issue, the system is kept up to date with "pacman -Syu" about once a day and it still doesn't work...
Some clue?
Thanks and happy new year

OK something happened that I can't explain...
I just controlled about all files related to hal/dbus/mounting etc and, I don't know why, all devices I've mounted had a corresponding line in fstab... really weird.
I juste deleted those lines, and, well, mounting seems to work again
So this issue is solved
And finally Arch Linux is again my favorite distro
Last edited by yannick555 (2010-01-03 14:37:55)

Need help getting servername from afp volume mount

Hello I am trying to write a script to take the path of a selected file or folder, put it on the clipboard, and make it a PC friendly link/path to email to pc users in my company. We are sharing files off of 3 servers.
My problem is not with the scripting, but with the fact that all mounted volumes from these servers show up only from their mountpoint in the Volumes folder, i.e. /Volumes/DeptShare/Inbox/ and the like. In the "Get Info" Window I can see the servername (Server: afp://servername/pathtofile/etc) but I cannot find any clean way to call that from a script, to tie a mountpoint (Volumes/DeptShare) to the server it's on, if the user has volumes from more than one server mounted...
So my script can't replace "Volumes" with the proper servername.
Hope Im being clear, happy to elaborate, much obliged for any help.

Hi Bob, thank you so much for the quick response.
Unfortunately system_profiler SPNetworkVolumeDataType isn't revealing a server name for me. I think part of the problem is that it is afp; smb does reveal the server name there. Similarly, when I type "mount" in terminal, the afp server/login for the volume is just listed as a long character string starting with afp_ instead of a username@servername like with smb. With the SPNetworkVolumeDataType all I'm seeing re: server info is this: (I think the first part is just bonjour looking at our domain, I actually can't browse any servers through that. But I included it anyways in case)
Servers:
Type: autofs
Mount Point: /Network/Servers
Mounted From: map -fstab
Automounted: Yes
MyShareName:
Type: afpfs
Mount Point: /Volumes/MyShareName
Automounted: No
Another way I was trying to do this was to try and somehow "ping" a path to filename on each server, to see if the file/path could be checked or return an error and the script could know which server it was on. But I can't figure out the right language to do that either. I can do it like this in terminal:
\[-a /Volumes/path/file\]
but not like this:
\[-a /servername/path/file\]
or this:
\[-a afp://servername/path/file\]
so I still don't have the server name tied to the path.
The only other thing I can think of is having the script check the mountpoint name against a list of share names on each server, but that's a little heavier than I was hoping this would be. Plus it drives me nuts that the "Get Info" window can see the servername I can't call it easily somewhere!!
Message was edited by: Mr hotdogz

10.4.11 breaks .dmg mounting - now I get fsck errors.

I am having problems. About 75% of my .dmg files give me errors.
Many of these .dmg files have been working flawlessly on three computers since the 10.3 days... The others were created more recently (including two which were created using 10.4.11).
But on about 75% of my .dmg files I get this error when I try to open them:
"The disk image you are opening may be damaged and could damage your system. Are you sure you want to open this disk image?" and it has two options, "Open" and "Don't Open".
If I chose "Open" it mounts just fine and works just like it used to before 10.4.11. But I get this in my console:
"/sbin/fsck_hfs(/dev/disk2s2) failure for /Users/myUser/Desktop/imac/DiskImages/myDiskImage.dmg.
Dec 31 10:17:52 myComputerName diskimages-helper[1544]: user is overriding fsck failure for myDiskImage.dmg."
If I chose "Don't Open" I get a window that says "Warning. The following disk images failed to mount. Image: myDiskImage.dmg Reason: no mountable file systems" and it presents me with an "OK" button, and I get the same fsck failure message in my console.
This only happens with 10.4.11 and it is happening on two PPC computers and one Intel computer.
This is happening with all sorts of .dmg files, like I mentioned - some were even CREATED WITH 10.4.11!!!
Now - this all works OK if you just need to mount a disk interactively because you can just click "Open" and it works fine. But it completely breaks any scripts I have that mount images automatically (non interactively).
So I am quite frustrated about this...
10.4.11 should be quite mature considering it is the 11th update. I don't see how they could introduce problems like this in such a late update...

Hi John,
I've seen a few with the same symptom, but never the option to Open or Not!
I believe it's not so much a bug in 10.4.11 as it is with not doing Permission fixes before & after any update/upgrade... you end up with components from different versions and incompatabilities arise.
Use Disk Utility to Repair Permissions, (never hurts to verify the HD first), reboot & try it again, if it doesn't work, then try reapplying the big Combo Updates...
The combo update for PowerPC-based Macs...
http://www.apple.com/support/downloads/macosx10411comboupdateppc.html
The combo update for Intel-based Macs...
http://www.apple.com/support/downloads/macosx10411comboupdateintel.html
Repair Permissions afterwards, reboot.
If that doesn't work, looks like an Archive & Install with Permission Repairs along the way.

Shortcut to new server volume mounts old server

I have recently transferred all files from a Windows NT Server and a Windows 2000 Server to an OSX Tiger Server. I duplicated the files to the new server using Retrospect but have left copies on the old server in case anything was missed.
On my four OSX Panther G4s, I have mounted the new server and created shortcuts (aliases) to the new volumes. Three of them work fine. On the fourth G4, however, the aliases to the new server mount the volumes on the old server! I have deleted all the aliases and recreated them to no avail. I have deleted the aliases to the old server entirely and all is well until it becomes necessary to mount the old server. Even if the old server is mounted manually, the next time the aliases to the new server are used, they will mount the old server.
All four G4s access the servers via AFP because we still have OS9 workstations which need to access the same files.
Any suggestions?
PowerMac G4 Mac OS X (10.4.4) Server

Hi There!!!!
In Exchange 2010, clients do not connect directly to the mailbox role, they go through the
CAS role, so it sounds like you need to set the RPCClientAccessServer to point to the new Exchange 2010 server.
Do this via PowerShell :
GET-MAILBOXDATA | SET-MAILBOXDATABASE -RPCCLIENTACCESSSERVER <FQDN OF NEW CAS SERVER>
But as you have 160 mailboxes to migrate , which would be quite time consuming and needs lots
of efforts, so rather than opting manual way for migration I would refer you to do this using any professional Migration Software like Stellar Mailbox Extractor for Exchange Server, which can perform the Migration of 160 mailboxes in quick time.

Make a volume mount read-only

Rather than dig for my Mac OS X Server DVD, I find it easier to clone the disc onto a small partition on a hard drive.
However, the volume always mounts read-write, and I always get warnings about low disk space because of it. (I made the partition as small as possible.) Plus, I don't want to have anything mess with my Mac OS X Server "DVD".
I noticed that Mac OS X doesn't use fstab for mounting volumes… is there a way to make a disc mount read-only all of the time? (chmod -R a-w * doesn't cut it for me.)

I don't mean having it mount read-only when booting from it. I mean, while the server is running normally (not booted from the "disc").
For peace of mind, I'd like to have my "disc" always be read-only, just to make sure that it isn't modified unless I explicitly allow it.
On Linux, I could add "ro" to the mount options. Since Mac OS X doesn't use fstab, is there some plist that determines how volumes are mounted? I'd rather not edit the /etc/rc.* files unless absolutely necessary.

Disk volume mounts displaying generic icon

I've been having a regular problem with a Drobo disk system, which becomes inaccessible periodically.
When I remount the device using
diskutil mount Drobo
... the volume reappears, but instead of the usual icon:
I get the generic icon:
Why is this, and is it fixable without physically disconnecting the Drobo's USB cable, and reconnecting?

Hello Stacie-P8
First welcome to the discussions area.
There are a few things to try before erasing the HD. That would be my last step.
I would try trashing the keyboard preferences. Open the HD go into the system folder, then to the library, then to preference panes. There you will find the prefs for the keyboard. Drag to trash and then see if that helps. The computer will generate new prefs.
Next I would try to borrow a keyboard and see if the problem occurs. It could be a short in the keyboard or a broken wire if it isn't an optical keyboard.
My feeling is that it is related to the keyboard and not the HD.....Jim

Unable to prevent Time Machine backing up volume mounted from sparsebundle

I have a password-protected sparsebundle that contains my financial files, private data, etc, which I mount as a volume at startup. It's about 8GB. If I'm going to be away from my computer for a bit, I'll unmount the volume as an extra security measure.
I don't need or want Time Machine to back up the files INSIDE the volume, just the sparsebundle itself. If I needed to access a backup of a file inside the volume, I'd rather just pull up an earlier version of the sparsebundle, mount it, and find the file in there.
However, I've recently discovered that I can't exclude the mounted volume from Time Machine backups in the usual way - the volume name is greyed out when I go through the System Preferences/Time Machine pane, and won't let me select it to be excluded from backup.
So what's happening is that TM is backing up the contents of the volume, which is showing up as folders on the TM backup drive. Inside these folders is the complete listing (and actual data) of all the files in my secured volume!
Even if I UNmount the volume from my system, it's still possible to access the data via Time Machine.app (and via Finder, on the TM backup disk).
So, essentially, even though I've password protected the sparsebundle CONTAINING the data, all a person needs to get the data is to have access to my user account on my Mac, and they can get the data via the above methods.
Is there any way to allow TM to back up the sparsebundle itself, but not the listing of the contents (and data) of the mounted image?
It seems odd that I can exclude the volume contents from being indexed by Spotlight, but can't exclude them from being specifically backed up by Time Machine.
Thanks in advance for any assistance!

I have exactly the same issue. I cannot exclude the content of mounted disk images from my backup using the GUI (strangely on my other computer the content is not backuped).
I have manually edited with a text editor the preference file (Library/Preferences/com.apple.TimeMachine.plist) today (I am using 10.6.3) and added in the SkipPaths section the mounting point of the disk image (typically /Volumes/NameofDisk ). So far so good. The corresponding folder appears in the backup but is empty.
Use at your own risk

Hal 0.5.13-3 breaks volume mounting

Similar Messages

Maybe you are looking for