Mount/fstab option 'nobootwait'

Hi!
I recently sitched from Ubuntu to Archlinux. In Ubuntu it is possible to use the mount option "nobootwait" in the /etc/fstab to tell the system that it does not have to report an error is the partition could not be found. This has the advantage that I can define partitions in the /etc/fstab that are on external HDDs or on the HDD in the Ultra Bay of my Thinkpad.
In Archlinux it seems that this option is unknown because it throws an error during boot, and also if the partitions are not present it is not possible to boot.
So, is the a similar option I could use in Archlinux?

No, the /etc/fstab mount option nofail has fsck skip non-existing devices. Works for me with jfs and ext3/4 partitions.
UUID=89538e7e-7ad7-492b-beca-24189928fe44 /mnt/arch-backup jfs noauto,nofail,rw,noatime,nodiratime 0 2
Last edited by thisoldman (2011-03-10 23:17:49)

Similar Messages

[Solved] Inconsistency in device naming concerning mount/fstab

This is not a problem that needs to be solved, but rather a gap in my understanding of a mechanism.
I have several partitions mounted in my fstab, they are identified by UUID.
# /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
UUID=0767c51a-0ba8-405e-ac98-106182fe4d83 /tmp ext4 noexec,rw,noatime,nodiratime 0 2
UUID=0ba14b78-1b36-4857-92ae-8b1ca41264b6 /boot ext2 defaults 0 1
UUID=4eb07abb-25b0-4683-badf-8d556b536d9c / ext4 defaults 0 1
UUID=e3fe5429-379b-4b6d-a01e-e30aa85784e2 /home ext4 defaults 0 1
UUID=e7fda340-ca00-4c4c-b42e-cfba13a3abbe swap swap defaults 0 0
UUID=e3ae11a4-b602-4ea2-bbf7-8c8c9dea52a6 /mnt/Esther ext4 defaults,rw,noatime,nodiratime 0 2
UUID=55525a1b-386b-4390-8f47-b078b0b2c06e /mnt/Ballamb ext4 defaults,rw,noatime,nodiratime 0 2
UUID=b71cfb8d-a4eb-4ded-a65b-fbc2db102332 /mnt/Galbadia ext4 defaults,rw,noatime,nodiratime 0 2
When all drives are mounted, they show up as mounted by device name (/dev/sd*), only / is displayed as mounted by UUID.
$ mount
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sys on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=10240k,nr_inodes=386283,mode=755)
run on /run type tmpfs (rw,nosuid,nodev,noexec,relatime,size=10240k,mode=755)
/dev/disk/by-uuid/4eb07abb-25b0-4683-badf-8d556b536d9c on / type ext4 (rw,relatime,barrier=1,data=ordered)
devpts on /dev/pts type devpts (rw,relatime,mode=600,ptmxmode=000)
shm on /dev/shm type tmpfs (rw,nosuid,nodev,relatime)
/dev/sdc2 on /tmp type ext4 (rw,noexec,noatime,nodiratime)
/dev/sda1 on /boot type ext2 (rw)
/dev/sda4 on /home type ext4 (rw)
/dev/sdb1 on /mnt/Esther type ext4 (rw,noatime,nodiratime)
/dev/sdc1 on /mnt/Ballamb type ext4 (rw,noatime,nodiratime)
/dev/sdd1 on /mnt/Galbadia type ext4 (rw,noatime,nodiratime)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
gvfs-fuse-daemon on /home/xy/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=xy)
$ df -h
Dateisystem Größe Benutzt Verf. Verw% Eingehängt auf
udev 10M 0 10M 0% /dev
run 10M 192K 9,9M 2% /run
/dev/disk/by-uuid/4eb07abb-25b0-4683-badf-8d556b536d9c 68G 8,5G 56G 14% /
shm 1,5G 4,0K 1,5G 1% /dev/shm
/dev/sdc2 289G 194M 274G 1% /tmp
/dev/sda1 251M 17M 222M 7% /boot
/dev/sda4 849G 62G 745G 8% /home
/dev/sdb1 1,8T 1,5T 223G 88% /mnt/Esther
/dev/sdc1 1,1T 223G 810G 22% /mnt/Ballamb
/dev/sdd1 1,8T 390G 1,4T 23% /mnt/Galbadia
Now I feel the urge to know why. Neither the mount nor the fstab manfile gave me insight on this one. So, what's behind this?
Last edited by Awebb (2011-10-08 17:51:26)

Now I feel stupid for not searching properly. Solved. Thanks, karol.
EDIT: So, in other words, if the UUID is passed by Grub, it shows as UUID in the system,
http://projects.archlinux.org/mkinitcpi … 3afd7e0001
So it was solved about a year ago? Well...
Last edited by Awebb (2011-05-29 14:12:06)

External drive won't mount. Options?

Hi everyone. I've used a LaCie 250GB D2 external hard drive for a little over two years with no problems. A few days ago, I bought a Western Digital 500GB drive to serve as my main external drive, so I decided to erase and reformat the LaCie drive, which I had previously partitioned into two volumes, to serve as an archive drive.
That's where my trouble started.
I deleted all my files off the drive and then selected Erase in Disk Utility. I checked the option to eight way random write over format the disk for increased security, but that seemed to be taking so long I just quit Disk Utility. I figured since I didn't have any data I was afraid of losing, it wouldn't be a problem.
The next day I tried to erase it again, but I got an error message that said something about my partition (sorry but I can't recall what the message was; at this point I still didn't think there would be any problem).
Yesterday night, I tried again to erase and reformat the disk. I selected the option to zero all data because I thought that might solve any hard-to-fix problems. I left Disk Utility running overnight and all day today--about 20 hours in all-- but the progress bar showed no progress. None.
Now, as of this evening, I can't get the drive to mount at all. When I plug the drive in (and I've tried all three interfaces), the blue activity light starts blinking and I can hear it spin for a little while. It eventually stops spinning but the light keeps blinking.
I've tried unplugging the drive and plugging it back in. Nothing. I own DiskWarrior, but as far as I can tell there's nothing DiskWarrior can do if the drive won't mount.
I'm wondering if disconnected the drive while it was running could have caused this problem. I might have done that inadvertently when it was taking so long to format. I figured that might result in loss of data, but I wouldn't think it would render a drive completely non functional.
I'm guessing the problem is probably a failure of the drive, but the fact that this only cropped up when I tried to reformat it seems suspicious to me.
If anyone has any suggestions for ways to get the drive to mount or format it, I'd sincerely appreciate hearing them. Thanks.

Thanks for quick reply. Boy, I really screwed up. I guess I didn't think I could permanently ruin a drive that way. I just assumed as long as the drive could spin and wasn't going bad, you could always reformat it.
Just so you know, I let my iBook run untouched for literally 20 hours in the zero out erase mode, but the progress bar showed no progress at all, so I think the drive must have already been broken by that point. I was prepared for it to take a day or more, but with no visible progress in 20 hours it would have taken weeks.

AFP Mount NO OPTION to mount entire hard disk

After installing Leopard, I'm no longer able to mount using the AFP protocol the entire hard drive. Earlier, it would give me the option of mounting "Hard_Drive" or "User", but now somehow it only gives me the "User" mount option. I'm the super user/root so I don't understand.
Any ideas?

The reason seems to have been that somehow my account (I'm the only user) lost administrative access. I found the solution here. It works.
http://discussions.apple.com/thread.jspa?messageID=5645315&#5645315
=============
1. Shut down the computer if it is on.
2. Press the power button to start the computer.
3. Immediately press and hold the Command (Apple) key and one of the following:
the "s" key for single-user mode.
4. Type mount -uw /
5. Type passwd
6. Enter new password (this will be for the root user account)
7. Type reboot
8. Login with any of your usernames just to get the desktop up.
9. After desktop comes up choose System Preferences, then choose accounts. Unlock if you have to and using the username: root ..... password you just setup in the single user mode You now should be able to make users including the top user on the left an admin...
(just so everyone knows... I didn't realize from above post that I was supppose to unlock with the USERNAME: "root" instead of my own user name.
==========================

Fstab and preferred options

At one time when I installed my arch systems it was recommended to use defaults,relatime for the mount options for ext4 partitions in fstab. However I am trying to look into an issue with mirror database syncing and I looked through the install wiki areas and did not see any mention of using relatime any more. However I did see in the fstab wiki that noatime was mentioned a number of times.
Can someone clarify what the current recommended mount options are for ext4 filesystems in fstab? (defaults,relatime or defaults,noatime for example)
Thanks

It's all quite a mess (man pages, wiki and reality all show different things), but relatime has been the kernel default for a long while; there is no need to specify it manually. My only fstab option is "discard", and mount outputs:
/dev/sda1 on / type ext4 (rw,relatime,discard,data=ordered)
Also, "defaults" are included by default ( ), so there is no need to specify this option explicitly (i.e. "defaults,noatime" is equivalent to "noatime"). The only situation in which it is needed is when you use no other options — then not writing it would leave a blank space and it would be an error.
So, "recommended options": leave it as it is and only specify what you need.

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).

Why do i need udev+udisks+udisks2+gvfs installed to dynamic mount?

hi there,
yes, i have used the search function on that, but still have unanswered questions.
1.
why do i need udev+udisks+udisks2+gvfs installed to dynamically mount internal (ntfs, ext4) partitions ?
If one these packages is missing, mounting an internal drive with "pcmanfm" is not possible.
I know how to static mount these drives via "fstab", but i want to mount them when i need the access.
2.
why are my removable devices not automatically mounted in "pcmanfm" when plugged in?
I have another OS (Lubuntu) running and this automatically recognizes when a cd is inserted or a usb stick is plugged in.
I have tried to install the package "gvfs-afc" and rebooted, still no usb stick to see. But when i enter:
sudo blkid -c /dev/null
The usb stick is listed as "sdb1"
I am using 64bit arch linux 3.9.3-1 with openbox+lxde.

jasonwryan wrote:
You don't. You need udev for a whole lot of other stuff, so leave that aside. To automount removable media, you can just use udisks and a helper like ud{iskie,evil}.
For an ntfs partition, you will also need that driver.
Comparing it with the Lubuntu; I am sure there is a lot more cruft preinstalled that makes this happen. In Arch, you just install what you need.
The udev page has the details.
so i have uninstalled the gvfs+udisks2 packages, rebooted and installed udevil-git and rebooted again.
No partition is shown in the filemanager now. I really dont get it. The udev wiki says udev needs rules but my "/etc/udev/rules.d" folder is empty.
The udisks wiki says that udisks and udisks2 are incompatible and that only one is needed and that udisks2 should be installed for gnome systems and udisks for xfce, but i have lxde installed. So it is not working with udisks and lxde (pcmanfm), when i try to install udisks2 additionally, it also does not work. Uninstalling udisks is also not possible because of the dependancy to libfm and so on...
Here is my /etc/udevil/udevil-user-harry.conf:
# udevil configuration file /etc/udevil/udevil.conf
# This file controls what devices, networks, and files users may mount and
# unmount via udevil (set suid).
# IMPORTANT: IT IS POSSIBLE TO CREATE SERIOUS SECURITY PROBLEMS IF THIS FILE
# IS MISCONFIGURED - EDIT WITH CARE
# Note: For greater control for specific users, including root, copy this
# file to /etc/udevil/udevil-user-USERNAME.conf replacing USERNAME with the
# desired username (eg /etc/udevil/udevil-user-jim.conf).
# Format:
# OPTION = VALUE[, VALUE, ...]
# DO NOT USE QUOTES except literally
# Lines beginning with # are ignored
# To log all uses of udevil, set log_file to a file path:
#log_file = /var/log/udevil.log
# Approximate number of days to retain log entries (0=forever, max=60):
log_keep_days = 10
# allowed_types determines what fstypes can be passed by a user to the u/mount
# program, what device filesystems may be un/mounted implicitly, and what
# network filesystems may be un/mounted.
# It may also include the 'file' keyword, indicating that the user is allowed
# to mount files (eg an ISO file). The $KNOWN_FILESYSTEMS variable may
# be included to include common local filesystems as well as those listed in
# /etc/filesystems and /proc/filesystems.
# allowed_types_USERNAME, if present, is used to override allowed_types for
# the specific user 'USERNAME'. For example, to allow user 'jim' to mount
# only vfat filesystems, add:
# allowed_types_jim = vfat
# Setting allowed_types = * does NOT allow all types, as this is a security
# risk, but does allow all recognized types.
# allowed_types = $KNOWN_FILESYSTEMS, file, cifs, smbfs, nfs, curlftpfs, ftpfs, sshfs, davfs, tmpfs, ramfs
allowed_types = $KNOWN_FILESYSTEMS, file, ntfs, vfat
# allowed_users is a list of users permitted to mount and unmount with udevil.
# Wildcards (* or ?) may be used in the usernames. To allow all users,
# specify "allowed_users=*". UIDs may be included using the form UID=1000.
# For example: allowed_users = carl, UID=1000, pre*
# Also note that permission to execute udevil may be limited to users belonging
# to the group that owns /usr/bin/udevil, such as 'plugdev' or 'storage',
# depending on installation.
# allowed_users_FSTYPE, if present, is used to override allowed_users when
# mounting or unmounting a specific fstype (eg nfs, ext3, file).
# Note that when mounting a file, fstype will always be 'file' regardless of
# the internal fstype of the file.
# For example, to allow only user 'bob' to mount nfs shares, add:
# allowed_users_nfs = bob
# The root user is NOT automatically allowed to use udevil in some cases unless
# listed here (except for unmounting anything or mounting fstab devices).
allowed_users = harry, root
# allowed_groups is a list of groups permitted to mount and unmount with
# udevil. The user MUST belong to at least one of these groups. Wildcards
# or GIDs may NOT be used in group names, but a single * may be used to allow
# all groups.
# Also note that permission to execute udevil may be limited to users belonging
# to the group that owns /usr/bin/udevil, such as 'plugdev' or 'storage',
# depending on installation.
# allowed_groups_FSTYPE, if present, is used to override allowed_groups when
# mounting or unmounting a specific fstype (eg nfs, ext3, file). For example,
# to allow only members of the 'network' group to mount smb and nfs shares,
# use both of these lines:
# allowed_groups_smbfs = network
# allowed_groups_nfs = network
# The root user is NOT automatically allowed to use udevil in some cases unless
# listed here (except for unmounting anything or mounting fstab devices).
allowed_groups = storage
# allowed_media_dirs specifies the media directories in which user mount points
# may be located. The first directory which exists and does not contain a
# wildcard will be used as the default media directory (normally /media or
# /run/media/$USER).
# The $USER variable, if included, will be replaced with the username of the
# user running udevil. Wildcards may also be used in any directory EXCEPT the
# default. Wildcards will not match a /
# allowed_media_dirs_FSTYPE, if present, is used to override allowed_media_dirs
# when mounting or unmounting a specific fstype (eg ext2, nfs). For example,
# to cause /media/network to be used as the default media directory for
# nfs and ftpfs mounts, use these two lines:
# allowed_media_dirs_nfs = /media/network, /media, /run/media/$USER
# allowed_media_dirs_ftpfs = /media/network, /media, /run/media/$USER
# NOTE: If you want only the user who mounted a device to have access to it
# and be allowed to unmount it, specify /run/media/$USER as the first
# allowed media directory.
# IMPORTANT: If an allowed file is mounted to a media directory, the user may
# be permitted to unmount its associated loop device even though internal.
# INCLUDING /MNT HERE IS NOT RECOMMENDED. ALL ALLOWED MEDIA DIRECTORIES
# SHOULD BE OWNED AND WRITABLE ONLY BY ROOT.
allowed_media_dirs = /media, /run/media/$USER
# allowed_devices is the first criteria for what block devices users may mount
# or unmount. If a device is not listed in allowed_devices, it cannot be
# un/mounted (unless in fstab). However, even if a device is listed, other
# factors may prevent its use. For example, access to system internal devices
# will be denied to normal users even if they are included in allowed_devices.
# allowed_devices_FSTYPE, if present, is used to override allowed_devices when
# mounting or unmounting a specific fstype (eg ext3, ntfs). For example, to
# prevent all block devices containing an ext4 filesystem from being
# un/mounted use:
# allowed_devices_ext4 =
# Note: Wildcards may be used, but a wildcard will never match a /, except
# for "allowed_devices=*" which allows any device. The recommended setting is
# allowed_devices = /dev/*
# WARNING: ALLOWING USERS TO MOUNT DEVICES OUTSIDE OF /dev CAN CAUSE SERIOUS
# SECURITY PROBLEMS. DO NOT ALLOW DEVICES IN /dev/shm
allowed_devices = /dev/*
# allowed_internal_devices causes udevil to treat any listed block devices as
# removable, thus allowing normal users to un/mount them (providing they are
# also listed in allowed_devices).
# allowed_internal_devices_FSTYPE, if present, is used to override
# allowed_internal_devices when mounting or unmounting a specific fstype
# (eg ext3, ntfs). For example, to allow block devices containing a vfat
# filesystem to be un/mounted even if they are system internal devices, use:
# allowed_internal_devices_vfat = /dev/sdb*
# Some removable esata drives look like internal drives to udevil. To avoid
# this problem, they can be treated as removable with this setting.
# WARNING: SETTING A SYSTEM DEVICE HERE CAN CAUSE SERIOUS SECURITY PROBLEMS.
# allowed_internal_devices =
# allowed_internal_uuids and allowed_internal_uuids_FSTYPE work similarly to
# allowed_internal_devices, except that UUIDs are specified instead of devices.
# For example, to allow un/mounting of an internal filesystem based on UUID:
# allowed_internal_uuids = cc0c4489-8def-1e5b-a304-ab87c3cb626c0
# WARNING: SETTING A SYSTEM DEVICE HERE CAN CAUSE SERIOUS SECURITY PROBLEMS.
# allowed_internal_uuids =
# forbidden_devices is used to prevent block devices from being un/mounted
# even if other settings would allow them (except devices in fstab).
# forbidden_devices_FSTYPE, if present, is used to override
# forbidden_devices when mounting or unmounting a specific fstype
# (eg ext3, ntfs). For example, to prevent device /dev/sdd1 from being
# mounted when it contains an ntfs filesystem, use:
# forbidden_devices_ntfs = /dev/sdd1
# NOTE: device node paths are canonicalized before being tested, so forbidding
# a link to a device will have no effect.
forbidden_devices =
# allowed_networks determines what hosts may be un/mounted by udevil users when
# using nfs, cifs, smbfs, curlftpfs, ftpfs, or sshfs. Hosts may be specified
# using a hostname (eg myserver.com) or IP address (192.168.1.100).
# Wildcards may be used in hostnames and IP addresses, but CIDR notation
# (192.168.1.0/16) is NOT supported. IP v6 is supported. For example:
# allowed_networks = 127.0.0.1, 192.168.1.*, 10.0.0.*, localmachine, *.okay.com
# Or, to prevent un/mounting of any network shares, set:
# allowed_networks =
# allowed_networks_FSTYPE, if present, is used to override allowed_networks
# when mounting or unmounting a specific network fstype (eg nfs, cifs, sshfs,
# curlftpfs). For example, to limit nfs and samba shares to only local
# networks, use these two lines:
# allowed_networks_nfs = 192.168.1.*, 10.0.0.*
# allowed_networks_cifs = 192.168.1.*, 10.0.0.*
allowed_networks = *
# forbidden_networks and forbidden_networks_FSTYPE are used to specify networks
# that are never allowed, even if other settings allow them (except fstab).
# NO REVERSE LOOKUP IS PERFORMED, so including bad.com will only have an effect
# if the user uses that hostname. IP lookup is always performed, so forbidding
# an IP address will also forbid all corresponding hostnames.
forbidden_networks =
# allowed_files is used to determine what files in what directories may be
# un/mounted. A user must also have read permission on a file to mount it.
# Note: Wildcards may be used, but a wildcard will never match a /, except
# for "allowed_files=*" which allows any file. For example, to allow only
# files in the /share directory to be mounted, use:
# allowed_files = /share/*
# NOTE: Specifying allowed_files_FSTYPE will NOT work because the fstype of
# files is always 'file'.
allowed_files = *
# forbidden_files is used to specify files that are never allowed, even if
# other settings allow them (except fstab). Specify a full path.
# Note: Wildcards may be used, but a wildcard will never match a /, except
# for "forbidden_files = *".
# NOTE: file paths are canonicalized before being tested, so forbidding
# a link to a file will have no effect.
forbidden_files =
# default_options specifies what options are always included when performing
# a mount, in addition to any options the user may specify.
# Note: When a device is present in /etc/fstab, and the user does not specify
# a mount point, the device is mounted with normal user permissions using
# the fstab entry, without these options.
# default_options_FSTYPE, if present, is used to override default_options
# when mounting a specific fstype (eg ext2, nfs).
# The variables $USER, $UID, and $GID are changed to the user's username, UID,
# and GID.
# FOR GOOD SECURITY, default_options SHOULD ALWAYS INCLUDE: nosuid,noexec,nodev
# WARNING: OPTIONS PRESENT OR MISSING CAN CAUSE SERIOUS SECURITY PROBLEMS.
default_options = nosuid, noexec, nodev, noatime
default_options_file = nosuid, noexec, nodev, noatime, uid=$UID, gid=$GID, ro
# mount iso9660 with 'ro' to prevent mount read-only warning
default_options_iso9660 = nosuid, noexec, nodev, noatime, uid=$UID, gid=$GID, ro, utf8
default_options_udf = nosuid, noexec, nodev, noatime, uid=$UID, gid=$GID
default_options_vfat = nosuid, noexec, nodev, noatime, fmask=0022, dmask=0022, uid=$UID, gid=$GID, utf8
default_options_msdos = nosuid, noexec, nodev, noatime, fmask=0022, dmask=0022, uid=$UID, gid=$GID
default_options_umsdos = nosuid, noexec, nodev, noatime, fmask=0022, dmask=0022, uid=$UID, gid=$GID
default_options_ntfs = nosuid, noexec, nodev, noatime, uid=$UID, gid=$GID, utf8
default_options_cifs = nosuid, noexec, nodev, uid=$UID, gid=$GID
default_options_smbfs = nosuid, noexec, nodev, uid=$UID, gid=$GID
default_options_sshfs = nosuid, noexec, nodev, noatime, uid=$UID, gid=$GID, nonempty, allow_other
default_options_curlftpfs = nosuid, noexec, nodev, noatime, uid=$UID, gid=$GID, nonempty, allow_other
default_options_ftpfs = nosuid, noexec, nodev, noatime, uid=$UID, gid=$GID
default_options_davfs = nosuid, noexec, nodev, uid=$UID, gid=$GID
default_options_tmpfs = nosuid, noexec, nodev, noatime, uid=$UID, gid=$GID
default_options_ramfs = nosuid, noexec, nodev, noatime, uid=$UID, gid=$GID
# allowed_options determines all options that a user may specify when mounting.
# All the options used in default_options above must be included here too, or
# they will be rejected. If the user attempts to use an option not included
# here, an error will result. Wildcards may be used.
# allowed_options_FSTYPE, if present, is used to override allowed_options
# when mounting a specific fstype (eg ext2, nfs).
# The variables $USER, $UID, and $GID are changed to the user's username, UID,
# and GID.
# If you want to forbid remounts, remove 'remount' from here.
# WARNING: OPTIONS HERE CAN CAUSE SERIOUS SECURITY PROBLEMS - CHOOSE CAREFULLY
allowed_options = nosuid, noexec, nodev, noatime, fmask=0022, dmask=0022, uid=$UID, gid=$GID, ro, rw, sync, flush, iocharset=*, utf8, remount
allowed_options_nfs = nosuid, noexec, nodev, noatime, ro, rw, sync, remount, port=*, rsize=*, wsize=*, hard, proto=*, timeo=*, retrans=*
allowed_options_cifs = nosuid, noexec, nodev, ro, rw, remount, port=*, user=*, username=*, pass=*, password=*, guest, domain=*, uid=$UID, gid=$GID, credentials=*
allowed_options_smbfs = nosuid, noexec, nodev, ro, rw, remount, port=*, user=*, username=*, pass=*, password=*, guest, domain=*, uid=$UID, gid=$GID, credentials=*
allowed_options_sshfs = nosuid, noexec, nodev, noatime, ro, rw, uid=$UID, gid=$GID, nonempty, allow_other, idmap=user, BatchMode=yes, port=*
allowed_options_curlftpfs = nosuid, noexec, nodev, noatime, ro, rw, uid=$UID, gid=$GID, nonempty, allow_other, user=*
allowed_options_ftpfs = nosuid, noexec, nodev, noatime, ro, rw, port=*, user=*, pass=*, ip=*, root=*, uid=$UID, gid=$GID
# mount_point_mode, if present and set to a non-empty value, will cause udevil
# to set the mode (permissions) on the moint point after mounting If not
# specified or if left empty, the mode is not changed. Mode must be octal
# starting with a zero (0755).
# mount_point_mode_FSTYPE, if present, is used to override mount_point_mode
# when mounting a specific fstype (eg ext2, nfs).
# NOT SETTING A MODE CAN HAVE SECURITY IMPLICATIONS FOR SOME FSTYPES
mount_point_mode = 0755
# don't set a mode for some types:
mount_point_mode_sshfs =
mount_point_mode_curlftpfs =
mount_point_mode_ftpfs =
# Use the settings below to change the default locations of programs used by
# udevil, or (advanced topic) to redirect commands to your scripts.
# When substituting scripts, make sure they are root-owned and accept the
# options used by udevil (for example, the mount_program must accept --fake,
# -o, -v, and other options valid to mount.)
# Be sure to specify the full path and include NO OPTIONS or other arguments.
# These programs may also be specified as configure options when building
# udevil.
# THESE PROGRAMS ARE RUN AS ROOT
# mount_program = /bin/mount
# umount_program = /bin/umount
# losetup_program = /sbin/losetup
# setfacl_program = /usr/bin/setfacl
# validate_exec specifies a program or script which provides additional
# validation of a mount or unmount command, beyond the checks performed by
# udevil. The program is run as a normal user (if root runs udevil,
# validate_exec will NOT be run). The program is NOT run if the user is
# mounting a device without root priviledges (a device in fstab).
# The program is passed the username, a printable description of what is
# happening, and the entire udevil command line as the first three arguments.
# The program must return an exit status of 0 to allow the mount or unmount
# to proceed. If it returns non-zero, the user will be denied permission.
# For example, validate_exec might specify a script which notifies you
# of the command being run, or performs additional steps to authenticate the
# user.
# Specify a full path to the program, with NO options or arguments.
# validate_exec =
# validate_rootexec works similarly to validate_exec, except that the program
# is run as root. validate_rootexec will also be run if the root user runs
# udevil. If both validate_exec and validate_rootexec are specified,
# validate_rootexec will run first, followed by validate_exec.
# The program must return an exit status of 0 to allow the mount or unmount
# to proceed. If it returns non-zero, the user will be denied permission.
# Unless you are familiar with writing root scripts, it is recommended that
# rootexec settings NOT be used, as it is easy to inadvertently open exploits.
# THIS PROGRAM IS ALWAYS RUN AS ROOT, even if the user running udevil is not.
# validate_rootexec =
# success_exec is run after a successful mount, remount, or unmount. The
# program is run as a normal user (if root runs udevil, success_exec
# will NOT be run).
# The program is passed the username, a printable description of what action
# was taken, and the entire udevil command line as the first three arguments.
# The program's exit status is ignored.
# For example, success_exec might run a script which informs you of what action
# was taken, and might perform further actions.
# Specify a full path to the program, with NO options or arguments.
# success_exec =
# success_rootexec works similarly to success_exec, except that the program is
# run as root. success_rootexec will also be run if the root user runs udevil.
# If both success_exec and success_rootexec are specified, success_rootexec
# will run first, followed by success_exec.
# Unless you are familiar with writing root scripts, it is recommended that
# rootexec settings NOT be used, as it is easy to inadvertently open exploits.
# THIS PROGRAM IS ALWAYS RUN AS ROOT, even if the user running udevil is not.
# success_rootexec =
I have no idea what to do next, the only way it works, is the combination i mentioned in the title of this post. Any suggestion to solve that problem?

WD My cloud USB drive mount command???

Hello,
I've a backup script which is autoscheduled and backs up my data to the usb drive. I would like to keep usb drive unmounted until the script starts since twonky scans my usb drive as well and I couldn't disable it from both twonky setup and my cloud UI. After reboot it starts scanning again. (if you know this, it will be a better solution)
So after reboot I would like to unmount the usb disk. I found the unmount command in the forum. Thansk to Nazar.
However I don't know how to mount the drive from the script.
Can you please help me on this?
Thanks...

mount [ -o options,.. ] /dev/sdb1 /path/to/existing/directory or if you know your stuffs let it auto mount on boot, edit /etc/fstab as below, then mount -a or mount /dev/sdb1: /dev/sdb1 /path/to/existing/directory filesystem(i.e. vfat) options(i.e. defaults) backup-dump(i.e. 0) pass-fsck(i.e. 0) Note all above is not supported by WD and warrants warranty void. Wrong fstab entries may not boot up your nas properly so I don't recommend this unless you fully understood. I did a mistake once while mounting additional swap space which end up opening the drive just to recover. Read more https://en.wikipedia.org/wiki/Fstab

Mount ro vs. rw,sync

I'm building a linux system that will be powered off simply by switching off the power, so the / partition is mounted read only. Problem is that it needs to copy or delete some files occasionally.
For this purpose I have another ext2 partition which is mounted with options rw,sync in fstab. The power would never be switched off during file creation, copy, ..., but only after such tasks are finished. Could I just switch off the power or would the filesystem get corrupted?
I could also mount ro, then before copying remount to rw and back to ro. It is a bit awkward, though. And I'd need root privileges for that.

I'm not sure about this unionfs. It means additional space and a kernel module.
I am not building a live distro. The data I need to write is small. And it needs to be written on very rare occasions. But it needs to stay on disk after shutdown.
Basically what I wanted to ask is: will an unclean poweroff cause any corruption on ext2 (non journalizing filesystem), mounted with "rw,sync"? I can safely assume none of write processes will still be in progress when the power is switched off. The media is compact flash, so there is no need to fear of any disk cache?

Global mounting default timeout of 1min 30s

I know that there are mount options in /etc/fstab to help control timeout for individual file system mounts, but I am not too fond of tinkering with /etc/fstab because it becomes less portable. is there a system-wide way to change this 1:30 min mounting timeout parameter globally, applying to all mounts, that I can change?
/iaw
PS: I hope everyone has forgotten my embarrassing post yesterday. long story. I was not mentally ill.

As mounting is just a service (edit: a systemd unit), I suspect you can't change this without affecting other services units (without using fstab options). In some cases, setting too low of a timeout may make some services fail when they would actually complete eventually. That said, I suspect that the following in /etc/systemd/system.conf are what you are looking for:
#DefaultTimeoutStartSec=90s
#DefaultTimeoutStopSec=90s
EDIT: corrected terminology from "service" to "unit" as noted below - the point remains the same.
Last edited by Trilby (2015-01-02 16:46:24)

Umount drives mounted with autofs

Is it possible to allow users to call "umount" on drives that were mounted with autofs? I have the following rules:
cdrom -fstype=iso9660,ro,users,nodev,nosuid :/dev/cdrom
floppy -fstype=auto,async,users,nodev,nosuid,umask=000 :/dev/fl
usb -fstype=auto,async,users,nodev,nosuid,umask=000 :/dev/sdb1
I am under the impression that if I mount with option "users", then users can umount the drives. However, that option does not actually seem to be used. Any ideas on how I can allow my users to umount these drives?

Nope. From `man mount':
users: Allow every user to mount and unmount the file system. This option implies the options noexec, nosuid, and nodev (unless overridden by subsequent options, as in the option line users,exec,dev,suid).
Only the user that mounted a filesystem can unmount it again. If any user should be able to unmount, then use users instead of user in the fstab line. The owner option is similar to the user option, with the restriction that the user must be the owner of the special file. This may be useful e.g. for /dev/fd if a login script makes the console user owner of this device. The group option is similar, with the restriction that the user must be member of the group of the special file.

Mac won't mount external HDD since 10.8.4 update

Hi All
I'm fairly new to Mac (3mths) so still finding my feet...hopefully someone is able to help me here!
Hardware:
MBP 2.7Ghz running (now) Os 10.8.4
WD HD5000D032-000 (the old drive)
3TB WD Red (the new drive)
Solutions tried to the problem (described in detail below):
- restart Mac
- restart eHDD
- different USB and power cables for eHH
- different Mac(mini)
- removed eHDD from stock housing and used SATA docking station
- bought new HDD and used with SATA docking station
Now to the detail of my problems:
I've had a WD 500GB external HDD for about 8yrs. Formatted FAT32. Used with PC/Win laptop no issues.
Switched to Mac and no issues at all. However after a recent trip to Japan I plugged in the HDD to back up all the photos and vids I'd taken (I took my Mac with me to download off the the various SD cards,etc), the HDD plugged in and booted fine as normal and file transfer was initiated. The folder was large (don't recall how much but a few GB at least). Everything seemed to be progressing fine so left both Mac and HDD plugged in and carried on watching tv. Noticed a few mins later that an error message had popped up saying disk could not be found (or something similar).
HDD was no longer visible. Therefore I unplugged and reconnected and.... nothing. I can see the HDD in Disk Utility but it's not mounted. Options to verify/repair disk are greyed out. At this point I tried using different cables and USB ports and still no improvement. I've also tried restarting both Mac and HDD.
A few hours of reading forum posts suggested the HDD housing may be the culprit as it was quite old and prone to failing. As I'd tried all else, I went out and bought a SATA docking station and removed the HDD from its stock housing. This yielded the same results - I can see the HDD clearly in Disk utility but can't mount or verify/repair.
I then tried plugging into mate's Macmini running and older Osx and this time, the verify/repair options are available. Tried them and result was disk could not be repaired by Disk Utility. I still couldn't mount the drive and access any files though.
I had been planning on setting up a NAS anyway so ordered a new 3TB eHDD (WD Red) which arrived yesterday. I plugged it in using the docking station ni order to format it to FAT32 so that I could at least download my data from my Mac (and then subsequently look to recover all the data from the old eHDD) but the option 'MS-DOS File System' isn't available in the drop down in Disk Utility/Erase.
All the steup guides on formatting HDDs using Mac suggest that I should have this option in order to format as FAT32. All I see are 3 types of 'MS-DOS (extended)' and 'exFAT'.
The twist:
All this time I just assumed that it was the hardware acting up but the fact that the new HDD isn't recognised properly either made me wonder. I remember updating the OS to 10.8.4 whilst I was away in Japan and connected to wifi. I presumed that any update that was pushed down to me was good to go - could I be wrong??
I've also noticed that my wifi sometimes takes a while to connect / disconnects by itself and skype repeatedly drops calls. From more reading around, I see that these are some issues people have experienced since updating to 10.8.4.
So could my HDD issues be being caused by 10.8. 4 as well?!
I'm out of ideas so now wondering whether I should try and roll back the 10.8.4 update but I've not idea whether this is safe/easy to do, etc...
Any help would be VERY much appreciated!!
Thanks in advance!
Vig

Duplicate post. Answered here: http://forums.macrumors.com/showthread.php?t=1614533

Rack mount kit - WLC 2100

What's the Part Number for the Cisco WLC 2100 rack mount kit?
Thanks in advance.

Allows for convenient desktop mounting or rack mounting, with optional rack mount kit for flexible deployment.
http://www.cisco.com/en/US/products/ps7206/products_data_sheet0900aecd805aaab9.html

NFS latency when Solaris 10 client mounts Linux NFS server(EMC NAS)

Hello,
One of our developers discovered a problem that for simplicity we call "latency". We have several 5.10 clients that we see the exact same symptoms on when NFS mounting our Celerra. The NAS is running a Linux variant "2.4.9-34.5406.EMC", but before you all jump on the "it's EMC's problem" bandwagon, let me explain. We set up an automated process (Perl) that watches an exported folder for the appearance of a request file (rand.req). When the request file comes in we rename the request file to (rand.sav) and then return a "report" named (rand.res). Very elegent I thought, and it runs at near lightspeed when only Linux NFS clients mount the share and create, monitor, delete, etc any files. In fact there is zero recorded latency from the time the report file appears and when the client detects it. But for all our Solaris 10 clients, they create the request file just fine, and the Perl process running on the Linux box sees the file instantaneously and returns the report, but it takes the Solaris client anywhere from 5 to up to 50 seconds before it see's any change in status for any files the Linux box manipulates. I've tried every possible combination of mount -o options there are including noac, rsize and wsize variants, vers=2, proto=udp, actimeo=0, etc, etc, etc. Nothing seems to be the magic bullet. nfsstat -c shows nothing out of the ordinary. There are no retransmits or dropepd packets anywhere in between, no firewall loads, no connectivity delays whatsoever. I'm completely out of ideas. Any ideas or clues would be greatly appreciated!
thanks
Dave

No specific recommendations. But maybe you can watch the cable and get more information.
Set up a case where the file has been created, then have the client check and snoop the cable at the same time. Does the client actually issue a directory check (or is it just displaying cached information)? Does the response contain the new file?
Something to test anyway...
Darren

Duplication problem: Drive or volume on which mount attempted is unusable.

Greetings.
I have a duplication job that's been trying to complete. That is, it starts and eventually fails with the following in the transcript (I put parameters in place of the actual names):
+2010/01/21.10:34:27 No volume could be found in <library name> (for drive tape1) to use for job 8171.+
+2010/01/21.10:34:27 Volume ID <volume label> is needed to perform a restore.+
and in the Job Properties window:
+2010/01/21.10:00:01 Dispatching job to run on administrative server.+
+2010/01/21.10:34:27 Drive or volume on which mount attempted is unusable.+
The requirement for the job is the following:
volume <volume label> and family <family> and host <hostname> and any device@<hostname> and any device@<hostname>
The volume with the above volume label is in the library. There are a number of unlabeled volumes ready for use in the library. Finally, there are several expired volumes from the required media family in the library.
Any ideas?
Thank you for your attention.
-Jeff
Edited by: user12198316 on Jan 21, 2010 8:19 AM

It's pretty huge.
cut out 17th through 21st
2010/01/22.10:00:01 ______________________________________________________________________
2010/01/22.10:00:01
2010/01/22.10:00:01 Transcript for job 8171 running on backup01
2010/01/22.10:00:01
2010/01/22.10:00:01 (amh) qdv__automount_in_mh tape1 at 2010/01/22.10:00:01, flags 0x100
2010/01/22.10:00:01 (amh) mount volume options list contains:
2010/01/22.10:00:01 (amh) vtype 1, vid PASWLY-000215, vs_create 0, family (null), retain (null), size 0, scratch 0
2010/01/22.10:00:02 (amh) don't preserve previous mh automount state
2010/01/22.10:00:02 (amh) loaded volume has no barcode
2010/01/22.10:00:03 (amh) beginning pass 1
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != PAS-RMAN-018887
2010/01/22.10:00:03 (mmr) oid 20543 (vid PAS-RMAN-018887, tag 000048L3) fails mount criteria
2010/01/22.10:00:03 (amh) 2 oid 20543 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != PASDLY-000487
2010/01/22.10:00:03 (mmr) oid 20909 (vid PASDLY-000487, tag 000021L3) fails mount criteria
2010/01/22.10:00:03 (amh) 3 oid 20909 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (amh) 4 no vid
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != PASDLY-000486
2010/01/22.10:00:03 (mmr) oid 20908 (vid PASDLY-000486, tag 000054L3) fails mount criteria
2010/01/22.10:00:03 (amh) 5 oid 20908 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != PASDLY-000488
2010/01/22.10:00:03 (mmr) oid 20911 (vid PASDLY-000488, tag 000047L3) fails mount criteria
2010/01/22.10:00:03 (amh) 6 oid 20911 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != PASDLY-000485
2010/01/22.10:00:03 (mmr) oid 20904 (vid PASDLY-000485, tag 000015L3) fails mount criteria
2010/01/22.10:00:03 (amh) 7 oid 20904 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != PASDLY-000483
2010/01/22.10:00:03 (mmr) oid 20889 (vid PASDLY-000483, tag 000008L3) fails mount criteria
2010/01/22.10:00:03 (amh) 8 oid 20889 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != PASDLY-000482
2010/01/22.10:00:03 (mmr) oid 20888 (vid PASDLY-000482, tag 000039L3) fails mount criteria
2010/01/22.10:00:03 (amh) 9 oid 20888 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != PASDLY-000490
2010/01/22.10:00:03 (mmr) oid 20914 (vid PASDLY-000490, tag 000100L3) fails mount criteria
2010/01/22.10:00:03 (amh) 10 oid 20914 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != PASDLY-000489
2010/01/22.10:00:03 (mmr) oid 20912 (vid PASDLY-000489, tag 000081L3) fails mount criteria
2010/01/22.10:00:03 (amh) 11 oid 20912 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != PASDLY-000491
2010/01/22.10:00:03 (mmr) oid 20915 (vid PASDLY-000491, tag 000101L3) fails mount criteria
2010/01/22.10:00:03 (amh) 12 oid 20915 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != PASWLY-000219
2010/01/22.10:00:03 (mmr) oid 20891 (vid PASWLY-000219, tag 000102L3) fails mount criteria
2010/01/22.10:00:03 (amh) 13 oid 20891 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != PASWLY-000220
2010/01/22.10:00:03 (mmr) oid 20892 (vid PASWLY-000220, tag 000103L3) fails mount criteria
2010/01/22.10:00:03 (amh) 14 oid 20892 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (amh) 15 no vid
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != OFFWLY-000151
2010/01/22.10:00:03 (mmr) oid 20739 (vid OFFWLY-000151, tag 000032L3) fails mount criteria
2010/01/22.10:00:03 (amh) 16 oid 20739 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != PASDLY-000484
2010/01/22.10:00:03 (mmr) oid 20903 (vid PASDLY-000484, tag 000106L3) fails mount criteria
2010/01/22.10:00:03 (amh) 17 oid 20903 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (amh) 18 no vid
2010/01/22.10:00:03 (amh) 19 no vid
2010/01/22.10:00:03 (amh) 20 no vid
2010/01/22.10:00:03 (amh) 21 no vid
2010/01/22.10:00:03 (amh) 22 no vid
2010/01/22.10:00:03 (amh) 23 no vid
2010/01/22.10:00:03 (amh) 24 no vid
2010/01/22.10:00:03 (amh) 25 no vid
2010/01/22.10:00:03 (amh) 26 no vid
2010/01/22.10:00:03 (amh) 27 no vid
2010/01/22.10:00:03 (amh) 28 no vid
2010/01/22.10:00:03 (amh) 29 no vid
2010/01/22.10:00:03 (amh) 30 no vid
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != PASWLY-000218
2010/01/22.10:00:03 (mmr) oid 20890 (vid PASWLY-000218, tag 000005L3) fails mount criteria
2010/01/22.10:00:03 (amh) 31 oid 20890 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (amh) 32 cleaning tape
2010/01/22.10:00:03 (amh) end of pass 1 at 2010/01/22.10:00:03
2010/01/22.10:00:03 (amh) beginning pass 2
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != PAS-RMAN-018887
2010/01/22.10:00:03 (mmr) oid 20543 (vid PAS-RMAN-018887, tag 000048L3) fails mount criteria
2010/01/22.10:00:03 (amh) 2 oid 20543 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != PASDLY-000487
2010/01/22.10:00:03 (mmr) oid 20909 (vid PASDLY-000487, tag 000021L3) fails mount criteria
2010/01/22.10:00:03 (amh) 3 oid 20909 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 !=
2010/01/22.10:00:03 (mmr) oid 20416 (000084L3) fails mount criteria
2010/01/22.10:00:03 (amh) 4 oid 20416 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != PASDLY-000486
2010/01/22.10:00:03 (mmr) oid 20908 (vid PASDLY-000486, tag 000054L3) fails mount criteria
2010/01/22.10:00:03 (amh) 5 oid 20908 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != PASDLY-000488
2010/01/22.10:00:03 (mmr) oid 20911 (vid PASDLY-000488, tag 000047L3) fails mount criteria
2010/01/22.10:00:03 (amh) 6 oid 20911 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != PASDLY-000485
2010/01/22.10:00:03 (mmr) oid 20904 (vid PASDLY-000485, tag 000015L3) fails mount criteria
2010/01/22.10:00:03 (amh) 7 oid 20904 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != PASDLY-000483
2010/01/22.10:00:03 (mmr) oid 20889 (vid PASDLY-000483, tag 000008L3) fails mount criteria
2010/01/22.10:00:03 (amh) 8 oid 20889 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != PASDLY-000482
2010/01/22.10:00:03 (mmr) oid 20888 (vid PASDLY-000482, tag 000039L3) fails mount criteria
2010/01/22.10:00:03 (amh) 9 oid 20888 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != PASDLY-000490
2010/01/22.10:00:03 (mmr) oid 20914 (vid PASDLY-000490, tag 000100L3) fails mount criteria
2010/01/22.10:00:03 (amh) 10 oid 20914 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != PASDLY-000489
2010/01/22.10:00:03 (mmr) oid 20912 (vid PASDLY-000489, tag 000081L3) fails mount criteria
2010/01/22.10:00:03 (amh) 11 oid 20912 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != PASDLY-000491
2010/01/22.10:00:03 (mmr) oid 20915 (vid PASDLY-000491, tag 000101L3) fails mount criteria
2010/01/22.10:00:03 (amh) 12 oid 20915 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != PASWLY-000219
2010/01/22.10:00:03 (mmr) oid 20891 (vid PASWLY-000219, tag 000102L3) fails mount criteria
2010/01/22.10:00:03 (amh) 13 oid 20891 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != PASWLY-000220
2010/01/22.10:00:03 (mmr) oid 20892 (vid PASWLY-000220, tag 000103L3) fails mount criteria
2010/01/22.10:00:03 (amh) 14 oid 20892 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 !=
2010/01/22.10:00:03 (mmr) oid 20145 (000065L3) fails mount criteria
2010/01/22.10:00:03 (amh) 15 oid 20145 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != OFFWLY-000151
2010/01/22.10:00:03 (mmr) oid 20739 (vid OFFWLY-000151, tag 000032L3) fails mount criteria
2010/01/22.10:00:03 (amh) 16 oid 20739 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != PASDLY-000484
2010/01/22.10:00:03 (mmr) oid 20903 (vid PASDLY-000484, tag 000106L3) fails mount criteria
2010/01/22.10:00:03 (amh) 17 oid 20903 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 !=
2010/01/22.10:00:03 (mmr) oid 20870 (000107L3) fails mount criteria
2010/01/22.10:00:03 (amh) 18 oid 20870 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 !=
2010/01/22.10:00:03 (mmr) oid 20871 (000108L3) fails mount criteria
2010/01/22.10:00:03 (amh) 19 oid 20871 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 !=
2010/01/22.10:00:03 (mmr) oid 20872 (000109L3) fails mount criteria
2010/01/22.10:00:03 (amh) 20 oid 20872 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 !=
2010/01/22.10:00:03 (mmr) oid 20873 (000110L3) fails mount criteria
2010/01/22.10:00:03 (amh) 21 oid 20873 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 !=
2010/01/22.10:00:03 (mmr) oid 20874 (000111L3) fails mount criteria
2010/01/22.10:00:03 (amh) 22 oid 20874 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 !=
2010/01/22.10:00:03 (mmr) oid 20875 (000112L3) fails mount criteria
2010/01/22.10:00:03 (amh) 23 oid 20875 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 !=
2010/01/22.10:00:03 (mmr) oid 20876 (000113L3) fails mount criteria
2010/01/22.10:00:03 (amh) 24 oid 20876 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 !=
2010/01/22.10:00:03 (mmr) oid 20877 (000114L3) fails mount criteria
2010/01/22.10:00:03 (amh) 25 oid 20877 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 !=
2010/01/22.10:00:03 (mmr) oid 20878 (000115L3) fails mount criteria
2010/01/22.10:00:03 (amh) 26 oid 20878 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 !=
2010/01/22.10:00:03 (mmr) oid 20879 (000116L3) fails mount criteria
2010/01/22.10:00:03 (amh) 27 oid 20879 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 !=
2010/01/22.10:00:03 (mmr) oid 20880 (000117L3) fails mount criteria
2010/01/22.10:00:03 (amh) 28 oid 20880 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 !=
2010/01/22.10:00:03 (mmr) oid 20881 (000118L3) fails mount criteria
2010/01/22.10:00:03 (amh) 29 oid 20881 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 !=
2010/01/22.10:00:03 (mmr) oid 20882 (000119L3) fails mount criteria
2010/01/22.10:00:03 (amh) 30 oid 20882 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != PASWLY-000218
2010/01/22.10:00:03 (mmr) oid 20890 (vid PASWLY-000218, tag 000005L3) fails mount criteria
2010/01/22.10:00:03 (amh) 31 oid 20890 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (amh) 32 cleaning tape
2010/01/22.10:00:03 (amh) end of pass 2 at 2010/01/22.10:00:03
2010/01/22.10:00:03 (amh) beginning pass 3
2010/01/22.10:00:03 (amh) 2 not unlabeled
2010/01/22.10:00:03 (amh) 3 not unlabeled
2010/01/22.10:00:03 (amh) 4 loading
2010/01/22.10:00:52 (mt) qdv__read_label() succeeded; read 65536 bytes
2010/01/22.10:00:52 (atv) automount failed after criteria check - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:52 (amh) 4 automount failed - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:01:26 (amh) 5 not unlabeled
2010/01/22.10:01:26 (amh) 6 not unlabeled
2010/01/22.10:01:26 (amh) 7 not unlabeled
2010/01/22.10:01:26 (amh) 8 not unlabeled
2010/01/22.10:01:26 (amh) 9 not unlabeled
2010/01/22.10:01:26 (amh) 10 not unlabeled
2010/01/22.10:01:26 (amh) 11 not unlabeled
2010/01/22.10:01:26 (amh) 12 not unlabeled
2010/01/22.10:01:26 (amh) 13 not unlabeled
2010/01/22.10:01:26 (amh) 14 not unlabeled
2010/01/22.10:01:26 (amh) 15 loading
2010/01/22.10:02:14 (mt) qdv__read_label() succeeded; read 65536 bytes
2010/01/22.10:02:14 (atv) automount failed after criteria check - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:02:14 (amh) 15 automount failed - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:02:48 (amh) 16 not unlabeled
2010/01/22.10:02:48 (amh) 17 not unlabeled
2010/01/22.10:02:48 (amh) 18 loading
2010/01/22.10:03:31 (mt) qdv__read_label() failed - filemark encountered (OB device mgr)
2010/01/22.10:03:31 (atv) volume unusable for reading - not labeled (it's unlabeled)
2010/01/22.10:03:31 (atv) automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:03:31 (amh) 18 automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:04:04 (amh) 19 loading
2010/01/22.10:04:46 (mt) qdv__read_label() failed - filemark encountered (OB device mgr)
2010/01/22.10:04:47 (atv) volume unusable for reading - not labeled (it's unlabeled)
2010/01/22.10:04:47 (atv) automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:04:47 (amh) 19 automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:05:21 (amh) 20 loading
2010/01/22.10:06:05 (mt) qdv__read_label() failed - filemark encountered (OB device mgr)
2010/01/22.10:06:05 (atv) volume unusable for reading - not labeled (it's unlabeled)
2010/01/22.10:06:05 (atv) automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:06:05 (amh) 20 automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:06:39 (amh) 21 loading
2010/01/22.10:07:23 (mt) qdv__read_label() failed - filemark encountered (OB device mgr)
2010/01/22.10:07:24 (atv) volume unusable for reading - not labeled (it's unlabeled)
2010/01/22.10:07:24 (atv) automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:07:24 (amh) 21 automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:07:58 (amh) 22 loading
2010/01/22.10:08:42 (mt) qdv__read_label() failed - filemark encountered (OB device mgr)
2010/01/22.10:08:43 (atv) volume unusable for reading - not labeled (it's unlabeled)
2010/01/22.10:08:43 (atv) automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:08:43 (amh) 22 automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:09:16 (amh) 23 loading
2010/01/22.10:10:00 (mt) qdv__read_label() failed - filemark encountered (OB device mgr)
2010/01/22.10:10:00 (atv) volume unusable for reading - not labeled (it's unlabeled)
2010/01/22.10:10:00 (atv) automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:10:00 (amh) 23 automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:10:34 (amh) 24 loading
2010/01/22.10:11:18 (mt) qdv__read_label() failed - filemark encountered (OB device mgr)
2010/01/22.10:11:18 (atv) volume unusable for reading - not labeled (it's unlabeled)
2010/01/22.10:11:18 (atv) automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:11:18 (amh) 24 automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:11:52 (amh) 25 loading
2010/01/22.10:12:37 (mt) qdv__read_label() failed - filemark encountered (OB device mgr)
2010/01/22.10:12:37 (atv) volume unusable for reading - not labeled (it's unlabeled)
2010/01/22.10:12:37 (atv) automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:12:37 (amh) 25 automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:13:12 (amh) 26 loading
2010/01/22.10:13:58 (mt) qdv__read_label() failed - filemark encountered (OB device mgr)
2010/01/22.10:13:59 (atv) volume unusable for reading - not labeled (it's unlabeled)
2010/01/22.10:13:59 (atv) automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:13:59 (amh) 26 automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:14:32 (amh) 27 loading
2010/01/22.10:15:18 (mt) qdv__read_label() failed - filemark encountered (OB device mgr)
2010/01/22.10:15:19 (atv) volume unusable for reading - not labeled (it's unlabeled)
2010/01/22.10:15:19 (atv) automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:15:19 (amh) 27 automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:15:53 (amh) 28 loading
2010/01/22.10:16:39 (mt) qdv__read_label() failed - filemark encountered (OB device mgr)
2010/01/22.10:16:39 (atv) volume unusable for reading - not labeled (it's unlabeled)
2010/01/22.10:16:39 (atv) automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:16:39 (amh) 28 automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:17:14 (amh) 29 loading
2010/01/22.10:18:00 (mt) qdv__read_label() failed - filemark encountered (OB device mgr)
2010/01/22.10:18:00 (atv) volume unusable for reading - not labeled (it's unlabeled)
2010/01/22.10:18:00 (atv) automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:18:00 (amh) 29 automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:18:34 (amh) 30 loading
2010/01/22.10:19:15 (mt) qdv__read_label() failed - blank medium encountered (OB device mgr)
2010/01/22.10:19:15 (atv) volume unusable for reading - not labeled (it's blank)
2010/01/22.10:19:15 (atv) automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:19:15 (amh) 30 automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:19:48 (amh) 31 not unlabeled
2010/01/22.10:19:48 (amh) 32 cleaning tape
2010/01/22.10:19:48 (amh) end of pass 3 at 2010/01/22.10:19:48
2010/01/22.10:19:48 (amh) beginning pass 4
2010/01/22.10:19:48 (amh) 2 not unlabeled
2010/01/22.10:19:48 (amh) 3 not unlabeled
2010/01/22.10:19:48 (amh) 4 not unlabeled
2010/01/22.10:19:48 (amh) 5 not unlabeled
2010/01/22.10:19:48 (amh) 6 not unlabeled
2010/01/22.10:19:48 (amh) 7 not unlabeled
2010/01/22.10:19:48 (amh) 8 not unlabeled
2010/01/22.10:19:48 (amh) 9 not unlabeled
2010/01/22.10:19:48 (amh) 10 not unlabeled
2010/01/22.10:19:48 (amh) 11 not unlabeled
2010/01/22.10:19:48 (amh) 12 not unlabeled
2010/01/22.10:19:48 (amh) 13 not unlabeled
2010/01/22.10:19:48 (amh) 14 not unlabeled
2010/01/22.10:19:48 (amh) 15 not unlabeled
2010/01/22.10:19:48 (amh) 16 not unlabeled
2010/01/22.10:19:48 (amh) 17 not unlabeled
2010/01/22.10:19:48 (amh) 18 loading
2010/01/22.10:20:29 (mt) qdv__read_label() failed - filemark encountered (OB device mgr)
2010/01/22.10:20:29 (atv) volume unusable for reading - not labeled (it's unlabeled)
2010/01/22.10:20:29 (atv) automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:20:29 (amh) 18 automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:21:01 (amh) 19 loading
2010/01/22.10:21:44 (mt) qdv__read_label() failed - filemark encountered (OB device mgr)
2010/01/22.10:21:44 (atv) volume unusable for reading - not labeled (it's unlabeled)
2010/01/22.10:21:44 (atv) automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:21:44 (amh) 19 automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:22:19 (amh) 20 loading
2010/01/22.10:23:03 (mt) qdv__read_label() failed - filemark encountered (OB device mgr)
2010/01/22.10:23:03 (atv) volume unusable for reading - not labeled (it's unlabeled)
2010/01/22.10:23:03 (atv) automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:23:03 (amh) 20 automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:23:36 (amh) 21 loading
2010/01/22.10:24:27 (mt) qdv__read_label() failed - filemark encountered (OB device mgr)
2010/01/22.10:24:27 (atv) volume unusable for reading - not labeled (it's unlabeled)
2010/01/22.10:24:27 (atv) automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:24:27 (amh) 21 automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:25:01 (amh) 22 loading
2010/01/22.10:25:45 (mt) qdv__read_label() failed - filemark encountered (OB device mgr)
2010/01/22.10:25:46 (atv) volume unusable for reading - not labeled (it's unlabeled)
2010/01/22.10:25:46 (atv) automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:25:46 (amh) 22 automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:26:39 (amh) 23 loading
2010/01/22.10:27:22 (mt) qdv__read_label() failed - filemark encountered (OB device mgr)
2010/01/22.10:27:23 (atv) volume unusable for reading - not labeled (it's unlabeled)
2010/01/22.10:27:23 (atv) automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:27:23 (amh) 23 automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:27:56 (amh) 24 loading
2010/01/22.10:28:40 (mt) qdv__read_label() failed - filemark encountered (OB device mgr)
2010/01/22.10:28:40 (atv) volume unusable for reading - not labeled (it's unlabeled)
2010/01/22.10:28:40 (atv) automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:28:40 (amh) 24 automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:29:13 (amh) 25 loading
2010/01/22.10:29:56 (mt) qdv__read_label() failed - filemark encountered (OB device mgr)
2010/01/22.10:29:57 (atv) volume unusable for reading - not labeled (it's unlabeled)
2010/01/22.10:29:57 (atv) automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:29:57 (amh) 25 automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:30:31 (amh) 26 loading
2010/01/22.10:31:17 (mt) qdv__read_label() failed - filemark encountered (OB device mgr)
2010/01/22.10:31:18 (atv) volume unusable for reading - not labeled (it's unlabeled)
2010/01/22.10:31:18 (atv) automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:31:18 (amh) 26 automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:31:52 (amh) 27 loading
2010/01/22.10:32:38 (mt) qdv__read_label() failed - filemark encountered (OB device mgr)
2010/01/22.10:32:39 (atv) volume unusable for reading - not labeled (it's unlabeled)
2010/01/22.10:32:39 (atv) automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:32:39 (amh) 27 automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:33:13 (amh) 28 loading
2010/01/22.10:33:59 (mt) qdv__read_label() failed - filemark encountered (OB device mgr)
2010/01/22.10:34:00 (atv) volume unusable for reading - not labeled (it's unlabeled)
2010/01/22.10:34:00 (atv) automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:34:00 (amh) 28 automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:34:34 (amh) 29 loading
2010/01/22.10:35:20 (mt) qdv__read_label() failed - filemark encountered (OB device mgr)
2010/01/22.10:35:20 (atv) volume unusable for reading - not labeled (it's unlabeled)
2010/01/22.10:35:20 (atv) automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:35:20 (amh) 29 automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:35:55 (amh) 30 loading
2010/01/22.10:36:35 (mt) qdv__read_label() failed - blank medium encountered (OB device mgr)
2010/01/22.10:36:36 (atv) volume unusable for reading - not labeled (it's blank)
2010/01/22.10:36:36 (atv) automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:36:36 (amh) 30 automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:37:08 (amh) 31 not unlabeled
2010/01/22.10:37:08 (amh) 32 cleaning tape
2010/01/22.10:37:08 (amh) end of pass 4 at 2010/01/22.10:37:08
2010/01/22.10:37:08 (amh) reporting no match in library
2010/01/22.10:37:08 (amh) end of automount at 2010/01/22.10:37:08 (0x20009624)
2010/01/22.10:37:08 ---
2010/01/22.10:37:08 No volume could be found in px500-1 (for drive tape1) to use for job 8171.
2010/01/22.10:37:08 Volume ID PASWLY-000215 is needed to perform a restore.

Mount/fstab option 'nobootwait'

Similar Messages

Maybe you are looking for