[SOLVED] systemd dhcpcd on boot failure

For the past month or so, my systemd service for dhcpcd has been failing to properly start on boot. However, I've noticed that this only occurs on a fresh start after a shutdown. It does not occur after a reboot.
I do not use any sort of connection manager such as: NetworkManager, netctl, connman, etc.. I am only using dhcpcd via systemd.
The command I've always used to create the service is:
# systemctl enable [email protected]
# systemctl start [email protected]
I've found some topics related to the issue from 2-3 years back, but they don't seem to be the exact same case from what I can tell.
Here is the output of systemctl --type=service --all: http://i.imgur.com/hqBZBoP.png
Here is the output of ip link show when the service is running:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
link/ether **:**:**:**:**:** brd ff:ff:ff:ff:ff:ff
Does anything seem off in my service list? This issue is really nagging at me, and I don't know enough about systemd or networking to isolate it.
Last edited by BlueYoshi (2015-05-17 22:50:51)

jasonwryan wrote:
What is in the journal after it fails to start?
Not a Sysadmin issue, moving to NC...
Just checked, and it looks like it's starting services in a strange order. "PIA" is my service to start my VPN using the https://aur.archlinux.org/packages/priv … access-vpn package. I would think dhcpcd should be starting first?
journalctl: https://bpaste.net/raw/28fe88297a78
pia.service (if relevant):
[Unit]
Description=PIA
[Service]
Type=simple
ExecStart=/usr/bin/pia
Restart=always
[Install]
WantedBy=multi-user.target

Similar Messages

  • [SOLVED]systemd-tmpfiles-setup.service failure

    Hi guys,
    I just reinstalled arch with the following partitions:
    [root@arch_vinnom vinnom]# gdisk -l /dev/sda
    GPT fdisk (gdisk) version 1.0.0
    Partition table scan:
    MBR: protective
    BSD: not present
    APM: not present
    GPT: present
    Found valid GPT with protective MBR; using GPT.
    Disk /dev/sda: 625142448 sectors, 298.1 GiB
    Logical sector size: 512 bytes
    Disk identifier (GUID): BD3CA679-FA08-4F60-9BAD-B845DE9FF7EB
    Partition table holds up to 128 entries
    First usable sector is 34, last usable sector is 625142414
    Partitions will be aligned on 2048-sector boundaries
    Total free space is 2014 sectors (1007.0 KiB)
    Number Start (sector) End (sector) Size Code Name
    1 2048 4095 1024.0 KiB EF02 BIOS
    2 4096 52432895 25.0 GiB 8300 ROOT
    3 52432896 53481471 512.0 MiB 8300 BOOT
    4 53481472 74452991 10.0 GiB 8300 TMP
    5 74452992 95424511 10.0 GiB 8300 VAR
    6 95424512 602935295 242.0 GiB 8300 HOME
    7 602935296 625142414 10.6 GiB 8200 SWAP
    The problem is that tmpfs is mounted at '/tmp' through '/usr/lib/systemd/system/tmp.mount'
    # This file is part of systemd.
    # systemd is free software; you can redistribute it and/or modify it
    # under the terms of the GNU Lesser General Public License as published by
    # the Free Software Foundation; either version 2.1 of the License, or
    # (at your option) any later version.
    [Unit]
    Description=Temporary Directory
    Documentation=man:hier(7)
    Documentation=http://www.freedesktop.org/wiki/Software/systemd/APIFileSystems
    ConditionPathIsSymbolicLink=!/tmp
    DefaultDependencies=no
    Conflicts=umount.target
    Before=local-fs.target umount.target
    [Mount]
    What=tmpfs
    Where=/tmp
    Type=tmpfs
    Options=mode=1777,strictatime
    Because of this, I'm always getting:
    ● systemd-tmpfiles-setup.service - Create Volatile Files and Directories
    Loaded: loaded (/usr/lib/systemd/system/systemd-tmpfiles-setup.service; static; vendor preset: disabled)
    Active: failed (Result: exit-code) since Dom 2015-05-03 03:29:58 BRT; 27min ago
    Docs: man:tmpfiles.d(5)
    man:systemd-tmpfiles(8)
    Process: 278 ExecStart=/usr/bin/systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev (code=exited, status=1/FAILURE)
    Main PID: 278 (code=exited, status=1/FAILURE)
    Then I tried to change '/tmp' to '/run/tmpfs', folder that I created for this, using tmpfs wiki as reference.
    # This file is part of systemd.
    # systemd is free software; you can redistribute it and/or modify it
    # under the terms of the GNU Lesser General Public License as published by
    # the Free Software Foundation; either version 2.1 of the License, or
    # (at your option) any later version.
    [Unit]
    Description=Temporary Directory
    Documentation=man:hier(7)
    Documentation=http://www.freedesktop.org/wiki/Software/systemd/APIFileSystems
    ConditionPathIsSymbolicLink=!/run/tmpfs
    DefaultDependencies=no
    Conflicts=umount.target
    Before=local-fs.target umount.target
    [Mount]
    What=tmpfs
    Where=/run/tmpfs
    Type=tmpfs
    Options=mode=1777,strictatime,nodev,nosuid,size=1536M
    But the error persists. What I'm missing?
    Last edited by vinnom (2015-05-03 16:51:38)

    ooo wrote:Couldn't you just mask the tmp.mount service? (as mentioned in the wiki page you linked)
    Then your /tmp partition would be mounted according to your fstab
    Raynman wrote:
    The tmp.mount generated from your fstab should override the tmp.mount in /usr/lib/systemd/system. You say
    The problem is that tmpfs is mounted at '/tmp' through '/usr/lib/systemd/system/tmp.mount'
    If that is true (could you show output of mount and your fstab?) that is worth investigating.
    However, your original problem seems to be that systemd-tmpfiles-setup.service fails. If something is wrong with your mounts, that could be related, but it might very well be something else. Is there any more information in the journal to indicate why the service fails (maybe even mentioning a tmpfiles.d config file that is responsible)? Did you create any config files for tmpfiles.d yourself?
    Sorry guys, I tried to be concise, but ended up that I didn't make myself clear.
    My '/tmp' is mounting fine as it takes priority over systemd. In fact, what I wanted to say is that '/tmp' mounts fine, systemd tried to mount tmpfs at '/tmp' and fails and I want to point tmpfs to mount at '/run/tmpfs' which I created for this, but just editing '/usr/lib/systemd/system/tmp.mount' didn't solve.
    As for journalctl, it repeats several times this message:
    Mai 02 22:43:32 arch_vinnom systemd[1]: systemd-tmpfiles-setup.service: main process exited, code=exited, status=1/FAILURE
    Mai 02 22:43:32 arch_vinnom systemd[1]: Failed to start Create Volatile Files and Directories.
    Mai 02 22:43:32 arch_vinnom systemd[1]: Unit systemd-tmpfiles-setup.service entered failed state.
    Mai 02 22:43:32 arch_vinnom systemd[1]: systemd-tmpfiles-setup.service failed.
    foutrelis wrote:
    Depending on how your '/var' file system is created/mounted, you might need to enable ACL on it:
    https://wiki.archlinux.org/index.php/Sy … rt_at_boot
    hmm
    I created my /var during arch installation, with mkfs.reiserfs.
    Using
    tune2fs -l /dev/sdXY | grep "Default mount options:"
    To check if acl was already enabled, I got:
    [root@arch_vinnom vinnom]# tune2fs -l /dev/sda5 | grep "Default mount options:"
    tune2fs: Bad magic number in super-block while trying to open /dev/sda5
    Couldn't find valid filesystem superblock.
    Then I searched a bit and noted that reiserfs isn't compatible with acl =/
    Last edited by vinnom (2015-05-03 15:12:18)

  • [SOLVED] systemd-fsck prolongs boot time considerably

    Hi folks, I've searched but come up blank on this one...
    I've just migrated fully to systemd and all's working well apart from my boot hanging for around 16 seconds on fsck. Disabling the checks via the final column of fstab reduces my boot to under 9 seconds, which is roughly what it was with initscripts. Boot drive's an SSD, all other partitions on 2 SATA HDDs.
    Here are the relevant parts of fstab
    # /dev/sda3 - Backup
    # ========= ------
    UUID=7e23c7f4-acf6-477c-9705-15ae8870181e /media/Backup ext4 defaults 0 2
    # /dev/sdb2 - ROOT (+/home)
    # ========= ------------
    UUID=ee99e089-a642-41c8-b1f4-5dc80307d438 / ext4 defaults,noatime,discard 0 1
    # /dev/sdc1 - Data
    # ========= ----
    UUID=66c7a8dd-8d92-4353-a4eb-1da425449322 /media/Data ext4 defaults 0 2
    # /dev/sdc2 - Scratch
    # ========= -------
    UUID=a8ca4753-ccca-4360-b702-8c12004bf8f8 /media/Scratch ext4 defaults,noatime 0 2
    # /dev/sdc4 - bootISOs
    # ========= --------
    UUID=eea21a23-b3fa-479d-8a62-2502f4f9edfc /media/bootISOs ext4 defaults,noatime 0 2
    I do have /var on the "Data" partition and a few other relocations...
    /media/Data/var /var none bind 0 0
    /media/Data/logs /home/paul/.logs none bind 0 0
    tmpfs /home/paul/.thumbnails tmpfs nodev,nosuid,noatime 0 0
    tmpfs /home/paul/.Skype/Logs tmpfs nodev,nosuid,noatime 0 0
    tmpfs /media/Data/wine/drive_c/windows/temp tmpfs nodev,nosuid,noatime 0 0
    Without fsck
    $ systemd-analyze
    Startup finished in 1280ms (kernel) + 2220ms (initramfs) + 5112ms (userspace) = 8614ms
    With fsck (typical)
    $ systemd-analyze
    Startup finished in 1276ms (kernel) + 3224ms (initramfs) + 20327ms (userspace) = 24829ms
    Any ideas as to the slowdown or is this to be expected with this many partitions?
    Thanks.
    Last edited by fabertawe (2012-09-06 17:48:57)

    WorMzy wrote:You can add "noauto,x-systemd.automount" to the options of non-essential partitions. That may speed up your boot time.
    Sorry, I should have mentioned I already tried this with the "Data" partition and just got a permanent hang in the boot sequence.
    Edit: I've had 2 boots where it's not had the delay but I've no idea why, nothing was changed.
    Edit2: Seems I was too quick to dismiss "noauto,x-systemd.automount"... I've applied it to all partitions except "Data" (and root, obviously) and now I'm consistently getting boot times under 9 seconds. Marking this thread as solved. Thanks to all who contributed
    Last edited by fabertawe (2012-09-06 17:45:48)

  • [solved] systemd dhcpcd service

    Not sure what is failing with this output, a service file start dependency?
    Mar 12 10:08:53 yrch systemd[1]: Timed out waiting for device sys-subsystem-net-devices-eth0.device.
    Mar 12 10:08:53 yrch systemd[1]: Dependency failed for dhcpcd on eth0.
    This is the dhcpcd service file
    [root@yrch multi-user.target.wants]# cat dh*
    [Unit]
    Description=dhcpcd on %I
    Wants=network.target
    Before=network.target
    BindsTo=sys-subsystem-net-devices-%i.device
    After=sys-subsystem-net-devices-%i.device
    [Service]
    Type=forking
    PIDFile=/run/dhcpcd-%I.pid
    ExecStart=/usr/sbin/dhcpcd -q -w %I
    ExecStop=/usr/sbin/dhcpcd -x %I
    [Install]
    WantedBy=multi-user.target
    Also running dhcpcd standalone fails first attempt, works correctly second attempt.
    Last edited by ackt1c (2014-11-23 08:36:28)

    Is your device eth0? The interface naming scheme has changed, it's no longet eth0, eth1 and so on, but udev gives names to devices based on the MAC address now. Unless you manually changed config files, you will have this new naming scheme in effect. Check with ip link.
    Last edited by elkoraco (2013-03-13 09:18:50)

  • Reclone of Recovery HD solved 10.8.3 boot failure

    After installing the OSX 10.8.3 update this weekend, my 3 year old stock 15" MBP refused to complete the boot sequence. I finally was able to fix this problem by recloning the Recovery HD using Carbon Copy Cloner, and for the good of the community I wanted to pass on what I learned in case others encounter the same problem.
    I had enabled both FileVault2 and a firmware password, so after the initial login screen the boot sequence would start but always hang just before launching the Finder with the message “Your computer restarted because of a problem. Press a key or wait a few seconds before starting up.” Of course, pressing a key or waiting would restart the login sequence and result in the same alert screen.
    Booting into the Recovery HD, I removed the firmware password and ran DiskUtility. DU gave the alert “Journal needs to be replayed but volume is read-only” and finally the dreaded “DiskUtility can’t repair this disk” with the instructions to make a backup, erase the drive and restore.
    I had made a bootable clone of the drive using CCC before installing the 10.8.3 update, so I booted the MBP from it. Running DiskUtility from the external drive ended with the message “Updating boot support partitions for volume as required” and the final alert “Couldn’t unmount disk” to complete the repair.
    Using my bootable clone, I ran DiskWarrior on the MBP’s internal drive. But rebuilding the directories made no difference to the boot up problem.
    Again from the bootable clone, I opened the Startup Disk system preference pane and tried to manually reconfirm the MPB’s internal HD as the boot volume. Upon confirming with the “Restart …” button, Startup Disk gave me the error message “Building boot caches on boot helper partition failed.”
    Following other suggestions I encountered in support forums, I also tried rewriting the com.apple.Boot.plist system preference and messing with the kextmanager and com.apple.text.chaches, but nothing fixed the boot problem.
    I finally gave up and decided to reformat the MPB’s drive and reinstall everything from my clone. But upon clicking on the “Erase” button in DiskUtility, it told me “Disk Encryption Failed - couldn’t unmount disk.” So now I really was hosed. I couldn’t repair the drive and I couldn’t reformat it.
    Researching each of these error messages for some clue as to what might be going on, I had earlier come across a support thread on the CCC site where the customer was getting the same “Building boot caches on boot helper partition failed” error in the Startup Disk preference pane. Mike Bombich at one point responded “Alternatively, you could open CCC’s Disk Center, click on the Recovery HD tab, click on your ‘OLD HD’ volume, then click the button to reclone the Recovery HD. Perhaps with a freshly-restored Recovery HD, the OS won’t have any trouble updating the kernel extension cache on that volume.” I assumed that made sense and I was desperate, so running CCC from my bootable clone I followed Mike’s suggestion.
    Voilà - boot problem fixed! DiskUtility now reports no problems or errors with the drive, and everything is back to running the way it should.
    So did the update to 10.8.3 somehow hose the boot instructions affecting the Recovery HD partition, thereby stopping a successful boot up process? Did the presence of a firmware password and FileVault2 create this situation during the update? It appears that drives encrypted with FileVault2 require a healthy Recovery HD partition, and if this is the case it explains what happened to me.
    What is clear to me is that my CCC clone backup and its Disk Center utility saved my MPB’s hard drive. I’m pretty sure that without CCC’s ability to reclone its Recovery HD partition I would have had to buy and install a replacement drive - and here in Brazil that would not have been cheap or easy.
    Hope this helps someone else in a similar situation.

    Borquist, thank you so much for your post and sharing of the solution, which also worked for me. Thank you, Mike Bombich, and CCC!

  • [SOLVED] systemd-journald & tmpfiles-setup Failures

    Hello,
    I have a weird situation. After I've finished installing my system, I got errors with journald...
    After logging as root I get the following errors:
    systemd-journald[338]: Failed to get machine id: No such file or directory
    systemd-journald[340]: Failed to get machine id: No such file or directory
    systemd-journald[345]: Failed to get machine id: No such file or directory
    systemd-journald[347]: Failed to get machine id: No such file or directory
    systemd-journald[349]: Failed to get machine id: No such file or directory
    systemd[1]: Failed to start Journal Service.
    systemd[1]: Dependency failed for Trigger Flushing of Journal to Presistent Storage.
    systemd[1]: Failed to start Journal Service
    and after I typed
    systemctl
    to see what's more, I got errors at the following:
    systemd-journal-flush.service loaded failed failed
    systemd-journald.service loaded failed failed
    systemd-tmpfiles-setup-dev.service loaded failed failed
    systemd-tmpfiles-setup.service loaded failed failed
    systemd-journald-dev-log.socket loaded failed failed
    systemd-journald.socket loaded failed failed
    and other problems related to the above like
    Failed to start Cleanup of Temporary Directories.
    Note that it is my first time I have problems with journald and tmpfiles-setup and I'm not sure what happened...
    Any help would be very appreciated and thank you very much in advance.
    Last edited by heyom (2014-08-30 09:24:24)

    I just had the same problem while installing a new Arch system. I managed to fix it by running `systemd-machine-id-setup` as root (not sudo).
    Also, before I did that, while installing a package I got an error message about dbus not finding a machine id, and that error message suggested running `dbus-uuidgen > /var/lib/dbus/machine-id` (again as root, not sudo). So, you may need to do that, too.

  • Systemd dhcpcd service failing on boot

    Hi folks,
    I'm trying to convert my workstation to "pure" systemd configuration (no initscripts-systemd):
    [csingley@quadrupel ~]$ pacman -Qs systemd
    local/libsystemd 185-3
    systemd client libraries
    local/systemd 185-3
    system and service manager
    local/systemd-arch-units 20120612-5
    Arch specific Systemd unit files
    local/systemd-sysvcompat 185-3
    sysvinit compat for systemd
    local/systemd-tools 185-3
    standalone tools from systemd
    Per the instructions on the wiki, I enabled [email protected], but the service fails to start upon boot.
    [root@quadrupel csingley]# systemctl status [email protected]
    [email protected] - dhcpcd on eth0
    Loaded: loaded (/usr/lib/systemd/system/[email protected]; enabled)
    Active: failed (Result: exit-code) since Thu, 28 Jun 2012 12:36:16 -0500; 39s ago
    Process: 299 ExecStart=/sbin/dhcpcd -A -q -w %I (code=exited, status=1/FAILURE)
    CGroup: name=systemd:/system/[email protected]/eth0
    However, I can start the service manually after the boot process is complete:
    [root@quadrupel csingley]# systemctl start [email protected]
    [root@quadrupel csingley]#
    Presumably not all dependencies have been satisfied when systemd tries to run dhcpcd during boot.
    I'm very new to systemd; any tips for troubleshooting this issue?
    TIA

    dj-x-cess wrote:
    I have the same problem.
    It seems, at least for my machine, dhcpcd starts before eth0 gets initialized on boot time:
    Sep 05 07:38:39 vostro dhcpcd[180]: version 5.6.0 starting
    Sep 05 07:38:39 vostro dhcpcd[180]: eth0: interface not found or invalid
    Sep 05 07:38:39 vostro kernel: r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
    Sep 05 07:38:39 vostro kernel: r8169 0000:13:00.0: irq 47 for MSI/MSI-X
    Sep 05 07:38:39 vostro kernel: r8169 0000:13:00.0: eth0: RTL8168d/8111d at 0xf9c00000, a4:ba:db:a6:a6:33, XID 083000c0 IRQ 47
    Sep 05 07:38:39 vostro kernel: r8169 0000:13:00.0: eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
    Yes. Same thing here with the latest install. I put "tg3" in /etc/modules-load.d/tigon.conf. Guess it loads it sooner then and now it gets an IP. Couldn't you make dhcpcd wait for eth0 to come up? It looks important, I mean dhcp should work I'm a newbie with Arch, installed it for the first time.
    Here are my logs before the fix (I was looking in /var/log/, but then I found out that there is a journalctl command):
    Nov 14 15:33:40 neimastina dhcpcd[176]: version 5.6.2 starting
    Nov 14 15:33:40 neimastina dhcpcd[176]: eth0: interface not found or invalid
    Nov 14 15:33:44 neimastina systemd[1]: [email protected]: control process exited, code=exited status=1
    Nov 14 15:33:45 neimastina kernel: EDAC MC: Ver: 3.0.0
    Nov 14 15:33:45 neimastina kernel: wmi: Mapper loaded
    Nov 14 15:33:45 neimastina kernel: iTCO_vendor_support: vendor-support=0
    Nov 14 15:33:45 neimastina kernel: tg3.c:v3.124 (March 21, 2012)
    Nov 14 15:33:45 neimastina kernel: EDAC MC0: Giving out device to 'x38_edac' 'x38': DEV 0000:00:00.0
    Nov 14 15:33:45 neimastina kernel: tg3 0000:34:00.0: eth0: Tigon3 [partno(BCM95751A519FLP) rev 4201] (PCI Express) MAC address 00:10:18:53:12:b7
    Nov 14 15:33:45 neimastina kernel: tg3 0000:34:00.0: eth0: attached PHY is 5750 (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[0])
    Nov 14 15:33:45 neimastina kernel: tg3 0000:34:00.0: eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1]
    Nov 14 15:33:45 neimastina kernel: tg3 0000:34:00.0: eth0: dma_rwctrl[76180000] dma_mask[64-bit]
    Nov 14 15:33:45 neimastina kernel: gpio_ich: GPIO from 195 to 255 on gpio_ich

  • Disk Boot Failure [solved]

    I'm installing arch on a rebuilt system, but I cannot get it to boot.  I have pared the system down to a a SCSI card, a video card, a single hard drive, an IDE CD, a SCSI tape drive, and a floppy.  I have tried my standard installation partitioning scheme, and the automatic version.
    No matter what I do, while the system seems to install correctly, when I reboot I get a Disk Boot Failure.
    I've zeroed the drive, I've tried an fdisk /mbr, I've run a Maxtor burn-in test which came back fine.  I'm convinced it isn't the drive.  The standard menu.lst uses root (0,0) and the kernel in /dev/discs/disc0/part3 after an automatic installation.  I mounted the /boot partition set up by the auto install, and the grub directory and files are there.
    What am I missing?
    Last edited by timm (2009-05-04 22:11:42)

    I think it's solved.
    Everybody who was mentioning the BIOS got me looking in there, but I found nothing out of the ordinary.  I decided to try to install Windows 2K to see if that would boot, which it did flawlessly.  I reinstalled arch, and go the disk failure.  Back to the BIOS.
    This is an IDE hard drive; the only thing SCSI is the tape drive.
    What I found was that the access on the hard drive was set to Auto, which I had seen before but didn't think to be a problem.  I tried changing that to LBA (which is what I thought Auto would do on a drive like this), and suddenly arch comes up just fine.
    I have a couple of RocketRaid cards that I'm installing, and will be playing around with the SCSI as well.  I'm going to play with things a bit more, but unless I can make it fail with some other tweaking, that BIOS setting appears to have been the problem. 
    Thanks to everyone for their help!

  • {Solved} Can not successfully boot into systemd

    I will first start off by saying I have read though the following threads:
    https://bbs.archlinux.org/viewtopic.php?id=151633
    https://bbs.archlinux.org/viewtopic.php?id=151885
    And have tried to follow the Systemd wiki.  I started out by switching to the new initscripts configuration system.  I have the current systemd package installed.  I then installed systemd-sysvcompat which of course had me remove sysvinit.  I then removed initscripts which moved my rc.conf to rc.conf.pacsave.
    I had to manually create /etc/hostname, /etc/locale.conf, and /etc/vconsole.conf as (mentioned in a previous post) I could not do with any "ctl" commands as I had not yet booted into a systemd setup.
    This also caused an issue with trying to set up the timezone as:
    # timedatectl set-timezone America/New_York
    resulted in:
    Failed to issue method call: Launch helper exited with unknown return code 1
    So at this point I decided to try a reboot and I get:
    Welcome to emergency mode! Type "systemctl defualt" or ^D to enter default mode.
    Type "journelctl -b" to view system logs. Type "systemctl reboot" to reboot.
    Give root password for maintenance
    (or typed Control-D to continue): [ 71.520184] radeon_cp: Failed to load firmware
    "radeon/R300_cp.bin"
    [ 71.520205] [drm:r100_cp_init] *ERROR* failed to load firmware!
    [ 71.520224] radeon 0000:01:05.0: failed initializing CP (-2)
    [ 71.520237] radeon 0000:01:05.0: Disabling GPU acceleration
    I entered emergency mode which brought me to the root terminal.  I first attempted to mv rc.conf.pacnew to rc.conf expecting there to possibly be an issue with the daemons I had running or attempted to run but after reboot I got the same thing.  Not sure what is going on with the radeon firmware because it's obviously there.
    So I re-imaged the hard drive and decided to try again.  This time I installed systemd-sysvcompat (removing sysvinit) and DID NOT remove initscripts.  I rebooted and got the exact same thing as above. So at this point I am at a loss of ideas with moving forward.  Why is systemd-sysvcompat causing the failure of the radeon firmware to load? I use Arch on my laptop, desktop as well as my server.  Systemd is coming so I am trying with the laptop first to convert to pure systemd.  If I am just missing a step please let me know and I appologize for posting.  But hopefully others have run into this issue and could possibly give me a nudge in the right direction.  It could be I am reading the wiki wrong or just not interpreting it correctly.
    Thanks in advance for your guidance and assistance,
    All the best,
    Ian
    Last edited by ichase (2012-11-16 16:55:10)

    hiciu,
    Here is what you requested taken from emergency mode:
    /etc/mkinitcpio.conf
    # vim:set ft=sh
    # MODULES
    # The following modules are loaded before any boot hooks are
    # run. Advanced users may wish to specify all system modules
    # in this array. For instance:
    # MODULES="piix ide_disk reiserfs"
    MODULES=""
    # BINARIES
    # This setting includes any additional binaries a given user may
    # wish into the CPIO image. This is run last, so it may be used to
    # override the actual binaries included by a given hook
    # BINARIES are dependency parsed, so you may safely ignore libraries
    BINARIES=""
    # FILES
    # This setting is similar to BINARIES above, however, files are added
    # as-is and are not parsed in any way. This is useful for config files.
    # Some users may wish to include modprobe.conf for custom module options
    # like so:
    # FILES="/etc/modprobe.d/modprobe.conf"
    FILES=""
    # HOOKS
    # This is the most important setting in this file. The HOOKS control the
    # modules and scripts added to the image, and what happens at boot time.
    # Order is important, and it is recommended that you do not change the
    # order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
    # help on a given hook.
    # 'base' is _required_ unless you know precisely what you are doing.
    # 'udev' is _required_ in order to automatically load modules
    # 'filesystems' is _required_ unless you specify your fs modules in MODULES
    # Examples:
    ## This setup specifies all modules in the MODULES setting above.
    ## No raid, lvm2, or encrypted root is needed.
    # HOOKS="base"
    ## This setup will autodetect all modules for your system and should
    ## work as a sane default
    # HOOKS="base udev autodetect pata scsi sata filesystems"
    ## This is identical to the above, except the old ide subsystem is
    ## used for IDE devices instead of the new pata subsystem.
    # HOOKS="base udev autodetect ide scsi sata filesystems"
    ## This setup will generate a 'full' image which supports most systems.
    ## No autodetection is done.
    # HOOKS="base udev pata scsi sata usb filesystems"
    ## This setup assembles a pata mdadm array with an encrypted root FS.
    ## Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
    # HOOKS="base udev pata mdadm encrypt filesystems"
    ## This setup loads an lvm2 volume group on a usb device.
    # HOOKS="base udev usb lvm2 filesystems"
    ## NOTE: If you have /usr on a separate partition, you MUST include the
    # usr, fsck and shutdown hooks.
    HOOKS="base udev autodetect pata scsi sata filesystems usbinput fsck"
    # COMPRESSION
    # Use this to compress the initramfs image. By default, gzip compression
    # is used. Use 'cat' to create an uncompressed image.
    #COMPRESSION="gzip"
    #COMPRESSION="bzip2"
    #COMPRESSION="lzma"
    #COMPRESSION="xz"
    #COMPRESSION="lzop"
    # COMPRESSION_OPTIONS
    # Additional options for the compressor
    #COMPRESSION_OPTIONS=""
    The next items due to length are linked to pastebin;
    bsdtar -t -f /boot/initramfs-linux.img
    http://pastebin.com/cZEJHVHm
    dmesg
    http://pastebin.com/MUGs1e9H
    journalctl -b
    http://pastebin.com/xgbfVJP8
    This is a lot to look at so do know that I am very appreciative of you and any one else looking at these files taking your time to help me with this issue.
    All the best,
    Ian
    Edit:  I also wanted to mention that I was able to get rid of the syslog-ng errors previously mentioned by performing:
    systemctl enable syslog-ng.service
    Then rebooting.  Granted I was still put back in emergency mode but was able to fix one issue.
    Last edited by ichase (2012-11-16 03:33:41)

  • [SOLVED] systemd-fsck does checks on every boot

    How do I say it to check only after crashes (bad unmounts and so on..) and just mount without checks otherwise?
    I use the classic /etc/fstab layout:
    /dev/drive/root / ext4 rw,relatime 0 1
    /dev/drive/boot /boot ext4 rw,relatime,noexec 0 2
    /dev/drive/swap none swap defaults 0 0
    /dev/drive/var /var ext4 rw,relatime,nodev,noexec,nosuid 0 2
    /dev/drive/home /home ext4 rw,relatime 0 2
    Here is some info from systemd's journal:
    дек. 08 22:43:20 localhost systemd[1]: Found device /dev/drive/var.
    дек. 08 22:43:21 localhost systemd-fsck[124]: /dev/mapper/drive-root: clean, 56204/2621440 files, 523339/10485760 blocks
    дек. 08 22:43:21 localhost systemd[1]: Started File System Check on Root Device.
    дек. 08 22:43:21 localhost systemd[1]: Starting File System Check on /dev/drive/var...
    дек. 08 22:43:21 localhost systemd[1]: Starting Remount Root and Kernel File Systems...
    дек. 08 22:43:21 localhost systemd[1]: Found device /dev/drive/swap.
    дек. 08 22:43:21 localhost systemd[1]: Activating swap /dev/drive/swap...
    дек. 08 22:43:21 localhost systemd[1]: Found device /dev/drive/boot.
    дек. 08 22:43:21 localhost systemd[1]: Starting File System Check on /dev/drive/boot...
    дек. 08 22:43:21 localhost systemd[1]: Found device /dev/drive/home.
    дек. 08 22:43:21 localhost systemd[1]: Starting File System Check on /dev/drive/home...
    дек. 08 22:43:21 localhost systemd-fsck[252]: /dev/mapper/drive-var: clean, 2007/262144 files, 463082/1048576 blocks
    дек. 08 22:43:22 localhost systemd[1]: Started Remount Root and Kernel File Systems.
    дек. 08 22:43:22 localhost systemd[1]: Starting Local File Systems (Pre).
    дек. 08 22:43:22 localhost systemd[1]: Reached target Local File Systems (Pre).
    дек. 08 22:43:22 localhost systemd[1]: Mounting /var...
    дек. 08 22:43:22 localhost systemd-fsck[257]: /dev/mapper/drive-boot: clean, 313/65536 files, 33914/262144 blocks
    дек. 08 22:43:22 localhost systemd[1]: Mounted /var.
    дек. 08 22:43:22 localhost systemd-fsck[262]: /dev/mapper/drive-home: clean, 5080/16375808 files, 2332630/65492992 blocks
    дек. 08 22:43:22 localhost systemd[1]: Started File System Check on /dev/drive/boot.
    дек. 08 22:43:22 localhost systemd[1]: Mounting /boot...
    дек. 08 22:43:22 localhost systemd[1]: Started File System Check on /dev/drive/home.
    дек. 08 22:43:22 localhost systemd[1]: Mounting /home...
    дек. 08 22:43:22 localhost systemd[1]: Mounted /boot.
    дек. 08 22:43:23 localhost systemd[1]: Mounted /home.
    дек. 08 22:43:23 localhost systemd[1]: Starting Local File Systems.
    дек. 08 22:43:23 localhost systemd[1]: Reached target Local File Systems.
    These filesystem checks seem to add huge delay to boot time. But I don't want this delay!
    Last edited by eruditorum (2012-12-10 19:26:54)

    falconindy wrote:These are the same checks that have always occurred.
    But I want to remove them!
    falconindy wrote:Notice that /home is mounted within the same second timestamp that it's fsck'd. Same goes for /boot, and /var is probably under a second as well. If you're seeing delays, go look elsewhere.
    I think filesystem checks add delays (about one second for each logical volume or so), also as you know systemd is doing everything in parallel it can at the given moment of time, for example I can say you that water has already boiled, while it is still going to boil but you don't know it:
    дек. 08 22:43:19 localhost systemd[1]: Starting File System Check on Root Device...
    дек. 08 22:43:21 localhost systemd-fsck[124]: /dev/mapper/drive-root: clean, 56204/2621440 files, 523339/10485760 blocks
    дек. 08 22:43:21 localhost systemd[1]: Started File System Check on Root Device.
    дек. 08 22:43:21 localhost systemd[1]: Starting Remount Root and Kernel File Systems...
    /var:
    дек. 08 22:43:20 localhost systemd[1]: Found device /dev/drive/var.
    дек. 08 22:43:21 localhost systemd[1]: Starting File System Check on /dev/drive/var...
    дек. 08 22:43:21 localhost systemd-fsck[252]: /dev/mapper/drive-var: clean, 2007/262144 files, 463082/1048576 blocks
    дек. 08 22:43:21 localhost systemd[1]: Started File System Check on /dev/drive/var.
    дек. 08 22:43:22 localhost systemd[1]: Mounting /var...
    дек. 08 22:43:22 localhost systemd[1]: Mounted /var.
    /boot:
    дек. 08 22:43:21 localhost systemd[1]: Found device /dev/drive/boot.
    дек. 08 22:43:21 localhost systemd[1]: Starting File System Check on /dev/drive/boot...
    дек. 08 22:43:22 localhost systemd-fsck[257]: /dev/mapper/drive-boot: clean, 313/65536 files, 33914/262144 blocks
    дек. 08 22:43:22 localhost systemd[1]: Started File System Check on /dev/drive/boot.
    дек. 08 22:43:22 localhost systemd[1]: Mounting /boot...
    дек. 08 22:43:22 localhost systemd[1]: Mounted /boot.
    /home:
    дек. 08 22:43:21 localhost systemd[1]: Found device /dev/drive/home.
    дек. 08 22:43:21 localhost systemd[1]: Starting File System Check on /dev/drive/home...
    дек. 08 22:43:22 localhost systemd-fsck[262]: /dev/mapper/drive-home: clean, 5080/16375808 files, 2332630/65492992 blocks
    дек. 08 22:43:22 localhost systemd[1]: Started File System Check on /dev/drive/home.
    дек. 08 22:43:22 localhost systemd[1]: Mounting /home...
    дек. 08 22:43:23 localhost systemd[1]: Mounted /home.
    Last edited by eruditorum (2012-12-09 13:20:15)

  • [Solved] Systemd automounts /boot (was mlocate not traversing /boot)

    For some reason, mlocate does not index my /boot:
    ┌─[Shiv ~ ]
    └─╼ locate vmlinuz-linux
    /home/jason/Build/chroot/root/boot/vmlinuz-linux
    ┌─[Shiv ~ ]
    └─╼ sudo updatedb -U /boot
    [sudo] password for jason:
    ┌─[Shiv ~ ]
    └─╼ locate vmlinuz-linux
    /boot/vmlinuz-linux
    /boot/vmlinuz-linux-jwr
    ┌─[Shiv ~ ]
    └─╼ sudo updatedb
    ┌─[Shiv ~ ]
    └─╼ locate vmlinuz-linux
    /home/jason/Build/chroot/root/boot/vmlinuz-linux
    My /etc/updatedb.conf is the stock Arch one, /boot is obviously mounted (as the -U switch works), but a plain updatedb does not return any results from /boot.
    I recently moved my ESP from /boot/efi to /boot, and as this is the only machine exhibiting this behaviour, it leads me to suspect something is amiss here.
    My fstab:
    # ESP: /dev/sda1
    UUID=696A-09B3 /boot vfat defaults,relatime,discard 0 2
    # /dev/mapper/vgroup-lvroot
    UUID=1d2dfd7d-adeb-4786-ag98-c8fg675f8e2f / ext4 rw,relatime,discard,data=ordered 0 1
    # /dev/mapper/vgroup-lvhome
    UUID=50798021-94b5-4011-a593-9087gfhcd59b8 /home ext4 rw,relatime,discard 0 2
    Am I missing something obvious?
    # edit: updated thread title with the cause, as opposed to the symptom...

    WonderWoofy wrote:There is a mechanism in systemd (or maybe gummiboot) that mounts the ESP on /boot as a systemd autostart unit.  So it shows up as autofs, which mlocate does not venture into.
    Bingo!
    ┌─[Shiv ~ ]
    └─╼ mount | grep boot
    systemd-1 on /boot type autofs (rw,relatime,fd=36,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
    /dev/sda1 on /boot type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro,discard)
    falconindy wrote:If there's one thing I've learned about remote debugging over the years, it's to not trust people.
    Especially Antipodeans
    lolilolicon wrote:I Googled for this and found this relevant talk in our (duh) wiki
    I spent some time yesterday searching, but missed this--to my shame
    65kid on the wiki wrote:* this feature isn't even documented in systemd yet
    Great. Any way to suppress this?

  • [Solved] systemd creates autofs after unmounting /boot

    After logging in, i unmount /boot, so that i can unplug the usb drive where it resides, then systemd creates this mount:
    # mount | grep /boot
    systemd-1 on /boot type autofs (rw,relatime,fd=26,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
    Typing this hangs forever:
    ls /boot
    /etc/fstab
    UUID=2D75-67FC /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro,nodev,nosuid,noexec 0 2
    I don't really know what to make of this. Seems like a bug, given that ls hangs forever instead of showing nothing.
    Last edited by teateawhy (2014-09-12 10:48:38)

    My bad, i really masked the mount unit. Will try again tomorrow.
    EDIT:
    After masking the automount unit, it looks like this:
    * /boot is mounted correctly at startup
    * after unmounting /boot manually, no autofs mount shows up anymore
    * ls does not hang and immediatly shows nothing, as expected
    # systemctl status boot.automount
    ● boot.automount
    Loaded: masked (/dev/null)
    Active: inactive (dead)
    # mount | grep /boot
    (No output)
    Last edited by teateawhy (2014-09-12 10:16:50)

  • System boot failure after upgrade from linux3.13.8-1 to linux3.14.6-1

    I have tried to update the kernel again from 3.13 to 3.14 again, but no luck.
    My arch system boot failure with black screen, tried [ctrl]+[alt]+[F1-6] and nothing happen, no any recure shell prompt out.
    Then I boot with kernel debug parameters
    systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M
    althrough the screen was black, when I reboot and chroot into my system,
    I entered the following to find any error messages, please see the link below:
    journalctl -b -0 >> ~/3.13_no_problem.log
    journalctl -b -1 >> ~/3.14-6_nodebug.log
    journalctl -b -2 >> ~/3.14-6_debug.log
    3.13_no_problem.log: http://pastebin.com/EQ2Mucq8
    3.14-6_nodebug.log: http://pastebin.com/18TRZVRp
    3.14-6_debug.log: http://pastebin.com/0QZJBPnf
    In both 3.14 journal messages, I found some similar error message:
    Jun 15 14:37:47 arch-desktop kernel: [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
    Jun 15 14:37:47 arch-desktop kernel: [drm:atom_execute_table_locked] *ERROR* atombios stuck executing D218 (len 62, WS 0, PS 0) @ 0xD234
    Jun 15 14:37:55 arch-desktop kernel: [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
    Jun 15 14:37:55 arch-desktop kernel: [drm:atom_execute_table_locked] *ERROR* atombios stuck executing D218 (len 62, WS 0, PS 0) @ 0xD234
    Jun 15 14:38:00 arch-desktop kernel: [drm:cypress_dpm_set_power_state] *ERROR* rv770_restrict_performance_levels_before_switch failed
    Jun 15 14:38:01 arch-desktop kernel: [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
    Jun 15 14:38:01 arch-desktop kernel: [drm:atom_execute_table_locked] *ERROR* atombios stuck executing D218 (len 62, WS 0, PS 0) @ 0xD234
    Jun 15 14:38:07 arch-desktop kernel: [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
    Jun 15 14:38:07 arch-desktop kernel: [drm:atom_execute_table_locked] *ERROR* atombios stuck executing D218 (len 62, WS 0, PS 0) @ 0xD234
    Jun 15 14:38:13 arch-desktop kernel: [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
    Jun 15 14:38:13 arch-desktop kernel: [drm:atom_execute_table_locked] *ERROR* atombios stuck executing D218 (len 62, WS 0, PS 0) @ 0xD234
    I searched on internet, I think this is caused by my graphic card(ATI 5750), but I have no idea to solve it
    I don't know my system boot failure due to these error or another things.
    my PC specs:
    motherbroad - gigabyte GA-P55A-UD3 (bios ver - F11)
    cpu -  i5-750
    display - ati 5750
    os - arch 64bit
    Currently, I have downgraded back to 3.13.
    I hope someone can give me some idea,
    Thanks
    Last edited by samtai (2014-06-17 12:17:02)

    As there are errors associated with ntpd, I would temporarily disable the ntpd service and also ipv6.
    If they are not the only problem, at least your logs would be easier to examine for other problems.

  • HP Probook 450 G1 Boot Failure....!!

    Dear forum viewes and experts...
    I hope you can provide me with your insights on this problem i am having...
    I bought a new laptop HP ProBook 450 G1 (i5 4200M, 8GB RAM, 1TB HDD, 2GB ATI Graphics card). The laptop comes with DOS free operating system.
    I installed Windows 7 Ultimate from ISO file on a USB stick, and then activated the Windows.
    After updating all drivers and having a clean device manager with no hardware left as unknown, i figured out that the laptop fails to make a cold BOOT.
    After several trials, and installations. the problem remained the same. I changed the installation to Windows 8.1 Pro and the problem remained the same.
    On cold booting, the laptop after showing HP logo in start-up starts to show Windows Logo animation but in Super Slow Motion for about 6-8 minutes, then followed by strange sounds which force me to shut it down by pressing power button for long until it shuts down.
    After huge number of trail and error, i found out that if I entered BIOS Setup (by pressing esc then F10) and then exiting it without doing any changes or even without saving, the Laptop boots Windows 7 very smoothly (in about 15-18 seconds) and works fine. it also can make endless number of smooth restarts without any problem.
    If it is shut down then turned on, the boot failure is the outcome.
    The only way to make a successful cold BOOT (i.e after a shut down) is to enter BIOS setup mode (by pressing esc then F10), then exiting it within seconds without changing anything or saving, then it boots smoothly.
    I tried MBR fixes through command prompt in Recovery Mode, I tried to change booting to make it boot as LEGACY or UEFI Hybrid. The BIOS is updated to the latest frimware on HP website verion 1.2 dated 15 July 2014.
    NO HELP.....All lead to the same disappointing result.
    Any idea whether this is a hardware issue/software issue/BIOS issue?
    Your insights will be highly appreciated

    Can you post a screenshot with the PCI\VEN hardware ids of the bluetooth device? The image below shows an example of what we need to identify the device properly.
    ****Please click on Accept As Solution if a suggestion solves your problem. It helps others facing the same problem to find a solution easily****
    2015 Microsoft MVP - Windows Experience Consumer

  • Boot failure following Windows 8.1 update. shows reason: irql_not_less_or_equal

    Hi,
    I have the dreaded BSOD with irql_not_less_or_equal boot failure. 
    The PC was running Vista when bought, which was subsequently upgraded to Windows 8. This was done via an online purchase & download of the Windows 8 Upgrade, so I do not have any installation media. I have also updated (again online, so no physical media)
    to Windows 8.1
    I have recently had to shut the PC down (it usually stays on all the time), but now it refuses to boot, going straight to the new style BSOD, showing 'irql_not_less_or_equal', which then restarts in to the system restore menu.
    I have tried to remove some peripherals - removing the video card (now using the display adapter on the MoBo), a USB 3 card & a USB head-set dongle - which  has improved the situation a little - it now boots to the log-in page (sometimes), but will
    BSOD after about 10 seconds, regardless of whether I am fast enough to log-in, or not.
    I have tried (from the System Restore menu) to do a restore to a previous state, but it doesn't seem to be able to find the restore points.
    Note, the BSOD occurs if I boot into 'Safe' Mode, or do a normal boot. 
    The bottom line is:...
    I can't boot to Safe Mode, get to any system maintenance tools, so I can't disable/uninstall any drivers.
    Windows 8 & the 8.1 update were purchased online & downloaded, so no boot disk(s).
    The recovery points I have made do not seem to be accessible.
    Any advise on how to proceed?
    cheers
    Paul

    now boots to the log-in page (sometimes), but will BSOD after about 10 seconds, regardless of whether I am fast enough to log-in, or not.
    That should be enough time to get to the Shift-Restart option.   <eg>
    Since you can see what you're doing you don't even have to do the backwards method that I was long proposing so that users who were trying to do this in the dark would be able to bypass their password field.   But maybe using a set of Backtab (Shift-Tab)
    Shift-Space would be more efficient anyway?
    Here is an example of an explanation of the technique:
    http://social.technet.microsoft.com/Forums/en-US/37eff8a6-74a3-4775-90d7-e0aa86c68424/windows-8-black-screen-at-boot?forum=w8itprogeneral#0dc40edd-4e3b-466b-b4af-37c532eb844a
    <quote>
    In order to try to avoid hitting the Password field in this uncertain state I suggested using Backtab (e.g. Shift-Tab) to do the navigation. Fortunately, the pressing of Shift- would solve the problem of whether you were on the Lock screen or already on
    the Login screen. So the iteration would be Shift-Tab, Shift-Space (Fortunately, the Restart item is at the bottom of the Shutdown menu.)
    </quote>
    HTH
    Robert Aldwinckle

Maybe you are looking for

  • Can not delete data from table which is queried in my stored procedure

    Hi, Anyone knows how to fix it: I have a table. In a stored procedure, I have a simple query running on this table. When I want to delete one record from that table, I got error message: ORA-04091: table *** is mutating, trigger/function may not see

  • Cost of sales goods accounting

    Dear all, We have different type of the sales order. At opm level we have accounting entries against sales order like this cost of goods "dr"  and finish product stock "cr". Now I have created one more order type and want dr account (expense ) that i

  • IPhone constantly wants to 'set up' and restore a backup

    Hi all.  Have installed the iOS 5  in my iPhone and after restoring a backup so that my music appears again, whenever I connect said iPhone to iTunes all I ever get now is SET UP YOUR iPHONE This Computer has previously been synced with an iPhone or

  • ATV2 Keeps Turning Itself On

    I have the new Apple TV 2. All works great except, after putting the unit to sleep, sometime later it will switch itself back on. After this has happened, although it shows that it is still connected to the WiFi network, there is no signal and the on

  • How to rename a EJB's jndi name?

    Using Sun Appserver, having deployed all EJBs, I want to rename a EJB's jndi name, for instance, to rename object "java:comp/env/ejb/User" to "java:comp/env/ejb/User1". By using InitialContext.rename(oldName,newName), a NamingException is thrown and