10.1.5 missing home directory

XnetZero

Registered
:confused:

So I update to 10.1.5, reboot and log back in only to discover that my home directory is missing...

Well actually it's not.

The home directory of my staff user is located on a seperate partition from the system volume:

/Volumes/partition/Documents/Users/joe_cool

This worked just fine in 10.1.4, as I modified netinfo of the new location.

Now when I boot my partition has been renamed to 'partition 1', but the computer seems to think that partition still exists (where exactly I'm unsure). An ls of my /Volumes directory looks something like this:

partition partition 1 swap swap 1

If I do a df I get the following:

Filesystem 512-blocks Used Avail Capacity Mounted on
/dev/disk0s9 10484880 8329952 2154928 79% /
devfs 65 65 0 100% /dev
fdesc 2 2 0 100% /dev
<volfs> 1024 1024 0 100% /.vol
/dev/disk0s10 1048392 172704 875688 16% /Volumes/swap 1
/dev/disk0s11 144753552 7810736 136942816 5% /Volumes/partition 1
automount -fstab [255] 0 0 0 100% /Network/Servers
automount -static [255] 0 0 0 100% /automount

Now, what I've never seen in the df before is this:

<volfs> 1024 1024 0 100% /.vol

And I have never named a partition swap 1 or partition 1, they should be swap and partition respectively...

Does anybody have any idea why this has happened?

Thanks in advanced...
 
First a little run down on the issue:

After installing 10.1.5, two of my partitions were automounting with the incorrect volume labels. Both had the number one appended to the end of their names. An 'ls' of /Volumes would show:

cosmos cosmos 1 swap swap 1

The actual volumes with my data were 'cosmos 1' and 'swap 1'.
cosmos and swap were both bogus directories.

To correct the issue I deleted cosmos and swap. After a reboot, the volumes mounted with their correct names.

I am not sure why 'cosmos' and 'swap' were taking up real estate in /Volumes. I was under the impression that only mounted devices would appear within this directory. I have assumed until now that when a volume (local or remote) was unmounted the mount point was removed.

Does anybody have any ideas on this?

:rolleyes:
 
...for the insight. My best guess with cosmos is that netinfo may have created the directory as my staff user resides on that volume.

Thanks again...
 
Back
Top