Mount points in fstab

I'm sure this isn't limited to Mavericks, but that is what I'm currently working with.
I want to mount a hard disk (volume) on a directory of my choosing. AFAIK this can be done in fstab and anything thus specified is ignored by OSX's other rmounting processes, so it should work.
The problem I'm having is that the mount point has a space in its name and this CANNOT be changed as something else relies on that exact name. Of course by default, a space in the mount point in fstab will cause problems as it will be seen as a separator, so I quoted the entire path string. Double or single quotes both still cause problems. I tried a back slash in front of the space, but that's no better.
I have since read in mumerous places that there is this problem, but it can be avoided and the solution I have seen is to instead use the octal \040. Aha I thought, this looks promising, but no, there is still a problem with the mount point name.
Anyone any thoughts on this, why \040 doesn't work and/or any other solutions?

Read the guides from Oracle and Linux. I've downloaded a couple of guides (it's not easy to find them). Start with Installation and Admin guides. They will refer to other guides where you can read more about OFA. Read the Linux guides/man pages about mount, fstab, fdisk and partitioning. BTW, I only made 2 partitions for Oracle. One for the system, and one for the data (I think it's enough, because on my system there will be only one database).

Similar Messages

Custom mount point in fstab

Hello,
I am setting up a nas. I have configured a partition scheme that seems suitable for me. I have a problem though, I can not seem to mount a partiton to a custom mount point.
The system is up to date, I just installed it last night. Here is my fstab:
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
tmpfs /tmp tmpfs nodev,nosuid 0 0
UUID=4e373785-4fc9-4b97-aadc-adcbc523bbac /boot ext2 defaults 0 1
UUID=50c83b59-b938-4945-9578-39ab7c40d93b / ext4 defaults 0 1
UUID=8e87d854-a344-4a3c-950f-9831c0811ea2 /data ext4 defaults 0 1
UUID=972cce0c-3c35-4d8a-a0d6-719794bc2766 /tm ext4 defaults 0 1
UUID=d6f940d8-ce03-45c3-bfa9-b7dd83cebbb9 /var reiserfs defaults 0 1
UUID=f01dc9e8-a182-4b89-8043-f6f73690ad6c swap swap defaults 0 0
I want /tm for time machine and /data for samba sharing. If I change /data to /home and /tm to /tmp, everything mounts fine. Is there some reason why I shouldn't be able to mount a partition to a custom mount point? I did this two weeks ago on another box that I set up as a test...
Also, if I run fdisk -l, it tells me that some of my partitions do not start on physical sector boundaries. Is that casue for alarm? I created the partitions with cfdisk and nothing seemed odd when I was doing it...??
[root@nas ~]# fdisk -l
Disk /dev/sda: 750.2 GB, 750156374016 bytes
255 heads, 63 sectors/track, 91201 cylinders, total 1465149168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sda1 * 63 192779 96358+ 83 Linux
Partition 1 does not start on physical sector boundary.
/dev/sda2 192780 1465149167 732478194 5 Extended
Partition 2 does not start on physical sector boundary.
/dev/sda5 192843 5076539 2441848+ 83 Linux
Partition 5 does not start on physical sector boundary.
/dev/sda6 5076603 6056504 489951 82 Linux swap / Solaris
Partition 6 does not start on physical sector boundary.
/dev/sda7 6056568 15824024 4883728+ 83 Linux
/dev/sda8 15824088 1090042379 537109146 83 Linux
/dev/sda9 1090042443 1465149167 187553362+ 83 Linux
Partition 9 does not start on physical sector boundary.
Any insight?

bnb2235 wrote:
Also, if I run fdisk -l, it tells me that some of my partitions do not start on physical sector boundaries. Is that casue for alarm? I created the partitions with cfdisk and nothing seemed odd when I was doing it...??
[root@nas ~]# fdisk -l
Disk /dev/sda: 750.2 GB, 750156374016 bytes
255 heads, 63 sectors/track, 91201 cylinders, total 1465149168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sda1 * 63 192779 96358+ 83 Linux
Partition 1 does not start on physical sector boundary.
/dev/sda2 192780 1465149167 732478194 5 Extended
Partition 2 does not start on physical sector boundary.
/dev/sda5 192843 5076539 2441848+ 83 Linux
Partition 5 does not start on physical sector boundary.
/dev/sda6 5076603 6056504 489951 82 Linux swap / Solaris
Partition 6 does not start on physical sector boundary.
/dev/sda7 6056568 15824024 4883728+ 83 Linux
/dev/sda8 15824088 1090042379 537109146 83 Linux
/dev/sda9 1090042443 1465149167 187553362+ 83 Linux
Partition 9 does not start on physical sector boundary.
AFAIK, if you don't align them it will cause performance issues. Check this site: http://johannes-bauer.com/linux/wdc/?menuid=3

[Solved] External Hard Drive mount point in fstab crashes launch

Hi there,
I have an external hard drive that I'd like to automount when I plug it in. Sometimes it seems to work, but other times I have to manually mount it. In order to make this a little easier, I copied the mounting info into my fstab file so that I could just run:
mount /dir/to/mount
However, now I can't actually boot up my machine unless the external drive is plugged in. I get some error from systemctrl saying one of the drives couldn't be loaded.
An obvious work around would be to write a one line script that mounts the drive for me, however, I'd like to learn how to do this correctly. I think the rules have changed a bit with systemd, as I didn't have this problem a few years ago.
Thanks for the help!
Last edited by B-80 (2015-05-17 08:14:08)

B-80 wrote:
Head_on_a_Stick wrote:
Add "nofail" to the options section.
EDIT: ...in /etc/fstab
Thanks for the answer, that fixed it.
You're welcome but I think Mr.Elendig's post gives the actual solution (my proposal is just a workaround -- using fstab for a filesystem that is not permanently attached is sub-optimal)

Unable to open and save across mount point

Why do these forums appear so neglected?
Here's is my on-going question/problem:
General input/output error while accessing /home/MyDir/mountedDir/SomeDire/TheFileName
I experience a "feature" wherein I cannot open and save documents across an NFS mount point from a Linux client.
This is an error rcv'd on Linux, GNOME 2.8.*, 2.6.10-gentoo-r6
The mount is accomplished via an entry in the fstab as shown:
server-hostname:/export/mydir /home/mydir/mountdir nfs tcp,user,rw,rsize=32768 0 0
server-hostname is a Solaris OS.

Sounds like you are missing some of the required plugins - possibly an updater failed, or someone moved/deleted the wrong directory.
Yes, you'll need to reinstall to restore the missing plugins.

[SOLVED] Mount Points In Arch Linux

When I performed my initial testing install of Arch Linux today, and I was setting up mount points after I finished partitioning with Cfdisk, I was surprised to see that one of the precanned mount points in the Installer was /etc. On OpenBSD, we were warned against having /etc on its own partition, probably because so much important stuff lives there (like the fstab). I was also surprised to see /var wasn't in the precanned list.
Anyway, my question is, can you really have /etc on it's own partition? And does the exclusion of /var indicate a problem with it being on its own partition?
Last edited by NerveJessen (2010-04-02 12:50:38)

NerveJessen wrote:
It almost sounds like /var was accidently replaced by /etc.
EDIT: I'll look into the bug reporting procedures.
http://bugs.archlinux.org/
There is the FLySpray link, and there is a button at the top right of your screen as well.
Post back within this thread with your bug report, so other users may vote for the task once it has been assigned to a developer.
Welcome to Arch!

Mount point /proc/bus/usb does not exist

Does anybody know why this mount point would not be there? There is indeed a directory at that location...

hi,
kleptophobiac wrote:Does anybody know why this mount point would not be there? There is indeed a directory at that location...
sarah31 wrote:perhaps it is the syntax in your fstab?
Nope, it's a miracle, concerning the scsi kernel only, AFAIK. Some devs have
rebuilt with some module variations but no clue so far where it does come
from.
It goes like that:
usbcore loads usbfs (when it shouldn't), at a time when proc is not mounted.
usbfs tries to create the dir and throws that error. Later on boot process
hotplug corrects that. So it's a kind of annoyance, but it does feel
uncomfortable as long as no one where it does come from :-/
-neri

Firewire mount points

Ladies and Gentlemen:
Ii have a difficult question to answer:
I have 2 daisy-chained Firewire LaCie Drives
1. Time Machine
2. for the User directory
The 2. drive is sometimes mounted on "/Volumes/Users" or "/Volumes Users 1" which causes problems accessing the "Users" directory and initiates a fallback to the harddrive.
I do not know why this happens. And I do not know how to prevent it.
Does anyone knows the reason for this behavior (obviously the "User 1" is created because a "User" mount point already exists…)
When the "Time Machine" is switched of the mount point stays the same. But when it is on it changes…
My temporarily solution now is to connect the "Time MAchine" with a FW400 cable. But thats not the desired final solution…
Any solutions available?
Thank you very much.
Kind regards
Dieter Zakel MD MA

Well, I went ahead and created the file fstab in /etc. Using df after a reboot showed that the volume was mounted at the pspecified place. So, the fstab file work. I used the LABEL= construct so as not to have to rely on the order the firewire devices were plugged in.
However, the volumes stall all show up on the desktop. I conclude that the volume list is not generated from the /Volumes directory. So ... still not solved.

Fixed mount points for USB disks via HAL

I've been trying to figure this out on my own but I've been able to achieve my goal.
I want to setup my system so that it auto-mounts a specific hard drive and makes its contents available at a specific file system location.
I'd love to do that by identifying my hard drives by UUID or ID and assigning each one a different mount point.
I've tried the approach described in the ArchWiki:
File: /etc/hal/fdi/policy/20-$device_name.fdi
<?xml version="1.0" encoding="UTF-8"?>
<deviceinfo version="0.2">
<device>
<match key="volume.uuid" string="$device_uuid">
<merge key="volume.label" type="string">$device_name</merge>
</match>
</device>
</deviceinfo>
http://wiki.archlinux.org/index.php/HAL#About_volumes_mount_points
and this one:
<device>
<match key="info.udi" string="/org/freedesktop/Hal/devices/volume_uuid_E265_5E6A">
<merge key="volume.policy.desired_mount_point" type="string">ipod</merge>
<merge key="volume.policy.mount_option.iocharset=iso8859-15" type="bool">true</merge>
<merge key="volume.policy.mount_option.sync" type="bool">true</merge>
</match>
</device>
http://www.mythic-beasts.com/~mark/random/hal/
I restart HAL each time I change the configuration of the 20-$device_name.fdi or preferences.fdi (the second code example). Nothing at all can be found in /var/log/messages. It just silently refuses to mount the devices.
It works okay without these configurations and HAL auto-mount all these hard drives but only if I do not mess with the configs in /etc/hal/fdi/policy.
Can someone please explain what could be wrong here?

Dehir wrote:Im actually having similar difficulties. Have created etc/hal/fdi/policy/20-$device_name.fdi names for each device. But when im trying mount them from pcmanfm they get mounted every single time by random order, which is not that i want. Id prefer hal mounting over fstab but still want them to be mounted with specific names.
Yeah, that's the whole point - I want to have it done automatically with only one condition - fixed mount point names.

Udev mount point

Hi,
I'm brand new to Arch from Gentoo so please take it easy. I'm trying to set a fixed mount point for my external hard drive (with my music on it) using udev. (as it doesn't make sense to put an external drive in fstab)
I've copied across my old rule from my gentoo install on the same machine:
/etc/udev/rules.d/10-local.rules
SUBSYSTEMS=="usb", ATTRS{serial}=="2HBEQTN2 ", KERNEL=="sd?", SYMLINK+="external", GROUP="storage"
SUBSYSTEMS=="usb", ATTRS{serial}=="2HBEQTN2 ", KERNEL=="sd?1", SYMLINK+="external", GROUP="storage"
But for some reason it doesn't seem to have any effect on my new Arch system (I have rebooted so shouldn't be an issue with restarting udev).
Since udev makes me want to cry does anyone have any ideas?

Here's my output of $udevadm info -a -p $(udevadm info -q path -n /dev/sdb)
Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.
looking at device '/devices/pci0000:00/0000:00:02.1/usb1/1-1/1-1:1.0/host6/target6:0:0/6:0:0:0/block/sdb':
KERNEL=="sdb"
SUBSYSTEM=="block"
DRIVER==""
ATTR{range}=="16"
ATTR{ext_range}=="256"
ATTR{removable}=="0"
ATTR{ro}=="0"
ATTR{size}=="976773168"
ATTR{alignment_offset}=="0"
ATTR{discard_alignment}=="0"
ATTR{capability}=="52"
ATTR{stat}==" 153 91 1362 25060 8 0 8 23 0 25030 25083"
ATTR{inflight}==" 0 0"
looking at parent device '/devices/pci0000:00/0000:00:02.1/usb1/1-1/1-1:1.0/host6/target6:0:0/6:0:0:0':
KERNELS=="6:0:0:0"
SUBSYSTEMS=="scsi"
DRIVERS=="sd"
ATTRS{device_blocked}=="0"
ATTRS{type}=="0"
ATTRS{scsi_level}=="3"
ATTRS{vendor}=="Maxtor "
ATTRS{model}=="Basics Desktop "
ATTRS{rev}=="0122"
ATTRS{state}=="running"
ATTRS{timeout}=="30"
ATTRS{iocounterbits}=="32"
ATTRS{iorequest_cnt}=="0xcd"
ATTRS{iodone_cnt}=="0xcc"
ATTRS{ioerr_cnt}=="0x1a"
ATTRS{modalias}=="scsi:t-0x00"
ATTRS{evt_media_change}=="0"
ATTRS{queue_depth}=="1"
ATTRS{queue_type}=="none"
ATTRS{max_sectors}=="240"
looking at parent device '/devices/pci0000:00/0000:00:02.1/usb1/1-1/1-1:1.0/host6/target6:0:0':
KERNELS=="target6:0:0"
SUBSYSTEMS=="scsi"
DRIVERS==""
looking at parent device '/devices/pci0000:00/0000:00:02.1/usb1/1-1/1-1:1.0/host6':
KERNELS=="host6"
SUBSYSTEMS=="scsi"
DRIVERS==""
looking at parent device '/devices/pci0000:00/0000:00:02.1/usb1/1-1/1-1:1.0':
KERNELS=="1-1:1.0"
SUBSYSTEMS=="usb"
DRIVERS=="usb-storage"
ATTRS{bInterfaceNumber}=="00"
ATTRS{bAlternateSetting}==" 0"
ATTRS{bNumEndpoints}=="02"
ATTRS{bInterfaceClass}=="08"
ATTRS{bInterfaceSubClass}=="06"
ATTRS{bInterfaceProtocol}=="50"
ATTRS{modalias}=="usb:v0D49p7410d0122dc00dsc00dp00ic08isc06ip50"
ATTRS{supports_autosuspend}=="0"
looking at parent device '/devices/pci0000:00/0000:00:02.1/usb1/1-1':
KERNELS=="1-1"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{configuration}==""
ATTRS{bNumInterfaces}==" 1"
ATTRS{bConfigurationValue}=="1"
ATTRS{bmAttributes}=="c0"
ATTRS{bMaxPower}==" 2mA"
ATTRS{urbnum}=="707"
ATTRS{idVendor}=="0d49"
ATTRS{idProduct}=="7410"
ATTRS{bcdDevice}=="0122"
ATTRS{bDeviceClass}=="00"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bDeviceProtocol}=="00"
ATTRS{bNumConfigurations}=="1"
ATTRS{bMaxPacketSize0}=="64"
ATTRS{speed}=="480"
ATTRS{busnum}=="1"
ATTRS{devnum}=="2"
ATTRS{devpath}=="1"
ATTRS{version}==" 2.00"
ATTRS{maxchild}=="0"
ATTRS{quirks}=="0x0"
ATTRS{authorized}=="1"
ATTRS{manufacturer}=="Maxtor "
ATTRS{product}=="Basics Desktop "
ATTRS{serial}=="2HBEQTN2 "
looking at parent device '/devices/pci0000:00/0000:00:02.1/usb1':
KERNELS=="usb1"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{configuration}==""
ATTRS{bNumInterfaces}==" 1"
ATTRS{bConfigurationValue}=="1"
ATTRS{bmAttributes}=="e0"
ATTRS{bMaxPower}==" 0mA"
ATTRS{urbnum}=="46"
ATTRS{idVendor}=="1d6b"
ATTRS{idProduct}=="0002"
ATTRS{bcdDevice}=="0206"
ATTRS{bDeviceClass}=="09"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bDeviceProtocol}=="00"
ATTRS{bNumConfigurations}=="1"
ATTRS{bMaxPacketSize0}=="64"
ATTRS{speed}=="480"
ATTRS{busnum}=="1"
ATTRS{devnum}=="1"
ATTRS{devpath}=="0"
ATTRS{version}==" 2.00"
ATTRS{maxchild}=="10"
ATTRS{quirks}=="0x0"
ATTRS{authorized}=="1"
ATTRS{manufacturer}=="Linux 2.6.33-ARCH ehci_hcd"
ATTRS{product}=="EHCI Host Controller"
ATTRS{serial}=="0000:00:02.1"
ATTRS{authorized_default}=="1"
looking at parent device '/devices/pci0000:00/0000:00:02.1':
KERNELS=="0000:00:02.1"
SUBSYSTEMS=="pci"
DRIVERS=="ehci_hcd"
ATTRS{vendor}=="0x10de"
ATTRS{device}=="0x005b"
ATTRS{subsystem_vendor}=="0x1043"
ATTRS{subsystem_device}=="0x815a"
ATTRS{class}=="0x0c0320"
ATTRS{irq}=="23"
ATTRS{local_cpus}=="ffff"
ATTRS{local_cpulist}=="0-15"
ATTRS{modalias}=="pci:v000010DEd0000005Bsv00001043sd0000815Abc0Csc03i20"
ATTRS{dma_mask_bits}=="32"
ATTRS{consistent_dma_mask_bits}=="31"
ATTRS{broken_parity_status}=="0"
ATTRS{msi_bus}==""
ATTRS{companion}==""
looking at parent device '/devices/pci0000:00':
KERNELS=="pci0000:00"
SUBSYSTEMS==""
DRIVERS==""

Does Solaris supports non-ASCII mount point?

Hi,
Does Solaris 10 supports non-ASCII mount point?
Kind regards,
Daniel

# fstab generated by gen_fstab
#<file system> <dir> <type> <options> <dump> <pass>
none /dev/pts devpts defaults 0 0
none /dev/shm tmpfs defaults 0 0
UUID=496E-7B5E /media/STORAGE vfat defaults,user,users,rw,exec,uid=777,gid=777 0 0
/dev/sr0 /mnt/sr0_cd auto user,noauto,exec,unhide 0 0
# This would do for a floppy
#/dev/fd0 /mnt/floppy vfat,ext2 rw,user,noauto 0 0
# + mkdir /mnt/floppy
# E.g. for USB storage:
#/dev/sdb1 /mnt/usb auto rw,user,noauto 0 0
# + mkdir /mnt/usb

Not mounting HDD from fstab

Hi!
Until last week my external HDD was mounted automatically during the boot but now it's not.
I haven't modified anything related to the fstab.
This is what the fstab file contains:
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
devpts /dev/pts devpts defaults 0 0
shm /dev/shm tmpfs nodev,nosuid 0 0
#/dev/cdrom /media/cd auto ro,user,noauto,unhide 0 0
#/dev/dvd /media/dvd auto ro,user,noauto,unhide 0 0
#/dev/fd0 /media/fl auto user,noauto 0 0
/dev/sda5 / ext4 defaults 0 1
/dev/sda6 swap swap defaults 0 0
/dev/sda7 /home ext4 defaults,user_xattr 0 2
/dev/sdc1 /media/HDD ntfs-3g defaults 0 0
# mount point for Acer A500
mtpfs /media/a500 fuse user,noauto,allow_other 0 0
tmpfs /tmp tmpfs defaults,nosuid 0 0
/dev/sc1 is the partition I want to mount during the boot:
Disk /dev/sda: 500.1 GB, 500107862016 bytes, 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00080fa8
Device Boot Start End Blocks Id System
/dev/sda1 63 976768064 488384001 5 Extended
/dev/sda5 126 52436159 26218017 83 Linux
/dev/sda6 52436223 54540674 1052226 82 Linux swap / Solaris
/dev/sda7 54540738 976768064 461113663+ 83 Linux
Disk /dev/sdc: 1000.2 GB, 1000170586112 bytes, 1953458176 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00073856
Device Boot Start End Blocks Id System
/dev/sdc1 2048 1953458175 976728064 7 HPFS/NTFS/exFAT
Any idea of what could be happening?

Lone_Wolf wrote:
sounds like sometimes the drive is not ready yet when the system tries to mount it.
Also you're fstab is not listing anything with dev/sdb .
please post the output of
#fdisk -l
so we can see what drives are present on your system.
Is sdc an external or internal harddrive ?
if an external drive how is it connected ( usb, eSata, firewire, bluetooth, network ) ?
I've posted that output before:
Disk /dev/sda: 500.1 GB, 500107862016 bytes, 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00080fa8
Device Boot Start End Blocks Id System
/dev/sda1 63 976768064 488384001 5 Extended
/dev/sda5 126 52436159 26218017 83 Linux
/dev/sda6 52436223 54540674 1052226 82 Linux swap / Solaris
/dev/sda7 54540738 976768064 461113663+ 83 Linux
Disk /dev/sdc: 1000.2 GB, 1000170586112 bytes, 1953458176 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00073856
Device Boot Start End Blocks Id System
/dev/sdc1 2048 1953458175 976728064 7 HPFS/NTFS/exFAT
Oh sorry! It's true, I forgot that info.
It's an external HDD. Exactly a WD My Book Essential of 1TB connected by USB

Which file defines mount point

In Linux, /etc/fstab tells the OS the details of a volume when mounting it. I wanted to edit this to have certain devices use different mount points than they do automatically, so either I'm not doing it properly or OS X works a little differently in this respect.
Thanks.
p.s. I have Tiger, I just haven't updated my info (below)

Brad,
See if this info helps you.
Beavis2084

How do I mount a partition at a specific mount point.

How do I mount a partition at a specific mount point? For example I see a Vol01 disk image, which is a partition of one of my hard drives, sitting on my desktop. Under the disk utility it says that its mount point is /Volumes/Vol01. How do I mount this partition as a file system at /Users?
Thanks, much appreciated.

why do you want to do this? it sounds like you want to keep your home directory on an external drive. this can be done without changing the mount point of the external. copy the home directory to the external. then in system preferences preferences->accounts, unlock the lock at the bottom, control-click on your user and select "advanced options." In the resulting popup change the location of the home directory to the external.
in general to change the default mount point of a drive see this link
http://beta.jamesstroud.com/jamess-miscellaneous-how-tos/os-x-admin/os-x-firewir e-mount-point

Computer no longer recognizes mount point of hard drive

Hello all,
I have a perplexing problem here. When I was running a Verify Disk in Disk Utilities I got a "Keys Out of Order" error, and I cannot repair with either Disk Utility or using fsck.
I ran a Hardware Test and nothing was wrong, so I decided to back everything up, wipe the drive, and re-install the OS. Problem is, DIsk Utility will not let me wipe my hard drive. The mount point shows up as just "/" instead of, for example, /Volumes/My Awesome Computer. I assume this is a symptom of my "Keys out of order" error, since I can see my boot camp partition just fine and can choose to erase it if I want to.
I guess my question is, how can I wipe my Apple partition if the option is not even available to me to begin with? I tried booting up from my installation disks and doing an Archive and Install from there already, but my disks don't even recognize my Apple partition, so I can't even begin to re-install the OS from them.
My only remaining idea is to re-partition my hard drive into another Apple partition, install there, and then unpartition, but I'm not sure if that'll work. Does anyone have any clues or advice?

Update: I tried re-partitioning my drive, but that failed to initiate. I got this error: filesystem verify or repair failed.
It's the same error that I get when I tried to repair my HD with Disk Utility. So, I cannot make new partitions, and my hard drive mount point remains unrecognized by my install CDs. Yet...I can log in and use it just fine. The only manifested problem I've had with this Keys Out of Order error is that I can no longer see my Apple partition from Boot Camp, but I'm worried this problem may get just worse and worse. Help would be greatly appreciated.

Mobile accounts WHICH MOUNT POINT?

How does a machine handling a mobile account
a. know how to set $HOME ?
b. know where to mount the folder during sync?
The scenario and problem:
(can u help?)(you'll win a free beer if you come to Switzerland).
I have the user's files stored in /Volumes/team1/users/user1
The folder /Volumes/team1 is mounted on a local drive on server1.
The server1 share point, called 'users' is /Volumes/team1/users
(sounds simple.. doesn't it
In config-scenario1 I do this:
The user's share point URL is afp://server1.disneyland.ch/users
The path to home folder is user1
The full path is /Network/Servers/server1.disneyland.ch/users/user1
THIS WORKS ON CLIENT MAC1
When logged in (via login panel), the $HOME is set to /Users/user1
and during syncing I see /Volumes/users mounted temporarily (weird,.. it used to show the temporary mount as /Network/Servers/server1.disneyland.ch/users )
user1@mac1:~ > pwd
/Users/user1
user1@mac1:~ >
THIS WORKS ON SERVER1
When I ssh into the user, on server1,
I see $HOME set to /Network/Servers/server1.disneyland.ch/users/user1
user1@server1:~ > pwd
/Network/Servers/server1.disneyland.ch/users/user1
user1@server1:~ >
THIS DOES NOT WORK ON SERVER2
On server2 where the same external drive is mounted (it's an Xsan using fiber-channel)
I get this:
user1$ cd ~
-bash: cd: /Network/Servers/server1.disneyland.ch/users/user1: No such file or directory
SOLUTION1 (that fails)(aka config-scenario 2)
The user's share point URL is afp://server1.disneyland.ch/users
The path to home folder is user1
Set the full path to /Volumes/team1/users/user1
THIS WORKS ON MAC1
THIS WORKS ON SERVER1
THIS CAUSES PROBLEMS ON SERVER2 : (see this posting: http://forums.macosxhints.com/showthread.php?p=581557 ).
Questions :
1. How is the HOME folder determined by the computer? Despite the two config-scenarios, the client mac1 uses HOME as /Users/user1 (as it should) but not on Server1 or Server2 (on Server1 it always uses the value in the full path specified in the Mobility>Home for the user)(In Server2 it sometimes uses that value and sometimes it uses the previous configuration value).
2. How is the MOUNT on the client determined? It seems that it is always /Volumes/users (as it should?); Perhaps it is identified by the system seeing what is behind the user's share point? What's weird is that I'm sure/certain that at one point, under config-scenario1, the mount point on mac8 was NOT /Volumes/users but rather /Network/Servers/server1.disneyland.ch ! Did I dream that ?
3. How can I PREVENT the mount happening on Server2 (it's mounting on top of the existing /Volumes/team1/users !!) ?
4. If I DO accept config-scenario1, couldn't I just create a symbolic link on server2 in /Network/Server/server1.disneyland.ch/users-->/Volumes/team1/users ?? Actually this doesn't work because even with sudo I can't mkdir /Networks/Servers/server1.disneyland.ch into which I wold have make the users-> link
ARGHHH!
Thanx for any insight.
/shawn

DrKdev wrote:
I've bumped the topic over there:
Then please do not do so here. The point of posting to the appropriate forum is to attract users with interest & expertise in that area. Bumping here, in an inappropriate forum, is annoying since it just keeps the topic near the top of this forum's list where users that have no expertise with or interest in the issue will keep seeing it.
This generally does not increase your chances of a reply; if anything it will prompt some users to ignore both of your topics.

Mount points in fstab

Similar Messages

Maybe you are looking for