Systemd.timesyncd fails on boot [Solved]

Upgraded systemd to 217-1 and now each boot sees timesyncd fail:
● systemd-timesyncd.service - Network Time Synchronization
Loaded: loaded (/usr/lib/systemd/system/systemd-timesyncd.service; enabled)
Active: failed (Result: start-limit) since Fri 2014-10-31 10:25:59 NZDT; 5min ago
Docs: man:systemd-timesyncd.service(8)
Process: 303 ExecStart=/usr/lib/systemd/systemd-timesyncd (code=exited, status=1/FAILURE)
Main PID: 303 (code=exited, status=1/FAILURE)
Status: "Shutting down..."
Oct 31 10:25:59 Shiv systemd[1]: Failed to start Network Time Synchronization.
Oct 31 10:25:59 Shiv systemd[1]: Unit systemd-timesyncd.service entered failed state.
Oct 31 10:25:59 Shiv systemd[1]: systemd-timesyncd.service failed.
Oct 31 10:25:59 Shiv systemd[1]: start request repeated too quickly for systemd-timesyncd.service
Oct 31 10:25:59 Shiv systemd[1]: Failed to start Network Time Synchronization.
Oct 31 10:25:59 Shiv systemd[1]: Unit systemd-timesyncd.service entered failed state.
Oct 31 10:25:59 Shiv systemd[1]: systemd-timesyncd.service failed.
Once I log in, I am able to restart the service without any complaint.
Anyone else seeing this?
# edit: perhaps related to this fixed(?) bug: http://lists.freedesktop.org/archives/s … 03199.html

tl;dr answer:
# sed -i 's/ remote-fs.target$//' /usr/lib/systemd/system/systemd-journal-flush.service
Long answer:
In systemd 217 a few changes were made with regard to ordering of early boot units, resulting in certain setups which used to work with systemd 216 to make problems with systemd 217. The fix above was also applied in systemd upstream by this commit:
commit 919699ec301ea507edce4a619141ed22e789ac0d
Author: Lennart Poettering <[email protected]>
Date: Fri Oct 31 16:22:36 2014 +0100
units: don't order journal flushing afte remote-fs.target
Instead, only depend on the actual file systems we need.
This should solve dep loops on setups where remote-fs.target is moved
into late boot.
For example, in my case, connman.service explicitly requests to be ordered before remote-fs.target, leading to all kinds of fun:
systemd[1]: Found ordering cycle on basic.target/start
systemd[1]: Found dependency on sysinit.target/start
systemd[1]: Found dependency on systemd-tmpfiles-setup.service/start
systemd[1]: Found dependency on systemd-journal-flush.service/start
systemd[1]: Found dependency on remote-fs.target/start
systemd[1]: Found dependency on connman.service/start
systemd[1]: Found dependency on basic.target/start
systemd[1]: Breaking ordering cycle by deleting job systemd-tmpfiles-setup.service/start
systemd-timesyncd[201]: Failed to allocate manager: No such file or directory
systemd[1]: systemd-timesyncd.service: main process exited, code=exited, status=1/FAILURE
systemd[1]: Failed to start Network Time Synchronization.
systemd[1]: Unit systemd-timesyncd.service entered failed state.
systemd[1]: systemd-timesyncd.service failed.
Explanation:
systemd-journal-flush.service wants to be ordered after remote-fs.target whereas connman.service wants to be ordered before remote-fs.target. Additionally, connman.service requires basic.target. (This is implicit behavior for units which don't declare "DefaultDependencies=no".) This is why basic.target ends up getting pulled in so early in the first place.
Furthermore, systemd-timesyncd.service relies on properly initialized runtime directories in order to work, so it wants to be ordered after systemd-tmpfiles-setup.service.
In order to be able to start basic.target, systemd breaks the ordering cycle by taking systemd-tmpfiles-setup.service out of the transaction, thereby preventing systemd-timesyncd.service from starting up correctly.
Last edited by csn (2014-11-01 22:18:37)

Similar Messages

Systemd-logind fails at boot

Hello,
systemd-logind.service fails at boot.
I get this status:
[root /home/bas] # systemctl status systemd-logind.service
● systemd-logind.service - Login Service
Loaded: loaded (/usr/lib/systemd/system/systemd-logind.service; static)
Active: failed (Result: start-limit) since Thu 2014-11-27 15:07:45 CET; 14s ago
Docs: man:systemd-logind.service(8)
man:logind.conf(5)
http://www.freedesktop.org/wiki/Software/systemd/logind
http://www.freedesktop.org/wiki/Software/systemd/multiseat
Process: 5742 ExecStart=/usr/lib/systemd/systemd-logind (code=exited, status=1/FAILURE)
Main PID: 5742 (code=exited, status=1/FAILURE)
Status: "Shutting down..."
Nov 27 15:07:45 bs2 systemd[1]: Failed to start Login Service.
Nov 27 15:07:45 bs2 systemd[1]: Unit systemd-logind.service entered failed state.
Nov 27 15:07:45 bs2 systemd[1]: systemd-logind.service failed.
Nov 27 15:07:45 bs2 systemd[1]: start request repeated too quickly for systemd-logind.service
Nov 27 15:07:45 bs2 systemd[1]: Failed to start Login Service.
Nov 27 15:07:45 bs2 systemd[1]: Unit systemd-logind.service entered failed state.
Nov 27 15:07:45 bs2 systemd[1]: systemd-logind.service failed.
I don't know where to go from here.. Any help would be very appreciated. Thank you!
bas

bump... Do you need more information? I did not post more because I did not know what. Also, I searched in the forum and on the web but I could not resolve it...

Systemd service failing on boot

Hello, im new to Arch and systemd
When I boot my computer the sabnzbd service fails to start, but if i start it manually afterwards it works fine.
I can make it work by adding a 'sleep 10' to the .service file but that seems like a hack and I'd like to learn the correct way.
It seems as though the sabnzbd.service is starting before the /run tmpfs partition has been mounted but I dont know.
I'm hoping someone smarter than me knows the answer to this
Thanks
Dave
Below is the messages.log
Oct 24 19:58:35 winter systemd[1]: PID file /run/sabnzbd/sabnzbd-8080.pid not readable (yet?) after start.
Oct 24 19:58:36 winter systemd[1]: sabnzbd.service never wrote its PID file. Failing.
Oct 24 19:58:36 winter systemd[1]: Unit sabnzbd.service entered failed state.
Oct 24 19:58:36 winter systemd[1]: Starting Multi-User.
Oct 24 19:58:36 winter systemd[1]: Reached target Multi-User.
Oct 24 19:58:36 winter systemd[1]: Starting Graphical Interface.
Oct 24 19:58:36 winter systemd[1]: Reached target Graphical Interface.
Oct 24 19:58:36 winter systemd[1]: Starting Update UTMP about System Runlevel Changes...
Oct 24 19:58:36 winter systemd[1]: Started Update UTMP about System Runlevel Changes.
Oct 24 19:58:36 winter systemd[1]: Startup finished in 4s 330ms 255us (kernel) + 8s 66ms 514us (userspace) = 12s 396ms 769us.
Oct 24 19:58:36 winter ifplugd[282]: Executing '/etc/ifplugd/netcfg.action eth0 up'.
Oct 24 19:58:36 winter ifplugd[282]: client: up
Oct 24 19:58:36 winter ifplugd[282]: client: loading ethernet-static
Oct 24 19:58:36 winter ifplugd[282]: client: :: ethernet-static up [done]
Oct 24 19:58:36 winter ifplugd[282]: Program executed successfully.
sabnzbd.service:
[Unit]
Description=SABnzbd binary newsreader
After=network.target
[Service]
EnvironmentFile=/etc/conf.d/sabnzbd_systemd
#ExecStartPre=/usr/bin/sleep 10
ExecStart=/bin/sh/ -c "python2 ${SABNZBD_DIR}/SABnzbd.py ${SABNZBD_ARGS} --pid /run/sabnzbd"
ExecStop=/usr/bin/curl -f "${SABNZBD_PROTOCOL}://${SABNZBD_USPW}${SABNZBD_IP}:${SABNZBD_PORT}/sabnzbd/api?mode=shutdown&apikey=${SABNZBD_KEY}"
Type=forking
PIDFile=/run/sabnzbd/sabnzbd-8080.pid
User=sabnzbd
Group=sabnzbd
[Install]
WantedBy=multi-user.target

For diagnostics try:
# systemctl status sabnzbd.service

Disk2vhd efi vhdx vm fails to boot (solved)

Edit: I was able to work around this. From what I've read, a bare metal restore from a physical to virtual machine is not supported, but that's what I tried and it worked beautifully. The only thing that went right today.
So, disk2vhd isn't needed (and as we've seen, didn't work). Instead I took these steps:
1. Control Panel -> File History. After it finishes searching for drives, at the bottom left of the page is a link to System Image Backup. Run it, and select a target drive for the backup. I used a 64Gb key drive. Next, it will
show you the volumes that will be backed up. It automatically selects (and you cannot deselect) the volumes required for a bare metal restore. Any additional volumes are optional. You'll probably want to deselect the target drive for the
backup.
2. After the backup is complete, either move the drive over to the Hyper-V host or access it over the network.
3. In Hyper-V Manager, create a VHDX virtual disk from the backup drive. Then create a blank VHDX that is at least the size of the original machine's system disk (which may have multiple volumes). In my case, this was a 2Tb disk, to which I added
an extra 128Gb just to be sure. This isn't the size of the image backup, it's the size of the disk from which the image backup was taken. I made my disks fixed size. I don't know if it would work otherwise.
4. Create a Gen 2 virtual machine (this was necessary for me since my original machine used EFI boot). On the SCSI host adapter, attach the blank disk that will take the image restore, and attach a second disk containing the image backup (this can
be deleted later).
5. Create a second SCSI host adapter and attach a DVD drive to it (also may be deleted later). Not sure if you really need the second adapter but I was just being cautious. Assign the ISO image for your original machine's install disc (Windows
8.1 Pro Update 1, in my case) to the DVD. Set the DVD to boot.
6. Run the VM and press a key when prompted to run from the DVD. Select the Repair option, and drill down until you get to a page with the option for a System Image Restore. Click on that and then select the drive containing your backup when
prompted. It will inform you that drive C: (your blank drive) will be wiped out and resized to match the original system drive that was backed up. Then let it run. In my case it took maybe three or four minutes, but it was a very sparsely
populated 2Tb drive.
7. After the restore completes, you should be good to go. After testing the new VM, I deleted the second SCSI disk with the backup image, as well as the DVD and its host adapter.
=================================================
I ran disk2vhd on a recently built Windows 8.1 x64 machine. The conversion completed successfully, but I'm having no luck finding the right recipe to booting it in Hyper-V on a Server 2012 R2 machine. I've tried both Gen 1 and Gen 2 (with and
without Secure Boot enabled). In both cases it apparently fails to find a boot loader. The virtual disk is VHDX.
I ran disk2vhd twice. Once including the additional volumes Windows creates for EFI, and once without. The result is the same either way.
Any help much appreciated.

Hi Michael,
Thanks for your sharing .
I am afraid the physical host is using UEFI .(I test disk2vhd on MBR partition ,it works )
EDIT:
Here is another similar thread :
http://social.technet.microsoft.com/Forums/windowsserver/en-US/9a668872-0f58-4da3-a407-2f2018d42b50/windows-server-2012-r2-datacenter-how-to-create-hyperv-which-will-be-the-replica-of-host-os?forum=winserverhyperv
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Dhcpcd fails at boot (SOLVED)

Hi peoples.....
this is a very common problem in arch so i've seen, but i followed many instructions and looked at the wiki,
and so far i can't fix it....
when i boot into arch... when it gets to "network" it says busy... and ends up failing... dhcp fails.........
to get internet working, i have to open a konsole, log in as root, and enter "dhcpcd" then my internet works....
i've tried quite a few suggestions... such as adding to my /etc/rc.local file... which is this:
#!/bin/bash
# /etc/rc.local: Local multi-user startup script.
dhcpcd -k eth0 dhcpcd -nd eth0
here is my rc.conf file which to me, looks right
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
LOCALE="en_US.utf8"
HARDWARECLOCK=""
USEDIRECTISA="no"
TIMEZONE="Australia/Perth"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
# HARDWARE
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=()
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# NETWORKING
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
HOSTNAME="archbox"
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
# DHCP: Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#Static IP example
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
eth0="dhcp"
INTERFACES=(eth0)
ROUTES=(!gateway)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network.d
# This now requires the netcfg package
#NETWORKS=(main)
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
DAEMONS=(syslog-ng network xorg hal kdm netfs crond)
I even tried making a profile copied from examples..... which for me... was wired ethernet-dhcp, since im using a wired connection with dhcp...... and trying to connect to it using netcfg then profile name..... here is my profile input
CONNECTION="ethernet-iproute"
DESCRIPTION="A basic dhcp ethernet connection using iproute"
INTERFACE="eth0"
IP="dhcp"
and theres also 1 other suggestion that i tried... which was adding "dhcp eth0" to my /etc/rc.d/network but dhcpcd still fails on reboot and i have to keep manually enabling it.....
any suggestions???
thanx in advance
kaddy
Last edited by kaddy (2009-09-28 15:53:04)

lol. anybody?????
I've tried everything in the wiki under networking, i've tried several other suggestions that helped others, but it seems i can only get my internet to work by manually runniny "dhcpcd"
but it is annoying to do that everytime i boot.....(i wonder if i can make it start during boot...? but how? its not a daemon.....?"
anyways.....
more than happy to try any suggestions..... theres bound to be something wrong here... unless dhcpcd is buggy!
I even tried wicd and couldn't get it to work properly.... but thats another story.....
I've tried removing ! from gateway in rc.conf...... i've tried moving the hal daemon last, as i found out it can effect other daemons if run before network........
funny thing is, about 1 out of 10 times, everything starts up ok, with no fails... but after another reboot, back to the norm.
im out of ideas........
im almost gonna give up on this issue........ i don't know what else i can try
Last edited by kaddy (2009-09-27 16:29:00)

Filesystem check failed while booting [SOLVED]

I tried to get some help from my previous post but got no answers, so I'll summarize in hope of getting an answer:
I've installed linux before windows because I had this operating system before. But, when I've partitioned I've made a NTFS type 83 for windows, cause I know I'd install it later on.
Now, I've restored my bootloader (grub) but when I try to boot my arch linux copy, a message tells me that my partition sda2 which is my Windows one, isn't clean or corrupt.
all my linux partition are clean, but my NTFS windows partition make me unable to boot on my linux OS with this error msg:
fsck.ext4: Bad magic number in super-block while trying to open /dev/sda2
/dev/sda2:
The superblock could not be read or does not describe a correct ext filesystem. If the devine is valid and it really contains an ext2 filesystem (and not swao or ufs or simething else), then the superblock is corrupt, and you might try running e2fsck with an alternate superbloc:
e2fsck -b 8193 <device>
Next I can do is entering the root psw and use the command line, I really need help to restore my linux partition without formating anything, please.
My guess is that linux doesn't reorganize the partition as it is NTFS and doesn't boot for this reason, but didn't find how to fix it over internet yet, some help would be really appreciated.
Last edited by Mazh (2011-06-10 20:30:39)

My partition layout is:
fdisk -l output:
/dev/sda1 ID (5) extended (don't know what's that didn't think I've made that myself, maybe coming from windows when I installed the NTFS partition)
/dev/sda2 * HPFS/NTFS/exFAT ID (7) (strange cause I had set 87 but well, windows is working correctly it seems)
/dev/sda3 ID (83) linux
/dev/sda5 ID (83) linux
/dev/sda6 ID (83) linux
/dev/sda7 ID (83) linux
/dev/sda8 * ID (83) linux
yep, it's actually strange that my fsck.ext4 check my sda2 partition NTFS...
cat /etc/fstab:
/dev/sda2 /home ext4 defaults 0 1
/dev/sda5 swap defaults 0 0
/dev/sda6 /var ext4 defaults 0 1
/dev/sda7 /usr ext4 defaults 0 1
/dev/sda8 / ext4 defaults 0 1
menu.lst
linux grub
/dev/sd0 (fd0)
/dev/sda (hd0)
/dev/sdb2 (hd1,1)
/dev/sda3 (hd0,2)
title arch linux
root (hd0,7)
kernel /bootvmlinuz26 root=/dev/sda8 ro
initrd /boot/kernel26.img
the arch fallback (same)
title Windows xp lite sp3
rootnoverify (hd0,1)
makeactive
chainloader +1
I really have to write by hands, so if you wants more info tell me and I'll write more.
it's strange, could you explain me what does mean hd1 or hd0? isn't the 1st and second hard drive? and the second array the partition? cause if so, i've only 1 drive. But I'm probably not correct. Hope you get enough info to get me out of this problem!
And no, I'm not using UUIDs, thx for your suggestion!

"Filesystem check failed" on boot [Solved]

It seems to not like /home or /. Tried reinstalling Arch using ext3 instead of ext4 but I still get the same error. I tried searching for a fix on the forums already but couldn't find one that worked for me.
Misc Info:
- Using VirtualBox 3.1.2
- Using 2009.08 netinstall iso
Last edited by NightKev (2010-02-17 05:15:11)

I don't know how you would do so in VB, but on my desktop I used an Arch LiveCD to reinstall GRUB in order to get /root and the kernel image working from the /boot directory. I entered the command "grub" as root in a terminal to open the grub prompt "grub>" then I entered "find /boot/grub/stage1" and received back" (hd1,1)" which is where my root partition was located. I then entered "root (hd1,1)" and then "setup (hd0)" and then "quit". It installed GRUB to the MBR. I don't know if that's helpful in your case though, but if GRUB is installed it could be.

Systemd: Slim fails to start automatically after boot

Hi, after some update a couple of weeks ago (I don't remember exactly), slim fails to start after boot. I use systemd and just had enabled the slim.service file that is included in the package. After boot, I can login on the tty and then restart the slim.service, and everything works.
In the slim.log file it says:
Fatal server error:
no screens found
Giving up.
slim: unable to connect to X server
/usr/bin/xauth: file /var/run/slim.auth does not exist
It seems like slim is started before X, since everything works when I restart the service manually. What is causing this problem and how can I solve it?
Best regards and thanks,
Jan Oliver

oliarch ~ sudo systemd-analyze blame
2460ms net-auto-wireless.service
243ms rsyslog.service
239ms sshd.service
183ms console-kit-log-system-start.service
136ms systemd-logind.service
124ms console-kit-daemon.service
119ms systemd-udev-trigger.service
99ms systemd-sysctl.service
82ms systemd-readahead-replay.service
80ms systemd-vconsole-setup.service
63ms systemd-user-sessions.service
62ms systemd-remount-fs.service
58ms systemd-readahead-collect.service
55ms sys-kernel-debug.mount
43ms dev-sda2.swap
43ms dev-mqueue.mount
42ms dev-hugepages.mount
26ms systemd-tmpfiles-setup.service
20ms srv.mount
13ms tmp.mount
12ms systemd-udev.service
10ms boot.mount
9ms home.mount
oliarch ~ sudo journalctl --no-pager -a | grep slim
Jun 24 14:25:01 oliarch systemd[1]: slim.service: main process exited, code=exited, status=1
Jun 24 14:25:01 oliarch systemd[1]: Unit slim.service entered failed state.

[SOLVED]systemd-timesyncd is not syncing time

Quick solution:
1) Check that systemd-networkd is running (if not, start it)
2) If it is running and timesyncd is not syncing, just restart systemd-networkd
more on this in the last post.
Hello,
I tried to replace ntp with systemd-timesyncd. I disabled ntpd, enabled systemd-timesyncd, enabled and set systemd-networkd (I found that it might help) over netctl (which I could uninstall then). It somehow worked for few reboots, but then it stopped. Of course there must be a reason why, but I can't figure out what it could be. Everything looks fine to me, but time is just not syncing and I'm 30 minutes in the past (compared with realtime). It loads saved time (as fake-hwclock does), but then there is no sync.
Here are my logs:
~ $ systemctl status systemd-networkd systemd-timedated systemd-timesyncd
* systemd-networkd.service - Network Service
Loaded: loaded (/usr/lib/systemd/system/systemd-networkd.service; enabled)
Active: active (running) since Sun 2014-06-08 16:48:36 CEST; 15h ago
Docs: man:systemd-networkd.service(8)
Main PID: 149 (systemd-network)
Status: "Processing requests..."
CGroup: /system.slice/systemd-networkd.service
`-149 /usr/lib/systemd/systemd-networkd
Jun 08 16:48:36 smecpi systemd[1]: Starting Network Service...
Jun 08 16:48:36 smecpi systemd-networkd[149]: eth0: link configured
Jun 08 16:48:36 smecpi systemd[1]: Started Network Service.
Jun 08 16:48:37 smecpi systemd-networkd[149]: eth0: gained carrier
* systemd-timedated.service - Time & Date Service
Loaded: loaded (/usr/lib/systemd/system/systemd-timedated.service; static)
Active: active (running) since Mon 2014-06-09 08:14:05 CEST; 11min ago
Docs: man:systemd-timedated.service(8)
man:localtime(5)
http://www.freedesktop.org/wiki/Software/systemd/timedated
Main PID: 4520 (systemd-timedat)
CGroup: /system.slice/systemd-timedated.service
`-4520 /usr/lib/systemd/systemd-timedated
Jun 09 08:14:05 smecpi systemd[1]: Started Time & Date Service.
* systemd-timesyncd.service - Network Time Synchronization
Loaded: loaded (/usr/lib/systemd/system/systemd-timesyncd.service; enabled)
Active: active (running) since Sun 2014-06-08 16:48:35 CEST; 15h ago
Docs: man:systemd-timesyncd.service(8)
Main PID: 125 (systemd-timesyn)
CGroup: /system.slice/systemd-timesyncd.service
`-125 /usr/lib/systemd/systemd-timesyncd
Jan 01 01:00:06 smecpi systemd-timesyncd[125]: System clock time unset or jumped backwards, restoring from recorded timestamp: Sun 2014-06-08 16:48:35 CEST
Jun 08 16:48:35 smecpi systemd[1]: Started Network Time Synchronization.
~ $ timedatectl
Local time: Mon 2014-06-09 08:29:51 CEST
Universal time: Mon 2014-06-09 06:29:51 UTC
RTC time: n/a
Time zone: Europe/Prague (CEST, +0200)
NTP enabled: yes
NTP synchronized: no
RTC in local TZ: no
DST active: yes
Last DST change: DST began at
Sun 2014-03-30 01:59:59 CET
Sun 2014-03-30 03:00:00 CEST
Next DST change: DST ends (the clock jumps one hour backwards) at
Sun 2014-10-26 02:59:59 CEST
Sun 2014-10-26 02:00:00 CET
Any ideas?
Last edited by Kotrfa (2014-06-11 16:30:15)

Ok, thank you for your help. I signed a bug here: https://bugs.freedesktop.org/show_bug.cgi?id=79836 .
Edit:
So here is a little help. timesyncd just waits for "network configuration change". I guess that (somehow) timesyncd is runned after networkd and then waits for change. All you have to do is
systemctl restart systemd-networkd
Here is example and steps to reproduce (after boot up, both networkd and timesyncd are enabled):
~ $ systemctl status systemd-timesyncd systemd-networkd
* systemd-timesyncd.service - Network Time Synchronization
Loaded: loaded (/usr/lib/systemd/system/systemd-timesyncd.service; enabled)
Active: active (running) since Wed 2014-06-11 17:55:50 CEST; 24min ago
Docs: man:systemd-timesyncd.service(8)
Main PID: 126 (systemd-timesyn)
CGroup: /system.slice/systemd-timesyncd.service
`-126 /usr/lib/systemd/systemd-timesyncd
Jun 01 01:00:06 locsmxp systemd-timesyncd[126]: System clock time unset or jumped backwards, restoring from recorded timestamp:...0 CEST
Jun 11 17:55:50 locsmxp systemd[1]: Started Network Time Synchronization.
* systemd-networkd.service - Network Service
Loaded: loaded (/usr/lib/systemd/system/systemd-networkd.service; enabled)
Active: active (running) since Wed 2014-06-11 17:55:51 CEST; 24min ago
Docs: man:systemd-networkd.service(8)
Main PID: 150 (systemd-network)
Status: "Processing requests..."
CGroup: /system.slice/systemd-networkd.service
`-150 /usr/lib/systemd/systemd-networkd
Jun 11 17:55:51 locsmxp systemd[1]: Started Network Service.
Jun 11 17:55:51 locsmxp systemd-networkd[150]: eth0: link configured
Jun 11 17:55:52 locsmxp systemd-networkd[150]: eth0: gained carrier
Hint: Some lines were ellipsized, use -l to show in full.
now restart networkd:
~ $ systemctl restart systemd-networkd
and result:
~ $ systemctl status systemd-timesyncd systemd-networkd
* systemd-timesyncd.service - Network Time Synchronization
Loaded: loaded (/usr/lib/systemd/system/systemd-timesyncd.service; enabled)
Active: active (running) since Wed 2014-06-11 17:55:50 CEST; 25min ago
Docs: man:systemd-timesyncd.service(8)
Main PID: 126 (systemd-timesyn)
Status: "Using Time Server 216.239.32.15:123 (time2.google.com)."
CGroup: /system.slice/systemd-timesyncd.service
`-126 /usr/lib/systemd/systemd-timesyncd
Jun 01 01:00:06 locsmxp systemd-timesyncd[126]: System clock time unset or jumped backwards, restoring from recorded timestamp:...0 CEST
Jun 11 17:55:50 locsmxp systemd[1]: Started Network Time Synchronization.
Jun 11 18:20:48 locsmxp systemd-timesyncd[126]: Network configuration changed, trying to establish connection.
Jun 11 18:20:48 locsmxp systemd-timesyncd[126]: Network configuration changed, trying to establish connection.
Jun 11 18:20:48 locsmxp systemd-timesyncd[126]: Using NTP server 216.239.32.15:123 (time2.google.com).
Jun 11 18:20:49 locsmxp systemd-timesyncd[126]: interval/delta/delay/jitter/drift 64s/+0.000s/0.000s/0.000s/+0ppm
* systemd-networkd.service - Network Service
Loaded: loaded (/usr/lib/systemd/system/systemd-networkd.service; enabled)
Active: active (running) since Wed 2014-06-11 18:20:48 CEST; 5s ago
Docs: man:systemd-networkd.service(8)
Main PID: 1129 (systemd-network)
Status: "Processing requests..."
CGroup: /system.slice/systemd-networkd.service
`-1129 /usr/lib/systemd/systemd-networkd
Jun 11 18:20:48 locsmxp systemd-networkd[1129]: eth0: gained carrier
Jun 11 18:20:48 locsmxp systemd[1]: Started Network Service.
Jun 11 18:20:48 locsmxp systemd-networkd[1129]: eth0: link configured
Hint: Some lines were ellipsized, use -l to show in full.
I solved this issue by adding new service (guide here: https://wiki.archlinux.org/index.php/Sy … rocess.3F) which runs this simple script
#!/usr/bin/bash
sleep 15
systemctl restart systemd-networkd
So workaround...
Last edited by Kotrfa (2014-06-11 16:46:06)

[SOLVED] Arch Linux Duke (2007) Fails to Boot

Folks, I have a unique and challenging problem that has exhausted my Arch Linux skills, and so I am now turning to you.
I have a vintage Pentium Pro 200 system (that’s 200 MHz folks! – 200 MHz 686 architecture – the original 686!), two CPUs, running a dual boot between Windows NT 4.0 and Arch Linux Duke (2007). It has 512 MB of RAM and a 120 GB hard drive, partitioned up between Windows NT and Linux. I built this system new in 2007, hence the dated version of Arch. It has run like a charm all these years, granted not getting that much use. After about a year of no use at all, I fired the system up last week to help with a little research for a blog post I was writing on networking Windows NT 4.0 and Mac OS 8.6. Windows NT 4.0 fired right up with no issue, and after I was done testing what needed to be tested I tried to boot over to Arch.
After a year of disuse, Arch unexpectedly and stubbornly refused to boot. The boot process started up just fine, but towards the end, it declared that it could not mount the root file system on the root device and took a kernel panic and stopped. My Arch skills have gotten a bit rusty in the last few years, but I dusted them off and went to work. My guess was a file system or superblock error. Arch wouldn’t boot, but I dragged out my trusty RIPLinux 2.9 Rescue Live CD and fired it up. It came right up and ran, and I was able to mount the Arch partition and view all the files… everything seemed to be there; it just wouldn’t boot. Windows NT 4.0 AND RIPLinux both boot and run on the machine, so the hardware is fine as well.
A little information on the disk layout. Windows NT 4.0 is in the first partition on the hard drive. The extended partition has a second Windows NT 4.0 partition (sort of a /home partition for Windows NT 4.0), followed by the main Arch partition (the one I am trying to boot), followed by a swap partition and then the largest partition, which I use to share data between Arch and Windows NT 4.0 (I have loaded an ext2/3 driver into Windows NT 4.0 and it happily accesses the Linux partitions on the box).
RIPLinux’s e2fsck did find some issues with the Arch partition and I had it repair them all. I checked again afterwards that all the files were still there, and they were. With the partition now known to be clean, and the superblock repaired from one of the backups, all should have been well. However, Arch still wouldn’t (and still won’t) boot.
RIPLinux has a kind of a chain loader function, so I had it attempt to start up Arch for me. However, this was flummoxed by the fact that Arch addresses all my hard drive partitions as /dev/sdax and RIPLinux addresses them as /dev/hdax. Hence, without a common language, it was hard to get the one to start the other. Still, using this function, I have been able to get a crippled version of Arch running on the machine again. No modules had been loaded, and so it couldn’t do almost anything, but there it was (and is), Arch Linux Duke, at the CLI level. From there, I can see all the files, I can move freely in and out of my user account and the root account, but I can’t make the thing actually boot properly.
If you have read this far, you are a trooper. Summarizing what I know, the hardware is good, the file system is clean, the superblock is good, I can mount it cleanly from a live CD and I can chain load a crippled version of Arch. Here is the boot process blow-by-blow. When I try to do a normal boot, the Windows NT 4.0 loader passes control to the Lilo boot sector I have placed on hda1 (sda1 in Duke’s parlance). Lilo takes over, present a menu and when I select Duke, takes off. Arch Linux Duke starts to boot. It gets a good long way along, all the way along to:
:: Loading udev events [Pass]
:: Mount root Read-only
:: Checking file systems
This is where it stops.
The next thing I see is:
/dev/sda6
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>
I then get a sort of character based splash screen that says
**********FILE SYSTEM CHECK FAILED ****************************
* Please repair manually and reboot. Note that the root file system
* is currently mounted read-only. To remount it read-write, type:
* mount –n –o remount,rw /. When you exit the maintenance
* shell, the system will reboot automatically
Give root password for maintenance
At this point, I give the root password and enter the maintenance shell as root. I typed in “mount” and the first entry I got back is
/dev/sda6 on / type ext3 (rw)
This is exactly the root partition that the start up complains about. It is clearly there. I can see it, I can walk around it… it is clearly there. Why won’t it boot? Despite the message, the superblock is fine – it passes every test e2fsck can throw at it.
At this point, I did a “e2fsck /dev/hda6 (which is how RIPLinux would have passed it into Arch” and it says it is “clean”. I suspect that the Superblock message is because Arch sees root as sda6, while RIP passed it in as hda6...
Deciding to see what Arch would be seeing as it tried to set things up in the boot sequence, I tried the following next:
# mknod “/dev/root2” b 3 6
(“3” because RIPLinux refers to my hard drive as IDE, while Arch refers to it by major number “8”, which is SCSI. By the way, it IS an IDE drive – not sure why Arch insists on using the sdx nomenclature instead of hdx)
Then I entered “mount /dev/root2 /mnt/hda6” and “ls /mnt/hda6”
All was well. I can make the node, I can mount it, and I can see the contents. All is clearly well, but something is clearly wrong enough that Arch can’t boot.
I am totally out of ideas. I have tried every trick I know and am out of tricks. I would welcome any insights as to what I could try to get this venerable Arch installation back on its legs.
By the way, the key section of the /etc/lilo.conf file (lest anyone want to know) is:
image = /boot/vmlinuz26
root = /dev/sda6
label = ArchLinux-Duke
initrd = /boot/kernel26.img
read-only
I am stumped. Thanks in advance for any and all pointers you may be able to offer.
Last edited by mac57 (2014-06-02 17:42:21)

Folks, thanks for all your helpful comments, and I wanted to report back to you that I finally overcame the issue, and ArchLinux-Duke (2007) is once again executing flawlessly on my old Pentium Pro 200 system. I won't bother reporting here all the blind allies I went down as I tried to figure out what was wrong, but in the end, literally moments before I was about to give up and overwrite my Arch installation with a new Linux variant (antiX seemed well suited for such old and low power hardware), my attention was drawn to a note I had made in my files back in 2007 about a problem with similar symptoms. In that case, I had just deleted ZenWalk Linux from the hard drive (both Arch and Zen had been on the drive), and merged several partitions to make use of the newly free space. This had changed Arch's view of the drive lettering, and what had been its /dev/sddx root device was now /dev/sdcx. Arch failed to boot, throwing off the same errors I was seeing now. I wish I had recalled that note a month or so ago! It would have saved me a lot of work and a lot of frustration.
At any rate, as a last step, and testing the idea that maybe the drive lettering had changed for some reason, I repeatedly manually booted Arch, specifying root=/dev/sda6, then /dev/sdb6, then /dev/sdd6, and finally, /dev/sdc6. Eureka! Arch now considered itself to be on /dev/sdc6 whereas previously it had been on /dev/sda6. This got me part way there, but the boot failed at the filesystem check stage and threw me into root. I disabled the file system check in /etc/rc.sysinit and got farther. Then I cleaned up /etc/fstab to agree with the new sdc naming, and I was back on the air fully.
So, what had happened was that Arch had changed its view of the drive it was on from sda6 to sdc6. While I could not understand why this "sudden" change had occurred, at least I had a solution, and had Arch back up and running.
Trolling through the rest of my notes, I found the answer. In 2012, the Tekram SCSI card in the machine failed, and I ultimately replaced it with an Adaptec card. The Tekram card did not have a BIOS segment on it. The Adaptec card did. My guess is that this caused the two internal SCSI devices I have built into the system (Iomega ZIP and Jaz respectively) to be enumerated first, claiming the "sda" and "sdb". device names. That left "sdc" for the root device, and that is where Arch went next. This is my guess anyway.
I should have caught this issue back in 2012, at the time, but from my notes, I can see that I tested the new card thoroughly using the Windows NT 4.0 side of the machine, but never thought to bring up Arch as well. Hence, this problem lay dormant for two years, before I attempted to fire up Arch last month and blundered right into it.
It has not all been bad. I have learned more about the ext2 and ext3 file systems and superblocks in the intervening time than I will ever need to use. I have learned how to manually boot Linux on a machine whose BIOS is so old that it cannot address the disk cylinder that the kernel is on and I have completely refreshed the many general Linux skills that used to just flow from my finger tips. It has been a frustrating experience, but ultimately a successful and useful one.
Just wanted to let everyone know that this is now [SOLVED]. I would mark the post as such, but I don't see any obvious way to do that. Thanks again everyone.

[SOLVED] systemd --user: "Failed to open private bus connection:"

EDIT: The solution was to set DBUS_SESSION_BUS_ADDRESS, as suggested by gtmanfred in irc. By putting the following before executing systemd --user, the error vanished:
export DBUS_SESSION_BUS_ADDRESS=/run/user/$(id -u)/dbus/user_bus_socket
===================
Original problem:
Everything on my box appears to be working ok, but I'm getting this error consistently in tty1 and at the top of journalctl (as user) whenever I start systemd --user:
systemd[3975]: Failed to open private bus connection: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
I roughly have my system setup per this wiki section https://wiki.archlinux.org/index.php/Sy … ur_Session. I start systemd --user via a small script in my .bash_profile. Here are my relevant dbus{.service,socket} files, from the package user-session-units mentioned in the wiki: (Edit: xorg is started through xorg-launch-helper, also from that wiki page) Edit2: I'm not using autologin. I noticed that under the autologin section of that page, DBUS_SESSION_BUS_ADDRESS is set to some path. In my setup that isn't set anywhere, so I may try to copy that later but I don't have time to play with it right now. Will post back later.
=====/usr/lib/systemd/user/dbus.service=====
[Unit]
Description=D-Bus System Message Bus
Requires=dbus.socket
[Service]
ExecStart=/usr/bin/dbus-daemon --session --address=systemd: --nofork --systemd-activation
ExecReload=/usr/bin/dbus-send --print-reply --session --type=method_call --dest=org.freedesktop.DBus / org.freedesktop.DBus.ReloadConfig
=====/usr/lib/systemd/user/dbus.socket=====
[Unit]
Description=D-Bus System Message Bus Socket
[Socket]
ListenStream=%t/dbus/user_bus_socket
And the output of sudo systemctl status dbus:
dbus.service - D-Bus System Message Bus
Loaded: loaded (/usr/lib/systemd/system/dbus.service; static)
Active: active (running) since Tue 2013-02-05 14:50:30 EST; 22min ago
Main PID: 369 (dbus-daemon)
CGroup: name=systemd:/system/dbus.service
└─369 /usr/bin/dbus-daemon --system --address=systemd: --no...
Feb 05 14:50:30 sellers-laptop systemd[1]: Starting D-Bus System Message Bus...
Feb 05 14:50:30 sellers-laptop systemd[1]: Started D-Bus System Message Bus.
Feb 05 14:51:18 sellers-laptop dbus-daemon[369]: dbus[369]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
Feb 05 14:51:18 sellers-laptop dbus[369]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
Feb 05 14:51:18 sellers-laptop dbus[369]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.Avahi.service' for details.
Feb 05 14:51:18 sellers-laptop dbus-daemon[369]: dbus[369]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.Avahi.service' for details.
I'm not sure what the error even means or how to go about debugging it. Any suggestions would be appreciated.
Last edited by Feynman (2013-02-05 22:07:23)

NVM...didn't notice it was already solved.
Last edited by the sad clown (2013-02-05 22:33:10)

Systemd fails on boot

After running systemd with absolutely no issues for a good month or two, my arch setup fails to boot with a cascade of errors, the first of which is
[Failed] Failed to start Setup Virtual Console
Consequently, I can't even get a terminal to attempt diagnostics. Using a live CD to create /var/log/journal/ for persistent logs (as instructed by the wiki) seems useless as nothing is saved to that directory.
Are there any diagnostic or repair steps I can take, or is my best bet to back up my files off of that partition and reinstall Arch?
Last edited by slavik262 (2012-09-26 23:38:03)

slavik262 wrote:
archie0 wrote:I'm not sure this helps, but did you configure your /etc/vconsole.conf?
https://wiki.archlinux.org/index.php/Sy … and_keymap
I don't believe I have one set up, but the defaults should be just fine. My other arch setup on my laptop doesn't have vconsole.conf and I'm having no issues.
By default, the file should be empty. Are you using SystemD on your laptop as well?

Netctl wireless fails every other boot [SOLVED]

This has me stumped.
Here is my netctl profile:
gdm@gdmThink ~$ cat /etc/netctl/mifi4510l
Description='A simple WPA encrypted wireless connection using a static IP'
Interface=wlp3s0
Connection=wireless
Security=wpa
ESSID='Verizon MIFI4510L E3A0 Secure'
Key='password'
IP=static
Address='192.168.1.11/24'
Gateway='192.168.1.1'
DNS=('192.168.1.1')
TimeoutWPA=30
Here is a pastebin link to the "journalctl -b" for a failed boot:
http://pastebin.com/GbELjqm0
Here is a pastebin link to the "journalctl -b for a successful boot.
http://pastebin.com/ywzDvkqD
Other than there is no attempt to authenticate in the failed boot, I see no significant difference.
Any help would be greatly appreciated.
Last edited by gdavid (2013-05-26 16:19:42)

[root@gdmThink gdm]# systemctl status -n 100 [email protected]
[email protected] - A simple WPA encrypted wireless connection using a static IP
Loaded: loaded (/etc/systemd/system/[email protected]; enabled)
Active: failed (Result: exit-code) since Sat 2013-05-25 17:57:53 EDT; 42s ago
Docs: man:netctl.profile(5)
Process: 830 ExecStart=/usr/lib/network/network start %I (code=exited, status=1/FAILURE)
[root@gdmThink gdm]#
From dmesg:
[ 11.726467] systemd[1]: Starting Login Service...
[ 11.726547] systemd[1]: About to execute: /usr/lib/systemd/systemd-logind
[ 11.726627] systemd[837]: Executing: /usr/lib/systemd/systemd-user-sessions start
[ 11.726685] systemd[1]: Forked /usr/lib/systemd/systemd-logind as 838
[ 11.726784] systemd[1]: systemd-logind.service changed dead -> start
[ 11.726799] systemd[1]: Starting D-Bus System Message Bus...
[ 11.726971] systemd[838]: Executing: /usr/lib/systemd/systemd-logind
[ 11.727515] systemd[1]: About to execute: /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
[ 11.727642] systemd[1]: Forked /usr/bin/dbus-daemon as 839
[ 11.727781] systemd[1]: dbus.service changed dead -> running
[ 11.727786] systemd[1]: Job dbus.service/start finished, result=done
[ 11.727923] systemd[839]: Executing: /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
[ 11.728498] systemd[1]: Started D-Bus System Message Bus.
[ 11.728602] systemd[1]: Set up jobs progress timerfd.
[ 11.728630] systemd[1]: Received SIGCHLD from PID 829 (alsactl).
[ 11.728645] systemd[1]: Got SIGCHLD for process 829 (alsactl)
[ 11.728674] systemd[1]: Child 829 died (code=exited, status=0/SUCCESS)
[ 11.728677] systemd[1]: Child 829 belongs to alsa-restore.service
[ 11.728685] systemd[1]: alsa-restore.service: main process exited, code=exited, status=0/SUCCESS
[ 11.728782] systemd[1]: alsa-restore.service changed start -> dead
[ 11.728841] systemd[1]: Job alsa-restore.service/start finished, result=done
[ 11.729552] systemd[1]: Started Restore Sound Card State.
[ 11.729583] systemd[1]: Got SIGCHLD for process 833 (modprobe)
[ 11.729609] systemd[1]: Child 833 died (code=exited, status=0/SUCCESS)
[ 11.729611] systemd[1]: Child 833 belongs to lm_sensors.service
[ 11.729618] systemd[1]: lm_sensors.service: main process exited, code=exited, status=0/SUCCESS
[ 11.729620] systemd[1]: lm_sensors.service running next main command for state start
[ 11.729652] systemd[1]: About to execute: /usr/bin/sensors -s
[ 11.729756] systemd[1]: Forked /usr/bin/sensors as 840
[ 11.729894] systemd[1]: Accepted connection on private bus.
[ 11.729900] systemd[1]: Incoming traffic on dbus.socket
[ 11.729908] systemd[1]: dbus.socket changed listening -> running
[ 11.729940] systemd[1]: Accepted connection on private bus.
[ 11.729978] systemd[1]: Accepted connection on private bus.
[ 11.729987] systemd[840]: Executing: /usr/bin/sensors -s
[ 11.730107] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
[ 11.730151] systemd[1]: systemd-update-utmp.service: cgroup is empty
[ 11.730175] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
[ 11.730195] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
[ 11.730237] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
[ 11.730264] systemd[1]: alsa-restore.service: cgroup is empty
[ 11.730282] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
[ 11.730299] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
[ 11.776646] systemd[835]: Executing: /usr/bin/laptop_mode init auto
[ 11.937296] systemd[1]: Received SIGCHLD from PID 837 (systemd-user-se).
[ 11.937318] systemd[1]: Got SIGCHLD for process 837 (systemd-user-se)
[ 11.937352] systemd[1]: Child 837 died (code=exited, status=0/SUCCESS)
[ 11.937354] systemd[1]: Child 837 belongs to systemd-user-sessions.service
[ 11.937366] systemd[1]: systemd-user-sessions.service: main process exited, code=exited, status=0/SUCCESS
[ 11.937490] systemd[1]: systemd-user-sessions.service changed start -> exited
[ 11.937494] systemd[1]: Job systemd-user-sessions.service/start finished, result=done
[ 11.938230] systemd[1]: Started Permit User Sessions.
[ 11.938264] systemd[1]: Starting Getty on tty1...
[ 11.938997] systemd[1]: About to execute: /sbin/agetty --noclear tty1 38400 linux
[ 11.939186] systemd[1]: Forked /sbin/agetty as 844
[ 11.939313] systemd[1]: [email protected] changed dead -> running
[ 11.939344] systemd[1]: Job [email protected]/start finished, result=done
[ 11.940070] systemd[1]: Started Getty on tty1.
[ 11.940089] systemd[1]: Starting Login Prompts.
[ 11.940092] systemd[1]: getty.target changed dead -> active
[ 11.940094] systemd[1]: Job getty.target/start finished, result=done
[ 11.940824] systemd[1]: Reached target Login Prompts.
[ 11.940886] systemd[1]: Accepted connection on private bus.
[ 11.941016] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
[ 11.941058] systemd[1]: systemd-user-sessions.service: cgroup is empty
[ 11.941085] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
[ 11.973600] e1000e 0000:00:19.0: irq 49 for MSI/MSI-X
[ 12.074517] e1000e 0000:00:19.0: irq 49 for MSI/MSI-X
[ 12.074737] IPv6: ADDRCONF(NETDEV_UP): enp0s25: link is not ready
[ 12.074979] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 12.075190] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[ 12.425688] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 12.425894] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[ 12.464645] systemd[1]: Received SIGCHLD from PID 840 (sensors).
[ 12.464666] systemd[1]: Got SIGCHLD for process 840 (sensors)
[ 12.464701] systemd[1]: Child 840 died (code=exited, status=0/SUCCESS)
[ 12.464704] systemd[1]: Child 840 belongs to lm_sensors.service
[ 12.464716] systemd[1]: lm_sensors.service: main process exited, code=exited, status=0/SUCCESS
[ 12.464829] systemd[1]: lm_sensors.service changed start -> exited
[ 12.464838] systemd[1]: Job lm_sensors.service/start finished, result=done
[ 12.465943] systemd[1]: Started Initialize hardware monitoring sensors.
[ 12.466053] systemd[1]: Accepted connection on private bus.
[ 12.466244] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
[ 12.466278] systemd[1]: lm_sensors.service: cgroup is empty
[ 12.466302] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
[ 12.648245] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[ 12.648631] systemd[1]: Received SIGCHLD from PID 831 (dhcpcd).
[ 12.648648] systemd[1]: Got SIGCHLD for process 831 (dhcpcd)
[ 12.648680] systemd[1]: Child 831 died (code=exited, status=0/SUCCESS)
[ 12.648682] systemd[1]: Child 831 belongs to dhcpcd.service
[ 12.648688] systemd[1]: dhcpcd.service: control process exited, code=exited status=0
[ 12.648719] systemd[1]: dhcpcd.service got final SIGCHLD for state start
[ 12.648735] systemd[1]: Main PID loaded: 872
[ 12.648782] systemd[1]: dhcpcd.service changed start -> running
[ 12.648786] systemd[1]: Job dhcpcd.service/start finished, result=done
[ 12.650040] systemd[1]: Started dhcpcd on all interfaces.
[ 12.838952] systemd[1]: Received SIGCHLD from PID 830 (network).
[ 12.838973] systemd[1]: Got SIGCHLD for process 830 (network)
[ 12.839025] systemd[1]: Child 830 died (code=exited, status=1/FAILURE)
[ 12.839028] systemd[1]: Child 830 belongs to [email protected]
[ 12.839038] systemd[1]: [email protected]: main process exited, code=exited, status=1/FAILURE
[ 12.839042] systemd[1]: [email protected] changed start -> failed
[ 12.839129] systemd[1]: Job [email protected]/start finished, result=failed
[ 12.841013] systemd[1]: Failed to start A simple WPA encrypted wireless connection using a static IP.
[ 12.842353] systemd[1]: Unit [email protected] entered failed state.
[ 12.842373] systemd[1]: Starting Network.
[ 12.842377] systemd[1]: network.target changed dead -> active
[ 12.842382] systemd[1]: Job network.target/start finished, result=done
[ 12.843262] systemd[1]: Reached target Network.
[ 12.843299] systemd[1]: Accepted connection on private bus.
[ 12.843488] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
[ 12.843531] systemd[1]: [email protected]: cgroup is empty
[ 12.843557] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
[ 12.843759] systemd[1]: Accepted connection on private bus.
Sorry for the delayed response. I am in the middle of moving.

[Solved]Hibernating without a swap, now systemd can't complete booting

Tried hibernating without a swap (by mistake, I forgot that I don't use a swap nowadays!), now systemd can't complete booting.
But, if I remove the init=whatever/systemd line from the bootloader, the old init system does its work nicely.. (though that's a poor permanent solution. )
I have saved the 1000+ line journalctl log, but have no idea where to start looking for the problem.
https://www.pastee.org/j3htz
It seems to be something to do with filesystem errors, as the following line is the last shown by systemd before stopping.
Nov 11 20:19:45 manasijd systemd-fsck[413]: Home: clean, 85694/1221600 files, 4430911/4883456 blocks
But running fsck(after unmounting the partitions) from the 'emergency mode' systemd drops me into, the results come up clean.
Any idea what can be wrong, or what exactly to look for in the log ?
Last edited by manasij7479 (2012-11-12 11:54:55)

Seems like I was correct about the filesystem problem @ /home .
Backed up the home folder and nuked the ext4 partition and created a new btrfs in its place.
Everything seems to be fine now, after copying back the folder (few issues with kde not cooperating, but nothing major) .
Btw, can anyone try to replicate this on a 'torture' rig or a virtual machine, seems to be a pretty important bug ?

[SOLVED] "Filesystem check failed" during boot process

I was using XFCE on my netbook recently and clicked "shutdown". It logged out to the command prompt and nothing happened. Assuming that I'd clicked "logout" by mistake, I typed "pacman -Syu" to run an update... And moments later it suddenly started the shutdown process.
Now, whenever I boot up, I see the message below. I tried booting from a GParted CD to check the filesystems for errors, but none were detected.
Can anyone suggest what I might need to do to fix the problem?
rootfs: clean, 11026/246512 files, 477083/984576 blocks
home: clean, 4386/527280 files, 237183/2105344 blocks
/dev/sdb2 is mounted. e2fsck: Cannot continue, aborting.
************* FILESYSTEM CHECK FAILED ************
* Please repair manually and reboot. Note that the root
* file system is currently mounted read-only. To remount
* it read-write type: mount -n -o remount,rw /
* when you exit the maintenance shell the system will
* reboot automatically.
Give root password for maintenance
(or type Control-D to continue):
Last edited by esuhl (2012-03-27 01:20:07)

Thank you all for your replies :-)
hadrons123 wrote:What happens when you do try the suggestion given by it?
I don't exactly know how I should "repair manually"... I thought a filesystem check in GParted would have been enough...
lijpbasin wrote:You can boot the system using a archlinux live cd, and run fsck manually on every linux partition in the old system with options.
DON'T mount any of the filesystems before running fsck, or your data will probably be lost. If you want to check the partition information first, run fdisk -l with root privileges.
Thanks. I tried booting from an ArchBang live CD last night and ran "e2fsck -pcv" on each partition. The check completed, but the problem persists... I just tried again using "fsck" as you suggested and got the following output (but the machine still fails to boot with the same error as before):
fsck from util-linux 2.20.1
e2fsck 1.41.14 (22-Dec-2010)
usr was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
usr: 115811/458752 files (1.7% non-contiguous), 783161/1834496 blocks
Gcool wrote:
/dev/sdb2 is mounted. e2fsck: Cannot continue, aborting.
As mentioned already, the reason it's failing is because the /dev/sdb2 partition is mounted before it can be fsck'd. What is this partition exactly (which filesystem, what's on it, mountpoint,...)?
I'm not overly familiar with the Linux boot process, but why would it suddenly be mounting this partition before fsck-ing it? Even if it was mounted when the netbook shutdown, surely the boot process starts with all partitions unmounted...? Anyway, the partition details from /etc/fstab are below.
<file system> <dir> <type> <options> <dump> <pass>
tmpfs /tmp tmpfs nodev,nosuid 0 0
/dev/sda1 / ext2 defaults,noatime 0 1
/dev/sdb1 /home ext2 defaults,noatime,user_xattr 0 1
/dev/sdb2 /usr ext2 defaults,noatime 0 1
I'm (now) aware that mounting /usr as a separate partition is a bad idea and (having read the "Error when booting with the new initscripts" thread), I have told pacman to ignore updates to the initscripts package (until I figure out how best to work round or fix that issue).
Shark wrote:Write umount /dev/sdb2 in konsole or unmount partition in gparted by right click on problematic partition and click unmount. Than proced.
If I type "umount /dev/sdb2" at the prompt, I get the following error:
umount: /usr: device is busy.
(In some cases useful info about processes that use
the device is found by lsof(8) or fuser(1))
I tried "umount -l /dev/sdb2" to unmount when the device becomes free... but it never does.
I also booted into GParted, but there is no option to "unmount" /dev/sdb2. There is a "mount" option in the menu, but it is greyed out. If I open a terminal window from the GParted Live environment and type "sudo umount /dev/sdb2" I get the following message:
umount: /dev/sdb2: not mounted
DSpider wrote:Are you mounting the root drive with "ro" (read only) in fstab?
No (as shown above). I don't *think* I've messed anything up with fstab or any other config files -- everything was working perfectly till the netbook shutdown whilst pacman was running.

Systemd.timesyncd fails on boot [Solved]

Similar Messages

Maybe you are looking for