Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Auto disk mount without user login causing disk mount failure System
I had the OS X disk automount option enabled so that my external FireWire disks were mounted when no user was logged into the GUI. However, it created a problem of somesort in that none of my disk images would mount any more. I had set it by running the following command in the Terminal:
sudo defaults write /Library/Preferences/SystemConfiguration/\
autodiskmount AutomountDisksWithoutUserLogin -bool true
You should be able to prevent automount in the future by just changing true to false at the end of the above command. But you may also want to remove (after verifying its contents) the following file: /Library: Preferences: SystemConfiguration: autodiskmount.plist -- you'll need sudo to do so.

It's probably a problem with some of the recent updates with 10.3.8 or above, because I didn't have the problem before. Perhaps some conflict with SystemUI, or something else. Anyway, here's how to disable it if you're having issues...

[robg adds: We ran a hint on enabling this feature back in 2003; I haven't enabled it myself, so I can't confirm any issues, but this is how you'd disable it...]
    •    
  • Currently 2.80 / 5
  You rated: 4 / 5 (5 votes cast)
 
[20,335 views]  

Auto disk mount without user login causing disk mount failure | 4 comments | Create New Account
Click here to return to the 'Auto disk mount without user login causing disk mount failure' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Auto disk mount without user login causing disk mount failure
Authored by: arg on Mar 28, '05 12:02:59PM

Using the defaults command to enable disks staying mounted at logout never worked for me. There were a couple of variants on the plist file method in the original hint. Below is the one that worked for me. Other variants failed or gave me problems, but the below has been happily doing its job since 10.3.0 all the way up to the present.

(The followng pasted in a file called autodiskmount.plist in my /Library/Preferences/SystemConfiguration folder.)

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>AutomountDisksWithoutUserLogin</key>
<true/>
</dict>
</plist>



[ Reply to This | # ]
Auto disk mount without user login causing disk mount failure
Authored by: mrchucho on Mar 28, '05 05:50:29PM
I'm sure this is a stupid question, but is there some way to prevent removable drives from being mounted -- if not already mounted -- at login? I don't want the drives to which I back-up to be mounted at login or when users switch. I manually mount them prior to back-up.

[ Reply to This | # ]
Auto disk mount without user login causing disk mount failure
Authored by: murali1080 on Mar 28, '05 06:43:43PM

There is a way to dynamically mount drives only when needed, in mac os x. I have read it somewhere. Will post the info or link if I can I find it!



[ Reply to This | # ]
How to prevent drives from mounting at boot.
Authored by: alittleknowledge on Aug 09, '05 10:36:53AM
I know it's been a while since you posted your question, but I stumbled across it, and may have an answer for you. On my system, I've usually got around 6 partitions, all set up with the various configurations that I need to maintain at work (I admin several labs, ~15 classrooms and a ton of faculty computers at a university). And with that many partitions hanging around, and my Home directory on its own drive (and visible on the desktop), I needed to find a way to minimize the clutter. Enter fstab. Apple keeps threatening to pull support from it completely, but from what I can tell, it's worked since the first version of OS X came out, and still works fine for me under 10.4. To set up fstab, all you need to know is the UUID of your drive, which can be found in your System.log - look for diskarbitrationd entries near the beginning of the boot process. Here's a quick look at the relevant parts of my System.log:

diskarbitrationd[65]: disk1s3    hfs      9C8794A4-71F8-34B5-89A3-E71000ED263A capn crunch              /Volumes/capn crunch

localhost diskarbitrationd[65]: disk3s3    hfs      D90BED09-B267-3730-B9CE-D62A85AE4EC5 tonto               /
localhost diskarbitrationd[65]: disk3s4    hfs     7E4137B1-9CD8-3A9E-8AF7-4895D84CC355 eDrive
The UUID is the 32-char long string in each entry. I've seen other hints that detail how to go about creating a UUID for your volumes, but it's not necessary. One quick caveat: fstab doesn't fully work as advertised in the fstab man page - you can't (or at least I couldn't) specify an arbitrary mount point for your file systems. That sounded like a KILLER feature - I'm thinking, I've got my Home folder on its own drive, but if I could use fstab to map that drive's mount point to
/Users/justin 
, that would be pretty cool. No more messing with netinfo. Too bad it didn't work. to keep this from getting much longer, I'll just include a copy of my fstab file, which I generated myself according to the instructions laid out in the fstab man page. Oh- one last thing. The fstab file, if your system has one already, will be in /etc. If there isn't an fstab file there, just go ahead and create one (ie, 'sudo pico' and write one directly, create a plain text UTF-8 file and option-drag it into
 /etc
....) Enough already! Here's the file! In order to keep things straight for future changes, I commented in the volume names for all of my partitions. Also, you can mount the volumes using diskutil or Disk Utility.

# entries should be formatted as follows, I think:

# all fields are tab-separated.
# UUID=somelongstringoflotsofcharacters		mntpt	fstype	mntopts

# ipmortant - safe values for for the mount point are (I think)
# 'none'	'/'	or '/Volumes/<partition name>'
# The /Volumes/<something> entries have to match the partition names.

# eDrive (techtool pro)
UUID=6C452289-45AD-3993-87EA-0AC884970434	none	hfs	rw,noauto

# bigRAID:
UUID=828929DC-2C26-3AB2-B6BE-DE978CE97FC0	none	hfs	rw,noauto

# root drive
# UUID=D90BED09-B267-3730-B9CE-D62A85AE4EC5	/	hfs	rw,noauto

# SATA backup
UUID=7E4137B1-9CD8-3A9E-8AF7-4895D84CC355	none	hfs	rw,noauto
Hope that helps!

---
0==

[ Reply to This | # ]