No Users to choose from in new install of arch+gnome.

I am trying to bring up gnome in a new virtualbox VM.
I have gotten to the gdm chooser screen, and while I can choose to power off, neither of my two non-root users are presented as a choice, nor is there a text box for user entry.
I am using today's current versions.  I did need to pacman -Syy to load the new version of libcups, and I did need to download the vesa driver for X.
I've tried this with and without the vboxvideo driver.  gdm:gdm has rwx access to its $HOME.
Thanks in advance.
    Keith
Here are the logs:
gnome https://dl.dropboxusercontent.com/u/198 … reeter.log
x11 https://dl.dropboxusercontent.com/u/198 … Xorg.0.log
chooser screencap https://dl.dropboxusercontent.com/u/198 … apture.PNG
passwd https://dl.dropboxusercontent.com/u/198 … der/passwd

I don't know anything about gdm, but if you ran `pacman -Syy` *then* updated some packages (and downgraded others??), please - before you do anything else - run `pacman -Syu` or at least `pacman -Su`.
edit: this is not to fix the present problem - but will prevent future ones.
Last edited by Trilby (2013-06-20 15:39:13)

Similar Messages

  • I need a control which allows a user to choose from specific values (which I specify), NOT 0, 1, 2 etc. [I KNOW I can let him enter 0, 1,2 fro

    m a listbox, and then change the value on the block diagram, but what I want is that on the subvi node itself he can enter the actual values, say 1, 10, 200. Does anyone know how to do this, creatively, since currently a control like this is not available.I need a control in Labview which allows a user to choose from specific values (which I specify), NOT 0, 1, 2 etc. [I KNOW I can let him enter 0, 1,2 from a listbox, and then change the value on the block diagram, but what I want is that on the subvi node itself he can enter the actual values, say 1, 10, 200. Does anyone know how to do this, creatively, since currently a con
    trol like this is not available.

    m a listbox, and then change the value on the block diagram, but what I want is that on the subvi node itself he can enter the actual values, say 1, 10, 200. Does anyone know how to do this, creatively, since currently a control like this is not available.> I need a control which allows a user to choose from specific values
    > (which I specify), NOT 0, 1, 2 etc. [I KNOW I can let him enter 0, 1,2
    > from a listbox, and then change the value on the block diagram, but
    > what I want is that on the subvi node itself he can enter the actual
    > values, say 1, 10, 200. Does anyone know how to do this, creatively,
    > since currently a control like this is not available.
    >
    One way of doing this is to use either a ring or enum where the strings
    presented to the user are "1", "10", or whatever you like. On the
    diagram, the values will be 0, 1, 2, in a compact counting sequence.
    Then do an array index into a constant. If this is done more than one
    place, make the control a typedef so you can keep them consistent an
    d
    make the index be done in a subVI. Then whenever you need this, you
    drop the control and the subVI, out comes the integer, float, or
    whatever it is you want to index.
    Greg McKaskle

  • I can't boot from CD (new install)

    Can this board load the OS (XP-Pro) from a CD on a new install?
    I have a 875P NEO-FIS2R board, P4 2.8, two SATA 80GB Hitachi drives and a NEC CD/DVD-Rom drive.  When I power up I get I get the logo screen and the a brief flash from a screen that looks like a Promise SATA bios screen that says something like "Bios not installed" and then a DOS like screen the says:
    Boot Failure
    Insert Boot Diskette in A:
    Press any key when ready
    Problem is I don't have a floppy drive.  The last two systems I made did not need one to boot.  They see the CD and boot.  
    Seem to me the System BIOS came pre-toasted from the factory.
    Any clues?

    I don’t think anything’s wrong with your board; just make sure (a) that your cd-rom shows up in the bios and (b) that it has the highest boot priority.
    Edit: you may also want to turn the logo off at least temporarily so that you can get a better idea as to what’s going on with the boot sequence. Also, don’t worry about the “bios not installed” message. It’s referring to the promise controller: if no drives are hooked up to it, it doesn’t load its bios. This has nothing to do with your system bios.

  • Maximum activation  count (1 user) already reached on a new install

    I just installed a new Adobe Acrobat XI Standard package ordered from a third party. The first time I invoked the application, I received an error message that the maximum activation count (1 user) had been reached. I had 30 days to deactivate one user and activate this computer, What has to be done to overcome this problem?
    I have contacted the seller, but have yet to hear from him.

    contact adobe support and ask for an activation count reset, http://www.adobe.com/support/chat/ivrchat.html

  • JSP, BC4J : Allowing users to choose from List of values when in Insert mode

    Hi,
    I have a requirement in which the user would be able to select a value from a combobox for populating a field when inserting a new record. The list of values in the combo box is derived from a look up table in the database. How can do this?
    Thanks.

    Use the version provided in Jdev 3.2. It has two methods:
    * Enables a LOV (list of values) for the specified attribute in
    * the UI. In the typical case, when an attribute is selected in an
    * HTML form, a LOV will be displayed.
    * <p>
    * This method enables a LOV for one or more of the RowSet's attributes.
    * To return all of the RowSet's attributes,
    * use the {@link #useLOV(String, String) useLOV} method.
    * <p>
    * @param sAtttibute name of the attribute for which an LOV
    * should be enabled.
    * @param voName name of the View Object to which the attribute belongs.
    * @param sDisplayAttributes a comma-separated list of the RowSet's attributes
    * that will be displayed when the attribute is selected.
    * @param sDataAttribute the location from which the attributes' values are
    * obtained.
    * @see #useLOV(String, String)
    public void useListOfValues(String sAttribute , String voName, String sDisplayAttributes, String sDataAttribute)
    JSlibNeeded |= WebBean.JSModalPageConstructorLib;
    LOVField lovField = new LOVField();
    ViewObject vo = qView.getApplicationModule().findViewObject(voName);
    ViewObject dupvo = qView.getApplicationModule().findViewObject(voName + "_query");
    if(dupvo == null)
    dupvo = qView.getApplicationModule().createViewObject(vo.getName() + "_query", vo.getDefFullName());
    lovField.setViewObject(getApplicationName() + "." + dupvo.getName());
    AttributeDef attr = qView.getViewObject().findAttributeDef(sAttribute);
    lovField.setPromptText(getAttributeLabel(qView, attr));
    lovField.setDisplayAttributes(sDisplayAttributes);
    lovField.setDataAttributes(sDataAttribute);
    setFieldRenderer(sAttribute , lovField);
    * Enables a LOV (list of values) for the specified attribute in the UI.
    * In the typical case, when the specified attribute is selected in an
    * HTML form, a LOV will be displayed.
    * <p>
    * This method enables a LOV for all of the RowSet's attributes.
    * To enable a LOV for a subset of the attributes,
    * use the {@link #useListOfValues(String, String, String, String)
    * useListOfValues} method.
    * <p>
    * @param sAtttibute name of the attribute for which an LOV
    * should be enabled.
    * @param voName name of the View Object to which the attribute belongs.
    * @see #useListOfValues(String, String, String, String)
    public void useLOV(String sAttribute, String voName)
    useListOfValues(sAttribute, voName, null, sAttribute);
    null

  • Can't log in with newly created user on new install of Arch [solved]

    Hi all,
    Yesterday I installed Arch anew (because I had a hardware failure that took out my hard drive), but now I'm encountering an issue with logging in.
    After following the installation guide, and creating a new user, I find that I'm unable to log in as said user.
    It complains about wrong password, but it's the exact same password that I entered mere moments before that, when creating the new user.
    I can "log in" as said user by first logging in as root (which does work) and doing "su - <username>" (though then it doesn't ask for a password).
    Can someone point me in the right direction to fix this problem?
    Last edited by madjo (2013-07-03 20:19:43)

    I think cfr meant to say you shouldn't "fix" bash path - as some users did. Unfortunately there's a bit confusion wrt which paths should be used - see this ML thread.
    Some say we should keep /bin/foo for compatibility, others say that we should boldly move to /usr/bin/foo.

  • How do i remove the DS_Store from my new installed MAMP?

    I am trying to remove the DS_Store from my MAMP so it doesnt show errors when i run MAMP.

    Check your php.ini file for errors. More info: http://www.meetup.com/bostonphp/messages/boards/thread/14417851?thread=14417851

  • Include file error from a new install of C++ compiler on Solaris 5.7

    Here is the command line being executed:
    CC test.cc
    Here is the sample cc file being compiled:
    #include <iostream>
    int main() {
    std::cout << "Real programmers write C++!" << std::endl;
    return 0;
    Error Output:
    "/opt/SUNWspro/WS6/include/CC/std/stddef.h", line 7: Error: Could not open inclu
    de file <sys/feature_tests.h>.
    "/opt/SUNWspro/WS6/include/CC/std/stddef.h", line 15: Error: Could not open incl
    ude file <sys/isa_defs.h>.
    "/opt/SUNWspro/WS6/include/CC/std/stdarg.h", line 7: Error: Could not open inclu
    de file <sys/feature_tests.h>.
    "/opt/SUNWspro/WS6/include/CC/std/string.h", line 7: Error: Could not open inclu
    de file <sys/feature_tests.h>.
    "/opt/SUNWspro/WS6/include/CC/std/ctype.h", line 7: Error: Could not open includ
    e file <sys/feature_tests.h>.
    "/opt/SUNWspro/WS6/include/CC/std/wchar.h", line 6: Error: Could not open includ
    e file <sys/feature_tests.h>.
    "/opt/SUNWspro/WS6/include/CC/wchar_iso_SUNWCC.h", line 34: Error: Could not ope
    n include file <sys/isa_defs.h>.
    "/opt/SUNWspro/WS6/include/CC/wchar_iso_SUNWCC.h", line 35: Error: Could not ope
    n include file <stdio_tag.h>.
    "/opt/SUNWspro/WS6/include/CC/wchar_iso_SUNWCC.h", line 36: Error: Could not ope
    n include file <wchar_impl.h>.
    "/opt/SUNWspro/WS6/include/CC/std/time.h", line 7: Error: Could not open include
    file <sys/feature_tests.h>.
    "/opt/SUNWspro/WS6/include/CC/std/time.h", line 42: Error: Could not open includ
    e file <sys/types.h>.
    "/opt/SUNWspro/WS6/include/CC/std/time.h", line 52: Error: Could not open includ
    e file <sys/time_impl.h>.
    "/opt/SUNWspro/WS6/include/CC/std/time.h", line 85: Error: Type name expected in
    stead of "pthread_attr_t".
    "/opt/SUNWspro/WS6/include/CC/std/time.h", line 85: Error: No storage class or t
    ype for this declaration.
    "/opt/SUNWspro/WS6/include/CC/std/time.h", line 85: Error: "," expected instead
    of "*".
    "/opt/SUNWspro/WS6/include/CC/std/time.h", line 86: Error: Use ";" to terminate
    declarations.
    "/opt/SUNWspro/WS6/include/CC/wchar_iso_SUNWCC.h", line 38: Error: Could not ope
    n include file <sys/va_list.h>.
    "/opt/SUNWspro/WS6/include/CC/wchar_iso_SUNWCC.h", line 94: Error: __FILE is not
    defined.
    "/opt/SUNWspro/WS6/include/CC/wchar_iso_SUNWCC.h", line 95: Error: __FILE is not
    defined.
    "/opt/SUNWspro/WS6/include/CC/wchar_iso_SUNWCC.h", line 96: Error: __FILE is not
    defined.
    "/opt/SUNWspro/WS6/include/CC/wchar_iso_SUNWCC.h", line 97: Error: __FILE is not
    defined.
    "/opt/SUNWspro/WS6/include/CC/wchar_iso_SUNWCC.h", line 98: Error: __FILE is not
    defined.
    "/opt/SUNWspro/WS6/include/CC/wchar_iso_SUNWCC.h", line 99: Error: __FILE is not
    defined.
    "/opt/SUNWspro/WS6/include/CC/wchar_iso_SUNWCC.h", line 100: Error: __FILE is no
    t defined.
    "/opt/SUNWspro/WS6/include/CC/wchar_iso_SUNWCC.h", line 152: Error: __FILE is no
    t defined.
    Compilation aborted, too many Error messages.
    Could someone please help with solving this compilation error.
    Thanks

    Hi there,
    I guess a simple modification to your PATH statement would solve this, you can also specify "-I /usr/include" in your makefile as a path to search for. So I only think your environment needs a little twinkling.
    M. Poels ([email protected])

  • I cannot get Elements 11 to launch from a new install.

    I have spent 1 1/2 hours trying to get elements 11 editor to start.

    Some more information would help: operating system?  Photoshop or Premiere?  How are you trying to start it, and what happens when you try?

  • [SOLVED]Multiple Problems after a new install on Arch Linux

    Hello all,
    I just finished installing Arch Linux from the core ISO which I downloaded from the site. The install went smoothly and booted up fine. Also I was able to install gnome and its extras fine as well. On the first boot after installing gnome I managed to get my resolution correct also. However later on after I installed compiz fusion everything with the resolution seems to be going wrong . My computer specs are shown below :
    AMD 64 3200
    Asus M2N MX-SE
    2 GB Ram
    Geforce 8600 GT
    Viewsonic VA1918wm (Native resolution is 1440x900)
    At the moment I can only manage to get upto 1024x768 and it looks quite bad at that resolution. I have attached the xorg.conf I have at the moment.
    Section "ServerLayout"
    Identifier "X.org Configured"
    Screen 0 "Screen0" 0 0
    InputDevice "Mouse0" "CorePointer"
    InputDevice "Keyboard0" "CoreKeyboard"
    EndSection
    Section "Files"
    ModulePath "/usr/lib/xorg/modules"
    FontPath "/usr/share/fonts/misc"
    FontPath "/usr/share/fonts/100dpi:unscaled"
    FontPath "/usr/share/fonts/75dpi:unscaled"
    FontPath "/usr/share/fonts/TTF"
    FontPath "/usr/share/fonts/Type1"
    EndSection
    Section "Module"
    Load "dbe"
    Load "record"
    Load "extmod"
    Load "glx"
    Load "dri2"
    Load "dri"
    EndSection
    Section "InputDevice"
    Identifier "Keyboard0"
    Driver "kbd"
    EndSection
    Section "InputDevice"
    Identifier "Mouse0"
    Driver "mouse"
    Option "Protocol" "auto"
    Option "Device" "/dev/input/mice"
    Option "ZAxisMapping" "4 5 6 7"
    EndSection
    Section "Monitor"
    Identifier "Monitor0"
    VendorName "Monitor Vendor"
    ModelName "Monitor Model"
    EndSection
    Section "Device"
    Identifier "Card0"
    Driver "nvidia"
    VendorName "nVidia Corporation"
    BoardName "G84 [GeForce 8600 GT]"
    BusID "PCI:2:0:0"
    EndSection
    Section "Screen"
    Identifier "Screen0"
    Device "Card0"
    Monitor "Monitor0"
    SubSection "Display"
    Viewport 0 0
    Depth 1
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 4
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 8
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 15
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 16
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 24
    EndSubSection
    EndSection
    While I was trying to fix this I noticed I was encountering other problems also. For one I found that sometimes dhcpcd times out on booting up and I cant seemt o connect to the Internet on booting. Although I just thought of trying a static IP and I'll post if that helped later on.
    Another problem is I found that I seem to get the following error randomly. Pressing ctrl + D after this just restarts the machine.
    The superblock could not be read or does not describe a correct ext2
    filesystem. If the device is valid and it really contains an ext2
    filesystem (and not swap or ufs or something else), then the superblock
    is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>
    Finally, while I boot up I noticed that it says "Mounting root partition as read only   [DONE]"  Is the root partition supposed ot be mounted as read only ? Attached my fstab just in case it is needed.
    # /etc/fstab: static file system information
    # <file system> <dir> <type> <options> <dump> <pass>
    none /dev/pts devpts defaults 0 0
    none /dev/shm tmpfs defaults 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/sda3 /boot ext3 defaults 0 1
    /dev/sdb1 / ext3 defaults 0 1
    /dev/sdb2 swap swap defaults 0 0
    /dev/sdb3 /home ext3 defaults 0 1
    As you can see I'm quite new to Arch Linux so any help would be deeply appreciated.
    Last edited by FilledVoid (2009-09-11 16:28:28)

    Thank you for all your suggestions . I tried replacing the ID to Card0 but it didnt seem to fix it . However on the bright side I checked more threads on the forum and found some that helped out . :)
    http://bbs.archlinux.org/viewtopic.php?id=75070&p=2
    http://bbs.archlinux.org/viewtopic.php?id=72788
    http://bbs.archlinux.org/viewtopic.php?id=76938
    I copied the xorg.conf file from the third link and just made minor changes to it like removing all the resolutions I didn't need and now its working fine :).
    Now Im just stuck with two problems. One is the following message which appears randomly.
    The superblock could not be read or does not describe a correct ext2
    filesystem. If the device is valid and it really contains an ext2
    filesystem (and not swap or ufs or something else), then the superblock
    is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>
    ******************* FILESYSTEM CHECK FAILED *************
    * Please repair manually and reboot. Note that the root *
    * filesystem is currently mounted read-only. To remount *
    * it read-write type: mount -n -o remount,rw / *
    * When you exit the mantenance shel the system will *
    * reboot automatically. *
    A thread about the same can be found http://bbs.archlinux.org/viewtopic.php?pid=295384 but there isn't a solution on it. 
    The second is the intermittent problems with the Network being setup. Sometimes when I boot up it just says dhcpcd timedout and I won't be able to connect . However I can connect on another machine at the same time.
    Took a look at the drive in question with gparted and it shows the below information:
    /dev/sdb1 ext3   /   32.59 GB    4.92 GB   27.68 GB  boot
    By any chance is any of the above information relevant :x ?

  • Intermittent crashes on new install

    Hi,
    I am seeing intermittent crashes on a new install of Arch.
    I see different messages on crash, quite often
    INFO: rcu_preempt_state detected stalls on CPUs/tasks:
    also
    BUG: Bad page map in process bash
    and other processes.
    sometimes:
    CPU: 1 PID: 1 Comm: shutdown tainted
    I am vague here in the specific messages because it's not always the same and partly because I usually lose the logs due to hard restarting the machine.
    I realize that the information here is somewhat lacking so I don't expect a magic answer to solve the problem. I am looking for advice on where to go from here to try and get it fixed.
    The system seems normal most of the time then crashes without warning. When it does happen it will almost certainly get stuck at what seems to be the very  last stage of shutdown (that is if it allowed me to use the shell). It might or might not go wrong after reboot then.
    I've done 2 cycles of test using memtest, both passing.
    Any advice? Could a faulty hard drive possible be the cause?

    TheSaint wrote:How much big is your RAM and swap ?
    Perhaps you may add one more swap file, for testing purposes.
    I suspect the most problem starts within swapping. You may look at this for references.
    I've 4GB RAM and another 4GB swap partition.
    I've tried using swapfile instead of the partition already to no avail.
    I've also played with the swap performance settings, again, to no avail.
    I've some more information to add now:
    I left the system on last night and using it normally to see whether the hard drive replacement actually fixed the crashes (assuming the swap issues were separate). After 24 hours and some fair use, I was optimistic that the drive was in fact at fault. I then made some changes to a smb.conf file and restarted using:
    sudo systemctl restart smbd.service
    The systemd returned with an error saying smbd failed to start. I checked the logs and smbd reported a segfault. I try again several times, leave it a few minutes and try again (having reverted to the last working smb.conf), segfault still occurs. I then checked "free -m" and noticed that the memory is mostly unused but the entire RAM is used for cache (which I guess is normal anyway). I then cleared the cache:
    echo 3 | tee /proc/sys/vm/drop_caches
    and immediately I was able to restart smbd.
    A few hours go by and I do some rsync'ing to a CIFS mounted share. Partway through I get the following:
    Jan 15 18:17:01 engserv sudo[7859]: sth : TTY=pts/0 ; PWD=/mnt/smb/share2 ; USER=root ; COMMAND=/usr/bin/rsync --info=PROGRESS2 -a /mnt/smb/pc1/Proj/All/ /media/data/Proj/All/
    Jan 15 18:17:01 engserv sudo[7859]: pam_unix(sudo:session): session opened for user root by sth(uid=0)
    Jan 15 18:36:00 engserv kernel: INFO: task jbd2/sdb1-8:215 blocked for more than 120 seconds.
    Jan 15 18:36:01 engserv kernel: Not tainted 3.17.6-1-ARCH #1
    Jan 15 18:36:01 engserv kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
    Jan 15 18:36:01 engserv kernel: jbd2/sdb1-8 D 0000000000000000 0 215 2 0x00000000
    Jan 15 18:36:01 engserv kernel: ffff8800bcc27c90 0000000000000046 ffff8800bd24c670 00000000000135c0
    Jan 15 18:36:01 engserv kernel: ffff8800bcc27fd8 00000000000135c0 ffff88003b934670 ffff8800bd24c670
    Jan 15 18:36:01 engserv kernel: ffff8800bcc27be0 ffff8800bcc27bf8 ffff8800bcc27be0 ffffffffa024b3c7
    Jan 15 18:36:01 engserv kernel: Call Trace:
    Jan 15 18:36:01 engserv kernel: [<ffffffffa024b3c7>] ? ext4_mb_unload_buddy.isra.18+0x27/0x30 [ext4]
    Jan 15 18:36:01 engserv kernel: [<ffffffff810b5f30>] ? cpuacct_charge+0x50/0x60
    Jan 15 18:36:01 engserv kernel: [<ffffffff810a4c9c>] ? update_curr+0xec/0x1b0
    Jan 15 18:36:01 engserv kernel: [<ffffffff810a51ff>] ? dequeue_entity+0x13f/0x580
    Jan 15 18:36:01 engserv kernel: [<ffffffff81539649>] schedule+0x29/0x70
    Jan 15 18:36:01 engserv kernel: [<ffffffffa00fb806>] jbd2_journal_commit_transaction+0x236/0x19c0 [jbd2]
    Jan 15 18:36:01 engserv kernel: [<ffffffff810a9954>] ? pick_next_task_fair+0x144/0x520
    Jan 15 18:36:01 engserv kernel: [<ffffffff810136b2>] ? __switch_to+0x1b2/0x5e0
    Jan 15 18:36:01 engserv kernel: [<ffffffff810af960>] ? __wake_up_sync+0x20/0x20
    Jan 15 18:36:01 engserv kernel: [<ffffffff810d659e>] ? try_to_del_timer_sync+0x5e/0x90
    Jan 15 18:36:01 engserv kernel: [<ffffffffa010280c>] kjournald2+0xec/0x2a0 [jbd2]
    Jan 15 18:36:01 engserv kernel: [<ffffffff810af960>] ? __wake_up_sync+0x20/0x20
    Jan 15 18:36:01 engserv kernel: [<ffffffffa0102720>] ? commit_timeout+0x10/0x10 [jbd2]
    Jan 15 18:36:01 engserv kernel: [<ffffffff8108e2ea>] kthread+0xea/0x100
    Jan 15 18:36:01 engserv kernel: [<ffffffff8108e200>] ? kthread_create_on_node+0x1b0/0x1b0
    Jan 15 18:36:01 engserv kernel: [<ffffffff8153dbbc>] ret_from_fork+0x7c/0xb0
    Jan 15 18:36:01 engserv kernel: [<ffffffff8108e200>] ? kthread_create_on_node+0x1b0/0x1b0
    Jan 15 18:36:01 engserv kernel: INFO: task rsync:7862 blocked for more than 120 seconds.
    Jan 15 18:36:01 engserv kernel: Not tainted 3.17.6-1-ARCH #1
    Jan 15 18:36:01 engserv kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
    Jan 15 18:36:01 engserv kernel: rsync D 0000000000000002 0 7862 7861 0x00000000
    Jan 15 18:36:01 engserv kernel: ffff8800bd337a80 0000000000000086 ffff88003b934670 00000000000135c0
    Jan 15 18:36:01 engserv kernel: ffff8800bd337fd8 00000000000135c0 ffff880138400000 ffff88003b934670
    Jan 15 18:36:01 engserv kernel: ffffffff00000e00 00000000010200da 0000000000000246 ffff88013eff96c0
    Jan 15 18:36:01 engserv kernel: Call Trace:
    Jan 15 18:36:01 engserv kernel: [<ffffffff8115ab54>] ? __alloc_pages_nodemask+0x174/0xb40
    Jan 15 18:36:01 engserv kernel: [<ffffffff81539649>] schedule+0x29/0x70
    Jan 15 18:36:01 engserv kernel: [<ffffffffa00f808d>] wait_transaction_locked+0x8d/0xd0 [jbd2]
    Jan 15 18:36:01 engserv kernel: [<ffffffff810af960>] ? __wake_up_sync+0x20/0x20
    Jan 15 18:36:01 engserv kernel: [<ffffffffa00f83c2>] start_this_handle+0x262/0x610 [jbd2]
    Jan 15 18:36:01 engserv kernel: [<ffffffff81150c1e>] ? __add_to_page_cache_locked+0x24e/0x2c0
    Jan 15 18:36:01 engserv kernel: [<ffffffff811ab9da>] ? kmem_cache_alloc+0x16a/0x170
    Jan 15 18:36:01 engserv kernel: [<ffffffffa00f8b6b>] jbd2__journal_start+0xfb/0x210 [jbd2]
    Jan 15 18:36:01 engserv kernel: [<ffffffffa021ce4f>] ? ext4_da_write_begin+0x10f/0x350 [ext4]
    Jan 15 18:36:01 engserv kernel: [<ffffffffa02486cd>] __ext4_journal_start_sb+0x6d/0x110 [ext4]
    Jan 15 18:36:01 engserv kernel: [<ffffffffa021ce4f>] ext4_da_write_begin+0x10f/0x350 [ext4]
    Jan 15 18:36:01 engserv kernel: [<ffffffff8115191a>] generic_perform_write+0xca/0x1e0
    Jan 15 18:36:01 engserv kernel: [<ffffffff81153345>] __generic_file_write_iter+0x1e5/0x3b0
    Jan 15 18:36:01 engserv kernel: [<ffffffffa0211eba>] ext4_file_write_iter+0x11a/0x3f0 [ext4]
    Jan 15 18:36:01 engserv kernel: [<ffffffff811dc05b>] ? core_sys_select+0x2cb/0x330
    Jan 15 18:36:01 engserv kernel: [<ffffffff8142935b>] ? sock_aio_read.part.29+0xcb/0x100
    Jan 15 18:36:01 engserv kernel: [<ffffffff811c71ee>] new_sync_write+0x8e/0xd0
    Jan 15 18:36:01 engserv kernel: [<ffffffff811c7967>] vfs_write+0xb7/0x200
    Jan 15 18:36:01 engserv kernel: [<ffffffff811c787c>] ? vfs_read+0x13c/0x170
    Jan 15 18:36:01 engserv kernel: [<ffffffff811c85d9>] SyS_write+0x59/0xd0
    Jan 15 18:36:01 engserv kernel: [<ffffffff8153dc69>] system_call_fastpath+0x16/0x1b
    Jan 15 18:38:00 engserv kernel: INFO: task jbd2/sdb1-8:215 blocked for more than 120 seconds.
    Jan 15 18:38:00 engserv kernel: Not tainted 3.17.6-1-ARCH #1
    Jan 15 18:38:00 engserv kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
    Jan 15 18:38:00 engserv kernel: jbd2/sdb1-8 D 0000000000000000 0 215 2 0x00000000
    Jan 15 18:38:00 engserv kernel: ffff8800bcc27c90 0000000000000046 ffff8800bd24c670 00000000000135c0
    Jan 15 18:38:00 engserv kernel: ffff8800bcc27fd8 00000000000135c0 ffff88003b934670 ffff8800bd24c670
    Jan 15 18:38:00 engserv kernel: ffff8800bcc27be0 ffff8800bcc27bf8 ffff8800bcc27be0 ffffffffa024b3c7
    Jan 15 18:38:00 engserv kernel: Call Trace:
    Jan 15 18:38:00 engserv kernel: [<ffffffffa024b3c7>] ? ext4_mb_unload_buddy.isra.18+0x27/0x30 [ext4]
    Jan 15 18:38:00 engserv kernel: [<ffffffff810b5f30>] ? cpuacct_charge+0x50/0x60
    Jan 15 18:38:00 engserv kernel: [<ffffffff810a4c9c>] ? update_curr+0xec/0x1b0
    Jan 15 18:38:00 engserv kernel: [<ffffffff810a51ff>] ? dequeue_entity+0x13f/0x580
    Jan 15 18:38:00 engserv kernel: [<ffffffff81539649>] schedule+0x29/0x70
    Jan 15 18:38:00 engserv kernel: [<ffffffffa00fb806>] jbd2_journal_commit_transaction+0x236/0x19c0 [jbd2]
    Jan 15 18:38:00 engserv kernel: [<ffffffff810a9954>] ? pick_next_task_fair+0x144/0x520
    Jan 15 18:38:00 engserv kernel: [<ffffffff810136b2>] ? __switch_to+0x1b2/0x5e0
    Jan 15 18:38:00 engserv kernel: [<ffffffff810af960>] ? __wake_up_sync+0x20/0x20
    Jan 15 18:38:00 engserv kernel: [<ffffffff810d659e>] ? try_to_del_timer_sync+0x5e/0x90
    Jan 15 18:38:00 engserv kernel: [<ffffffffa010280c>] kjournald2+0xec/0x2a0 [jbd2]
    Jan 15 18:38:00 engserv kernel: [<ffffffff810af960>] ? __wake_up_sync+0x20/0x20
    Jan 15 18:38:00 engserv kernel: [<ffffffffa0102720>] ? commit_timeout+0x10/0x10 [jbd2]
    Jan 15 18:38:00 engserv kernel: [<ffffffff8108e2ea>] kthread+0xea/0x100
    Jan 15 18:38:00 engserv kernel: [<ffffffff8108e200>] ? kthread_create_on_node+0x1b0/0x1b0
    Jan 15 18:38:00 engserv kernel: [<ffffffff8153dbbc>] ret_from_fork+0x7c/0xb0
    Jan 15 18:38:00 engserv kernel: [<ffffffff8108e200>] ? kthread_create_on_node+0x1b0/0x1b0
    Jan 15 18:38:00 engserv kernel: INFO: task rsync:7862 blocked for more than 120 seconds.
    Jan 15 18:38:00 engserv kernel: Not tainted 3.17.6-1-ARCH #1
    Jan 15 18:38:00 engserv kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
    Jan 15 18:38:00 engserv kernel: rsync D 0000000000000002 0 7862 7861 0x00000000
    Jan 15 18:38:00 engserv kernel: ffff8800bd337a80 0000000000000086 ffff88003b934670 00000000000135c0
    Jan 15 18:38:00 engserv kernel: ffff8800bd337fd8 00000000000135c0 ffff880138400000 ffff88003b934670
    Jan 15 18:38:00 engserv kernel: ffffffff00000e00 00000000010200da 0000000000000246 ffff88013eff96c0
    Jan 15 18:38:00 engserv kernel: Call Trace:
    Jan 15 18:38:00 engserv kernel: [<ffffffff8115ab54>] ? __alloc_pages_nodemask+0x174/0xb40
    Jan 15 18:38:00 engserv kernel: [<ffffffff81539649>] schedule+0x29/0x70
    Jan 15 18:38:00 engserv kernel: [<ffffffffa00f808d>] wait_transaction_locked+0x8d/0xd0 [jbd2]
    Jan 15 18:38:00 engserv kernel: [<ffffffff810af960>] ? __wake_up_sync+0x20/0x20
    Jan 15 18:38:00 engserv kernel: [<ffffffffa00f83c2>] start_this_handle+0x262/0x610 [jbd2]
    Jan 15 18:38:00 engserv kernel: [<ffffffff81150c1e>] ? __add_to_page_cache_locked+0x24e/0x2c0
    Jan 15 18:38:01 engserv kernel: [<ffffffff811ab9da>] ? kmem_cache_alloc+0x16a/0x170
    Jan 15 18:38:01 engserv kernel: [<ffffffffa00f8b6b>] jbd2__journal_start+0xfb/0x210 [jbd2]
    Jan 15 18:38:01 engserv kernel: [<ffffffffa021ce4f>] ? ext4_da_write_begin+0x10f/0x350 [ext4]
    Jan 15 18:38:01 engserv kernel: [<ffffffffa02486cd>] __ext4_journal_start_sb+0x6d/0x110 [ext4]
    Jan 15 18:38:01 engserv kernel: [<ffffffffa021ce4f>] ext4_da_write_begin+0x10f/0x350 [ext4]
    Jan 15 18:38:01 engserv kernel: [<ffffffff8115191a>] generic_perform_write+0xca/0x1e0
    Jan 15 18:38:01 engserv kernel: [<ffffffff81153345>] __generic_file_write_iter+0x1e5/0x3b0
    Jan 15 18:38:01 engserv kernel: [<ffffffffa0211eba>] ext4_file_write_iter+0x11a/0x3f0 [ext4]
    Jan 15 18:38:01 engserv kernel: [<ffffffff811dc05b>] ? core_sys_select+0x2cb/0x330
    Jan 15 18:38:01 engserv kernel: [<ffffffff8142935b>] ? sock_aio_read.part.29+0xcb/0x100
    Jan 15 18:38:01 engserv kernel: [<ffffffff811c71ee>] new_sync_write+0x8e/0xd0
    Jan 15 18:38:01 engserv kernel: [<ffffffff811c7967>] vfs_write+0xb7/0x200
    Jan 15 18:38:01 engserv kernel: [<ffffffff811c787c>] ? vfs_read+0x13c/0x170
    Jan 15 18:38:01 engserv kernel: [<ffffffff811c85d9>] SyS_write+0x59/0xd0
    Jan 15 18:38:01 engserv kernel: [<ffffffff8153dc69>] system_call_fastpath+0x16/0x1b
    Jan 15 18:40:00 engserv kernel: INFO: task jbd2/sdb1-8:215 blocked for more than 120 seconds.
    Jan 15 18:40:00 engserv kernel: Not tainted 3.17.6-1-ARCH #1
    Jan 15 18:40:00 engserv kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
    Jan 15 18:40:00 engserv kernel: jbd2/sdb1-8 D 0000000000000000 0 215 2 0x00000000
    Jan 15 18:40:00 engserv kernel: ffff8800bcc27c90 0000000000000046 ffff8800bd24c670 00000000000135c0
    Jan 15 18:40:00 engserv kernel: ffff8800bcc27fd8 00000000000135c0 ffff88003b934670 ffff8800bd24c670
    Jan 15 18:40:00 engserv kernel: ffff8800bcc27be0 ffff8800bcc27bf8 ffff8800bcc27be0 ffffffffa024b3c7
    Jan 15 18:40:00 engserv kernel: Call Trace:
    Jan 15 18:40:00 engserv kernel: [<ffffffffa024b3c7>] ? ext4_mb_unload_buddy.isra.18+0x27/0x30 [ext4]
    Jan 15 18:40:00 engserv kernel: [<ffffffff810b5f30>] ? cpuacct_charge+0x50/0x60
    Jan 15 18:40:00 engserv kernel: [<ffffffff810a4c9c>] ? update_curr+0xec/0x1b0
    Jan 15 18:40:00 engserv kernel: [<ffffffff810a51ff>] ? dequeue_entity+0x13f/0x580
    Jan 15 18:40:00 engserv kernel: [<ffffffff81539649>] schedule+0x29/0x70
    Jan 15 18:40:00 engserv kernel: [<ffffffffa00fb806>] jbd2_journal_commit_transaction+0x236/0x19c0 [jbd2]
    Jan 15 18:40:00 engserv kernel: [<ffffffff810a9954>] ? pick_next_task_fair+0x144/0x520
    Jan 15 18:40:01 engserv kernel: [<ffffffff810136b2>] ? __switch_to+0x1b2/0x5e0
    Jan 15 18:40:01 engserv kernel: [<ffffffff810af960>] ? __wake_up_sync+0x20/0x20
    Jan 15 18:40:01 engserv kernel: [<ffffffff810d659e>] ? try_to_del_timer_sync+0x5e/0x90
    Jan 15 18:40:01 engserv kernel: [<ffffffffa010280c>] kjournald2+0xec/0x2a0 [jbd2]
    Jan 15 18:40:01 engserv kernel: [<ffffffff810af960>] ? __wake_up_sync+0x20/0x20
    Jan 15 18:40:01 engserv kernel: [<ffffffffa0102720>] ? commit_timeout+0x10/0x10 [jbd2]
    Jan 15 18:40:01 engserv kernel: [<ffffffff8108e2ea>] kthread+0xea/0x100
    Jan 15 18:40:01 engserv kernel: [<ffffffff8108e200>] ? kthread_create_on_node+0x1b0/0x1b0
    Jan 15 18:40:01 engserv kernel: [<ffffffff8153dbbc>] ret_from_fork+0x7c/0xb0
    Jan 15 18:40:01 engserv kernel: [<ffffffff8108e200>] ? kthread_create_on_node+0x1b0/0x1b0
    Jan 15 18:40:01 engserv kernel: INFO: task rsync:7862 blocked for more than 120 seconds.
    Jan 15 18:40:01 engserv kernel: Not tainted 3.17.6-1-ARCH #1
    Jan 15 18:40:01 engserv kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
    Jan 15 18:40:01 engserv kernel: rsync D 0000000000000002 0 7862 7861 0x00000000
    Jan 15 18:40:01 engserv kernel: ffff8800bd337a80 0000000000000086 ffff88003b934670 00000000000135c0
    Jan 15 18:40:01 engserv kernel: ffff8800bd337fd8 00000000000135c0 ffff880138400000 ffff88003b934670
    Jan 15 18:40:01 engserv kernel: ffffffff00000e00 00000000010200da 0000000000000246 ffff88013eff96c0
    Jan 15 18:40:01 engserv kernel: Call Trace:
    Jan 15 18:40:01 engserv kernel: [<ffffffff8115ab54>] ? __alloc_pages_nodemask+0x174/0xb40
    Jan 15 18:40:01 engserv kernel: [<ffffffff81539649>] schedule+0x29/0x70
    Jan 15 18:40:01 engserv kernel: [<ffffffffa00f808d>] wait_transaction_locked+0x8d/0xd0 [jbd2]
    Jan 15 18:40:01 engserv kernel: [<ffffffff810af960>] ? __wake_up_sync+0x20/0x20
    Jan 15 18:40:01 engserv kernel: [<ffffffffa00f83c2>] start_this_handle+0x262/0x610 [jbd2]
    Jan 15 18:40:01 engserv kernel: [<ffffffff81150c1e>] ? __add_to_page_cache_locked+0x24e/0x2c0
    Jan 15 18:40:01 engserv kernel: [<ffffffff811ab9da>] ? kmem_cache_alloc+0x16a/0x170
    Jan 15 18:40:01 engserv kernel: [<ffffffffa00f8b6b>] jbd2__journal_start+0xfb/0x210 [jbd2]
    Jan 15 18:40:01 engserv kernel: [<ffffffffa021ce4f>] ? ext4_da_write_begin+0x10f/0x350 [ext4]
    Jan 15 18:40:01 engserv kernel: [<ffffffffa02486cd>] __ext4_journal_start_sb+0x6d/0x110 [ext4]
    Jan 15 18:40:01 engserv kernel: [<ffffffffa021ce4f>] ext4_da_write_begin+0x10f/0x350 [ext4]
    Jan 15 18:40:01 engserv kernel: [<ffffffff8115191a>] generic_perform_write+0xca/0x1e0
    Jan 15 18:40:01 engserv kernel: [<ffffffff81153345>] __generic_file_write_iter+0x1e5/0x3b0
    Jan 15 18:40:01 engserv kernel: [<ffffffffa0211eba>] ext4_file_write_iter+0x11a/0x3f0 [ext4]
    Jan 15 18:40:01 engserv kernel: [<ffffffff811dc05b>] ? core_sys_select+0x2cb/0x330
    Jan 15 18:40:01 engserv kernel: [<ffffffff8142935b>] ? sock_aio_read.part.29+0xcb/0x100
    Jan 15 18:40:01 engserv kernel: [<ffffffff811c71ee>] new_sync_write+0x8e/0xd0
    Jan 15 18:40:01 engserv kernel: [<ffffffff811c7967>] vfs_write+0xb7/0x200
    Jan 15 18:40:01 engserv kernel: [<ffffffff811c787c>] ? vfs_read+0x13c/0x170
    Jan 15 18:40:01 engserv kernel: [<ffffffff811c85d9>] SyS_write+0x59/0xd0
    Jan 15 18:40:01 engserv kernel: [<ffffffff8153dc69>] system_call_fastpath+0x16/0x1b
    Jan 15 18:42:00 engserv kernel: INFO: task jbd2/sdb1-8:215 blocked for more than 120 seconds.
    Jan 15 18:42:01 engserv kernel: Not tainted 3.17.6-1-ARCH #1
    Jan 15 18:42:01 engserv kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
    Jan 15 18:42:01 engserv kernel: jbd2/sdb1-8 D 0000000000000000 0 215 2 0x00000000
    Jan 15 18:42:01 engserv kernel: ffff8800bcc27c90 0000000000000046 ffff8800bd24c670 00000000000135c0
    Jan 15 18:42:01 engserv kernel: ffff8800bcc27fd8 00000000000135c0 ffff88003b934670 ffff8800bd24c670
    Jan 15 18:42:01 engserv kernel: ffff8800bcc27be0 ffff8800bcc27bf8 ffff8800bcc27be0 ffffffffa024b3c7
    Jan 15 18:42:01 engserv kernel: Call Trace:
    Jan 15 18:42:01 engserv kernel: [<ffffffffa024b3c7>] ? ext4_mb_unload_buddy.isra.18+0x27/0x30 [ext4]
    Jan 15 18:42:01 engserv kernel: [<ffffffff810b5f30>] ? cpuacct_charge+0x50/0x60
    Jan 15 18:42:01 engserv kernel: [<ffffffff810a4c9c>] ? update_curr+0xec/0x1b0
    Jan 15 18:42:01 engserv kernel: [<ffffffff810a51ff>] ? dequeue_entity+0x13f/0x580
    Jan 15 18:42:01 engserv kernel: [<ffffffff81539649>] schedule+0x29/0x70
    Jan 15 18:42:01 engserv kernel: [<ffffffffa00fb806>] jbd2_journal_commit_transaction+0x236/0x19c0 [jbd2]
    Jan 15 18:42:01 engserv kernel: [<ffffffff810a9954>] ? pick_next_task_fair+0x144/0x520
    Jan 15 18:42:01 engserv kernel: [<ffffffff810136b2>] ? __switch_to+0x1b2/0x5e0
    Jan 15 18:42:01 engserv kernel: [<ffffffff810af960>] ? __wake_up_sync+0x20/0x20
    Jan 15 18:42:01 engserv kernel: [<ffffffff810d659e>] ? try_to_del_timer_sync+0x5e/0x90
    Jan 15 18:42:01 engserv kernel: [<ffffffffa010280c>] kjournald2+0xec/0x2a0 [jbd2]
    Jan 15 18:42:01 engserv kernel: [<ffffffff810af960>] ? __wake_up_sync+0x20/0x20
    Jan 15 18:42:01 engserv kernel: [<ffffffffa0102720>] ? commit_timeout+0x10/0x10 [jbd2]
    Jan 15 18:42:01 engserv kernel: [<ffffffff8108e2ea>] kthread+0xea/0x100
    Jan 15 18:42:01 engserv kernel: [<ffffffff8108e200>] ? kthread_create_on_node+0x1b0/0x1b0
    Jan 15 18:42:01 engserv kernel: [<ffffffff8153dbbc>] ret_from_fork+0x7c/0xb0
    Jan 15 18:42:01 engserv kernel: [<ffffffff8108e200>] ? kthread_create_on_node+0x1b0/0x1b0
    Jan 15 18:42:01 engserv kernel: INFO: task rsync:7862 blocked for more than 120 seconds.
    Jan 15 18:42:01 engserv kernel: Not tainted 3.17.6-1-ARCH #1
    Jan 15 18:42:01 engserv kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
    Jan 15 18:42:01 engserv kernel: rsync D 0000000000000002 0 7862 7861 0x00000000
    Jan 15 18:42:01 engserv kernel: ffff8800bd337a80 0000000000000086 ffff88003b934670 00000000000135c0
    Jan 15 18:42:01 engserv kernel: ffff8800bd337fd8 00000000000135c0 ffff880138400000 ffff88003b934670
    Jan 15 18:42:01 engserv kernel: ffffffff00000e00 00000000010200da 0000000000000246 ffff88013eff96c0
    Jan 15 18:42:01 engserv kernel: Call Trace:
    Jan 15 18:42:01 engserv kernel: [<ffffffff8115ab54>] ? __alloc_pages_nodemask+0x174/0xb40
    Jan 15 18:42:01 engserv kernel: [<ffffffff81539649>] schedule+0x29/0x70
    Jan 15 18:42:01 engserv kernel: [<ffffffffa00f808d>] wait_transaction_locked+0x8d/0xd0 [jbd2]
    Jan 15 18:42:01 engserv kernel: [<ffffffff810af960>] ? __wake_up_sync+0x20/0x20
    Jan 15 18:42:01 engserv kernel: [<ffffffffa00f83c2>] start_this_handle+0x262/0x610 [jbd2]
    Jan 15 18:42:01 engserv kernel: [<ffffffff81150c1e>] ? __add_to_page_cache_locked+0x24e/0x2c0
    Jan 15 18:42:01 engserv kernel: [<ffffffff811ab9da>] ? kmem_cache_alloc+0x16a/0x170
    Jan 15 18:42:01 engserv kernel: [<ffffffffa00f8b6b>] jbd2__journal_start+0xfb/0x210 [jbd2]
    Jan 15 18:42:01 engserv kernel: [<ffffffffa021ce4f>] ? ext4_da_write_begin+0x10f/0x350 [ext4]
    Jan 15 18:42:01 engserv kernel: [<ffffffffa02486cd>] __ext4_journal_start_sb+0x6d/0x110 [ext4]
    Jan 15 18:42:01 engserv kernel: [<ffffffffa021ce4f>] ext4_da_write_begin+0x10f/0x350 [ext4]
    Jan 15 18:42:01 engserv kernel: [<ffffffff8115191a>] generic_perform_write+0xca/0x1e0
    Jan 15 18:42:01 engserv kernel: [<ffffffff81153345>] __generic_file_write_iter+0x1e5/0x3b0
    Jan 15 18:42:01 engserv kernel: [<ffffffffa0211eba>] ext4_file_write_iter+0x11a/0x3f0 [ext4]
    Jan 15 18:42:01 engserv kernel: [<ffffffff811dc05b>] ? core_sys_select+0x2cb/0x330
    Jan 15 18:42:01 engserv kernel: [<ffffffff8142935b>] ? sock_aio_read.part.29+0xcb/0x100
    Jan 15 18:42:01 engserv kernel: [<ffffffff811c71ee>] new_sync_write+0x8e/0xd0
    Jan 15 18:42:01 engserv kernel: [<ffffffff811c7967>] vfs_write+0xb7/0x200
    Jan 15 18:42:01 engserv kernel: [<ffffffff811c787c>] ? vfs_read+0x13c/0x170
    Jan 15 18:42:01 engserv kernel: [<ffffffff811c85d9>] SyS_write+0x59/0xd0
    Jan 15 18:42:01 engserv kernel: [<ffffffff8153dc69>] system_call_fastpath+0x16/0x1b
    Jan 15 18:44:00 engserv kernel: INFO: task jbd2/sdb1-8:215 blocked for more than 120 seconds.
    Jan 15 18:44:00 engserv kernel: Not tainted 3.17.6-1-ARCH #1
    Jan 15 18:44:00 engserv kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
    Jan 15 18:44:00 engserv kernel: jbd2/sdb1-8 D 0000000000000000 0 215 2 0x00000000
    Jan 15 18:44:00 engserv kernel: ffff8800bcc27c90 0000000000000046 ffff8800bd24c670 00000000000135c0
    Jan 15 18:44:00 engserv kernel: ffff8800bcc27fd8 00000000000135c0 ffff88003b934670 ffff8800bd24c670
    Jan 15 18:44:00 engserv kernel: ffff8800bcc27be0 ffff8800bcc27bf8 ffff8800bcc27be0 ffffffffa024b3c7
    Jan 15 18:44:00 engserv kernel: Call Trace:
    Jan 15 18:44:00 engserv kernel: [<ffffffffa024b3c7>] ? ext4_mb_unload_buddy.isra.18+0x27/0x30 [ext4]
    Jan 15 18:44:00 engserv kernel: [<ffffffff810b5f30>] ? cpuacct_charge+0x50/0x60
    Jan 15 18:44:00 engserv kernel: [<ffffffff810a4c9c>] ? update_curr+0xec/0x1b0
    Jan 15 18:44:00 engserv kernel: [<ffffffff810a51ff>] ? dequeue_entity+0x13f/0x580
    Jan 15 18:44:00 engserv kernel: [<ffffffff81539649>] schedule+0x29/0x70
    Jan 15 18:44:00 engserv kernel: [<ffffffffa00fb806>] jbd2_journal_commit_transaction+0x236/0x19c0 [jbd2]
    Jan 15 18:44:00 engserv kernel: [<ffffffff810a9954>] ? pick_next_task_fair+0x144/0x520
    Jan 15 18:44:00 engserv kernel: [<ffffffff810136b2>] ? __switch_to+0x1b2/0x5e0
    Jan 15 18:44:00 engserv kernel: [<ffffffff810af960>] ? __wake_up_sync+0x20/0x20
    Jan 15 18:44:00 engserv kernel: [<ffffffff810d659e>] ? try_to_del_timer_sync+0x5e/0x90
    Jan 15 18:44:00 engserv kernel: [<ffffffffa010280c>] kjournald2+0xec/0x2a0 [jbd2]
    Jan 15 18:44:00 engserv kernel: [<ffffffff810af960>] ? __wake_up_sync+0x20/0x20
    Jan 15 18:44:00 engserv kernel: [<ffffffffa0102720>] ? commit_timeout+0x10/0x10 [jbd2]
    Jan 15 18:44:00 engserv kernel: [<ffffffff8108e2ea>] kthread+0xea/0x100
    Jan 15 18:44:00 engserv kernel: [<ffffffff8108e200>] ? kthread_create_on_node+0x1b0/0x1b0
    Jan 15 18:44:00 engserv kernel: [<ffffffff8153dbbc>] ret_from_fork+0x7c/0xb0
    Jan 15 18:44:00 engserv kernel: [<ffffffff8108e200>] ? kthread_create_on_node+0x1b0/0x1b0
    Jan 15 18:44:00 engserv kernel: INFO: task rsync:7862 blocked for more than 120 seconds.
    Jan 15 18:44:00 engserv kernel: Not tainted 3.17.6-1-ARCH #1
    Jan 15 18:44:00 engserv kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
    Jan 15 18:44:00 engserv kernel: rsync D 0000000000000002 0 7862 7861 0x00000000
    Jan 15 18:44:00 engserv kernel: ffff8800bd337a80 0000000000000086 ffff88003b934670 00000000000135c0
    Jan 15 18:44:00 engserv kernel: ffff8800bd337fd8 00000000000135c0 ffff880138400000 ffff88003b934670
    Jan 15 18:44:00 engserv kernel: ffffffff00000e00 00000000010200da 0000000000000246 ffff88013eff96c0
    Jan 15 18:44:00 engserv kernel: Call Trace:
    Jan 15 18:44:01 engserv kernel: [<ffffffff8115ab54>] ? __alloc_pages_nodemask+0x174/0xb40
    Jan 15 18:44:01 engserv kernel: [<ffffffff81539649>] schedule+0x29/0x70
    Jan 15 18:44:01 engserv kernel: [<ffffffffa00f808d>] wait_transaction_locked+0x8d/0xd0 [jbd2]
    Jan 15 18:44:01 engserv kernel: [<ffffffff810af960>] ? __wake_up_sync+0x20/0x20
    Jan 15 18:44:01 engserv kernel: [<ffffffffa00f83c2>] start_this_handle+0x262/0x610 [jbd2]
    Jan 15 18:44:01 engserv kernel: [<ffffffff81150c1e>] ? __add_to_page_cache_locked+0x24e/0x2c0
    Jan 15 18:44:01 engserv kernel: [<ffffffff811ab9da>] ? kmem_cache_alloc+0x16a/0x170
    Jan 15 18:44:01 engserv kernel: [<ffffffffa00f8b6b>] jbd2__journal_start+0xfb/0x210 [jbd2]
    Jan 15 18:44:01 engserv kernel: [<ffffffffa021ce4f>] ? ext4_da_write_begin+0x10f/0x350 [ext4]
    Jan 15 18:44:01 engserv kernel: [<ffffffffa02486cd>] __ext4_journal_start_sb+0x6d/0x110 [ext4]
    Jan 15 18:44:01 engserv kernel: [<ffffffffa021ce4f>] ext4_da_write_begin+0x10f/0x350 [ext4]
    Jan 15 18:44:01 engserv kernel: [<ffffffff8115191a>] generic_perform_write+0xca/0x1e0
    Jan 15 18:44:01 engserv kernel: [<ffffffff81153345>] __generic_file_write_iter+0x1e5/0x3b0
    Jan 15 18:44:01 engserv kernel: [<ffffffffa0211eba>] ext4_file_write_iter+0x11a/0x3f0 [ext4]
    Jan 15 18:44:01 engserv kernel: [<ffffffff811dc05b>] ? core_sys_select+0x2cb/0x330
    Jan 15 18:44:01 engserv kernel: [<ffffffff8142935b>] ? sock_aio_read.part.29+0xcb/0x100
    Jan 15 18:44:01 engserv kernel: [<ffffffff811c71ee>] new_sync_write+0x8e/0xd0
    Jan 15 18:44:01 engserv kernel: [<ffffffff811c7967>] vfs_write+0xb7/0x200
    Jan 15 18:44:01 engserv kernel: [<ffffffff811c787c>] ? vfs_read+0x13c/0x170
    Jan 15 18:44:01 engserv kernel: [<ffffffff811c85d9>] SyS_write+0x59/0xd0
    Jan 15 18:44:01 engserv kernel: [<ffffffff8153dc69>] system_call_fastpath+0x16/0x1b
    Jan 15 18:48:48 engserv sudo[7897]: sth : TTY=tty1 ; PWD=/home/sth ; USER=root ; COMMAND=/usr/bin/journalctl -xb --no-pager
    Jan 15 18:48:48 engserv sudo[7897]: pam_unix(sudo:session): session opened for user root by sth(uid=0)
    Jan 15 18:48:49 engserv sudo[7897]: pam_unix(sudo:session): session closed for user root
    Jan 15 18:51:45 engserv sudo[7859]: pam_unix(sudo:session): session closed for user root
    Jan 15 18:52:38 engserv sudo[7911]: sth : TTY=pts/0 ; PWD=/mnt/smb/share2 ; USER=root ; COMMAND=/usr/bin/pkill rsync
    Jan 15 18:52:38 engserv sudo[7911]: pam_unix(sudo:session): session opened for user root by sth(uid=0)
    Jan 15 18:52:38 engserv sudo[7911]: pam_unix(sudo:session): session closed for user root
    Jan 15 18:52:50 engserv sudo[7916]: sth : TTY=pts/0 ; PWD=/mnt/smb/share2 ; USER=root ; COMMAND=/usr/bin/pkill rsync
    Jan 15 18:52:50 engserv sudo[7916]: pam_unix(sudo:session): session opened for user root by sth(uid=0)
    Jan 15 18:52:50 engserv sudo[7916]: pam_unix(sudo:session): session closed for user root
    Jan 15 18:53:06 engserv sudo[7918]: sth : TTY=pts/0 ; PWD=/mnt/smb/share2 ; USER=root ; COMMAND=/usr/bin/pkill -9 rsync
    Jan 15 18:53:06 engserv sudo[7918]: pam_unix(sudo:session): session opened for user root by sth(uid=0)
    Jan 15 18:53:06 engserv sudo[7918]: pam_unix(sudo:session): session closed for user root
    Jan 15 18:55:59 engserv sudo[7949]: sth : TTY=pts/0 ; PWD=/mnt/smb/share2 ; USER=root ; COMMAND=/usr/bin/pkill -9 rsync
    Jan 15 18:55:59 engserv sudo[7949]: pam_unix(sudo:session): session opened for user root by sth(uid=0)
    Jan 15 18:55:59 engserv sudo[7949]: pam_unix(sudo:session): session closed for user root
    Jan 15 18:56:21 engserv systemd[1]: Starting Getty on tty2...
    -- Subject: Unit [email protected] has begun with start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit [email protected] has begun starting up.
    Jan 15 18:56:21 engserv systemd[1]: Started Getty on tty2.
    -- Subject: Unit [email protected] has finished start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit [email protected] has finished starting up.
    -- The start-up result is done.
    Jan 15 18:56:25 engserv login[7954]: pam_unix(login:session): session opened for user sth by LOGIN(uid=0)
    Jan 15 18:56:25 engserv systemd[1]: Starting Session c4 of user sth.
    -- Subject: Unit session-c4.scope has begun with start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit session-c4.scope has begun starting up.
    Jan 15 18:56:25 engserv systemd-logind[275]: New session c4 of user sth.
    -- Subject: A new session c4 has been created for user sth
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat
    -- A new session with the ID c4 has been created for the user sth.
    -- The leading process of the session is 7954.
    Jan 15 18:56:25 engserv systemd[1]: Started Session c4 of user sth.
    -- Subject: Unit session-c4.scope has finished start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit session-c4.scope has finished starting up.
    -- The start-up result is done.
    Jan 15 18:56:25 engserv login[7954]: LOGIN ON tty2 BY sth
    Jan 15 18:56:39 engserv sudo[7960]: sth : TTY=tty2 ; PWD=/home/sth ; USER=root ; COMMAND=/usr/bin/umount /media/data/
    Jan 15 18:56:39 engserv sudo[7960]: pam_unix(sudo:session): session opened for user root by sth(uid=0)
    Jan 15 18:56:39 engserv sudo[7960]: pam_unix(sudo:session): session closed for user root
    Jan 15 19:02:43 engserv sudo[7984]: sth : TTY=pts/0 ; PWD=/mnt/smb/share2 ; USER=root ; COMMAND=/usr/bin/tee /proc/sys/vm/drop_caches
    Jan 15 19:02:43 engserv sudo[7984]: pam_unix(sudo:session): session opened for user root by sth(uid=0)
    Jan 15 19:02:43 engserv kernel: ------------[ cut here ]------------
    Jan 15 19:02:43 engserv kernel: WARNING: CPU: 3 PID: 7985 at mm/truncate.c:508 invalidate_mapping_pages+0x1c1/0x1f0()
    Jan 15 19:02:43 engserv kernel: Modules linked in: des3_ede_x86_64 des_generic arc4 ecb md4 md5 hmac nls_utf8 cifs dns_resolver fscache cfg80211 rfkill nls_iso8859_1 nls_cp437 vfat fat nouveau video ttm drm_kms_helper drm kvm_amd r8169 i2c_algo_bit kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel mxm_wmi evdev snd_hda_codec_realtek snd_hda_codec_hdmi sp5100_tco aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd mac_hid pcspkr serio_raw edac_core snd_hda_codec_generic edac_mce_amd mii fam15h_power i2c_piix4 k10temp hwmon i2c_core shpchp tpm_infineon snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep snd_pcm snd_timer snd soundcore wmi tpm_tis tpm button acpi_cpufreq processor sch_fq_codel ext4 crc16 mbcache jbd2 sd_mod crc_t10dif crct10dif_common atkbd libps2 ahci firewire_ohci
    Jan 15 19:02:43 engserv kernel: ehci_pci libahci ohci_pci firewire_core ohci_hcd libata crc_itu_t xhci_hcd ehci_hcd scsi_mod usbcore usb_common i8042 serio
    Jan 15 19:02:43 engserv kernel: CPU: 3 PID: 7985 Comm: tee Not tainted 3.17.6-1-ARCH #1
    Jan 15 19:02:43 engserv kernel: Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./990FXA-UD3, BIOS FC 02/05/2013
    Jan 15 19:02:43 engserv kernel: 0000000000000000 000000008e7f3f05 ffff8800b9727c58 ffffffff81537c3e
    Jan 15 19:02:43 engserv kernel: 0000000000000000 ffff8800b9727c90 ffffffff8107079d 0000000000000003
    Jan 15 19:02:43 engserv kernel: 0000000000000003 ffff880137e2c0a8 ffffffffffffffff ffffea0000637e00
    Jan 15 19:02:43 engserv kernel: Call Trace:
    Jan 15 19:02:43 engserv kernel: [<ffffffff81537c3e>] dump_stack+0x4d/0x6f
    Jan 15 19:02:43 engserv kernel: [<ffffffff8107079d>] warn_slowpath_common+0x7d/0xa0
    Jan 15 19:02:43 engserv kernel: [<ffffffff810708ca>] warn_slowpath_null+0x1a/0x20
    Jan 15 19:02:43 engserv kernel: [<ffffffff811627c1>] invalidate_mapping_pages+0x1c1/0x1f0
    Jan 15 19:02:43 engserv kernel: [<ffffffff81224e0c>] drop_pagecache_sb+0xac/0xf0
    Jan 15 19:02:43 engserv kernel: [<ffffffff81224d60>] ? do_coredump+0xec0/0xec0
    Jan 15 19:02:43 engserv kernel: [<ffffffff811cb432>] iterate_supers+0xb2/0x110
    Jan 15 19:02:43 engserv kernel: [<ffffffff81224ed6>] drop_caches_sysctl_handler+0x86/0x140
    Jan 15 19:02:43 engserv kernel: [<ffffffff81206dac>] ? fsnotify+0x28c/0x370
    Jan 15 19:02:43 engserv kernel: [<ffffffff812387a3>] proc_sys_call_handler+0xd3/0xf0
    Jan 15 19:02:43 engserv kernel: [<ffffffff812387d4>] proc_sys_write+0x14/0x20
    Jan 15 19:02:43 engserv kernel: [<ffffffff811c7967>] vfs_write+0xb7/0x200
    Jan 15 19:02:43 engserv kernel: [<ffffffff811c787c>] ? vfs_read+0x13c/0x170
    Jan 15 19:02:43 engserv kernel: [<ffffffff811c85d9>] SyS_write+0x59/0xd0
    Jan 15 19:02:43 engserv kernel: [<ffffffff8153dc69>] system_call_fastpath+0x16/0x1b
    Jan 15 19:02:43 engserv kernel: ---[ end trace 2601969f96a93148 ]---
    Jan 15 19:02:44 engserv kernel: tee (7985): drop_caches: 3
    Jan 15 19:08:04 engserv sudo[8011]: sth : TTY=tty2 ; PWD=/home/sth ; USER=root ; COMMAND=/usr/bin/reboot
    Jan 15 19:08:04 engserv sudo[8011]: pam_unix(sudo:session): session opened for user root by sth(uid=0)
    Jan 15 19:08:04 engserv systemd[1]: Unmounting /media/data...
    -- Subject: Unit media-data.mount has begun shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit media-data.mount has begun shutting down.
    Jan 15 19:08:04 engserv systemd[1]: Stopping Timers.
    -- Subject: Unit timers.target has begun shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit timers.target has begun shutting down.
    Jan 15 19:08:04 engserv systemd[1]: Stopped target Timers.
    -- Subject: Unit timers.target has finished shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit timers.target has finished shutting down.
    Jan 15 19:08:04 engserv systemd[1]: Stopping Session c3 of user sth.
    -- Subject: Unit session-c3.scope has begun shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit session-c3.scope has begun shutting down.
    Jan 15 19:08:04 engserv systemd[1]: Stopped Session c3 of user sth.
    -- Subject: Unit session-c3.scope has finished shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit session-c3.scope has finished shutting down.
    Jan 15 19:08:04 engserv systemd[1]: Stopping system-systemd\x2dfsck.slice.
    -- Subject: Unit system-systemd\x2dfsck.slice has begun shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit system-systemd\x2dfsck.slice has begun shutting down.
    Jan 15 19:08:04 engserv systemd[1]: Removed slice system-systemd\x2dfsck.slice.
    -- Subject: Unit system-systemd\x2dfsck.slice has finished shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit system-systemd\x2dfsck.slice has finished shutting down.
    Jan 15 19:08:04 engserv systemd[1]: Stopping Sound Card.
    -- Subject: Unit sound.target has begun shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit sound.target has begun shutting down.
    Jan 15 19:08:04 engserv systemd[1]: Stopped target Sound Card.
    -- Subject: Unit sound.target has finished shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit sound.target has finished shutting down.
    Jan 15 19:08:04 engserv systemd[1]: Deactivating swap Swap Partition...
    -- Subject: Unit dev-sda3.swap has begun shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit dev-sda3.swap has begun shutting down.
    Jan 15 19:08:04 engserv systemd[1]: Stopping Graphical Interface.
    -- Subject: Unit graphical.target has begun shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit graphical.target has begun shutting down.
    Jan 15 19:08:04 engserv systemd[1]: Stopped target Graphical Interface.
    -- Subject: Unit graphical.target has finished shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit graphical.target has finished shutting down.
    Jan 15 19:08:04 engserv systemd[1]: Deactivating swap Swap Partition...
    -- Subject: Unit dev-sda3.swap has begun shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit dev-sda3.swap has begun shutting down.
    Jan 15 19:08:04 engserv systemd[1]: Stopping Daily Cleanup of Temporary Directories.
    -- Subject: Unit systemd-tmpfiles-clean.timer has begun shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit systemd-tmpfiles-clean.timer has begun shutting down.
    Jan 15 19:08:04 engserv systemd[1]: Stopped Daily Cleanup of Temporary Directories.
    -- Subject: Unit systemd-tmpfiles-clean.timer has finished shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit systemd-tmpfiles-clean.timer has finished shutting down.
    Jan 15 19:08:04 engserv systemd[1]: Stopping Session c1 of user sth.
    -- Subject: Unit session-c1.scope has begun shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit session-c1.scope has begun shutting down.
    Jan 15 19:08:04 engserv systemd[1]: Stopped Session c1 of user sth.
    -- Subject: Unit session-c1.scope has finished shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit session-c1.scope has finished shutting down.
    Jan 15 19:08:04 engserv systemd[1]: Stopping User Manager for UID 1000...
    -- Subject: Unit [email protected] has begun shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit [email protected] has begun shutting down.
    Jan 15 19:08:04 engserv systemd[1]: Stopping Avahi mDNS/DNS-SD Stack...
    -- Subject: Unit avahi-daemon.service has begun shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit avahi-daemon.service has begun shutting down.
    Jan 15 19:08:04 engserv systemd[1]: Deactivating swap Swap Partition...
    -- Subject: Unit dev-sda3.swap has begun shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit dev-sda3.swap has begun shutting down.
    Jan 15 19:08:04 engserv systemd[1]: Stopping Session c4 of user sth.
    -- Subject: Unit session-c4.scope has begun shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit session-c4.scope has begun shutting down.
    Jan 15 19:08:04 engserv login[276]: pam_unix(login:session): session closed for user sth
    Jan 15 19:08:04 engserv login[276]: pam_systemd(login:session): Failed to release session: Interrupted system call
    Jan 15 19:08:04 engserv avahi-daemon[411]: Got SIGTERM, quitting.
    Jan 15 19:08:04 engserv avahi-daemon[411]: Leaving mDNS multicast group on interface enp5s0.IPv4 with address 172.16.1.2.
    Jan 15 19:08:04 engserv avahi-daemon[411]: avahi-daemon 0.6.31 exiting.
    Jan 15 19:08:04 engserv sshd[359]: Received signal 15; terminating.
    Jan 15 19:08:04 engserv systemd[1]: Stopped Session c4 of user sth.
    -- Subject: Unit session-c4.scope has finished shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit session-c4.scope has finished shutting down.
    Jan 15 19:08:04 engserv systemd[1]: Stopping Multi-User System.
    -- Subject: Unit multi-user.target has begun shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit multi-user.target has begun shutting down.
    Jan 15 19:08:04 engserv systemd[1]: Stopped target Multi-User System.
    -- Subject: Unit multi-user.target has finished shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit multi-user.target has finished shutting down.
    Jan 15 19:08:04 engserv systemd[1]: Stopping Daily verification of password and group files.
    -- Subject: Unit shadow.timer has begun shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit shadow.timer has begun shutting down.
    Jan 15 19:08:04 engserv systemd[1]: Stopped Daily verification of password and group files.
    -- Subject: Unit shadow.timer has finished shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit shadow.timer has finished shutting down.
    Jan 15 19:08:04 engserv systemd[1]: Stopping D-Bus System Message Bus...
    -- Subject: Unit dbus.service has begun shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit dbus.service has begun shutting down.
    Jan 15 19:08:04 engserv systemd[1]: Stopping Daily man-db cache update.
    -- Subject: Unit man-db.timer has begun shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit man-db.timer has begun shutting down.
    Jan 15 19:08:04 engserv systemd[1]: Stopped Daily man-db cache update.
    -- Subject: Unit man-db.timer has finished shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit man-db.timer has finished shutting down.
    Jan 15 19:08:04 engserv systemd[1]: Stopping Login Prompts.
    -- Subject: Unit getty.target has begun shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit getty.target has begun shutting down.
    Jan 15 19:08:04 engserv systemd[1]: Stopped target Login Prompts.
    -- Subject: Unit getty.target has finished shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit getty.target has finished shutting down.
    Jan 15 19:08:04 engserv systemd[1]: Stopping Getty on tty1...
    -- Subject: Unit [email protected] has begun shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit [email protected] has begun shutting down.
    Jan 15 19:08:04 engserv systemd-logind[275]: Failed to abandon session scope: Transport endpoint is not connected
    Jan 15 19:08:04 engserv systemd[364]: Stopping Default.
    -- Subject: Unit UNIT has begun shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit UNIT has begun shutting down.
    Jan 15 19:08:04 engserv systemd[364]: Stopped target Default.
    -- Subject: Unit UNIT has finished shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit UNIT has finished shutting down.
    Jan 15 19:08:04 engserv systemd[1]: Starting Generate shutdown-ramfs...
    -- Subject: Unit mkinitcpio-generate-shutdown-ramfs.service has begun with start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit mkinitcpio-generate-shutdown-ramfs.service has begun starting up.
    Jan 15 19:08:04 engserv systemd[364]: Stopping Basic System.
    -- Subject: Unit UNIT has begun shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit UNIT has begun shutting down.
    Jan 15 19:08:04 engserv systemd[364]: Stopped target Basic System.
    -- Subject: Unit UNIT has finished shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit UNIT has finished shutting down.
    Jan 15 19:08:04 engserv systemd[364]: Stopping Timers.
    -- Subject: Unit UNIT has begun shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit UNIT has begun shutting down.
    Jan 15 19:08:04 engserv systemd[364]: Stopped target Timers.
    -- Subject: Unit UNIT has finished shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit UNIT has finished shutting down.
    Jan 15 19:08:04 engserv systemd[364]: Stopping Paths.
    -- Subject: Unit UNIT has begun shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit UNIT has begun shutting down.
    Jan 15 19:08:04 engserv systemd[364]: Stopped target Paths.
    -- Subject: Unit UNIT has finished shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit UNIT has finished shutting down.
    Jan 15 19:08:04 engserv systemd[364]: Stopping Sockets.
    -- Subject: Unit UNIT has begun shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit UNIT has begun shutting down.
    Jan 15 19:08:04 engserv systemd[1]: Stopping Samba SMB/CIFS server...
    -- Subject: Unit smbd.service has begun shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit smbd.service has begun shutting down.
    Jan 15 19:08:04 engserv systemd[364]: Stopped target Sockets.
    -- Subject: Unit UNIT has finished shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit UNIT has finished shutting down.
    Jan 15 19:08:04 engserv systemd[364]: Starting Shutdown.
    -- Subject: Unit UNIT has begun with start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit UNIT has begun starting up.
    Jan 15 19:08:04 engserv systemd[364]: Reached target Shutdown.
    -- Subject: Unit UNIT has finished start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit UNIT has finished starting up.
    -- The start-up result is done.
    Jan 15 19:08:04 engserv systemd[364]: Starting Exit the Session...
    -- Subject: Unit UNIT has begun with start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit UNIT has begun starting up.
    Jan 15 19:08:04 engserv systemd[364]: Received SIGRTMIN+24 from PID 8032 (kill).
    Jan 15 19:08:04 engserv systemd[1]: Stopped User Manager for UID 1000.
    -- Subject: Unit [email protected] has finished shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit [email protected] has finished shutting down.
    Jan 15 19:08:04 engserv systemd[1]: Stopping user-1000.slice.
    -- Subject: Unit user-1000.slice has begun shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit user-1000.slice has begun shutting down.
    Jan 15 19:08:04 engserv systemd[1]: Removed slice user-1000.slice.
    -- Subject: Unit user-1000.slice has finished shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit user-1000.slice has finished shutting down.
    Jan 15 19:08:04 engserv systemd[1]: Stopping Permit User Sessions...
    -- Subject: Unit systemd-user-sessions.service has begun shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit systemd-user-sessions.service has begun shutting down.
    Jan 15 19:08:04 engserv systemd[1]: Stopped Permit User Sessions.
    -- Subject: Unit systemd-user-sessions.service has finished shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit systemd-user-sessions.service has finished shutting down.
    Jan 15 19:08:04 engserv systemd[1]: Stopping Remote File Systems.
    -- Subject: Unit remote-fs.target has begun shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit remote-fs.target has begun shutting down.
    Jan 15 19:08:04 engserv systemd[1]: Stopped target Remote File Systems.
    -- Subject: Unit remote-fs.target has finished shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit remote-fs.target has finished shutting down.
    Jan 15 19:08:04 engserv systemd[1]: Unmounting /mnt/smb/share2...
    -- Subject: Unit mnt-smb-share2.mount has begun shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit mnt-smb-share2.mount has begun shutting down.
    Jan 15 19:08:04 engserv systemd[1]: Unmounting /mnt/smb/share1...
    -- Subject: Unit mnt-smb-share1.mount has begun shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit mnt-smb-share1.mount has begun shutting down.
    Jan 15 19:08:05 engserv systemd[1]: media-data.mount mount process exited, code=exited status=32
    Jan 15 19:08:04 engserv nmbd[7459]: STATUS=daemon 'nmbd' finished starting up and ready to serve connectionsGot SIGTERM: going down...
    Jan 15 19:08:04 engserv systemd[366]: pam_unix(systemd-user:session): session closed for user sth
    Jan 15 19:08:05 engserv umount[8015]: umount: /media/data: target is busy
    Jan 15 19:08:05 engserv umount[8015]: (In some cases useful info about processes that
    Jan 15 19:08:05 engserv umount[8015]: use the device is found by lsof(8) or fuser(1).)
    Jan 15 19:08:05 engserv systemd[1]: Unmounted /mnt/smb/share2.
    -- Subject: Unit mnt-smb-share2.mount has finished shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit mnt-smb-share2.mount has finished shutting down.
    Jan 15 19:08:05 engserv systemd[1]: Unmounted /mnt/smb/share1.
    -- Subject: Unit mnt-smb-share1.mount has finished shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit mnt-smb-share1.mount has finished shutting down.
    Jan 15 19:08:05 engserv systemd[1]: Stopping Network.
    -- Subject: Unit network.target has begun shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit network.target has begun shutting down.
    Jan 15 19:08:05 engserv systemd[1]: Stopped target Network.
    -- Subject: Unit network.target has finished shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit network.target has finished shutting down.
    Jan 15 19:08:05 engserv systemd[1]: Stopping dhcpcd on enp5s0...
    -- Subject: Unit [email protected] has begun shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit [email protected] has begun shutting down.
    Jan 15 19:08:05 engserv dhcpcd[8049]: dhcpcd[8049]: sending signal TERM to pid 358
    Jan 15 19:08:05 engserv dhcpcd[8049]: sending signal TERM to pid 358
    Jan 15 19:08:05 engserv dhcpcd[8049]: waiting for pid 358 to exit
    Jan 15 19:08:05 engserv dhcpcd[358]: received signal TERM from PID 8049, stopping
    Jan 15 19:08:05 engserv dhcpcd[358]: enp5s0: removing interface
    Jan 15 19:08:05 engserv dhcpcd[8049]: dhcpcd[8049]: waiting for pid 358 to exit
    Jan 15 19:08:05 engserv mkinitcpio[8024]: ==> Starting build: none
    Jan 15 19:08:05 engserv dhcpcd[358]: exited
    Jan 15 19:08:05 engserv systemd[1]: [email protected]: main process exited, code=exited, status=1/FAILURE
    Jan 15 19:08:05 engserv mkinitcpio[8024]: -> Running build hook: [sd-shutdown]
    Jan 15 19:08:05 engserv systemd[1]: Stopped dhcpcd on enp5s0.
    -- Subject: Unit [email protected] has finished shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit [email protected] has finished shutting down.
    Jan 15 19:08:05 engserv systemd[1]: Unit [email protected] entered failed state.
    Jan 15 19:08:05 engserv systemd[1]: [email protected] failed.
    Jan 15 19:08:05 engserv systemd[1]: Stopping system-dhcpcd.slice.
    -- Subject: Unit system-dhcpcd.slice has begun shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit system-dhcpcd.slice has begun shutting down.
    Jan 15 19:08:05 engserv systemd[1]: Removed slice system-dhcpcd.slice.
    -- Subject: Unit system-dhcpcd.slice has finished shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit system-dhcpcd.slice has finished shutting down.
    Jan 15 19:08:05 engserv systemd[1]: Stopping Basic System.
    -- Subject: Unit basic.target has begun shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit basic.target has begun shutting down.
    Jan 15 19:08:05 engserv systemd[1]: Stopped target Basic System.
    -- Subject: Unit basic.target has finished shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit basic.target has finished shutting down.
    Jan 15 19:08:05 engserv systemd[1]: Stopping Paths.
    -- Subject: Unit paths.target has begun shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit paths.target has begun shutting down.
    Jan 15 19:08:05 engserv systemd[1]: Stopped target Paths.
    -- Subject: Unit paths.target has finished shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit paths.target has finished shutting down.
    Jan 15 19:08:05 engserv systemd[1]: Stopping Forward Password Requests to Wall Directory Watch.
    -- Subject: Unit systemd-ask-password-wall.path has begun shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit systemd-ask-password-wall.path has begun shutting down.
    Jan 15 19:08:05 engserv systemd[1]: Stopped Forward Password Requests to Wall Directory Watch.
    -- Subject: Unit systemd-ask-password-wall.path has finished shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit systemd-ask-password-wall.path has finished shutting down.
    Jan 15 19:08:05 engserv systemd[1]: Stopping Dispatch Password Requests to Console Directory Watch.
    -- Subject: Unit systemd-ask-password-console.path has begun shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit systemd-ask-password-console.path has begun shutting down.
    Jan 15 19:08:05 engserv systemd[1]: Stopped Dispatch Password Requests to Console Directory Watch.
    -- Subject: Unit systemd-ask-password-console.path has finished shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit systemd-ask-password-console.path has finished shutting down.
    Jan 15 19:08:05 engserv systemd[1]: Stopping Slices.
    -- Subject: Unit slices.target has begun shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit slices.target has begun shutting down.
    Jan 15 19:08:05 engserv systemd[1]: Stopped target Slices.
    -- Subject: Unit slices.target has finished shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit slices.target has finished shutting down.
    Jan 15 19:08:05 engserv systemd[1]: Stopping User and Session Slice.
    -- Subject: Unit user.slice has begun shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit user.slice has begun shutting down.
    Jan 15 19:08:05 engserv systemd[1]: Removed slice User and Session Slice.
    -- Subject: Unit user.slice has finished shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit user.slice has finished shutting down.
    Jan 15 19:08:05 engserv systemd[1]: Stopping Sockets.
    -- Subject: Unit sockets.target has begun shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit sockets.target has begun shutting down.
    Jan 15 19:08:05 engserv systemd[1]: Stopped target Sockets.
    -- Subject: Unit sockets.target has finished shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit sockets.target has finished shutting down.
    Jan 15 19:08:05 engserv systemd[1]: Stopping D-Bus System Message Bus Socket.
    -- Subject: Unit dbus.socket has begun shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit dbus.socket has begun shutting down.
    Jan 15 19:08:05 engserv systemd[1]: Closed D-Bus System Message Bus Socket.
    -- Subject: Unit dbus.socket has finished shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit dbus.socket has finished shutting down.
    Jan 15 19:08:05 engserv systemd[1]: Stopping Avahi mDNS/DNS-SD Stack Activation Socket.
    -- Subject: Unit avahi-daemon.socket has begun shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit avahi-daemon.socket has begun shutting down.
    Jan 15 19:08:05 engserv systemd[1]: Closed Avahi mDNS/DNS-SD Stack Activation Socket.
    -- Subject: Unit avahi-daemon.socket has finished shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit avahi-daemon.socket has finished shutting down.
    Jan 15 19:08:05 engserv systemd[1]: Stopping System Initialization.
    -- Subject: Unit sysinit.target has begun shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit sysinit.target has begun shutting down.
    Jan 15 19:08:05 engserv systemd[1]: Stopped target System Initialization.
    -- Subject: Unit sysinit.target has finished shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit sysinit.target has finished shutting down.
    Jan 15 19:08:05 engserv systemd[1]: Stopping Swap.
    -- Subject: Unit swap.target has begun shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit swap.target has begun shutting down.
    Jan 15 19:08:05 engserv systemd[1]: Stopped target Swap.
    -- Subject: Unit swap.target has finished shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit swap.target has finished shutting down.
    Jan 15 19:08:05 engserv systemd[1]: Stopping Encrypted Volumes.
    -- Subject: Unit cryptsetup.target has begun shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit cryptsetup.target has begun shutting down.
    Jan 15 19:08:05 engserv systemd[1]: Stopped target Encrypted Volumes.
    -- Subject: Unit cryptsetup.target has finished shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit cryptsetup.target has finished shutting down.
    Jan 15 19:08:05 engserv systemd[1]: Stopping Update UTMP about System Boot/Shutdown...
    -- Subject: Unit systemd-update-utmp.service has begun shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit systemd-update-utmp.service has begun shutting down.
    Jan 15 19:08:05 engserv systemd[1]: Stopping Load/Save Random Seed...
    -- Subject: Unit systemd-random-seed.service has begun shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit systemd-random-seed.service has begun shutting down.
    Jan 15 19:08:05 engserv systemd[1]: Stopping Setup Virtual Console...
    -- Subject: Unit systemd-vconsole-setup.service has begun shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit systemd-vconsole-setup.service has begun shutting down.
    Jan 15 19:08:05 engserv systemd[1]: Stopped Setup Virtual Console.
    -- Subject: Unit systemd-vconsole-setup.service has finished shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit systemd-vconsole-setup.service has finished shutting down.
    Jan 15 19:08:05 engserv systemd[1]: Stopping Apply Kernel Variables...
    -- Subject: Unit systemd-sysctl.service has begun shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit systemd-sysctl.service has begun shutting down.
    Jan 15 19:08:05 engserv systemd[1]: Stopped Apply Kernel Variables.
    -- Subject: Unit systemd-sysctl.service has finished shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit systemd-sysctl.service has finished shutting down.
    Jan 15 19:08:05 engserv systemd[1]: Stopped Update UTMP about System Boot/Shutdown.
    -- Subject: Unit systemd-update-utmp.service has finished shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit systemd-update-utmp.service has finished shutting down.
    Jan 15 19:08:05 engserv systemd[1]: Stopping Create Volatile Files and Directories...
    -- Subject: Unit systemd-tmpfiles-setup.service has begun shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit systemd-tmpfiles-setup.service has begun shutting down.
    Jan 15 19:08:05 engserv systemd[1]: Stopped Create Volatile Files and Directories.
    -- Subject: Unit systemd-tmpfiles-setup.service has finished shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit systemd-tmpfiles-setup.service has finished shutting down.
    Jan 15 19:08:05 engserv systemd[1]: Stopping Local File Systems.
    -- Subject: Unit local-fs.target has begun shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit local-fs.target has begun shutting down.
    Jan 15 19:08:05 engserv systemd[1]: Stopped target Local File Systems.
    -- Subject: Unit local-fs.target has finished shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit local-fs.target has finished shutting down.
    Jan 15 19:08:05 engserv systemd[1]: Unmounting /home...
    -- Subject: Unit home.mount has begun shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit home.mount has begun shutting down.
    Jan 15 19:08:05 engserv systemd[1]: Unmounting /run/user/1000...
    -- Subject: Unit run-user-1000.mount has begun shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit run-user-1000.mount has begun shutting down.
    Jan 15 19:08:05 engserv systemd[1]: Unmounting /boot...
    -- Subject: Unit boot.mount has begun shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit boot.mount has begun shutting down.
    Jan 15 19:08:05 engserv systemd[1]: Unmounting Temporary Directory...
    -- Subject: Unit tmp.mount has begun shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit tmp.mount has begun shutting down.
    Jan 15 19:08:05 engserv umount[8075]: umount: /home: target is busy
    Jan 15 19:08:05 engserv umount[8075]: (In some cases useful info about processes that
    Jan 15 19:08:05 engserv umount[8075]: use the device is found by lsof(8) or fuser(1).)
    Jan 15 19:08:05 engserv systemd[1]: home.mount mount process exited, code=exited status=32
    Jan 15 19:08:05 engserv systemd[1]: Failed unmounting /home.
    -- Subject: Unit home.mount has finished shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit home.mount has finished shutting down.
    Jan 15 19:08:05 engserv systemd[1]: U

  • [Solved] Grub Error 15 at boot on new install.

    So I was trying to avoid asking for help, but I honestly can't see what's wrong with my new install of arch.  I followed the beginner's guide all the way up to the part where you reboot and remove the liveCD.  It all went swimmingly until I rebooted and got:
    GRUB Loading stage1.5.
    GRUB Loading, please wait...
    Error 15
    I don't know what's going on.  Error 15 is supposedly "file not found," but I don't know what file it's looking for since I have a grub.cfg that I created from the steps posted on the guide.  Any help is greatly appreciated.
    --Wes
    EDIT:
    Just to be clear I followed the BIOS motherboard steps for GRUB.
    Last edited by Wesman26 (2012-11-09 01:25:38)

    Xacky wrote:Which instructions did you follow? This would normaly do it when chrooted (during install).
    Wat your disk en partition lay-out?
    -One or more harddisks?
    -Partitions? Everything on / or separate /home /boot (/var)?
    I'm following the beginner's guide instructions for a BIOS install.  After chroot I used the following:
    # pacman -S grub-bios
    # grub-install --target=i386-pc --recheck --force --debug /dev/sdb
    # cp /usr/share/locale/en\@quot/LC_MESSAGES/grub.mo /boot/grub/locale/en.mo
    # grub-mkconfig -o /boot/grub/grub.cfg
    Aside from the warnings (that I think most people ignored) of a few files not existing during the installation of grub-bios, it all went fine.  The harddrive is definitely sdb (fdisk -l shows sda as my windows drive, not to mention I just formatted and partitioned sdb).  My partitions are laid out exactly as the guide tells me to (/ on /dev/sdb1 and /home on /dev/sdb2).  They are the only partitions on sdb.
    DSpider wrote:Lol... a full reinstall wasn't needed. This mentality is typical to a Windows user.
    I don't appreciate your condescension.  These forums have (up to this point) always been really helpful and friendly to me; just because I'm posting in the newbie corner doesn't mean I'm not familiar with linux, and even if I were unfamiliar with linux I would hope that you could show more respect and compassion for someone who needs help than to ostracize them and laugh about their problem.  I posted here because I figured I didn't need to waste the time of the mods and users who offer help in the installation subforum with something that I assumed would be a trivial fix.  I expected courteous, thoughtful responses.  I was apparently wrong to assume.
    I reinstalled because I didn't know what else to do, and figured that there might have been a chance that I made a mistake.  Since your previous advice was literally getting me nowhere I figured the 10 minutes of my time reinstalling took up would be worth the potential of fixing my problem. 
    To answer your questions that are actually helpful:
    I don't have grub installed on another drive and my drive and partition layout is detailed above.  As for boot priority, it hasn't changed since I first installed linux in 2006 and it's worked ever since; I'm performing this operation to clear what was once a drive cluttered with a few other distros that I've abandoned since 2007 when I found Arch (yes I am actually that lazy).
    Is it possible that my old installation of grub might have stayed on the drive even after I rid it of the old partitions (since it's stored in MBR)?  If so does the installation of grub2 I'm performing not get rid of it?
    Hope this helps,
    --Wes
    Last edited by Wesman26 (2012-11-08 20:53:27)

  • Fonts after a new install

    Hello Forum,
    Having completed a new install of arch, and sucessfully installed the Gnome Desktop Environment, I am having trouble printing legibly and viewing web pages properly, problems that I assume are to do with incorrectly/insufficiently installing fonts.
    I have tried to learn about what fonts can/should be installed as a basis for 'normal' web browsing and printing from reading the ArchWiki, but I have become somewhat confused, and seem to have got stuck at this point.
    I wondered if someone could give me some advice on the 'basics' to get me 'up and running' with printing and web browsing please?
    Many thanks everyone.
    Last edited by fitzyj (2015-01-07 13:12:15)

    fitzyj wrote:I have tried to learn about what fonts can/should be installed as a basis for 'normal' web browsing and printing from reading the ArchWiki, but I have become somewhat confused
    The first part of that is good.  The second part is understandable - but if we're to help we need to know which wiki pages you've followed, and what you've already done.
    There are many approaches.  It seems many archers use the infinality configurations (I tried it, but it didn't suit me).  But for a simple pragmatic approach, I'd suggest installing ttf-ms-fonts from the AUR.  For better or for worse, many websites rely on ms fonts.

  • New Install -- X Won't Work [SOLVED]

    I have to migrate to a new hard drive, and am doing a new install of Arch. I installed from net to have up-to-date packages...
    I installed X and what I think are the necessary packages, namely:
    ati-dri, libgl, mesa, xf86-input-evdev, xf86-input-synaptics, xf86-video-ati, xorg, hal, and dbus
    I start hal with /etc/rc.d/hal start and do a startx but it replies:
    error setting MTRR (base = 0xc0000000, size = 0x04000000, type = 1) Inappopriate ioctl for device (25)
    I am really stressing out because I need this new hard drive up and running like the old one, so I may be missing something major. Please, please help me get the bottom of this! Configuring xorg in my previous two installs for this computer have been a breeze but this time is killing me.
    EDIT:
    Okay so the culprit was really stupid and quite annoying! Apparently a default .xinitrc was placed in my home directory. Removing it allowed me to test xorg by having twm load. For some reason I wasn't expecting a default file to placed by Arch of all distros. GRR... got a bit frantic for no reason. I will probably add a note to the wiki so no one else hits this snag.
    Last edited by egan (2010-01-07 03:58:32)

    Perhaps I do not understand what you are doing but I would expect that if you want to use X in a graphical mode you need xorg.conf be it that you use hal to create it for you or you create it by other means.
    I know that if I use KDE I can run it without an X configuration file these days but I'm not sure if that is the same for plain old X.
    R.
    Edit: This is what I was able to find:
    Starting with version 7.4, Xorg can use HAL to autodetect keyboards and mice. The sysutils/hal and devel/dbus ports are installed as dependencies of x11/xorg, but must be enabled by the following entries in the /etc/rc.conf file:
    hald_enable="YES"
    dbus_enable="YES"
    Edit 2: Also notice this:
    The automatic configuration may fail to work with some hardware, or may not set things up quite as desired. In these cases, manual configuration will be necessary.
    Last edited by ralvez (2010-01-07 02:42:01)

  • I'm a new user and learning, I bought and installed Premiere Pro cs6.  I got a nice video clip but has a baby cried in the background and very annoying.  My question is, is this noise remover is separate from the cs6 or I need to get this software downloa

    I'm a new user and learning, I bought and installed Premiere Pro cs6.  I got a nice video clip but has a baby cried in the background and very annoying.  I have tried all of the sounds in Prem cs6 but didn't work. My question is, do I need to get a separate sound software download and install to be able to use it?

    In the CS versions, there was some audio capability in PrPro but you needed to get a separate audio program for major work. Lessening a baby definitely qualifies as major work. That's lessening, i dont mean eliminating. Adobe's audio program is Audition. There are others "out there'. In the CC versions one just downloads Audution also.
    Neil

Maybe you are looking for

  • SharePoint 2013 Blog Site not showing current navigation(Left Navigation)

    I have created a blog site but blog pages are not showing my current navigation, it has got its own left navigation, Can i show left (current) navigation? I am trying to find the page layout being used for blog items but unable to find.

  • [Solved]How can I create a bootable backup of my arch linux partition?

    I'm trying to get my arch linux installation to have a gui, specifically KDE. I downloaded Xorg and the nvidia proprietary driver 340.24. After installing the nvidia driver and rebooting, my screen stays black and I can't see my console. I can still

  • Files won't open

    I cannot get any of the files to open up in elements. I get an error message and it closes

  • [Dynamic array creation]

    Hi, I would like to create an array (2 dimensions) but my problem is that I don't know in advance the length of the first dimension of my array. I can't do a first pass to have the length of the array because it's too long so i don't know how to do!!

  • Photoshop 5 and .NEF

    Hi I'm trying to work in .NEF files from a nikon D40 I download camera raw 3.7 and installed it in the plug-ins but I still get the error that it isn't compatible any ideas thanks Lneilson