Mount USB, Shutdown,

Hello,
I'm not very new to Linux and switched to arch after using Ubuntu and a little bit gentoo and Mandriva. So I know how to mount beeing root, howto modify confugration files (fstab),
But here is some things that not works, probably a configuration to adjust : I able to mount with the xfce panel since I added a entry in the fstab, but I am unable to write as normal user. This is not useful when I need programs to write (editors). On the others distro this worked the first time. I plugged the key and the Icons appeared on the desktop and where mountable. My user is added to storage and the groups necessary to access usb drives. (May be not all).
2. I'm unable to shutdown the laptop with xfce. I have to enter as root and write halt each time. If needed I will bring the error message of xfce wich says something like unable to access ????????.
3. Some others errors appears during the start of xfce like ???missing on display????
Yes I know I should bring more infos. They will follow if some one answers to the first
Thanks for all.

On a Winbox right now, so I can't check my files. I had the same issue (well both of them actually). As I recall the shutdown and reboot from X, was another policy.fdi for HAL. I'll check back when I get home and boot the archbox - if there is no answer yet I post again.
Yes I think that was it. this is my
/etc/PolicyKit/PolicyKit.conf
<?xml version="1.0" encoding="UTF-8"?> <!-- -*- XML -*- -->
<!DOCTYPE pkconfig PUBLIC "-//freedesktop//DTD PolicyKit Configuration 1.0//EN"
"http://hal.freedesktop.org/releases/PolicyKit/1.0/config.dtd">
<!-- See the manual page PolicyKit.conf(5) for file format -->
<config version="0.1">
<match user="$storage_users">
<match action="org.freedesktop.hal.storage.*">
<return result="yes"/>
</match>
<match action="hal-storage-mount-fixed-extra-options">
<return result="yes" />
</match>
<match action="hal-storage-mount-removable-extra-options">
<return result="yes" />
</match>
</match>
<match user="$power_users">
<match action="org.freedesktop.hal.power-management.shutdown">
<return result="yes"/>
</match>
<match action="org.freedesktop.hal.power-management.reboot">
<return result="yes"/>
</match>
</match>
</config>
Anyway I started at this threadhttp://bbs.archlinux.org/viewtopic.php?id=64951&p=2, but where I found this part
<match user="$power_users">
I'm not sure, but I doubt I thought it up myself , anyway if the "match user" is left out as I understand it anybody(any user I suppose) can just reboot and shutdown at will. Some see this as a problem, so I'd just mention it.
Last edited by XAD (2009-03-11 21:16:40)

Similar Messages

  • [SOLVED][XFCE] Cannot mount usb disks & manage network connections

    Hi guys,
    I'm using XFCE with 3.3.1-1 kernel. Since yesterday I'm not able anymore to automatically mount usb disks,  manage my WiFi networks (networkmanage connects to the default access point but I can't select another AP nor editing my settings). I'm also prompted to type my password when I clik on the shutdown icon;
    So it seems I lost some privileges but I can't figured out why...
    I still belong to the same grousp as before:
    [root@archLaptop sclarckone]# groups sclarckone
    lp wheel games video audio optical storage scanner power users
    Does anybody has an idea where to take a look?
    Thanks
    Last edited by sclarckone (2012-04-15 20:54:38)

    Me too. Start a new thread?
    Edit; Nope, this worked for me https://bbs.archlinux.org/viewtopic.php?id=142110
    Last edited by Glinx (2012-05-25 11:44:47)

  • HAL mounts USB flash devices without support for non-latin characters

    Hey folks!
    How can I make HAL mount USB flash devices with support for German characters such as ä, ö, ü, ß, etc? At the moment there's only a silly question mark instead: http://www12.file-upload.net/20.08.08/3cpcpx.png .
    Can anyone help me?
    Thanks.
    Henrik

    I think it's a bug in KDE4, because no other window manager or desktop environment has such problems. I had it as well, when I used KDE4.0.* for testing and seems like this remained. Do you have a completely german KDE4? Check the system settings!
    A thing comes to my mind, did you check it with konqueror? I guess this bug appears in dolphin, richtig? I schätz mal schon Try it with konqueror, if it doesn't appear there, it's a dolphin thing

  • [SOLVED] How to automatically mount USB drives with custom mount point

    edit:
    Original title was : 'Unable to mount USB disk via /etc/rc.local', but got changed since the /etc/rc.local problem isn't relevant for me anymore.
    Hello,
    Since I am new to this forum, I'll start off with this :
    Thanks to archlinux, its founder and all its contributors, cause this is the operating system (flavour) that annoys me the least.
    The root problem :
    I want to automount USB storage devices to other places than /media/ and without the need for programs that depend on gnome and the like. As I tried some stuff with hald and such, I didn't really get to a nice and easy to configure solution. Any hints in that direction are always welcome.
    For now, automount of known USB storages devices during boot, will do.
    So the things I tried and didnt work :
    1.
    Provide the disk info to /etc/fstab (via the disks UUID and 'auto' filesystem)
    Add 'mount /mountpoint' to /etc/rc.local
    Result : the mount command in rc.local says '... specify filesystem'
    However, after boot, running /etc/rc.local mounts the USB disks correctly.
    2.
    Provide the disk info to /etc/fstab (via the disks UUID and the correct filesystem)
    Add 'mount /mountpoint' to /etc/rc.local
    Result : pc doesn't get through boot process and gives me the 'ctrl-d to reboot or root passwd for maintenance'
    3.
    Provide no disk info in /etc/fstab
    Add the full mount line to /etc/rc.local (mount -t fs /dev/disks/by-uuid/MyUUID /MyMountpoint )
    Result : don't remember the output of the mount execution, but well, it didn't mount
    However, after boot, running /etc/rc.local mounts the USB disks correctly.
    Is there something that isn't loaded at the time of rc.local execution that I need for mounting of USB devices ? Or why else is this failing ?
    Regards,
    BasiK
    Last edited by BasiK (2009-08-28 07:22:50)

    Thanks for the hint hunterthomson, but the pc I will be using it on, is an own-built HTPC/home file server, so there is no way I want to use a graphical file manager to get the usb disks mounted.
    I tried to figure out a little about udev rules, and I got to do what I wanted to do, so thx for pointing me in that direction Mr.Elendig.
    Btw, I am indeed also using auto-sleep/park disks, but this udev way works perfectly.
    I added two rules files to /etc/udev/rules.d/ :
    The first for a known usb disk (with its volume uuid), with a named mountpoint under my media dir /symbiosis/ :
    [basik@plox ~]$ cat /etc/udev/rules.d/80-usb-utopia.rules
    ACTION=="add", KERNEL=="sd[b-z][0-9]", ENV{ID_FS_UUID}=="a59332c2-07ba-4c52-afb5-20e361bdf71a",SYMLINK+="usb-%n", GROUP="storage", NAME="%k"
    ACTION=="add", KERNEL=="sd[b-z][0-9]", ENV{ID_FS_UUID}=="a59332c2-07ba-4c52-afb5-20e361bdf71a",RUN+="/bin/mkdir -p /symbiosis/utopia"
    ACTION=="add", KERNEL=="sd[b-z][0-9]", ENV{ID_FS_UUID}=="a59332c2-07ba-4c52-afb5-20e361bdf71a", RUN+="/bin/mount -t auto -o rw,noauto,sync,dirsync,noexec,nodev,noatime /dev/%k /symbiosis/utopia", OPTIONS="last_rule"
    ACTION=="remove", KERNEL=="sd[b-z][0-9]", ENV{ID_FS_UUID}=="a59332c2-07ba-4c52-afb5-20e361bdf71a", RUN+="/bin/umount -l /symbiosis/utopia", OPTIONS="last_rule"
    The second for unknown usb disks, to mount under the same dir. This is simply taken from the archwiki http://wiki.archlinux.org/index.php/Ude … .26_Tricks
    Make sure these rules are executed after the ones for specific usb disks.
    [basik@plox ~]$ cat /etc/udev/rules.d/usb-disks.rules
    KERNEL=="sd[a-z]", NAME="%k", SYMLINK+="usb%m", GROUP="storage", OPTIONS="last_rule"
    ACTION=="add", KERNEL=="sd[a-z][0-9]", SYMLINK+="usb%n", GROUP="storage", NAME="%k"
    ACTION=="add", KERNEL=="sd[a-z][0-9]", RUN+="/bin/mkdir -p /symbiosis/usb%n"
    ACTION=="add", KERNEL=="sd[a-z][0-9]", RUN+="/bin/mount -t auto -o rw,noauto,sync,dirsync,noexec,nodev,noatime /dev/%k /symbiosis/usb%n", OPTIONS="last_rule"
    ACTION=="remove", KERNEL=="sd[a-z][0-9]", RUN+="/bin/umount -l /symbiosis/usb%n"
    ACTION=="remove", KERNEL=="sd[a-z][0-9]", RUN+="/bin/rmdir /symbiosis/usb%n", OPTIONS="last_rule"
    These may not be the nicest looking udev rules, but it works for what I wanted to do with it.

  • Mounting USB devices in arch guest

    I'm new to virtualbox, but not to linux.  I have been using arch for at least 3 years, so I have some familiarity with it.  I have recently installed arch as a guest OS on virtualbox (on OSX host).  I am having some trouble accessing an attached USB device from the arch guest.  I have defined the virtualbox USB filter for my device, and it appears to work, detecting the identified device and attaching it to the guest (at least as far as virtualbox is concerned).   I can see the device in the virtualbox pull-down menu, and it shows with a "checkmark" next to it, showing (I think) that it has been attached to my arch guest.
    Problem is, I cannot see the device from the arch guest.  no entry in /dev for any USB device.  symptoms are the same whether i insert ther USB device before or after starting the arch guest.  I have HAL and dbus active in my guest.  Also, I have made this work in arch installed natively.  since there is no /dev entry, this might appear to be some form of udev issue?  is there a specific udev setup that I should be aware of for arch as a guest?
    Please help if you can.  I will appreciate all comments and suggestions.
    -dvh

    hey, ive got Arch setup in virtualbox as well, and can mount usb's and cd's etc. (although with some issues i may need to bring up in another thread...) anyways, im assuming you have the PUEL virtualbox and not the OSE one?
    also, your certain that you've mounted the correct USB (on the Virtual Box pull-down menu)? because you may have mounted a USB which was already attached to your host, and not the actual USB?
    just checking, i dont know much about how to fix this issue so im just going at the simple solutions...

  • MOUNT USB STORAGE FOR VM BACKUP

    Hi, I just tried to mount USB Storage to my host with linux version.
    I detect it with fdisk -l and esxcli storage core device list | grep -i usb, after stopping usbarbitrator
    Result:
    /dev/disks #dmesg
    ScsiDevice: 3385: Successfully registered device "mpx.vmhba50:C0:T0:L0" from plugin "NMP" of type 0
    /dev/disks # esxcli storage core device list | grep -i usb
       Display Name: Local USB Direct-Access (mpx.vmhba32:C0:T0:L0)
       Display Name: Local USB Direct-Access (mpx.vmhba50:C0:T0:L0)
    How can I get disk usable for perform a VM backup?

    hooya wrote:
    It's in debugging mode now, which is why I can adb push to the phone. The phone should (and has in the past) mounted USB storage even in debugging mode.
    That wouldn't change the fact that no other USB mass storage will mount either. I'm just using my phone as an example. USB Hard drives and my SD card reader don't show up either, but I can't do a "push" command to those like I can my phone...
    If you are wondering where your post went, I think you meant to hit the 'reply' link rather than the 'report' link.  It happens more often than you would think
    Edit: Oh, I see you already figured that out.
    Last edited by ewaller (2012-07-06 02:30:26)

  • Pcmanfm is "Not Authorized" to mount usb drives

    Hi,
    I recently installed arch linux it's a nice distro but I got a few problem with it.
    The biggest one is that I am actually not able to mount usb drives with pcmanfm this means that I am not able to use my old debian /home so far.
    I tired multiple thinks (some of them are still active)  e.g for example I used to setup a udev rules which wasn't helpful at all (and even after deleting this rule I always see server empty folder in /media (but that's another problem)).
    Any ideas why I am not able to mount encrypted and not encrypted USB drives in arch linux?
    Last edited by 42sec (2011-12-28 13:21:41)

    wonder wrote:paste ck-list-sessions output, uname -r and cat /etc/pam.d/login
    [sec42@archlinux ~]$ ck-list-sessions
    Session1:
    unix-user = '1000'
    realname = ''
    seat = 'Seat1'
    session-type = ''
    active = FALSE
    x11-display = ''
    x11-display-device = ''
    display-device = '/dev/tty1'
    remote-host-name = ''
    is-local = TRUE
    on-since = '2011-12-28T14:28:01.840505Z'
    login-session-id = '1'
    idle-since-hint = '2011-12-28T14:28:32.462384Z'
    [sec42@archlinux ~]$ uname -r
    3.1.5-1-ARCH
    [sec42@archlinux ~]$ cat /etc/pam.d/login
    #%PAM-1.0
    auth required pam_securetty.so
    auth requisite pam_nologin.so
    auth required pam_unix.so nullok
    auth required pam_tally.so onerr=succeed file=/var/log/faillog
    # use this to lockout accounts for 10 minutes after 3 failed attempts
    #auth required pam_tally.so deny=2 unlock_time=600 onerr=succeed file=/var/log/faillog
    account required pam_access.so
    account required pam_time.so
    account required pam_unix.so
    #password required pam_cracklib.so difok=2 minlen=8 dcredit=2 ocredit=2 retry=3
    #password required pam_unix.so sha512 shadow use_authtok
    session required pam_unix.so
    session required pam_env.so
    session required pam_motd.so
    session required pam_limits.so
    session optional pam_mail.so dir=/var/spool/mail standard
    session optional pam_lastlog.so
    session optional pam_loginuid.so
    -session optional pam_ck_connector.so nox11
    -session optional pam_systemd.so

  • [SOLVED] Cannot mount usb (as normal user)

    Hello
    I'm facing this problem for the first time, but can't tell if it came after an update or an unexpected reboot (light went out).
    I'm using latest kde (4.9.2?), and the latest kernel,
    Linux gantz 3.6.6-1-ARCH #1 SMP PREEMPT Mon Nov 5 11:57:22 CET 2012 x86_64 GNU/Linux
    When I plug any usb device, kde ask me what to do. When trying to mount it, either from the kde "mount" plasmoid or from dolphin, I get a "Not authorized" error. Mounting via cli with sudo works fine.
    After doing some research, I found that I need to be in the storage group in order to be able to mount, so I checked, and I was already on the storage group. Next.
    More research sent me to lots of pages talking abour .xinitrc, wich doesn't exists (on my home, at least). Also tons of pages where talking about somethin like "exec ck-launch-session dbus-launch session-manager" (I login via kdm), but the ck-launch-session is not found on my computer either.
    So i'm stucked right now, and don't know how to proceed, any clues? Thanks
    Last edited by mzneverdies (2012-11-10 13:10:09)

    mzneverdies wrote:
    Solved, it was a polkit issue, don't know what caused it, since i didn't touch any config file/dialog.
    after changing allow any to "yes" in this section
    <action id="org.freedesktop.udisks.filesystem-mount">
    <description>Mount a device</description>
    <description xml:lang="da">Montér en enhed</description>
    <message>Authentication is required to mount the device</message>
    <message xml:lang="da">Autorisering er påkrævet for at montere et fil system</message>
    <defaults>
    <allow_any>yes</allow_any>
    <allow_inactive>yes</allow_inactive>
    <allow_active>yes</allow_active>
    </defaults>
    </action>
    on file /usr/share/polkit-1/actions/org.freedesktop.udisks.policy, everything came back to normal, and i'm able to mount usb devices.
    pd @Raynman: removing myself from the storage group did not change anything.
    that's not a fix, it's a crappy workaround. You are not supposed to touch these files, they will be overwritten on an upgrade. My guess is that you are simply not using systemd and therefore you are not in an active logind session. You have to boot with systemd, as mentioned in the news. Everything should then just work out of the box.

  • Can't mount usb devices as a normal user

    Hi.
    I woud like to ask for help. I've been struggling with some "bug" that i came with Arch and usb devices (disks, pendrives). I can't mount it as a normal user using KDE default mounting software (Dolphin, for an exmample). I can mount it only in therminal by using sudo privileages. Is there a way to fix it? I read it, the same problem:
    https://bbs.archlinux.org/viewtopic.php?id=180025
    I tried to check everything according this topic, also with udisk2 archwiki thread but on my desktop machine i just can't mount usb devices without root password. This is how the error looks like for a Dolphin:
    <Over sized Image removed. URL link preserved>
    This is the error, from picture
    Error when trying to use acces to "removable device 7,5GB". System showed: The requested operation has failed. Error checking authorization:
    GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: action org.freedesktop.udisks2.filesystem-mount is not registered (polkit-error-quark, 0)
    Could somebody help me? I even installed udisk mounting tool to mont without root password, added 50-udisks.policy and it just does not work.
    Help.
    I can mount it wit terminal by typing
    sudo mount /dev/sdXY /mnt/usb
    than i'm asked for password and it is mounted. Don't know why i can't mount it without password when connecting usb devices to usb port.
    moderator edit [ewaller]Removed link to over sized image..  Note, you set up a click through thumbnail correctly, but the "Thumbnail" was the same image and was too large
    Last edited by ewaller (2014-09-28 16:37:41)

    Some refresh. I followed this topic:
    https://bbs.archlinux.org/viewtopic.php?id=180025
    with the same problem. I found errors here:
    firekage@arch_desktop ~]$ journalctl -r -u polkit
    -- Logs begin at pią 2014-06-13 18:04:12 CEST, end at czw 2014-12-25 20:15:01 CET. --
    cze 23 15:59:15 arch_desktop polkitd[306]: Unregistered Authentication Agent for unix-session:c1 (system bus name :1.24, object path /org/kde/PolicyKit1/AuthenticationAgent, locale pl_PL.UTF-8) (disconnected from bus)
    cze 23 15:29:59 arch_desktop polkitd[306]: Operator of unix-session:c1 FAILED to authenticate to gain authorization for action org.freedesktop.udisks2.filesystem-mount-system for system-bus-name::1.11 [kdeinit4: kded4 [kdeinit]] (owned by unix-user:firekage)
    cze 20 22:21:05 arch_desktop polkitd[306]: Operator of unix-session:c1 FAILED to authenticate to gain authorization for action org.freedesktop.udisks2.filesystem-mount-system for system-bus-name::1.11 [kdeinit4: kded4 [kdeinit]] (owned by unix-user:firekage)
    cze 20 22:21:03 arch_desktop polkitd[306]: Operator of unix-session:c1 FAILED to authenticate to gain authorization for action org.freedesktop.udisks2.filesystem-mount-system for system-bus-name::1.11 [kdeinit4: kded4 [kdeinit]] (owned by unix-user:firekage)
    cze 20 22:21:01 arch_desktop polkitd[306]: Operator of unix-session:c1 FAILED to authenticate to gain authorization for action org.freedesktop.udisks2.filesystem-mount-system for system-bus-name::1.11 [kdeinit4: kded4 [kdeinit]] (owned by unix-user:firekage)
    cze 20 22:21:00 arch_desktop polkitd[306]: Operator of unix-session:c1 FAILED to authenticate to gain authorization for action org.freedesktop.udisks2.filesystem-mount-system for system-bus-name::1.11 [kdeinit4: kded4 [kdeinit]] (owned by unix-user:firekage)
    cze 20 22:20:59 arch_desktop polkitd[306]: Operator of unix-session:c1 FAILED to authenticate to gain authorization for action org.freedesktop.udisks2.filesystem-mount-system for system-bus-name::1.11 [kdeinit4: kded4 [kdeinit]] (owned by unix-user:firekage)
    cze 20 22:20:58 arch_desktop polkitd[306]: Operator of unix-session:c1 FAILED to authenticate to gain authorization for action org.freedesktop.udisks2.filesystem-mount-system for system-bus-name::1.11 [kdeinit4: kded4 [kdeinit]] (owned by unix-user:firekage)
    cze 20 22:20:06 arch_desktop polkitd[306]: Registered Authentication Agent for unix-session:c1 (system bus name :1.24 [/usr/lib/kde4/libexec/polkit-kde-authentication-agent-1], object path /org/kde/PolicyKit1/AuthenticationAgent, locale pl_PL.UTF-8)
    cze 20 22:19:49 arch_desktop systemd[1]: Started Authorization Manager.
    cze 20 22:19:49 arch_desktop polkitd[306]: Acquired the name org.freedesktop.PolicyKit1 on the system bus
    cze 20 22:19:49 arch_desktop polkitd[306]: Finished loading, compiling and executing 1 rules
    cze 20 22:19:49 arch_desktop polkitd[306]: Loading rules from directory /usr/share/polkit-1/rules.d
    cze 20 22:19:49 arch_desktop polkitd[306]: Loading rules from directory /etc/polkit-1/rules.d
    cze 20 22:19:49 arch_desktop polkitd[306]: Started polkitd version 0.112
    -- Reboot --
    cze 20 22:15:10 arch_desktop systemd[1]: Stopping Authorization Manager...
    cze 20 22:15:08 arch_desktop polkitd[304]: Unregistered Authentication Agent for unix-session:c1 (system bus name :1.23, object path /org/kde/PolicyKit1/AuthenticationAgent, locale pl_PL.UTF-8)
    cze 20 22:02:59 arch_desktop polkitd[304]: Operator of unix-session:c1 FAILED to authenticate to gain authorization for action org.freedesktop.udisks2.filesystem-mount-system for system-bus-name::1.11 [kdeinit4: kded4 [kdeinit]] (owned by unix-user:firekage)
    cze 20 22:02:56 arch_desktop polkitd[304]: Operator of unix-session:c1 FAILED to authenticate to gain authorization for action org.freedesktop.udisks2.filesystem-mount-system for system-bus-name::1.11 [kdeinit4: kded4 [kdeinit]] (owned by unix-user:firekage)
    cze 20 22:02:55 arch_desktop polkitd[304]: Operator of unix-session:c1 FAILED to authenticate to gain authorization for action org.freedesktop.udisks2.filesystem-mount-system for system-bus-name::1.11 [kdeinit4: kded4 [kdeinit]] (owned by unix-user:firekage)
    cze 20 22:02:54 arch_desktop polkitd[304]: Operator of unix-session:c1 FAILED to authenticate to gain authorization for action org.freedesktop.udisks2.filesystem-mount-system for system-bus-name::1.11 [kdeinit4: kded4 [kdeinit]] (owned by unix-user:firekage)
    cze 20 22:02:53 arch_desktop polkitd[304]: Operator of unix-session:c1 FAILED to authenticate to gain authorization for action org.freedesktop.udisks2.filesystem-mount-system for system-bus-name::1.11 [kdeinit4: kded4 [kdeinit]] (owned by unix-user:firekage)
    cze 20 22:00:00 arch_desktop polkitd[304]: Registered Authentication Agent for unix-session:c1 (system bus name :1.23 [/usr/lib/kde4/libexec/polkit-kde-authentication-agent-1], object path /org/kde/PolicyKit1/AuthenticationAgent, locale pl_PL.UTF-8)
    cze 20 21:59:26 arch_desktop systemd[1]: Started Authorization Manager.
    cze 20 21:59:26 arch_desktop polkitd[304]: Acquired the name org.freedesktop.PolicyKit1 on the system bus
    cze 20 21:59:26 arch_desktop polkitd[304]: Finished loading, compiling and executing 1 rules
    cze 20 21:59:26 arch_desktop polkitd[304]: Loading rules from directory /usr/share/polkit-1/rules.d
    cze 20 21:59:26 arch_desktop polkitd[304]: Loading rules from directory /etc/polkit-1/rules.d
    cze 20 21:59:26 arch_desktop polkitd[304]: Started polkitd version 0.112
    cze 20 21:59:26 arch_desktop systemd[1]: Starting Authorization Manager...
    -- Reboot --
    cze 20 21:58:39 arch_desktop systemd[1]: Stopped Authorization Manager.
    cze 20 21:58:39 arch_desktop systemd[1]: Stopping Authorization Manager...
    cze 20 21:55:01 arch_desktop polkitd[306]: Operator of unix-session:c1 FAILED to authenticate to gain authorization for action org.freedesktop.udisks2.filesystem-mount-system for system-bus-name::1.10 [kdeinit4: kded4 [kdeinit]] (owned by unix-user:firekage)
    cze 20 21:54:59 arch_desktop polkitd[306]: Operator of unix-session:c1 FAILED to authenticate to gain authorization for action org.freedesktop.udisks2.filesystem-mount-system for system-bus-name::1.10 [kdeinit4: kded4 [kdeinit]] (owned by unix-user:firekage)
    cze 20 21:54:58 arch_desktop polkitd[306]: Operator of unix-session:c1 FAILED to authenticate to gain authorization for action org.freedesktop.udisks2.filesystem-mount-system for system-bus-name::1.10 [kdeinit4: kded4 [kdeinit]] (owned by unix-user:firekage)
    cze 20 21:54:56 arch_desktop polkitd[306]: Operator of unix-session:c1 FAILED to authenticate to gain authorization for action org.freedesktop.udisks2.filesystem-mount-system for system-bus-name::1.10 [kdeinit4: kded4 [kdeinit]] (owned by unix-user:firekage)
    cze 20 21:54:56 arch_desktop polkitd[306]: Operator of unix-session:c1 FAILED to authenticate to gain authorization for action org.freedesktop.udisks2.filesystem-mount-system for system-bus-name::1.10 [kdeinit4: kded4 [kdeinit]] (owned by unix-user:firekage)
    cze 20 21:47:40 arch_desktop polkitd[306]: Registered Authentication Agent for unix-session:c1 (system bus name :1.21 [/usr/lib/kde4/libexec/polkit-kde-authentication-agent-1], object path /org/kde/PolicyKit1/AuthenticationAgent, locale pl_PL.UTF-8)
    cze 20 21:47:22 arch_desktop systemd[1]: Started Authorization Manager.
    cze 20 21:47:22 arch_desktop polkitd[306]: Acquired the name org.freedesktop.PolicyKit1 on the system bus
    cze 20 21:47:22 arch_desktop polkitd[306]: Finished loading, compiling and executing 1 rules
    cze 20 21:47:22 arch_desktop polkitd[306]: Loading rules from directory /usr/share/polkit-1/rules.d
    cze 20 21:47:22 arch_desktop polkitd[306]: Loading rules from directory /etc/polkit-1/rules.d
    cze 20 21:47:22 arch_desktop polkitd[306]: Started polkitd version 0.112
    cze 20 21:47:22 arch_desktop systemd[1]: Starting Authorization Manager...
    -- Reboot --
    cze 20 19:56:46 arch_desktop systemd[1]: Stopping Authorization Manager...
    cze 20 19:56:45 arch_desktop polkitd[310]: Unregistered Authentication Agent for unix-session:c1 (system bus name :1.21, object path /org/kde/PolicyKit1/AuthenticationAgent, locale pl_PL.UTF-8)
    cze 20 19:55:51 arch_desktop polkitd[310]: Registered Authentication Agent for unix-session:c1 (system bus name :1.21 [/usr/lib/kde4/libexec/polkit-kde-authentication-agent-1], object path /org/kde/PolicyKit1/AuthenticationAgent, locale pl_PL.UTF-8)
    cze 20 19:55:16 arch_desktop systemd[1]: Started Authorization Manager.
    cze 20 19:55:16 arch_desktop polkitd[310]: Acquired the name org.freedesktop.PolicyKit1 on the system bus
    cze 20 19:55:16 arch_desktop polkitd[310]: Finished loading, compiling and executing 1 rules
    cze 20 19:55:16 arch_desktop polkitd[310]: Loading rules from directory /usr/share/polkit-1/rules.d
    cze 20 19:55:16 arch_desktop polkitd[310]: Loading rules from directory /etc/polkit-1/rules.d
    cze 20 19:55:16 arch_desktop polkitd[310]: Started polkitd version 0.112
    cze 20 19:55:16 arch_desktop systemd[1]: Starting Authorization Manager...
    -- Reboot --
    cze 20 19:54:38 arch_desktop systemd[1]: Stopping Authorization Manager...
    cze 20 19:54:13 arch_desktop polkitd[305]: Unregistered Authentication Agent for unix-session:c1 (system bus name :1.21, object path /org/kde/PolicyKit1/AuthenticationAgent, locale pl_PL.UTF-8)
    cze 20 16:47:01 arch_desktop polkitd[305]: Operator of unix-session:c1 FAILED to authenticate to gain authorization for action org.freedesktop.udisks2.filesystem-mount-system for system-bus-name::1.10 [kdeinit4: kded4 [kdeinit]] (owned by unix-user:firekage)
    cze 20 03:02:19 arch_desktop polkitd[305]: Operator of unix-session:c1 FAILED to authenticate to gain authorization for action org.freedesktop.udisks2.filesystem-mount-system for system-bus-name::1.10 [kdeinit4: kded4 [kdeinit]] (owned by unix-user:firekage)
    cze 19 21:32:38 arch_desktop polkitd[305]: Operator of unix-session:c1 FAILED to authenticate to gain authorization for action org.freedesktop.udisks2.filesystem-mount-system for system-bus-name::1.10 [kdeinit4: kded4 [kdeinit]] (owned by unix-user:firekage)
    cze 19 19:25:08 arch_desktop polkitd[305]: Operator of unix-session:c1 FAILED to authenticate to gain authorization for action org.freedesktop.udisks2.filesystem-mount-system for system-bus-name::1.10 [kdeinit4: kded4 [kdeinit]] (owned by unix-user:firekage)
    cze 19 19:24:40 arch_desktop polkitd[305]: Operator of unix-session:c1 FAILED to authenticate to gain authorization for action org.freedesktop.udisks2.filesystem-mount-system for system-bus-name::1.10 [kdeinit4: kded4 [kdeinit]] (owned by unix-user:firekage)
    cze 19 19:24:38 arch_desktop polkitd[305]: Operator of unix-session:c1 FAILED to authenticate to gain authorization for action org.freedesktop.udisks2.filesystem-mount-system for system-bus-name::1.10 [kdeinit4: kded4 [kdeinit]] (owned by unix-user:firekage)
    cze 19 19:24:36 arch_desktop polkitd[305]: Operator of unix-session:c1 FAILED to authenticate to gain authorization for action org.freedesktop.udisks2.filesystem-mount-system for system-bus-name::1.10 [kdeinit4: kded4 [kdeinit]] (owned by unix-user:firekage)
    cze 19 19:24:35 arch_desktop polkitd[305]: Operator of unix-session:c1 FAILED to authenticate to gain authorization for action org.freedesktop.udisks2.filesystem-mount-system for system-bus-name::1.10 [kdeinit4: kded4 [kdeinit]] (owned by unix-user:firekage)
    cze 19 19:24:34 arch_desktop polkitd[305]: Operator of unix-session:c1 FAILED to authenticate to gain authorization for action org.freedesktop.udisks2.filesystem-mount-system for system-bus-name::1.10 [kdeinit4: kded4 [kdeinit]] (owned by unix-user:firekage)
    Could somebody help me? I even checked all rules in /etc/polkit-1/rules.d and /usr/share/polkit-1/actions on my notebook, and all files are the same with the same user permission but on notebook i can mount usb without problem, but on my desktop can't at all.

  • Help me, why i canot auto mount Usb harddisk?

    hi all,
    i have install a new archlinux, but i found i cant auto mount Usb harddisk
    Canot mount volume
    Canot get volume.fstype.alternative
    i have install hal,dbus , ntfs-3g, and add hal,dbus to rc.conf, why it still donnot work?

    yes, i add to storage group:
    [root@myhost figo]# groups figo
    wheel network video audio optical storage power users dbus hal stb-admin figo
    [root@myhost figo]#
    i have confuse, i use dolpin which is kde4 program, i cant mount my usb harddisk, but
    i have nautilus ,it canot mount.
    [root@myhost figo]# hal-device /dev/sdb1
    libhal.c 522 : invalid udi: /dev/sdb1 doesn't startwith '/org/freedesktop/Hal/devices/'.
    (null): (null)
    [root@myhost figo]#
    what is the problem?

  • KDE mount USB device fails

    Hi,
    I am running KDE and having problems mounting USB devices via the KDE Device Notifier in the task bar. When I insert the USB stick there is the normal little popup giving me the option to open the flash drive in dolphin. When I click it, I get the following error:
    "Could not mount the following device"
    Mounting the device via terminal works fine. I also put my user into the "storage" group like the wiki tells me. Still no change.
    Any ideas?

    willtriv wrote:
    Note: slim is ConsoleKit capable since version 1.3.3. Unless you happen to run an old version, you must no longer include ck-launch-session in your .xinitrc or slim.conf login_cmd.
    These kind of changes without notifications to users cause headaches. Someone was kind enough to update the wiki!
    You are my personal hero for today, I was suffering the same problem. Manifests itself as 2 CK sessions listed by ck-launch-session, with the wrong session being marked as active.
    Last edited by crobe2 (2012-06-11 14:28:12)

  • Problem mounting usb stick with ISO installed on it [SOLVED]

    I'm experiencing a weird problem regarding mounting usb sticks. Archlinux stopped auto-mounting usb sticks on my machine, but only those that contains an operating system.  Empty or data usb sticks mount without problem.
    A few weeks or month ago, I don't remember exactly, still everything was all right, but due to updates(?) usb sticks won't auto mount any more.
    I have two arch partitions none of them mount usb sticks anymore with operating systems on them.
    Today, I wanted to test a new operating system and write it on my usb stick, and of course I couldn't because arch didn't mount it. Luckily, on my other partitions a few old distos are still installed – I don't use them anymore for years- I booted them up and they mounted the usb stick without problem; it seems only the up-to-date system have problem handling the usb sticks. I have two Arch system installed on two different partitions, Gnome 3 and Enlightenment, both system are up to date.
    Here are some info:
    [mak@myhost ~]$ dmesg | grep -E "sd[a-z]"
    [ 1.369732] sd 2:0:0:0: [sda] 234441648 512-byte logical blocks: (120 GB/111 GiB)
    [ 1.369819] sd 2:0:0:0: [sda] Write Protect is off
    [ 1.369821] sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
    [ 1.369872] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    [ 1.369924] sd 3:0:0:0: [sdb] 625142448 512-byte logical blocks: (320 GB/298 GiB)
    [ 1.369982] sd 3:0:0:0: [sdb] Write Protect is off
    [ 1.369985] sd 3:0:0:0: [sdb] Mode Sense: 00 3a 00 00
    [ 1.370070] sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    [ 1.371642] sda: sda1 sda2 sda3 sda4 sda5 sda6
    [ 1.372298] sd 2:0:0:0: [sda] Attached SCSI disk
    [ 1.429438] sdb: sdb1 sdb2 sdb3 sdb4 sdb5 sdb6 sdb7 sdb8 sdb9
    [ 1.430159] sd 3:0:0:0: [sdb] Attached SCSI disk
    [ 2.244580] EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: (null)
    [ 2.348031] systemd[1]: Expecting device dev-sdb8.device...
    [ 2.362842] EXT4-fs (sda5): re-mounted. Opts: discard,data=ordered
    [ 3.358252] Adding 2097148k swap on /dev/sdb8. Priority:-1 extents:1 across:2097148k FS
    [ 5.458907] EXT4-fs (sda5): re-mounted. Opts: discard,data=ordered,commit=0
    [ 52.120360] sd 6:0:0:0: [sdc] 15679488 512-byte logical blocks: (8.02 GB/7.47 GiB)
    [ 52.121310] sd 6:0:0:0: [sdc] Write Protect is off
    [ 52.121319] sd 6:0:0:0: [sdc] Mode Sense: 43 00 00 00
    [ 52.122191] sd 6:0:0:0: [sdc] No Caching mode page present
    [ 52.122199] sd 6:0:0:0: [sdc] Assuming drive cache: write through
    [ 52.125825] sd 6:0:0:0: [sdc] No Caching mode page present
    [ 52.125838] sd 6:0:0:0: [sdc] Assuming drive cache: write through
    [ 52.126999] sdc: sdc1 sdc2
    [ 52.131071] sd 6:0:0:0: [sdc] No Caching mode page present
    [ 52.131084] sd 6:0:0:0: [sdc] Assuming drive cache: write through
    [ 52.131093] sd 6:0:0:0: [sdc] Attached SCSI removable disk
    [mak@myhost ~]$
    [root@myhost mak]# fdisk -l
    WARNING: fdisk GPT support is currently new, and therefore in an experimental phase. Use at your own discretion.
    Disk /dev/sda: 120.0 GB, 120034123776 bytes, 234441648 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 label type: gpt
    # Start End Size Type Name
    1 2048 18431 8M BIOS boot parti BIOS boot
    2 18432 56641478 27G Linux filesyste sda2
    3 56641536 113264582 27G Linux filesyste sda3
    4 113264640 169887686 27G Linux filesyste sda4
    5 169887744 226510790 27G Linux filesyste sda5
    6 226510848 234441614 3.8G Linux filesyste Spare
    WARNING: fdisk GPT support is currently new, and therefore in an experimental phase. Use at your own discretion.
    Disk /dev/sdb: 320.1 GB, 320072933376 bytes, 625142448 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 label type: gpt
    # Start End Size Type Name
    1 2048 18431 8M BIOS boot parti Bios boot
    2 18432 54544383 26G Microsoft basic Partition 2
    3 54544384 109070335 26G Linux filesyste Partition 3
    4 109070336 163596287 26G Microsoft basic
    5 163596288 218122239 26G EFI System Partition 5
    6 218122240 272647630 26G Microsoft basic Partition 6
    7 272648192 327174143 26G Linux filesyste Partition 7
    8 327174144 331368447 2G Linux swap Swap
    9 331368448 625142414 140.1G Linux filesyste Storage
    Disk /dev/sdc: 8027 MB, 8027897856 bytes, 15679488 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 label type: dos
    Disk identifier: 0x5fadc669
    Device Boot Start End Blocks Id System
    /dev/sdc1 * 0 4040703 2020352 0 Empty
    /dev/sdc2 4036 38595 17280 ef EFI (FAT-12/16/32)
    Disk /dev/sdc1: 2068 MB, 2068840448 bytes, 4040704 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 label type: dos
    Disk identifier: 0x5fadc669
    Device Boot Start End Blocks Id System
    /dev/sdc1p1 * 0 4040703 2020352 0 Empty
    /dev/sdc1p2 4036 38595 17280 ef EFI (FAT-12/16/32)
    [root@myhost mak]#
    [root@myhost mak]# blkid -o list -c /dev/null
    device fs_type label mount point UUID
    /dev/sda1 (not mounted)
    /dev/sda2 ext4 (not mounted) 0a76a275-1798-495b-aa27-732626029de2
    /dev/sda3 ext4 (not mounted) 0e9363ef-3791-409c-8db9-393385007689
    /dev/sda4 ext4 (not mounted) 8f043c02-8b56-4689-a0ee-ed34ccc6f21f
    /dev/sda5 ext4 / 82699b0e-8fe9-41e2-be13-65c798ed8a73
    /dev/sda6 ext4 (not mounted) 3eaab6bf-2d05-4a7b-a6f7-8675e5f18723
    /dev/sdb1 (not mounted)
    /dev/sdb2 ext4 (not mounted) 17069311-9f14-4430-8298-be48194eb874
    /dev/sdb3 ext4 (not mounted) 2e3b383d-3fa7-40df-b52d-c5d07caf252e
    /dev/sdb4 ext4 (not mounted) 9d9b0656-d4ca-4efa-b6f8-1797bd4ead1f
    /dev/sdb5 ext4 (not mounted) 05abf58a-ae6e-4377-9b3d-d6bacd92226d
    /dev/sdb6 ext4 (not mounted) 8d7c6d55-dc47-471f-84f6-aae8864dfdd7
    /dev/sdb7 ext4 (not mounted) b2155741-8f88-4063-bd1b-39b210004b17
    /dev/sdb8 swap <swap> 97cf7cdf-299c-4e0d-a438-c8b79766699c
    /dev/sdb9 ext4 (not mounted) 426648fd-98f5-4fb0-9114-bdbdfea9047c
    /dev/sdc1 udf Sabayon GNOME (not mounted) 2013-07-29-13-08-13-27
    /dev/sdc2 vfat (not mounted) CF68-C2B6
    [root@myhost mak]#
    Thanks for the help.
    jmak
    Last edited by jmak (2013-08-14 00:12:54)

    cfr wrote:
    What is sdc1p? Is that another USB stick? It seems to have an equally weird partition map.
    By the way, you can't create an Arch USB bootable in EFI mode with dd. Obviously don't know about sabayon.
    EDIT: Did you dd to the disk or to a partition? What command exactly did you use? Because it almost looks as if you did something like dd once and create one thing and then dd over the top of one of the partition so you've got a partition which itself has a partition map. Not sure that's possible but it sure looks weird.
    I would wipe the key and start over.
    I don't know what is that. It is a partition on the same usb stick, it was the “dd” that made that partition automatically, I guess. When I burn images into usb, I always use this command:
    # dd bs=4M if=/path/to/archlinux.iso of=/dev/sdx && sync
    I used this when burned Sabayon and it works perfectly.
    The problem is that Arch can't auto-mount its own installation usb either. I put the arch install usb in and I get the following output:
    [root@myhost mak]# blkid -o list -c /dev/null
    device fs_type label mount point UUID
    /dev/sda1 (not mounted)
    /dev/sda2 ext4 (not mounted) 0a76a275-1798-495b-aa27-732626029de2
    /dev/sda3 ext4 (not mounted) 0e9363ef-3791-409c-8db9-393385007689
    /dev/sda4 ext4 (not mounted) 8f043c02-8b56-4689-a0ee-ed34ccc6f21f
    /dev/sda5 ext4 / 82699b0e-8fe9-41e2-be13-65c798ed8a73
    /dev/sda6 ext4 (not mounted) 3eaab6bf-2d05-4a7b-a6f7-8675e5f18723
    /dev/sdb1 (not mounted)
    /dev/sdb2 ext4 (not mounted) 17069311-9f14-4430-8298-be48194eb874
    /dev/sdb3 ext4 (not mounted) 2e3b383d-3fa7-40df-b52d-c5d07caf252e
    /dev/sdb4 ext4 (not mounted) 9d9b0656-d4ca-4efa-b6f8-1797bd4ead1f
    /dev/sdb5 ext4 (not mounted) 05abf58a-ae6e-4377-9b3d-d6bacd92226d
    /dev/sdb6 ext4 (not mounted) 8d7c6d55-dc47-471f-84f6-aae8864dfdd7
    /dev/sdb7 ext4 (not mounted) b2155741-8f88-4063-bd1b-39b210004b17
    /dev/sdb8 swap <swap> 97cf7cdf-299c-4e0d-a438-c8b79766699c
    /dev/sdb9 ext4 /run/media/mak/426648fd-98f5-4fb0-9114-bdbdfea9047c 426648fd-98f5-4fb0-9114-bdbdfea9047c
    /dev/sdc1 iso9660 ARCH_201305 (not mounted) 2013-05-01-07-12-33-00
    [root@myhost mak]#
    It doesn't appear in nautilus side panel.
    Last edited by jmak (2013-08-13 02:44:45)

  • Domain User cannot mount USB or shutdown

    Hello,
    after a few weeks when I installed Samba and joined a Domain I realized that when I put in an USB stick my file manager tells me that this operation is not allowed. So I have to mount the USB stick with sudo. Did I make something wrong in the PAM configuration? My domain user is in the local group of storage and power ...
    It would be great if some one can give me some direction where to look for the problem.
    Regards
    Debellator

    Thanks for your fast response.
    When there is a kernel update I do a restart.
    I do not use a login manager.
    #!/bin/sh
    # ~/.xinitrc
    # Executed by startx (run your window manager from here)
    if [ -d /etc/X11/xinit/xinitrc.d ]; then
    for f in /etc/X11/xinit/xinitrc.d/*; do
    [ -x "$f" ] && . "$f"
    done
    unset f
    fi
    setxkbmap de
    # exec gnome-session
    # exec startkde
    # exec startxfce4
    # ...or the Window Manager of your choice
    exec ck-launch-session startlxde

  • [solved] Permissions issue - can't mount usb device as user, just root

    In my last post I learned how to mount a secondary HDD from the command line.  Problem is I did it as root. Now I have xfce4 running and I need mount permissions as user.
    Here's my fstab:
    [dennis@archlinux media]$ cat /etc/fstab
    # /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/sdb /media/disk0 ext4 rw,user,noauto 0 0
    /dev/sdb1 /media/disk1 ext4 rw,user,noauto 0 0
    /dev/sdb3 /media/disk3 ext4 rw.user,noauto 0 0
    UUID=1f813152-615e-41a1-b3e7-ce2b5b6836a5 / ext4 defaults 0 1
    UUID=aba18f0f-5f37-4ab0-8241-5a271dc3dddb swap swap defaults 0 0
    UUID=c4332450-df9e-4571-8256-8e1b10b4d162 /home ext4 defaults 0 1
    UUID=f0a6eca0-9668-454b-b444-371566663510 /boot ext2 defaults 0 1
    [dennis@archlinux media]$
    ....and these are the system messages I got when I plugged the device:
    Unable to mount "74G Volume":
    mount: only root can mount /dev/sdb3 on /media/disk3
    Unable to mount "4G Volume":
    mount: must be superuser to use mount
    What do I do here?
    Last edited by dennola4 (2010-06-28 00:56:51)

    Karol:
    # Cmnd alias specification
    # Defaults specification
    # Runas alias specification
    # User privilege specification
    root ALL=(ALL) ALL
    dennis ALL=(ALL) ALL
    %users ALL=(ALL) NOPASSWD: /usr/sbin/pppd
    %users ALL=(ALL) NOPASSWD: /usr/sbin/hibernate
    %users ALL=(ALL) NOPASSWD: /usr/sbin/standby
    # Uncomment to allow people in group wheel to run all commands
    %wheel ALL=(ALL) ALL
    # Same thing without a password
    %wheel ALL=(ALL) NOPASSWD: ALL
    # Samples
    # %users ALL=/sbin/mount /cdrom,/sbin/umount /cdrom
    # %users localhost=/sbin/shutdown -h now
    Mr. Elendig:
    Why not use automounting instead?
    To install Arch packages I needed an Internet connection, which required use of a Sierra Wireless card, which required chatscripts stored on another filesystem.  In my first Arch forum post ever, the one preceding this one, I learned to mount a device by creating a mountpoint in /media then invoking #mount.  After installing all packages and creating a user name, I signed on with xfce4 and plugged in the usb device again.  It didn't mount.  So I did it manually using sudo.  Since that worked I had the idea that adding the mountpoints to /etc/fstab would be useful, so I did.  When that didn't work I decided to just ask for help.
    So sure, I'm down for some automounting action.  How do I do it?

  • Systemd (auto)mount USB fails due to fsck

    Hi,
    I am trying to get 'hotplugging' functionality working for usb storage devices with systemd with the ultimate goal of running a backup service via systemd which will require certain devices and mounts to be active.
    After a few searchers, I decided the approach of adding the external storage device to fstab with a couple systemd options
    Here's the relevant line in my fstab
    # USB for data where CoW not desired
    UUID=964cc231-af3f-49ef-94f3-f73ffd551fda /media/storage_nocow ext4 noauto,x-systemd.automount 0 2
    That worked nicely. The device is mounted anytime the mountpoint is requested (e.g. by cd'ing into that directory) provided that the device has not been unmounted.
    If the device has been unmounted (with systemctl stop media-storage_nocow.mount) or removed, and then plugged back in, the mount unit fails with very vague error message. I looked around but didn't find anything definitive on how to address the issue
    systemctl status media-storage_nocow.mount | tail -n 2
    #May 28 11:40:57 archLenFlex systemd[1]: Dependency failed for /media/storage_nocow.
    #May 28 11:40:57 archLenFlex systemd[1]: Job media-storage_nocow.mount/start failed with result 'dependency'.
    I checked that the device is active
    systemctl status --full dev-disk-by\\x2dlabel-CORSAIR64.device
    ● dev-disk-by\x2dlabel-CORSAIR64.device - Voyager_VEGA CORSAIR64
    Follow: unit currently follows state of sys-devices-pci0000:00-0000:00:14.0-usb3-3\x2d1-3\x2d1:1.0-host4-target4:0:0-4:0:0:0-block-sdb-sdb1.device
    Loaded: loaded
    Active: active (plugged) since Thu 2015-05-28 15:43:36 EDT; 2h 2min ago
    Device: /sys/devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1:1.0/host4/target4:0:0/4:0:0:0/block/sdb/sdb1
    The messages from journalctl were of little help. I dug around into the unit files which are generated from fstab and found that the mount requires a couple services
    RequiresOverridable=systemd-fsck@dev-disk-by\x2duuid-964cc231\x2daf3f\x2d49ef\x2d94f3\x2df73ffd551fda.service
    After=systemd-fsck@dev-disk-by\x2duuid-964cc231\x2daf3f\x2d49ef\x2d94f3\x2df73ffd551fda.service
    [Mount]
    What=/dev/disk/by-uuid/964cc231-af3f-49ef-94f3-f73ffd551fda
    Where=/media/storage_nocow
    Type=ext4
    Options=nofail,rw,noauto,x-systemd.automount
    the requires/after units failed
    systemctl status --full systemd-fsck@dev-disk-by\\x2duuid-964cc231\\x2daf3f\\x2d49ef\\x2d94f3\\x2df73ffd551fda.service
    ● systemd-fsck@dev-disk-by\x2duuid-964cc231\x2daf3f\x2d49ef\x2d94f3\x2df73ffd551fda.service - File System Check on /dev/disk/by-uuid/964cc231-af3f-49ef-94f3-f73ffd551fda
    Loaded: loaded (/usr/lib/systemd/system/[email protected]; static; vendor preset: disabled)
    Active: inactive (dead) since Thu 2015-05-28 15:43:26 EDT; 30min ago
    Docs: man:[email protected](8)
    Process: 797 ExecStart=/usr/lib/systemd/systemd-fsck %f (code=exited, status=0/SUCCESS)
    Main PID: 797 (code=exited, status=0/SUCCESS)
    May 28 15:31:27 archLenFlex systemd[1]: Starting File System Check on /dev/disk/by-uuid/964cc231-af3f-49ef-94f3-f73ffd551fda...
    May 28 15:31:27 archLenFlex systemd-fsck[797]: CORSAIR64: clean, 12/3784704 files, 283568/15123984 blocks
    May 28 15:31:27 archLenFlex systemd[1]: Started File System Check on /dev/disk/by-uuid/964cc231-af3f-49ef-94f3-f73ffd551fda.
    May 28 15:43:26 archLenFlex systemd[1]: Stopped File System Check on /dev/disk/by-uuid/964cc231-af3f-49ef-94f3-f73ffd551fda.
    May 28 15:43:26 archLenFlex systemd[1]: Stopping File System Check on /dev/disk/by-uuid/964cc231-af3f-49ef-94f3-f73ffd551fda...
    May 28 15:45:22 archLenFlex systemd[1]: Dependency failed for File System Check on /dev/disk/by-uuid/964cc231-af3f-49ef-94f3-f73ffd551fda.
    May 28 15:45:22 archLenFlex systemd[1]: Job systemd-fsck@dev-disk-by\x2duuid-964cc231\x2daf3f\x2d49ef\x2d94f3\x2df73ffd551fda.service/start failed with result 'dependency'.
    Looking further into those units - the fsck service has a couple dependencies:
    After=%i.device systemd-fsck-root.service local-fs-pre.target
    Before=shutdown.target
    [Service]
    Type=oneshot
    RemainAfterExit=yes
    ExecStart=/usr/lib/systemd/systemd-fsck %f
    StandardOutput=journal+console
    TimeoutSec=0
    The only one that failed was the sytemd-fsck-root.service - the other two were active/successful.
    ● systemd-fsck-root.service - File System Check on Root Device
    Loaded: loaded (/usr/lib/systemd/system/systemd-fsck-root.service; static; vendor preset: disabled)
    Active: inactive (dead)
    Docs: man:systemd-fsck-root.service(8)
    So, I figured I can skip the fsck in fstab and it should work. This is the case, with the following fstab line for the device,
    UUID=964cc231-af3f-49ef-94f3-f73ffd551fda /media/storage_nocow ext4 noauto,x-systemd.automount 0 0
    From there, requesting the mountpoint activates the mount via the automount, provided the mount unit was stopped but the device wasn't unplugged. If the device is unplugged, it is necessary stop the mount unit and reload the systemctl daemon.
    I think it is preferable to have the device fsck'd.
    So can anyone advise why the fsck is failing and how to get the mount to work while keeping the fsck option in fstab? Why does the usb device mount even require the root fsck? I would think it should only require its own fsck.
    Thanks in advance.
    Last edited by akpol (2015-05-28 22:16:44)

    Hi,
    I am trying to get 'hotplugging' functionality working for usb storage devices with systemd with the ultimate goal of running a backup service via systemd which will require certain devices and mounts to be active.
    After a few searchers, I decided the approach of adding the external storage device to fstab with a couple systemd options
    Here's the relevant line in my fstab
    # USB for data where CoW not desired
    UUID=964cc231-af3f-49ef-94f3-f73ffd551fda /media/storage_nocow ext4 noauto,x-systemd.automount 0 2
    That worked nicely. The device is mounted anytime the mountpoint is requested (e.g. by cd'ing into that directory) provided that the device has not been unmounted.
    If the device has been unmounted (with systemctl stop media-storage_nocow.mount) or removed, and then plugged back in, the mount unit fails with very vague error message. I looked around but didn't find anything definitive on how to address the issue
    systemctl status media-storage_nocow.mount | tail -n 2
    #May 28 11:40:57 archLenFlex systemd[1]: Dependency failed for /media/storage_nocow.
    #May 28 11:40:57 archLenFlex systemd[1]: Job media-storage_nocow.mount/start failed with result 'dependency'.
    I checked that the device is active
    systemctl status --full dev-disk-by\\x2dlabel-CORSAIR64.device
    ● dev-disk-by\x2dlabel-CORSAIR64.device - Voyager_VEGA CORSAIR64
    Follow: unit currently follows state of sys-devices-pci0000:00-0000:00:14.0-usb3-3\x2d1-3\x2d1:1.0-host4-target4:0:0-4:0:0:0-block-sdb-sdb1.device
    Loaded: loaded
    Active: active (plugged) since Thu 2015-05-28 15:43:36 EDT; 2h 2min ago
    Device: /sys/devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1:1.0/host4/target4:0:0/4:0:0:0/block/sdb/sdb1
    The messages from journalctl were of little help. I dug around into the unit files which are generated from fstab and found that the mount requires a couple services
    RequiresOverridable=systemd-fsck@dev-disk-by\x2duuid-964cc231\x2daf3f\x2d49ef\x2d94f3\x2df73ffd551fda.service
    After=systemd-fsck@dev-disk-by\x2duuid-964cc231\x2daf3f\x2d49ef\x2d94f3\x2df73ffd551fda.service
    [Mount]
    What=/dev/disk/by-uuid/964cc231-af3f-49ef-94f3-f73ffd551fda
    Where=/media/storage_nocow
    Type=ext4
    Options=nofail,rw,noauto,x-systemd.automount
    the requires/after units failed
    systemctl status --full systemd-fsck@dev-disk-by\\x2duuid-964cc231\\x2daf3f\\x2d49ef\\x2d94f3\\x2df73ffd551fda.service
    ● systemd-fsck@dev-disk-by\x2duuid-964cc231\x2daf3f\x2d49ef\x2d94f3\x2df73ffd551fda.service - File System Check on /dev/disk/by-uuid/964cc231-af3f-49ef-94f3-f73ffd551fda
    Loaded: loaded (/usr/lib/systemd/system/[email protected]; static; vendor preset: disabled)
    Active: inactive (dead) since Thu 2015-05-28 15:43:26 EDT; 30min ago
    Docs: man:[email protected](8)
    Process: 797 ExecStart=/usr/lib/systemd/systemd-fsck %f (code=exited, status=0/SUCCESS)
    Main PID: 797 (code=exited, status=0/SUCCESS)
    May 28 15:31:27 archLenFlex systemd[1]: Starting File System Check on /dev/disk/by-uuid/964cc231-af3f-49ef-94f3-f73ffd551fda...
    May 28 15:31:27 archLenFlex systemd-fsck[797]: CORSAIR64: clean, 12/3784704 files, 283568/15123984 blocks
    May 28 15:31:27 archLenFlex systemd[1]: Started File System Check on /dev/disk/by-uuid/964cc231-af3f-49ef-94f3-f73ffd551fda.
    May 28 15:43:26 archLenFlex systemd[1]: Stopped File System Check on /dev/disk/by-uuid/964cc231-af3f-49ef-94f3-f73ffd551fda.
    May 28 15:43:26 archLenFlex systemd[1]: Stopping File System Check on /dev/disk/by-uuid/964cc231-af3f-49ef-94f3-f73ffd551fda...
    May 28 15:45:22 archLenFlex systemd[1]: Dependency failed for File System Check on /dev/disk/by-uuid/964cc231-af3f-49ef-94f3-f73ffd551fda.
    May 28 15:45:22 archLenFlex systemd[1]: Job systemd-fsck@dev-disk-by\x2duuid-964cc231\x2daf3f\x2d49ef\x2d94f3\x2df73ffd551fda.service/start failed with result 'dependency'.
    Looking further into those units - the fsck service has a couple dependencies:
    After=%i.device systemd-fsck-root.service local-fs-pre.target
    Before=shutdown.target
    [Service]
    Type=oneshot
    RemainAfterExit=yes
    ExecStart=/usr/lib/systemd/systemd-fsck %f
    StandardOutput=journal+console
    TimeoutSec=0
    The only one that failed was the sytemd-fsck-root.service - the other two were active/successful.
    ● systemd-fsck-root.service - File System Check on Root Device
    Loaded: loaded (/usr/lib/systemd/system/systemd-fsck-root.service; static; vendor preset: disabled)
    Active: inactive (dead)
    Docs: man:systemd-fsck-root.service(8)
    So, I figured I can skip the fsck in fstab and it should work. This is the case, with the following fstab line for the device,
    UUID=964cc231-af3f-49ef-94f3-f73ffd551fda /media/storage_nocow ext4 noauto,x-systemd.automount 0 0
    From there, requesting the mountpoint activates the mount via the automount, provided the mount unit was stopped but the device wasn't unplugged. If the device is unplugged, it is necessary stop the mount unit and reload the systemctl daemon.
    I think it is preferable to have the device fsck'd.
    So can anyone advise why the fsck is failing and how to get the mount to work while keeping the fsck option in fstab? Why does the usb device mount even require the root fsck? I would think it should only require its own fsck.
    Thanks in advance.
    Last edited by akpol (2015-05-28 22:16:44)

Maybe you are looking for

  • I am having problem when I am installing magic bullet look 1.4 please help

    Hi, I am having an issue with my Red giant magic bullet look 1.4 When I am installing this plug ins I receive a message saying: your graphic card did not meet the minimum requirement but actually my graphic card did meet the requirement and I was loo

  • Iphone cannot be synced message

    I finally broke down and synced my iphone to get 3.1.3 but when I did it synced the new firmware but then at the end it gave me this message, "The Iphone cannot be synced. The required file cannot be found". I reset it using a backup but still the sa

  • What is the problem with this code ? Race condition??

    Guys, The idea behind the attached code is quite simple. I have a 2D parent array. First, I print a subset of this array into a table control (based on a sensor selection). Now, I want edit the numbers in the table. I need the changes to be reflected

  • If pictures are deleted and not backed up can they be retreived from phone

    can you retreive photos from and I phone 5 if they been deleted and not backed to a computer?

  • Itunes volume not staying where I set it

    I have iTunes 10.6.0.40 on my Windows 7 PC and everytime I turn the volume down with the slider in the top left of the iTunes window in about 10 seconds the volume is back up to 100% but the slider didn't move at all. Is there a setting I need to cha