Systemd crypttab issue

Prior to rolling over to systemd I used the following line in my crypttab:
cryptodev /dev/sdb1 /dev/sdc1:vfat:/unlockfile luks
With systemd that seems to be broken, so I tried mounting the usb stick(sdc1) in fstab as /mnt/usb then mod the cryptab to:
cryptodev /dev/sdb1 /mnt/usb/unlockfile luks
However this does not work because the [email protected] script runs prior to mounts. I attempted to add "Requires=mnt-usb.mount" and "After=mnt-usb.mount" in /run/systemd/generator/[email protected] but I believe this is a generated file. My first thought is to move the .service to the /etc/systemd/service folder and perform edits there, then remove the crypttab all together. Thoughts, or an easier solution?
Thanks,
Jason

jayray wrote:My first thought is to move the .service to the /etc/systemd/service folder and perform edits there, then remove the crypttab all together. Thoughts, or an easier solution?
This sounds like the correct solution, though no need to remove crypttab, the copy in /etc will take precedence over the generated one. We should probably improve the crypttab generator to add this automatically. In the meantime: I'm not sure why this does not work for you without more info. After "systemctl daemon-reload" with the modified file in place, can you paste "systemctl show [email protected]" ?

Similar Messages

  • Systemd migration issue

    I'm having some serious issues migrating a machine to systemd. 
    The first error I had was with dbus refusing to start, apparently when I did my upgrade this morning it did not add the dbus user/group. I created the user and then dbus.service starts but it crashes / gets restarted about every 30 seconds, here is the repeated entry in the journal:
    May 28 16:29:07 brain dbus-daemon[1827]: dbus[1827]: [system] Failed to activate service 'org.freedesktop.Avahi': timed out
    May 28 16:29:07 brain dbus-daemon[1827]: dbus[1827]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
    May 28 16:29:07 brain dbus-daemon[1827]: process 1827: arguments to dbus_message_set_reply_serial() were incorrect, assertion "reply_serial != 0" failed in file dbus-message.c line 1070.
    May 28 16:29:07 brain dbus-daemon[1827]: This is normally a bug in some application using the D-Bus library.
    May 28 16:29:07 brain dbus-daemon[1827]: D-Bus not built with -rdynamic so unable to print a backtrace
    May 28 16:29:07 brain systemd[1]: dbus.service: main process exited, code=killed, status=6/ABRT
    May 28 16:29:07 brain systemd[1]: Unit dbus.service entered failed state.
    May 28 16:29:07 brain systemd[1]: Starting D-Bus System Message Bus...
    May 28 16:29:07 brain systemd[1]: Started D-Bus System Message Bus.
    May 28 16:29:08 brain systemd[1]: RequestName() failed: Access denied
    May 28 16:29:08 brain dbus-daemon[1829]: dbus[1829]: [system] Activating systemd to hand-off: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
    I followed the wiki but when I try setting the hostname I get this:
    hostnamectl set-hostname brain
    Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: The connection is closed (g-io-error-quark, 18)
    Failed to issue method call: Connection was disconnected before a reply was received
    Additionally, systemd-analyze does not work (Failed to issue method call: Connection was disconnected before a reply was received) and systemd-logind.service shows as failed
    May 28 16:32:56 brain systemd-logind[1873]: Failed to fully start up daemon: Input/output error
    May 28 16:32:56 brain systemd[1]: systemd-logind.service: main process exited, code=exited, status=1/FAILURE
    May 28 16:32:56 brain systemd[1]: Failed to start Login Service.
    -- Subject: Unit systemd-logind.service has failed
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/be02cf6855d2428ba40df7e9d022f03d
    -- Unit systemd-logind.service has failed.
    -- The result is failed.
    May 28 16:32:56 brain systemd[1]: Unit systemd-logind.service entered failed state.
    May 28 16:32:56 brain systemd[1]: systemd-logind.service holdoff time over, scheduling restart.
    May 28 16:32:56 brain systemd[1]: Stopping Login Service...
    -- Subject: Unit systemd-logind.service has begun shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit systemd-logind.service has begun shutting down.
    May 28 16:32:56 brain systemd[1]: Starting Login Service...
    -- Subject: Unit systemd-logind.service has begun with start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit systemd-logind.service has begun starting up.
    May 28 16:32:56 brain systemd[1]: systemd-logind.service start request repeated too quickly, refusing to start.
    May 28 16:32:56 brain systemd[1]: Failed to start Login Service.
    -- Subject: Unit systemd-logind.service has failed
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/be02cf6855d2428ba40df7e9d022f03d
    -- Unit systemd-logind.service has failed.
    I have tried uninstalling and re-installing dbus-core, and 'cat /proc/1/comm' shows systemd. I've searched google for a few hours and haven't found anything!

    If you are still using dbus-core, then your system is out of date.  Did you first update your entire system before trying to switch to systemd?  I kind of suspect you are just trying to install only the packages you need and do the update... if this is what you are doing then it is bound to cause problems.

  • [SOLVED] Systemd locale issue

    I have a recent fresh install of Arch, it's a "pure" systemd installation.
    I'm using XFCE4 and Terminal.
    I can't manage get proper unicode support, only in the terminal: I'm always stuck on POSIX.
    All of this code is run as root.
    $ grep -v '#' /etc/locale.gen
    en_US.UTF-8 UTF-8
    fr_FR.UTF-8 UTF-8
    $ locale-gen
    Generating locales...
    en_US.UTF-8... done
    fr_FR.UTF-8... done
    Generation complete.
    $ locale -a
    C
    en_US.utf8
    fr_FR.utf8
    POSIX
    $ cat /etc/locale.conf
    LANG="en_US.UTF-8"
    LC_COLLATE="C"
    $ locale
    LANG=
    LC_CTYPE="POSIX"
    LC_NUMERIC="POSIX"
    LC_TIME="POSIX"
    LC_COLLATE="POSIX"
    LC_MONETARY="POSIX"
    LC_MESSAGES="POSIX"
    LC_PAPER="POSIX"
    LC_NAME="POSIX"
    LC_ADDRESS="POSIX"
    LC_TELEPHONE="POSIX"
    LC_MEASUREMENT="POSIX"
    LC_IDENTIFICATION="POSIX"
    LC_ALL=
    Pressing my "é" key on the keyboard just produces a "?" in the terminal.
    I don't have this issue in any other application.
    I have also tried the following:
    $ export LANG=en_US.utf8
    $ locale
    LANG=en_US.utf8
    LC_CTYPE="en_US.utf8"
    LC_NUMERIC="en_US.utf8"
    LC_TIME="en_US.utf8"
    LC_COLLATE="en_US.utf8"
    LC_MONETARY="en_US.utf8"
    LC_MESSAGES="en_US.utf8"
    LC_PAPER="en_US.utf8"
    LC_NAME="en_US.utf8"
    LC_ADDRESS="en_US.utf8"
    LC_TELEPHONE="en_US.utf8"
    LC_MEASUREMENT="en_US.utf8"
    LC_IDENTIFICATION="en_US.utf8"
    LC_ALL=
    But I still can't input accented characters.
    All of the following lines don't help:
    $ export LANG="en_US.utf8"
    $ export LANG=en_US.UTF-8
    $ export LANG="en_US.UTF-8"
    Rebooting multiple times between modifications has not helped.
    Help would be greatly appreciated !
    Thanks.
    Last edited by qdm (2012-09-15 15:32:24)

    qdm wrote:
    Thanks ! I googled this issue for a while and did not find any relevant information.
    The solution that worked was in the comments to that post:
    I had to force installing the filesystem package which now provides locale.sh and after that I proceeded with installing systemd-sysvcompat which deleted the same file.
    Reinstalling filesystem solves the issue.
    Thank you, that problem was driving me nuts, was almoust a showstopper to systemd for me.

  • Systemd --user issues

    Hi,
    upon running
    systemctl --user status
    I get
    Failed to read server status: Input/output error
    Here are my dumps of systemctl status user@$UID and journalctl -b _SYSTEMD_UNIT=[email protected] I know pulseaudio is not starting correctly, I probably still have it set up to start the service instead of the socket. Wanted to change that but --user is not working at all. Any tips welcome!

    mauritiusdadd wrote:
    Is that the only message displayed? Is there anything interesting in the journal? What is the output of the following commands?
    systemctl status dbus.service
    systemctl status --no-pager
    systemctl --state failed --no-pager
    Here is dbus, systemctl status --no-pager and failed. Tor fails with this, so it doesn't seem to be related.
    karol wrote:https://bbs.archlinux.org/viewtopic.php?id=186232 ?
    I read the thing and at the end he says it was a conflicting symlink. How can I find that? I don't know from logs what is causing the issue and browsing through folders I don't see anything specific. Tor is the only failing service and there is just 1 symlink pointing at the correct place. For pulseaudio I don't see a symlink at all.

  • Systemd startup issues

    after following the wiki step-for-step on switching over to systemd, i can't seem to get it to work. every time i try to boot with it it gives me an error about the mounting of the root partition being successful but being unable to find /boot/systemd. i then get dumped to a rescue shell, where i can mount /boot normally but have no systemd file/folder in boot nor do i see any mention of said folder through various google searches. systemctl and journalctl, the commands used to interact with systemd are unusable from this prompt so i'm not sure how to get any further info or how it could be useful. after mounting boot and having no success, i exit the shell and bam kernel panic. i've heard all this raving of crazy boot times with it, etc. and am obviously intrigued so any knowledge/advice on the situation would be appreciated.
    cheers.

    Odd, there is no (nor should there be) any /boot/systemd.
    Are you by chance at the point where you add "init=/bin/systemd" to your bootloader kernel line?  Could you have made a typo and put init=/boot/systemd?  Or perhaps if you didn't put any path to systemd *perhaps* /boot/ would be inferred as that may be the current working directory when init is called.
    (edit: beat by 15 seconds - but apparently that confirms this is a good suspicion)
    Last edited by Trilby (2012-10-03 17:21:24)

  • Mysql-5.5.30-6 : temp files issue

    since I upgraded mysql, I beginning to encounter suddenly this kind of error on any sql statement after some times :
    mysql> show fields from jos_banner;
    ERROR 1 (HY000): Can't create/write to file '/tmp/#sql_25e6_0.MYI' (Errcode: 2)
    I find that restarting mysqld is sufficient without actually changing any configuration files, but the problem shows up again the next day.
    After some research, I find out that "PrivateTmp=true" in /usr/lib/systemd/system/mysqld.service is the guilty :
    mysqld creates temp files in a private namespace (ie : /tmp/systemd-private-6DfdVO). The errors happen because the directory no more exists.
    I can't figure who removes these directories, is it a systemd configuration issue ?

    Did the file come from a Mac user? If the fonts are Mac-format TT, T1 or .dfont you cannot use them even if they are available in the Document fonts folder (presuming there is one), nor will Windows T1 fonts work from that folder, though they could be installed.
    Bottom line is you need Windows compatible fonts, either OpenType, Windows TrueType, or (if you are willing to install them) Windows Type 1. If those are not available already on your system, or in a document fonts folder supplied with the file, you need to get them.

  • Trouble with booting system after upgrade udev= systemd

    Hi everybody,
    I have been trouble with my system since last upgrade (udev => systemd)
    My issue is something like this: https://bbs.archlinux.org/viewtopic.php?pid=1106157 but advice from this discussion doesn't work.
    When system booting, *immediately* (very fast, too fast) display login screen after start parsing hook [udev]
    Of course, i can't login - type username and i have redraw screen again on all /dev/tty* - i have no chance to type password.
    Many invalid logins suspend init for 5 minutes and allow me see display error due stop redraw screen - libpam.so.0 cannot find.
    I suspect that, partitions aren't mount (this fast login screen doesn't have even hostname). I have a 4 discs, with many partitions - mounting
    this take a some time (+- 5 secs).
    In rescuecd, i can mount all partitions and chroot. In chroot all works fine - /bin/login (i was checked authorization on all users),
    paths and pams are ok. Of course i try ,,default rescue trick'': `pacman -Suy linux udev mkinitcpio` and 'mkinitcpio -p linux' on rescuecd
    but nothing it's changed after reboot. I checking grub config, and unpack and check initramfs-linux.img - all ok.
    In my mkinitcpio.conf ofcourse i have MODULES="ext3" (for my filesystems).
    Please help.

    crab wrote:
    This may or may not be related... but I saw this message just now during an upgrade:
    (121/168) upgrading mkinitcpio [###################] 100%
    ==> If your /usr is on a separate partition, you must add the "usr" hook
    to /etc/mkinitcpio.conf and regenerate your images before rebooting
    And am wondering what the message means by if /usr is on a separate partition - separate partition to what?  /boot? / ?
    I have my /usr partition in the same partition as /  (but /boot is in a different partition)
    Logic tells me I'm safe (haven't rebooted yet), as / is "master", and anything else is a separate partition, and I have /usr on the same partition as /.
    Do you guys have separate /usr and/or /boot partitions?  As stated in first sentence this may not be related, but looks important...
    It means separate from /. So yes, you're right, you are "safe" from having to do anything with this message on your system.
    And to the other people on this thread: make sure you do have all your packages uniformly updated, including any pam-related AUR or ABS-build packages. libpam and the pam module directory (.../lib/security) were moved from /lib to /usr/lib a little while back, so make sure that anything that cares about where these may be have been updated so they aren't confused by this move.
    Last edited by ataraxia (2012-06-03 22:40:22)

  • KDE's Dolphin can't mount NTFS partitions after upgrade to systemd

    Hi, I just finished to migrate my system to a pure systemd setup. Everithing seems to work fine, except that Dolphin can't mount NTFS partitions anymore, as it was able to do before. I'm not 100% sure that systemd is the culprit, but nevertheless it is a big change in my system so I assume that it may be the problem.
    Trying to mount with Dolphin I get this error message:
    An error occurred while accessing 'sATA-a', the system responded: The requested operation has failed.: Error mounting: mount exited with exit code 1: helper failed with:
    Error opening '/dev/sdb1': Permesso negato
    Failed to mount '/dev/sdb1': Permesso negato
    Please check '/dev/sdb1' and the ntfs-3g binary permissions,
    and the mounting user ID. More explanation is provided at
    http://tuxera.com/community/ntfs-3g-faq/#unprivileged
    I used to get this kind of error aeons ago when trying to mount from CL; puzzling enough, mounting from CL now works:
    $ mount /media/disks/sATA-a
    $ ls /media/disks/sATA-a
    Documenti Download $RECYCLE.BIN RECYCLER sATA-b System Volume Information Temp Video
    This is the relevant entry in my fstab (I don't know if Dolphin cares about it...):
    #sATA-a
    UUID=D6789B21789B0003 /media/disks/sATA-a ntfs-3g noauto,users 0 0
    And finally:
    $ ll `which ntfs-3g`
    -rwsr-xr-x 1 root root 125K 21 apr 12.13 /bin/ntfs-3g
    Can anybody give me a hint? Thanks.

    OK, the mess is growing up. Today I switched my laptop to systemd, and the mount problem has appeared  on this system as well. So I am confident that this is a systemd-related issue, and maybe some stock Arch config file is broken. I have this entry on my /etc/fstab for the ntfs-3g drive:
    UUID=88705BA9705B9D2E /media/vista ntfs-3g noauto,users,exec 0 0
    I compiled ntfs-3g with internal fuse support and did the setuid trick:
    $ ls -l `which ntfs-3g`
    -rwsr-xr-x 1 root root 125K 16 apr 2012 /bin/ntfs-3g
    I can mount the disk using the command:
    $ mount /media/vista/
    $
    It works flawlessly, so ntfs-3g works. If I try to mount it with udisks I get:
    $ /usr/bin/udisks --mount /dev/sda2 --mount-options users,exec
    Mount failed: Error mounting: mount exited with exit code 1: helper failed with:
    Error opening '/dev/sda2': Permesso negato
    Failed to mount '/dev/sda2': Permesso negato
    Please check '/dev/sda2' and the ntfs-3g binary permissions,
    and the mounting user ID. More explanation is provided at
    http://tuxera.com/community/ntfs-3g-faq/#unprivileged
    It sounds to me that udisks is trying to mount the disk as a different user, but I'm not an expert so I might be wrong. If I remove the entry in /etc/fstab then udisks will ask for the password. Repeating the same steps but for an ext3 partition, I am able to mount with udisks when there is a proper fstab entry, and I'm asked for a password when that entry is commented out.
    Based on these findings, I strongly suspect that there is some problem with logind configuration in my system. I have been going round and round for hours, serching the web and the wiki (which BTW is in a very bad shape, containing outdated or no informations about mount policies in the polkit and udev sections), and now I feel I need some help to go through it... thanks.

  • Systemd takes 100% of a single thread and will not allow shutdown

    A few systemd updates ago I started to have this problem. On update, systemd takes up 100% of one of my four threads (switching theads on every so often according to Conky) and will not let me reboot properly. If I run "sudo poweroff" it broadcasts that the system is going down then just doesn't. No amount of waiting after the update is finished sees systemd finish whatever it's atempting to do.
    Holding the power button to force the computer off causes it to be unbootable. The system hangs as it checks the file system. No amount of waiting sees the file system check completed.
    So far the only "fix" that I've found is to load the system up in a ch-root environment and roll systemd back.
    I really don't know enough to fix this myself and google searches have turned up seemingly similar problems who's fixes don't work in my case.

    Stebalien wrote:
    Anything in dmesg after updating? When you reboot, try replacing the quiet command line argument with verbose and see where systemd actually stops. Also, immediately after updating, try attaching strace to it (strace -p 1) and logging the output.
    Regardless, this really sounds like a bug.
    I couldn't find anything in dmesg. I grepped "systemd" and nothing strange showed up.
    When booting verbosely the system prints "Welcome to Arch Linux" then hangs.
    The newest installation media does the same thing so I'm going to have to find an older one to roll the package back. It doesn't hang on my laptop so it must be an issue with this netbook.
    I couldn't find anything about systemd having issues with the atom N2600 and it's not old hardware so I doubt they've just dropped support.
    Last edited by Deyna (2013-12-24 05:54:22)

  • Fan (fancontrol) issue: Dell Inspiron 3521

    Hello everyone, please bear with me as I am a novice arch user. Also I am not  native english speaker (just in case )
    I have a problem with the laptop fan working constantly, which is annoying and disturbing. It has to be due to a system configuration, because I am coming form the other distro, where problem didn't exist. Also just after arch installation the fan was working fine (meaning in intervals, not constantly). It's just broken recently. The temp. is fine, around 50 degrees with medium load (browser, mplayer).
    [mateusz@mateusz ~]$ sensors
    coretemp-isa-0000
    Adapter: ISA adapter
    Physical id 0: +52.0°C (high = +87.0°C, crit = +105.0°C)
    Core 0: +52.0°C (high = +87.0°C, crit = +105.0°C)
    Core 1: +50.0°C (high = +87.0°C, crit = +105.0°C)
    So obviously I made my research, and came to that conclusion:
    -Due to the nature of systemd, the config for fancontrol stopped being loaded properly
    [mateusz@mateusz ~]$ systemctl status lm_sensors
    ● lm_sensors.service - Initialize hardware monitoring sensors
    Loaded: loaded (/usr/lib/systemd/system/lm_sensors.service; disabled)
    Active: inactive (dead)
    [mateusz@mateusz ~]$ systemctl status fancontrol
    ● fancontrol.service - Start fan control, if configured
    Loaded: loaded (/usr/lib/systemd/system/fancontrol.service; disabled)
    Active: inactive (dead)
    sie 08 08:54:01 mateusz systemd[1]: Started Start fan control, if configured.
    I suspect it's the same thing explained in this post: https://bbs.archlinux.org/viewtopic.php … 6#p1251766 ,
    "assignments of various hwmon symlinks change on each reboot". The advice is to load modules manually. But I got only one module:
    [mateusz@mateusz ~]$ ls /sys/class/hwmon/ -al
    razem 0
    drwxr-xr-x 2 root root 0 08-08 09:12 .
    drwxr-xr-x 45 root root 0 08-08 09:45 ..
    lrwxrwxrwx 1 root root 0 08-08 09:12 hwmon0 -> ../../devices/platform/coretemp.0/hwmon/hwmon0
    This is the place I got stuck. I have a general idea what to do, but I'd like to confirm and double check. I don't want to mess up my system, since I got to like it quite a bit.
    My thinking is:
    1. Set up lm_sensors
    2. Remove it from autostart (or not configure it to autostart, but I'd rather remove it later, just to be on the safe side)
    3. Load modules manually to /etc/modules-load.d/load_these.conf        However, I am worried that I see only coretemp. Just seems that something is wrong.
    4. See if default  /etc/fancontrol is ok. If not try to configure it, as explained in wiki. https://wiki.archlinux.org/index.php/fan_speed_control
    5. Do not run /usr/bin/fancontrol as I have Dell Ispiron ? Install instead i8kutils? See which is better/working at all?
    6. Enable working solution from 5.
    Thank you for reading this rather long one. I'd greatly appreciated any healp, hints, leads and so on.
    Best regards
    Last edited by ewaller (2014-08-10 17:01:16)

    I am sorry to drag that issue, but It's a quite big problem for me. I realize that previous post are not proper, and I should've educated myself better. I read and googled a lot, but still can't figure what to do next. Please help.
    Using i8k I set fancontrol, and It's working (done the manual modules loading to prevent systemd boot issue)
    Now the rpm for my fan is ridiculous when the fan is on (I mean on software wise, because it's working constantly)
    [mateusz@mateusz ~]$ sensors
    i8k-virtual-0
    Adapter: Virtual device
    Right Fan: 90000 RPM
    CPU: +49.0°C
    coretemp-isa-0000
    Adapter: ISA adapter
    Physical id 0: +49.0°C (high = +87.0°C, crit = +105.0°C)
    Core 0: +48.0°C (high = +87.0°C, crit = +105.0°C)
    Core 1: +47.0°C (high = +87.0°C, crit = +105.0°C)
    I set up minimal temp to 45 to prevent fan from working in the lower tempratures
    [mateusz@mateusz ~]$ systemctl status fancontrol
    ● fancontrol.service - Start fan control, if configured
    Loaded: loaded (/usr/lib/systemd/system/fancontrol.service; enabled)
    Active: active (running) since sob 2014-08-09 08:26:49 CEST; 1h 50min ago
    Main PID: 248 (fancontrol)
    CGroup: /system.slice/fancontrol.service
    ├─ 248 /bin/bash /usr/sbin/fancontrol
    └─4191 sleep 10
    sie 09 08:26:56 mateusz fancontrol[248]: Depends on hwmon1/temp3_input
    sie 09 08:26:56 mateusz fancontrol[248]: Controls hwmon0/fan2_input
    sie 09 08:26:56 mateusz fancontrol[248]: MINTEMP=45
    sie 09 08:26:56 mateusz fancontrol[248]: MAXTEMP=85
    sie 09 08:26:56 mateusz fancontrol[248]: MINSTART=150
    sie 09 08:26:56 mateusz fancontrol[248]: MINSTOP=100
    sie 09 08:26:56 mateusz fancontrol[248]: MINPWM=0
    sie 09 08:26:56 mateusz fancontrol[248]: MAXPWM=255
    sie 09 08:26:56 mateusz fancontrol[248]: Enabling PWM on fans...
    sie 09 08:26:56 mateusz fancontrol[248]: Starting automatic fan control...
    And the sensors gives expected output:
    [mateusz@mateusz ~]$ sensors
    i8k-virtual-0
    Adapter: Virtual device
    Right Fan: 0 RPM
    CPU: +45.0°C
    coretemp-isa-0000
    Adapter: ISA adapter
    Physical id 0: +46.0°C (high = +87.0°C, crit = +105.0°C)
    Core 0: +46.0°C (high = +87.0°C, crit = +105.0°C)
    Core 1: +44.0°C (high = +87.0°C, crit = +105.0°C)
    But despite the 0 RPM reading the fan is noising all the way. I read more about i8kutils, installed it and tested. I got weird output:
    [mateusz@mateusz ~]$ i8kctl
    1.0 A12 7YDQ0X1 47 -1 0 -1 0 -1 -1
    [mateusz@mateusz ~]$ i8kctl fan
    -1 0
    -1 entry is not even in the man page. What does it mean? It's the left one, the usual cpu one. And the other one is switched off, which is consistent with sesnors output (while sensors give RPM speed i8kctl gives 1 for the right fan) . But like I said, it's fanning all the time, constantly. The other thing is that this laptop, to my limited knowledge has got one fan.
    Please help, I am lost here.
    Best regards
    Last edited by matman (2014-08-09 08:32:53)

  • Pulseaudio and systemd --user: DBus scope issues?

    Hi,
    I have a multi-seat setup, so I need user-wide pulseaudio and whatnot. I'm trying to setup my boot through systemd --user.
    Testing audio working apps are firefox, mpv, and mpd. The problem is:
    - If I start pulseaudio and mpd manually everything is fine (no use of systemd)
    - If I start pulseaudio through systemd no application has sound.
    - If I start pulseaudio and mpd through systemd only mpd has sound.
    raimundoyamtech~$ cat .config/systemd/user/pulseaudio.service
    [Unit]
    Description=PulseAudio Sound System
    After=sound.target
    [Service]
    ExecStart=/usr/bin/pulseaudio
    [Install]
    WantedBy=multi-user.target
    raimundoyamtech~$ cat .config/systemd/user/mpd.service
    [Unit]
    Description=Music Player Daemon
    After=network.target sound.target
    [Service]
    ExecStart=/usr/bin/mpd %h/.config/mpd/mpd.conf --no-daemon
    ExecStop=/usr/bin/mpd %h/.config/mpd/mpd.conf --kill
    Restart=always
    [Install]
    WantedBy=multi-user.target
    If I add BusName=org.pulseaudio.Server to the pulseaudio.service nothing changes.
    Using pulseaudio's autospawn=yes leads to what seems to be same behaviour: mpd by systemd starts pulseaudio and is the only app with sound.
    ./config/pulse/client.conf only contains default-sink. Everything else is default.
    Using alsa alone is not an option because of firefox.
    Any thoughts?
    EDIT:
    raimundoyamtech~$ systemctl --version
    systemd 208
    +PAM -LIBWRAP -AUDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ
    raimundoyamtech~$ pulseaudio --version
    pulseaudio 4.0
    Last edited by Raimundo (2013-10-23 10:08:13)

    ewaller wrote:
    Please do not bump.   I understand the frustration; really, I do.  But, these are very active forums with some very good technical people lurking about.  I guarantee your post had been read.  I read it.  I did not have an answer, as I have never seen that behavior afore.   I am certain that was true for many other regulars.
    In the future, you can bring focus to a thread by providing more information..  Tell us what you have tried, what you have read since the last post, etc.  At least it gives the impression that you are working the problem rather than merely waiting for a response.
    I don't know almost anything about systemd, especially because it changes so rapidly and documention is so scarce and outdated that either I read the whole documentantion for my version in hopes of finding my problem (something for which I do not have time) or post a topic.
    I posted everything I touched regarding systemd since the installation of my system, that's all the relevant information I know I can give, so at this point I had no more info to give.
    Actually posting a topic is really my last resort, it usually means that I have already tried everything I knew and I'm hopeless already.
    raimundoyamtech~$ loginctl list-sessions
    SESSION UID USER SEAT
    2 1002 carla seat0
    1 1000 raimundo seat0
    2 sessions listed.
    raimundoyamtech~$ loginctl show-session 1
    Id=1
    Timestamp=Tue 2013-10-29 12:33:47 WET
    TimestampMonotonic=6670234
    VTNr=1
    TTY=tty1
    Remote=no
    Service=login
    Scope=session-1.scope
    Leader=1456
    Audit=1
    Type=tty
    Class=user
    Active=no <----- Is this what you are talking about?
    State=online
    IdleHint=yes
    IdleSinceHint=1383050072367636
    IdleSinceHintMonotonic=0
    Name=raimundo
    raimundoyamtech~$ loginctl show-session 2
    Id=2
    Timestamp=Tue 2013-10-29 12:33:47 WET
    TimestampMonotonic=6667439
    VTNr=2
    TTY=tty2
    Remote=no
    Service=login
    Scope=session-2.scope
    Leader=1453
    Audit=2
    Type=tty
    Class=user
    Active=no <----- Is this what you are talking about?
    State=online
    IdleHint=yes
    IdleSinceHint=1383050025387636
    IdleSinceHintMonotonic=0
    Name=carla
    raimundoyamtech~$ loginctl show-session 3
    Failed to issue method call: No such file or directory
    What is an active session? Oo Never heard of it
    I could start things. Pulseaudio started, so did mpd. I also have a /usr/lib/systemd/systemd --user process started for each user. I assumed this would be it since this
    raimundoyamtech~$ systemctl --user
    Failed to issue method call: Process /bin/false exited with status 1
    always happens and I've read that systemctl --user is no longer required.
    [EDIT]
    Fixed it. Don't remember where I read that it wasn't required, just that it was in the same place I found someone else complaining about getting this error.
    For anyone else encountering this: sed -i s/system-auth/system-login/g /etc/pam.d/systemd-user
    and systemctl --user will work. Insults fly out to the one who wrote it wasn't required!
    Still am not able to get an active session though
    [/EDIT]
    Why would there be a need for anything else? I'm gonna check on that. Thanks!
    See, the bump worked ^^ but ok I'll try to refrain from doing that next time. Sorry.
    Last edited by Raimundo (2013-10-29 16:27:55)

  • I915 power consumption issue after switch to systemd?

    After switching to systemd I noticed a massive increase of power consumption on my Thinkpad X220 (i5 Sandy Bridge).
    The strange thing is, that after some reboots it randomly seems to catch the i915 power saving mode and the consumption gets from ~24W to ~7W at idle. But only after several reboots.
    Adding the good old i915.i915_enable_rc6=1 to the boot parameters doesn't make any differences. But looking at the powertop detail outputs it seems to be a i915 issue.
    Using the latest linux kernel from core (3.6.4) and latest intel drivers (2.20.12).

    I started to get suspicious because I have only ever had the issue in my office. Last week, when I encrypted my drive, my machine wrote to disk for more than 14 hours solid. I then did all the set up and all the restoring from backup etc. with no issue whatsoever. Lenovo ran the thing for 48 hours straight with no problem. But once in my office...
    So I asked the local IT people if they could think of anything other than overheating and explained the issue. They took my laptop yesterday , booted it from a hardware testing CD and ran it for a couple of hours sitting on top of a hot computer in the server room which is definitely hot. (It has a whole bunch of computers, I guess.) No issue. They then ran stress tests for a while in the same place. No problem. Highest recorded temp: 65C.
    The head of IT then took my power adapter to a more general IT service to be tested and inspected. They looked at it, they opened the plug to check the fuse, they tested it. No problem. Of course, the guy also explained why he was asking and the other IT person said, "Oh, is that on level 1?" "Yes..." So apparently there was another machine (a Mac), I think, doing just the same thing in an office in my part of the building. Testing showed that the power spikes and when the power spikes, the laptop shut down as a safety measure. Solution: they installed a UPS for that one laptop. They didn't tell anybody else, including the local IT people.
    What the local IT people were going to do was to install equipment to monitor the power in my office and see if anything weird was causing my laptop to react. However, that was when this was an extremely-unlikely-but-we-are-getting-desperate-for-theories scenario. Clearly, that theory no longer seems wildly implausible at all. So the current hypothesis is that it is most likely that my machine is also reacting to the spikes in power by shutting itself off. (I'm not sure why it should have just started doing this but who knows what the state of the electricals is and how that might vary?)
    I have been told that a surge protector will do no good. (They've given me one anyway but apparently it will not deal with spikes in phase 3 power or something - I didn't understand this bit but the head IT person said he didn't understand it either but the electricals IT person showed him with graphs on the whiteboard. So it must be true.)
    The current plan is to try to get the UPS from central IT which was provided for the other laptop since that person's discipline has since moved to another floor of the building so the UPS probably went back to central IT. They are going to ask during a meeting tomorrow about this possibility. Otherwise, they are planning to order a UPS for me on Monday.
    I'm somewhat surprised that the abrupt shutdowns haven't screwed my data. I've lost work but not seen fs corruption. I didn't take my laptop today. I'll need it next week but I do not plan to plug it in in my office until I have a UPS.
    I'm pretty annoyed, to be honest. I've wasted hours on this and got incredibly stressed about it. The IT people have also wasted a (smaller) amount of time. I hoped to have a new draft of an article I'm working on written by the end of reading week but that didn't happen due to all of this. And they *knew*. It would be different if this was an unknown problem just discovered - of course, one could understand that. But there's a known problem which can cause this type of problem and presumably could well damage equipment without these sorts of safety shutdown features and they don't tell anybody.
    And, no, I doubt very much indeed that a damaged personal machine would be considered the institution's liability. (Maybe if it was a student's machine and the student was required to use it or something but even then...)
    I can't believe it does much good to their equipment either.
    The local IT people did know there was an issue with some burnt out devices but that was about eight years ago and only got mentioned as a outside possibility when other diagnostics turned up no result.
    What gets me is that the proposed solution will only solve the issue for me - not for anybody else in my part of the building on level 1.

  • Having issues with starting systemd as user.

    I am trying to process through the steps for configuring SABnzbd for local user configs but after rebooting from completing the steps here. I double checked my work but I still get an error when I am trying to start the service as me.
    This is what I am getting:
    $ systemctl --user
    Failed to issue method call: Process /bin/false exited with status 1

    MPD is not running:
    % ps -ef | grep mpd !1004
    honza 2625 1629 0 22:41 pts/0 00:00:00 grep mpd
    Then I made that /etc/systemd/system/[email protected] file, same as yours.
    % sudo systemctl enable mpd@honza !1006
    ln -s '/etc/systemd/system/[email protected]' '/etc/systemd/system/multi-user.target.wants/[email protected]'
    % sudo systemctl start mpd@honza
    This seems OK, but MPD is not running.
    % systemctl list-units | grep 'mpd' !1009
    [email protected] loaded failed failed Music Player Daemon
    [email protected] loaded failed failed Music Player Daemon
    That was your first example. The second one:
    honza@inkognito ~
    % systemctl list-units | grep 'mpd'
    honza@inkognito ~
    % systemd --user &
    [1] 1703
    honza@inkognito ~
    % mpd.service: main process exited, code=exited, status=1/FAILURE
    mpd.service: control process exited, code=exited status=1
    Unit mpd.service entered failed state
    I used the same service file.
    But at least the "systemd --user &" line in terminal helped a little, because I'm not getting that first error anymore.
    % systemctl --user status mpd
    mpd.service - Music Player Daemon
    Loaded: loaded (/home/honza/.config/systemd/user/mpd.service; enabled)
    Active: failed (Result: exit-code) since Čt, 2012-12-20 22:59:14 CET; 2min 37s ago
    Process: 1710 ExecStop=/usr/bin/mpd --kill (code=exited, status=1/FAILURE)
    Process: 1708 ExecStart=/usr/bin/mpd %h/.config/mpd/mpd.conf --no-daemon (code=exited, status=1/FAILURE)
    CGroup: name=systemd:/user/honza/2/systemd-1703/mpd.service
    So.. something's wrong.
    Thank you for your help, btw.

  • Login issues with systemd 204

    Hello,
    Every time I'm trying to upgrade systemd from 204, it hangs on login (at terminal) or at execution of kde (using kdm) "forever".
    The terminal Login does not accept my password and after 30 seconds prompt again for login.
    And the splash screen of KDE hangs with the K icon for a long time (more then 20 minutes, that I was willing to wait, untill sysrq things).
    When downgrading from (207/208) back to 204 the issue stop.
    I'm not sure that  if the problem is that I moved sysctl to /etc/sysctl.d/ or something else.
    [rebirth:/etc/sysctl.d] ik $ ls
    99-sysctl.conf
    [rebirth:/etc/sysctl.d] ik $
    My sysctl settings:
    # /etc/sysctl.conf - Configuration file for setting system variables
    # See sysctl.conf (5) for information.
    # you can have the CD-ROM close when you use it, and open
    # when you are done.
    dev.cdrom.autoeject = 1
    dev.cdrom.autoclose = 1
    # protection from the SYN flood attack
    net.ipv4.tcp_syncookies = 1
    # see the evil packets in your log files
    net.ipv4.conf.all.log_martians = 1
    # if not functioning as a router, there is no need to accept redirects or source routes
    #net.ipv4.conf.all.accept_redirects = 0
    #net.ipv4.conf.all.accept_source_route = 0
    #net.ipv6.conf.all.accept_redirects = 0
    #net.ipv6.conf.all.accept_source_route = 0
    # Disable packet forwarding
    net.ipv4.ip_forward = 1
    net.ipv6.conf.all.forwarding = 0
    # Enable IPv6 Privacy Extensions
    net.ipv6.conf.default.use_tempaddr = 2
    net.ipv6.conf.all.use_tempaddr = 2
    # sets the port range used for outgoing connections
    #net.ipv4.ip_local_port_range = 32768 61000
    # Swapping too much or not enough? Disks spinning up when you'd
    # rather they didn't? Tweak these.
    #vm.vfs_cache_pressure = 100
    vm.laptop_mode = 1
    vm.swappiness = 5
    #kernel.printk_ratelimit_burst = 10
    #kernel.printk_ratelimit = 5
    #kernel.panic_on_oops = 0
    # Reboot 600 seconds after a panic
    #kernel.panic = 600
    # Disable SysRq key (note: console security issues)
    kernel.sysrq = 1
    # disable firewall with bridge
    net.bridge.bridge-nf-call-ip6tables = 0
    net.bridge.bridge-nf-call-iptables = 0
    net.bridge.bridge-nf-call-arptables = 0
    If there is additional information that requires, please tell me

    Regarding the error "Logon not possible (error in license check),
    Few suggestions:
    1. Please copy and paste the output from the following commands:
       -> saplicense -version
       -> saplicense -install trace=2    (this generate dev_slic file)
       -> saplicense -get
       -> saplicense -show
    2. DB connect problem... Sometimes this error can occur when there are
    connection problems to the central instance. During logon system checks
    if a valid license is installed by reading the entries in table MLICHECK.
    SAP* will bypass the MLICHECK check.  So, sometimes this error can occur when there are connection problems to the central instance (message server). This could be a temporary problem. Please try to restart your SAP servers if this helps.
    3. See SAP note 359944, 193800
    4. Copy and paste the output of command "R3trans -dx"
    5. Check the file /etc/services for missing entries, example like
       sapms<SID> 3600/tcp
       sapdp00    3200/tcp
       sapdp99    3299/tcp
       sapgw00    3300/tcp
       sapgw99    3399/tcp
    6.  use the message-server-test tool 'lgtst' as per SAP note
    64015 to see whether you can connect to the server.
    7. can you ping the message server ? check parameter rdisp/mshost, IP
    address on host table ?
    cheers,
    Vincent

  • [SOLVED] SystemD NTFS partition issue's

    Hey archers,
    hope someone here can help me
    recently began testing systemd & I am facing a problem where I have to ctrl+d or give root password during every boot up due to systemd having problems with my ntfs partition ( i mount at boot as I have symlinks to that partition for documents & programs which run in wine)
    I have not enabled anything to do with mounting or even added the fuse module to load as it has already picked that up!
    here are the entries I think are related to this from journalctl:
    Aug 29 07:57:37 b0x ntfs-3g[568]: Version 2012.1.15 external FUSE 29
    Aug 29 07:57:37 b0x ntfs-3g[568]: Mounted /dev/sdb1 (Read-Write, label "Win7-sys", NTFS 3.1)
    Aug 29 07:57:37 b0x ntfs-3g[568]: Cmdline options: rw,noatime,sync,gid=100,umask=002
    Aug 29 07:57:37 b0x ntfs-3g[568]: Mount options: rw,sync,allow_other,nonempty,noatime,fsname=/dev/sdb1,blkdev,blksize=4096,default_permissions
    Aug 29 07:57:37 b0x ntfs-3g[568]: Global ownership and permissions enforced, configuration type 7
    Aug 29 07:57:37 b0x ntfs-3g[568]: Warning : using problematic uid==0 and gid!=0
    Aug 29 07:57:37 b0x mount[572]: Mount is denied because the NTFS volume is already exclusively opened.
    Aug 29 07:57:37 b0x mount[572]: The volume may be already mounted, or another software may use it which
    Aug 29 07:57:37 b0x mount[572]: could be identified for example by the help of the 'fuser' command.
    Aug 29 07:57:37 b0x systemd[1]: media-Win7.mount mount process exited, code=exited status=16
    Aug 29 07:57:37 b0x systemd[1]: Job local-fs.target/start failed with result 'dependency'.
    Aug 29 07:57:37 b0x systemd[1]: Triggering OnFailure= dependencies of local-fs.target.
    Aug 29 07:57:37 b0x systemd[1]: Job systemd-user-sessions.service/start failed with result 'dependency'.
    Aug 29 07:57:37 b0x systemd[1]: Job lightdm.service/start failed with result 'dependency'.
    Aug 29 07:57:37 b0x systemd[1]: Job graphical.target/start failed with result 'dependency'.
    Aug 29 07:57:37 b0x systemd[1]: Job multi-user.target/start failed with result 'dependency'.
    Aug 29 07:57:37 b0x systemd[1]: Job systemd-logind.service/start failed with result 'dependency'.
    Aug 29 07:57:37 b0x systemd[1]: Job dbus.service/start failed with result 'dependency'.
    Aug 29 07:57:37 b0x systemd[1]: Job [email protected]/start failed with result 'dependency'.
    Aug 29 07:57:37 b0x systemd[1]: Job hwclock.service/start failed with result 'dependency'.
    Aug 29 07:57:37 b0x systemd[1]: Job syslog-ng.service/start failed with result 'dependency'.
    Aug 29 07:57:37 b0x systemd[1]: Job network.service/start failed with result 'dependency'.
    Aug 29 07:57:37 b0x systemd[1]: Job cronie.service/start failed with result 'dependency'.
    Aug 29 07:57:37 b0x systemd[1]: Job snmpd.service/start failed with result 'dependency'.
    Aug 29 07:57:37 b0x systemd[1]: Job samba.service/start failed with result 'dependency'.
    Aug 29 07:57:37 b0x systemd[1]: Job webmin.service/start failed with result 'dependency'.
    Aug 29 07:57:37 b0x systemd[1]: Job systemd-tmpfiles-clean.timer/start failed with result 'dependency'.
    Aug 29 07:57:37 b0x systemd-journal[181]: Journal stopped
    Aug 29 07:57:37 b0x systemd-journal[584]: Journal started
    Aug 29 07:57:37 b0x ntfs-3g[568]: Unmounting /dev/sdb1 (Win7-sys)
    Aug 29 07:57:37 b0x systemd-udevd[224]: '/usr/sbin/alsactl restore 0' [500] terminated by signal 15 (Terminated)
    Aug 29 07:57:38 b0x systemd[1]: Startup finished in 3s 111ms 648us (kernel) + 6s 425ms 155us (userspace) = 9s 536ms 803us.
    Aug 29 07:57:38 b0x systemd[582]: Failed at step EXEC spawning /bin/plymouth: No such file or directory
    Aug 29 07:58:25 b0x systemd[1]: Cannot add dependency job for unit avani-dnsconfd.service, ignoring: Unit avani-dnsconfd.service failed to load: No such file or directory. See system lo...e' for details.
    Aug 29 07:58:25 b0x systemd[1]: Socket service syslog.service not loaded, refusing.
    Aug 29 07:58:26 b0x arch-modules-load[609]: mkdir: cannot create directory ‘/run/modules-load.d’: File exists
    Aug 29 07:58:26 b0x systemd-modules-load[706]: Module 'vhba' is already loaded
    Aug 29 07:58:26 b0x systemd-modules-load[706]: Module 'fuse' is already loaded
    Aug 29 07:58:26 b0x systemd-fsck[646]: public: clean, 385878/2039808 files, 5060668/8159011 blocks
    Aug 29 07:58:26 b0x systemd-fsck[653]: VM: clean, 228/5677056 files, 5637221/22680575 blocks
    Aug 29 07:58:26 b0x systemd-fsck[644]: Home: clean, 90204/1327104 files, 984778/5305458 blocks
    Aug 29 07:58:26 b0x ntfs-3g[871]: Version 2012.1.15 external FUSE 29
    Aug 29 07:58:26 b0x ntfs-3g[871]: Mounted /dev/sdb1 (Read-Write, label "Win7-sys", NTFS 3.1)
    Aug 29 07:58:26 b0x ntfs-3g[871]: Cmdline options: rw,gid=100,fmask=113,dmask=002
    Aug 29 07:58:26 b0x ntfs-3g[871]: Mount options: rw,allow_other,nonempty,relatime,fsname=/dev/sdb1,blkdev,blksize=4096,default_permissions
    Aug 29 07:58:26 b0x ntfs-3g[871]: Global ownership and permissions enforced, configuration type 7
    Aug 29 07:58:26 b0x ntfs-3g[871]: Warning : using problematic uid==0 and gid!=0
    Here is the entry in /etc/fstab for this partition:
    ## Entry for /dev/sdb1 SYSTEM:(Win7)
    UUID=44083B9668A3E0CC /media/Win7 ntfs-3g gid=users,fmask=113,dmask=002 0 0
    I have been all over goggle & am unable to find out anything which can help.
    As stated before I have links to this partition & so really want/need this partition to be mounted at boot.
    Any help on this will be greatly appreciated
    Thanks in advance
    EDIT #1
    rebooted again, still the same happening
    ran:
    $ sudo mount -l
    proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
    sys on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
    dev on /dev type devtmpfs (rw,nosuid,relatime,size=3022708k,nr_inodes=755677,mode=755)
    run on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
    /dev/sda1 on / type ext4 (rw,relatime,data=ordered) [Arch-sys]
    securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
    tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
    devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
    tmpfs on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,mode=755)
    cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd)
    cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
    cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpuacct,cpu)
    cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
    cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
    cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
    cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls)
    cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
    systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=30,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
    debugfs on /sys/kernel/debug type debugfs (rw,relatime)
    mqueue on /dev/mqueue type mqueue (rw,relatime)
    hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
    fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
    tmpfs on /tmp type tmpfs (rw,nosuid,nodev,relatime)
    /dev/sdb3 on /media/wine type ext4 (rw,noatime,errors=remount-ro,data=ordered) [wine] <<<THIS SHOULD NOT BE HERE!<<<<<<<<<
    /dev/sdd1 on /media/spare2 type ext4 (rw,noatime,errors=remount-ro,data=ordered) [spare2] <<<THIS SHOULD NOT BE HERE!<<<<<<<<<<
    /dev/sdc1 on /media/spare type ext4 (rw,noatime,errors=remount-ro,data=ordered) [spare] <<<THIS SHOULD NOT BE HERE!<<<<<<<<<<<
    /dev/sde1 on /media/USB-HDD2 type vfat (rw,noatime,sync,gid=100,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro) [USB-HDD2] <<<<<THIS IS NORMAL
    /dev/sdb4 on /media/pac type ext4 (rw,noatime,errors=remount-ro,data=ordered) [pac] <<<THIS SHOULD NOT BE HERE!
    /dev/sdd1 on /media/Spare2 type ext4 (rw,relatime,errors=remount-ro,data=ordered) [spare2] <<<<<THIS IS NORMAL
    /dev/sdc1 on /media/Spare type ext4 (rw,relatime,errors=remount-ro,data=ordered) [spare] <<<<<THIS IS NORMAL
    /dev/sdb2 on /media/VM type ext4 (rw,relatime,errors=remount-ro,data=ordered) [VM] <<<<<THIS IS NORMAL
    /dev/sdb3 on /var/wine type ext4 (rw,relatime,errors=remount-ro,data=ordered) [wine] <<<<<THIS IS NORMAL
    /dev/sdb4 on /var/cache/pacman type ext4 (rw,relatime,errors=remount-ro,data=ordered) [pac] <<<<<THIS IS NORMAL
    /dev/sdb1 on /media/Win7 type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096) [Win7-sys] <<<<<THIS IS NORMAL
    /dev/sda3 on /public type ext4 (rw,relatime,errors=remount-ro,data=ordered) [public] <<<<<THIS IS NORMAL
    /dev/sda5 on /home type ext4 (rw,relatime,errors=remount-ro,data=ordered) [Home] <<<<<THIS IS NORMAL
    gvfs-fuse-daemon on /run/user/1000/gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,relatime,user_id=1000,group_id=100)
    binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
    gvfs-fuse-daemon on /root/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,relatime,user_id=0,group_id=0)
    as you can see my partitions are being mounted TWICE which is not what I want or expected!
    is there more documentation on what systemd does with mounts that could explain why i have multiple mount points for partitions or is this due to systemd discovering my partitions & mounting them at points based on label names & then parsing my FSTAB as well!
    I have read the wikki but there is very small info there & the links have not provided an explanation for this unwanted behaviour
    EDIT #2
    >>>>>>>>>>>SOLVED<<<<<<<<<<<<<<
    not an NTFS or FUSE issue
    I had previously installed mnttools!
    removed & now all is well
    sorry
    Last edited by t0m5k1 (2012-08-29 08:30:11)

    OK,
    After being spurred on to try to do this thing properly, this is what I came up with today.
    My fstab line (for a USB NTFS disk):
    /dev/sdb1 /media/samsung ntfs-3g noauto,users,rw,nodev 0 0
    Then I created the /media/samsung folder and gave the audio group read/write permissions.
    It seems that non-root users can only mount an ntfs partition if they use a version of ntfs-3g with fuse included, so I replaced ntfs-3g with the version from AUR, having removed from the PKGBUILD file the option "-with-fuse=external" (see this thread: http://bbs.archlinux.org/viewtopic.php?id=44844 ).   I also had to set
    the ntfs-3g binary to setuid-root, dealt with here: http://www.tuxera.com/community/ntfs-3g … privileged (note- the instructions say this is discouraged, but it seems using ntfs partitions in linux requires some compromises).
    I can now mount the drive as an ordinary user.
    Then I set mpd back to run as user mpd, checked the audio group had access to all the mpd folders, and all was well.
    One hiccup which you might not have: mpd was unable to access my (external) sound card at first.  To solve this one, I used
    chmod 770 /dev/snd -R && chgrp audio /dev/snd -R
    As far as I can remember, that's everything.
    Last edited by Henry Flower (2010-04-20 12:54:26)

Maybe you are looking for