Systemd boot fails

My /home is on a raid 1 disk which is in /dev/mapper/nvidia_cjjcaiiep1.
First of all my home partition is part of a raid 1.
When booting with init=/bin/systemd I have the following phenomenon:
Job dev-mapper-nvidia_cjjcaiiep1.device/start timed out and booting stops and I'm in a rescue shell.
my /home partition is not mounted.
/dev/mapper/nvidia_cjjcaiiep1 exists.
Systemctl start dev-mapper-nvidia_cjjcaiiep1.device gives the same result timeout.
and my /home is not mounted
After:
#mount /dev/mapper/nvidia_cjjcaiiep1 /boot this is a typo I ment /home
mount /dev/mapper/nvidia_cjjcaiiep1 /home
/home is mounted
Systemctl default
my system resumes booting and finally comes online.
I 'm new to systemd so if someone can be so kind to give me some hints how / where to start searching for the problem or maybe the problem is already known ...
Thanks in advance.
Fred
Last edited by fvsc (2012-08-14 09:07:36)

I have the same problem, since I updated my system yesterday and resized my root-partition online (by this time I do not believe that the later is the reason):
When I boot my system, systemd comes to the point, where it has mounted /boot, waits there for a minute and tells me that it ran into problems. root was mounted, but it failed on home (in my case /dev/mapper/main-home). It was however possible to mount it by hand. However, starting my login-manager (slim) didn't work after that.
This is the output of journalctl:
Aug 14 16:41:55 merkur systemd-journal[180]: Journal started
Aug 14 16:41:55 merkur systemd-modules-load[181]: Inserted module 'vboxdrv'
Aug 14 16:41:59 merkur mtp-probe[332]: checking bus 3, device 2: "/sys/devices/pci0000:00/0000:00:1a.1/usb3/3-1"
Aug 14 16:41:59 merkur mtp-probe[342]: checking bus 1, device 4: "/sys/devices/pci0000:00/0000:00:1a.7/usb1/1-6"
Aug 14 16:41:59 merkur mtp-probe[342]: bus: 1, device: 4 was not an MTP device
Aug 14 16:41:59 merkur mtp-probe[332]: bus: 3, device: 2 was not an MTP device
Aug 14 16:42:00 merkur systemd-fsck[388]: boot: sauber, 30/122880 Dateien, 48260/489948 Blöcke (Prüfung nach nächstem Einhängen)
Aug 14 16:43:25 merkur systemd[1]: ^[[1;39mJob dev-mapper-main\x2dhome.device/start timed out.
Aug 14 16:43:25 merkur systemd[1]: ^[[1;39mJob local-fs.target/start failed with result 'dependency'.
Aug 14 16:43:25 merkur systemd[1]: Triggering OnFailure= dependencies of local-fs.target.
Aug 14 16:43:25 merkur systemd[1]: ^[[1;39mJob systemd-user-sessions.service/start failed with result 'dependency'.
Aug 14 16:43:25 merkur systemd[1]: ^[[1;39mJob slim.service/start failed with result 'dependency'.
Aug 14 16:43:25 merkur systemd[1]: ^[[1;39mJob graphical.target/start failed with result 'dependency'.
Aug 14 16:43:25 merkur systemd[1]: ^[[1;39mJob multi-user.target/start failed with result 'dependency'.
Aug 14 16:43:25 merkur systemd[1]: ^[[1;39mJob syslog-ng.service/start failed with result 'dependency'.
Aug 14 16:43:25 merkur systemd[1]: ^[[1;39mJob cronie.service/start failed with result 'dependency'.
Aug 14 16:43:25 merkur systemd[1]: ^[[1;39mJob acpid.service/start failed with result 'dependency'.
Aug 14 16:43:25 merkur systemd[1]: ^[[1;39mJob rc-local.service/start failed with result 'dependency'.
Aug 14 16:43:25 merkur systemd[1]: ^[[1;39mJob systemd-logind.service/start failed with result 'dependency'.
Aug 14 16:43:25 merkur systemd[1]: ^[[1;39mJob dbus.service/start failed with result 'dependency'.
Aug 14 16:43:25 merkur systemd[1]: ^[[1;39mJob [email protected]/start failed with result 'dependency'.
Aug 14 16:43:25 merkur systemd[1]: ^[[1;39mJob home.mount/start failed with result 'dependency'.
Aug 14 16:43:25 merkur systemd-journal[180]: Journal stopped
Aug 14 16:43:25 merkur systemd-journal[403]: Journal started
Aug 14 16:43:25 merkur systemd[401]: ^[[1;39mFailed at step EXEC spawning /bin/plymouth: No such file or directory
Aug 14 16:49:31 merkur systemd[1]: ^[[1;39mRequested transaction contradicts existing jobs: Transaction is destructive.
Aug 14 16:49:31 merkur systemd[1]: ^[[1;39memergency.service: control process exited, code=exited status=1
Aug 14 16:49:31 merkur systemd[1]: ^[[1;39mUnit emergency.service entered failed state.
Aug 14 16:49:31 merkur systemd[1]: ^[[1;39mShutting down.
Aug 14 16:49:31 merkur systemd[1]: Hardware watchdog 'iTCO_wdt', version 0
Aug 14 16:49:31 merkur systemd[1]: Set hardware watchdog to 10min.
Aug 14 16:49:31 merkur systemd-journal[403]: Journal stopped
my /etc/mkinitcpio.conf only differs in the following line from the default:
HOOKS="base udev autodetect pata scsi sata usb usbinput keymap encrypt lvm2 filesystems fsck"
My /etc/fstab
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
tmpfs /tmp tmpfs nodev,nosuid 0 0
LABEL=boot /boot ext4 defaults 0 1
LABEL=root / ext4 defaults 0 1
#Those are not working:
LABEL=home /home ext4 defaults 0 1
LABEL=swap swap swap defaults 0 0
A possible workaround is to comment the home-partition in /etc/fstab (in my case the swap too) and login as root on a virtual terminal, where you mount your home by hand and then restart the login-manager.
Edit:
PS: using device-names instead of Labels in /etc/fstab didn't change anything
Last edited by FlorianJW (2012-08-14 15:27:40)

Similar Messages

[SOLVED] systemd boot fails - Removable on fstab

Just converted to the dark (systemd) side.
Very straight forward, simple and easy enough.
I have one problem with boot process.
I have three usb devices that i use frequently, below is my fstab
# Removable Media
UUID=6e4bc1aa-3414-48b9-9598-5eedfaadbe2b /media/FreeAgent1 ext4 defaults,user 0 0
UUID=14219291-0703-45b6-95db-976c5b7c3b7b /media/FreeAgent2 ext4 defaults,user 0 0
UUID=0590bbe0-d098-4f81-a9c7-c72654aa54a5 /media/Sandisk ext4 defaults,user 0 0
USB devices at the moment arent on the pc.
With init process, everything was fine.
Boot process gave me prompt.
With systemd, my archlinux box doesnt boot (at all)
http://ebalaskas.gr/img/systemd_removeable.png
Reading https://bbs.archlinux.org/viewtopic.php?id=146982 & http://lists.freedesktop.org/archives/s … 06292.html
i get the feeling that perhaps is a bug.
But i am not sure.
The emergency mode (^D) doesnt work either - keyboard seemed dead.
Used old transitional init=/bin/sh to comment out the removable devices from my fstab
-- mod edit: read the Forum Etiquette and only post thumbnails http://wiki.archlinux.org/index.php/For … s_and_Code [jwr] --
Last edited by ebal (2012-08-24 06:43:52)

ebal wrote:
Nothing is needed to be done to fstab file !
it shouldnt
it mustnt
with the heck i must edit my fstab cause systemd doesnt have a proper function to timeout when there are devices that are not present at boot time !!!
That dont even make sense.
Thank you all for your answers but PLZ ... try to focus on the actual problem that systemd is failing to boot and not to fstab !
btw from my first post i 've already mentioned that i commented out these entries just to boot with systemd.
what is the problem with using nofail or noauto,x-systemd.automount? systemd does the right thing here, it tries to mount the device on boot and waits for it - it's just that the timeout is very long (afaik 90 seconds).
the only reason this worked with initscripts is that afaik initscripts just tries to mount the device and won't wait for it if it isn't there, but instead just fails immediately. While this worked, it was still the wrong approach. You should have added noauto or nofail in the first place.

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.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)

Tip regarding the "systemd[1]: Failed to start Journal Service" error

Just a tip regarding the well-known
systemd[1]: Failed to start Journal Service
error (which I ran into last weekend) to maybe save one or two among you a couple of hours of your time:
The error is described here https://bbs.archlinux.org/viewtopic.php?id=151012 as well as in several other threads in other language boards / in other forums etc. It is usually (as in the linked thread) 'solved' by reinstalling the system - good old Windows magic, also useful when dealing with systemd.
The Problem with this error is that you do not get into your system. Instead, systemd will print you the mentioned "Failed to start Journal Service" error message a couple of million times. There are also no logs that you could retrieve (when booting from a livesystem) and that would give you any helpful hints, since journal is systemd's logging service, old-style system logs are not kept, and the dmesg log doesn't survive the reboot with default settings.
As pointed out in the above mentioned thread, you will see a few more instructive error messages when adding 'emergency' to the kernel line in the bootloader config.
Now there may be plenty of reasons why the systemd journal service might not work. The most common and most annoying, however, appears to be this one:
In this case you will see that the problem actually lies in
systemd[1]: Cannot open /etc/machine-id: No such file or directory
Now, 'man machine-id' reveals that "the /etc/machine-id file contains the unique machine id of the local system that is set during installation. (...) The machine ID is usually generated from a random source (...)". It is obviously perfectly justified to refuse to boot the system because an absolutely insignificant random number is missing. As far as systemd is concerned anyway.
Usually, it seems, the /etc/machine-id is set by /usr/bin/systemd-machine-id-setup during installation or system upgrade. It is not documented anywhere that this is a rather important step and that you should better check if this was or was not actually done before rebooting. Obviously (but for no apparent reasons) systemd fails to run this (or to run this successfully) sometimes.
Also to be recommended: Always retain (back up) your old kernel and initramfs and edit your bootloader config appropriately to be able to boot with your old kernel again ... just to have one or two options left to get back into the system in case of running into an unpleasant surprise from the side of systemd or other packages.
The solution is, obviously, to create this file /etc/machine-id ... You probably want to do that from a livesystem (if you want to try it from the emergency shell, you would need to remount / (i.e. root) as rw and hope that systemd will not punish you for that) by just running the program that was designed for creating this file manually: /usr/bin/systemd-machine-id-setup
http://permalink.gmane.org/gmane.comp.s … devel/7528 states that it might also work with merely creating the file 'touch /etc/machine-id'. Though I didn't try that since I had enough fun with systemd for one week and didn't want to break my system again just to see if that works.

Jristz wrote:
ackalker wrote:Sorry for necrobumping this.
Generating the machine-id in a consistent way is very important when working with KVM and containers, where the machine-id can be set for the VM or container. See `man systemd-machine-id-setup`.
Again, _don't_ just put some random UUID in there, especially not in the systemd package install script, this makes provisioning Arch Linux containers a PITA.
If you thing that the way that arch is handlynbg the machine-id is wrong or can be improved, then file a bug.
He already did.
Jristz wrote:Anyway, I thing if reinstalling systemd package or if systemd have a command to reinitialize the machine-id file.
Like so many of your posts, I had to read this a half dozen times before it made any sense. I think you're hinting at the utility that ackalker already pointed out in the post you're replying to. And, if you read the install scriptlet, you wouldn't need to think about whether or not reinstalling would be an option. You would know that it isn't.

Got systemd-logind: failed to get session: when optirun glxgrears

I installed nvidia and bumblebee, primus.
When I tried to test optirun, I ran
optirun glxgrears -info
Then I got this,
[ 2376.692764] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) systemd-logind: failed to get session: PID 1540 does not belong to any known session
[ 2376.692829] [ERROR]Aborting because fallback start is disabled.
Here is my /var/log/Xorg.8.log ,
[ 2376.692764] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) systemd-logind: failed to get session: PID 1540 does not belong to any known session
[ 2376.692829] [ERROR]Aborting because fallback start is disabled.
[hk@hkpc ~]$ cat /var/log/Xorg.8.log
[ 2376.682]
X.Org X Server 1.16.0
Release Date: 2014-07-16
[ 2376.682] X Protocol Version 11, Revision 0
[ 2376.682] Build Operating System: Linux 3.15.5-2-ARCH x86_64
[ 2376.682] Current Operating System: Linux hkpc 3.15.8-1-ARCH #1 SMP PREEMPT Fri Aug 1 08:51:42 CEST 2014 x86_64
[ 2376.682] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=669c53af-9ee3-4bbf-b62f-14c76e81da89 rw quiet
[ 2376.682] Build Date: 31 July 2014 11:53:19AM
[ 2376.682]
[ 2376.682] Current version of pixman: 0.32.6
[ 2376.682] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 2376.682] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 2376.683] (==) Log file: "/var/log/Xorg.8.log", Time: Mon Aug 4 22:39:09 2014
[ 2376.683] (++) Using config file: "/etc/bumblebee/xorg.conf.nouveau"
[ 2376.683] (++) Using config directory: "/etc/bumblebee/xorg.conf.d"
[ 2376.683] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 2376.683] (==) ServerLayout "Layout0"
[ 2376.683] (==) No screen section available. Using defaults.
[ 2376.683] (**) |-->Screen "Default Screen Section" (0)
[ 2376.683] (**) | |-->Monitor "<default monitor>"
[ 2376.683] (==) No device specified for screen "Default Screen Section".
Using the first device section listed.
[ 2376.683] (**) | |-->Device "DiscreteNvidia"
[ 2376.683] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 2376.683] (**) Option "AutoAddDevices" "false"
[ 2376.683] (**) Option "AutoAddGPU" "false"
[ 2376.683] (**) Not automatically adding devices
[ 2376.683] (==) Automatically enabling devices
[ 2376.683] (**) Not automatically adding GPU devices
[ 2376.683] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 2376.683] Entry deleted from font path.
[ 2376.683] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[ 2376.683] Entry deleted from font path.
[ 2376.683] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 2376.683] Entry deleted from font path.
[ 2376.683] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 2376.683] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 2376.683] Entry deleted from font path.
[ 2376.683] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 2376.683] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/
[ 2376.683] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 2376.683] (==) |-->Input Device "<default pointer>"
[ 2376.684] (==) |-->Input Device "<default keyboard>"
[ 2376.684] (==) The core pointer device wasn't specified explicitly in the layout.
Using the default mouse configuration.
[ 2376.684] (==) The core keyboard device wasn't specified explicitly in the layout.
Using the default keyboard configuration.
[ 2376.684] (II) Loader magic: 0x818d80
[ 2376.684] (II) Module ABI versions:
[ 2376.684] X.Org ANSI C Emulation: 0.4
[ 2376.684] X.Org Video Driver: 18.0
[ 2376.684] X.Org XInput driver : 21.0
[ 2376.684] X.Org Server Extension : 8.0
[ 2376.685] (EE) systemd-logind: failed to get session: PID 2304 does not belong to any known session
[ 2376.686] (II) xfree86: Adding drm device (/dev/dri/card1)
[ 2376.686] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 2376.686] (EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
[ 2376.688] (--) PCI:*(0:1:0:0) 10de:0fd4:1558:3700 rev 161, Mem @ 0xf6000000/16777216, 0xe0000000/268435456, 0xf0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
[ 2376.688] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 2376.688] (II) LoadModule: "glx"
[ 2376.688] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 2376.690] (II) Module glx: vendor="X.Org Foundation"
[ 2376.690] compiled for 1.16.0, module version = 1.0.0
[ 2376.690] ABI class: X.Org Server Extension, version 8.0
[ 2376.690] (==) AIGLX enabled
[ 2376.690] (II) LoadModule: "nouveau"
[ 2376.690] (WW) Warning, couldn't open module nouveau
[ 2376.690] (II) UnloadModule: "nouveau"
[ 2376.690] (II) Unloading nouveau
[ 2376.690] (EE) Failed to load module "nouveau" (module does not exist, 0)
[ 2376.690] (II) LoadModule: "mouse"
[ 2376.691] (WW) Warning, couldn't open module mouse
[ 2376.691] (II) UnloadModule: "mouse"
[ 2376.691] (II) Unloading mouse
[ 2376.691] (EE) Failed to load module "mouse" (module does not exist, 0)
[ 2376.691] (II) LoadModule: "kbd"
[ 2376.691] (WW) Warning, couldn't open module kbd
[ 2376.691] (II) UnloadModule: "kbd"
[ 2376.691] (II) Unloading kbd
[ 2376.691] (EE) Failed to load module "kbd" (module does not exist, 0)
[ 2376.691] (EE) No drivers available.
[ 2376.691] (EE)
Fatal server error:
[ 2376.691] (EE) no screens found(EE)
[ 2376.691] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 2376.691] (EE) Please also check the log file at "/var/log/Xorg.8.log" for additional information.
What should I do?

barchiesi wrote:
Oedner wrote:after updating to linux 3.16 i got this error too. using the command without the -info works however.
Are you sure that it only doesn't work with the '-info'? I see no difference.
i just tried it a couple of times and it looks like its completely random o.O
you are right, using it (with or without -info) only works like every third attempt while the others throw the error mentioned by the op. i got that idea because it worked when i tried it. starting nvidia-settings with optirun is the same, error, working, error, working. can't say whats the problem here, i just switched to arch again recently.

Systemd Boot Problem - Times out waiting for LVM partitions

At first I had a problem in which the initramfs didn't map LVM partitions to /dev/vg0/lv, only /dev/mapper/vg0-lv. I changed /dev/vg0/root to /dev/mapper/vg0-root in bootloader configuration as a hacky workaround.
Getting closer to a working system, systemd failed boot because my fstab entries are uuids, and for some reason, my LVM volumes aren't showing up in /dev/disk/by-*. My flash drive boot partition shows up in there though.
I replaced the uuids with /dev/mapper/vg0-* and tried again. Now my boot fails with this:
Oct 21 19:19:31 archserver systemd[1]: Job dev-mapper-vg0\x2dmedia.device/start timed out.
Oct 21 19:19:31 archserver systemd[1]: Timed out waiting for device dev-mapper-vg0\x2dmedia.device.
Oct 21 19:19:31 archserver systemd[1]: Dependency failed for /mnt/media.
Oct 21 19:19:31 archserver systemd[1]: Dependency failed for Local File Systems.
Boot log: http://sprunge.us/LEhG
mkinitcpio.conf: http://sprunge.us/QEBK
What should I do?

This may be LVM's incompatibility with anything hotplug (it may not be, your issue sounds more obscure). You need to create your own, local lvm service file. I'll tell you how. This is /usr/lib/systemd/system/lvm.service:
[Unit]
Description=LVM activation
DefaultDependencies=no
Requires=systemd-udev-settle.service
After=systemd-udev-settle.service
Before=basic.target shutdown.target
Conflicts=shutdown.target
[Service]
ExecStart=/sbin/vgchange --available y
Type=oneshot
TimeoutSec=0
RemainAfterExit=yes
[Install]
WantedBy=basic.target
Create /etc/systemd/system/lvm_local.service:
[Unit]
Description=LVM activation
DefaultDependencies=no
Requires=dev-something-something1.device
After=dev-something-something1.device
Requires=dev-something-something2.device
After=dev-something-something2.device
Before=basic.target shutdown.target
Conflicts=shutdown.target
[Service]
ExecStart=/sbin/vgchange --available y
Type=oneshot
TimeoutSec=0
RemainAfterExit=yes
[Install]
WantedBy=basic.target
No, what to you put in those "something-something1" places above? For each LVM physical volume, run 'systemctl status /dev/disk/by-uuid/$UUID' where $UUID is the UUID of your physical volume. You'll get a status output showing the exact name of the correct .device unit. Then 'systemctl enable lvm_local.service'.
This speeds up boot and makes sure lvm is properly initialized. After writing all this, I am unsure if this is at all related to your problem, as your volume group is activated in initramfs and the links should be set up by udev.

Systemd Issues - Failed to start MyApp daemon

Hi all,
Sorry if I'm asking a stupid question, I'm new to Arch Linux, Pi, and Python. I have a Python script I'd like to start automatically after boot so I created a myapp.service file:
[Unit]
Description=MyApp daemon
Requires=network.target
[Service]
Type=forking
ExecStart=/root/bin/myapp/initmyapp.py
ExecStop=/bin/kill $MAINPID
[Install]
WantedBy=multi-user.target
After initmyapp.py runs it calls "myapp.py &" that's why I tried type=forking. I tested "systemctl start myapp" and it looks like it's working; I can see the process running. So, I did "systemctl enable myapp" which ran without errors and then I rebooted. After reboot, however, the process is not running and "systemctl status myapp" tells me this:
myapp.service - MyApp daemon
Loaded: loaded (/etc/systemd/system/myapp.service; enabled)
Active: failed (Result: exit-code) since Wed, 1969-12-31 19:00:10 EST; 43 years and 0 months ago
Process: 102 ExecStart=/root/bin/myapp/initmyapp.py (code=exited, status=1/FAILURE)
CGroup: name=systemd:/system/myapp.service
Dec 31 19:00:09 mybox initmyapp.py[102]: '_open', req)
Dec 31 19:00:09 mybox initmyapp.py[102]: File "/usr/lib/python2.7/urllib2.py", line 378, in _call_chain
Dec 31 19:00:09 mybox initmyapp.py[102]: result = func(*args)
Dec 31 19:00:09 mybox initmyapp.py[102]: File "/usr/lib/python2.7/urllib2.py", line 1207, in http_open
Dec 31 19:00:09 mybox initmyapp.py[102]: return self.do_open(httplib.HTTPConnection, req)
Dec 31 19:00:09 mybox initmyapp.py[102]: File "/usr/lib/python2.7/urllib2.py", line 1177, in do_open
Dec 31 19:00:10 mybox initmyapp.py[102]: raise URLError(err)
Dec 31 19:00:10 mybox initmyapp.py[102]: urllib2.URLError: <urlopen error [Errno -2] Name or service not known>
Dec 31 19:00:10 mybox systemd[1]: Failed to start MyApp daemon.
Dec 31 19:00:10 mybox systemd[1]: Unit myapp.service entered failed state
Does this mean that networking is not ready yet? Instead of Requires=network.target I also tried Requires=multi-user.target but didn't work. I have no idea what I'm doing so any suggestion would be appreciated.

Thank you for the quick response. I removed the kill part and "stop" still works. I also removed all the network includes to test it out and the background call too and after hours of trial and error I was finally able to make it work. Now I just have to figure out how to tell when the network is up. That article covers it for C (I think) but not for Python. It also seems very technical.
Anyway, thanks again for your help.

Hyper-V 2012 R2 new VM with ISO in DVD boot failed - default SCSI not IDE

Hi, have created some VMs fine on 2008R2 and 2012 Hyper-V but now onto 2012 R2, am using the Gen 2 VM and hitting install error when booting them from the 2012R2 RTM .ISO (downloaded straight from Technet) loaded into virtual DVD:
I see from http://social.technet.microsoft.com/Forums/windowsserver/en-US/53f901e4-5bd0-4e13-80a2-bca2f57b15e9/hyperv-unable-to-boot-from-cd-or-iso-in-vm-machine?forum=winserverhyperv that Hyper-V seems unable to boot from a synthetic SCSI until guest OS actually
installed - so Catch-22! But I can't add an IDE Controller because it's not on the list:
I tried the Integration Services and it seems fine on the Settings (including ticking the only one unticked - Guest Services) although if you need to run them from the DVD, it has the same problem - you can see them loaded (or the Win2012R2 ISO) in the DVD
Media but you can't make them run through booting on SCSI!
The physical drives are SATA not SCSI but presumably no matter as Hyper-V runs SCSI virtually, but why does Hyper-V default to SCSI and how do I get the DVD to run off an IDE instead if that is the way to install a base OS from .ISO? Or is there an easier
way than all this?
TIA, Phil.

I found this article:
http://blogs.technet.com/b/jhoward/archive/2013/11/11/hyper-v-generation-2-virtual-machines-part-9.aspx
I hope this help.
"...yes, we’re acutely aware that the generation 2 EFI boot loader messages persist on the screen and it can be a little confusing. Essentially what the generation 2 virtual machine did was:
Attempt to boot from the CD SCSI device containing the Windows 8 ISO. This is where the ‘Press any key…’ message came from. As no key was pressed, we went to the next boot entry. (And this is where we didn’t clear the message from the EFI CD boot loader)
I didn’t press F12 (in fact, this VM wasn’t connected to a network), so network boot failed
The SCSI VHDX is raw with no partitioning or file system, so this too failed
So why did the generation 1 virtual machine start setup from the Windows media? The answer is simply that it’s the way Windows media is built, and it’s inconsistent between the PCAT and EFI loaders.
However, it’s relatively simple to solve if you want to avoid the press any key message. In fact, we almost have all the pieces from previous parts. In particular, part 4 where we injected keyboard drivers into the Windows 8 media.
If you loopback mount Windows 8 or 8.1 RTM media, and navigate to the \efi\microsoft\boot directory, you will see there are two versions of cdboot.efi
The default version, cdboot.efi prompts for a keypress. The unused version, cdboot_noprompt.efi doesn’t prompt.
So it’s fairly simple to create modified media which uses the noprompt version. First, copy the contents of the ISO to a working directory, rename cdboot.efi to cdboot_prompt.efi, and rename cdboot_noprompt.efi to cdboot.efi.
Do the same with efisys.bin and efisys_prompt.bin
Then re-use our oscdimg command (in an elevated deployment and imaging tools environment) from part 4 to recreate the media.
Best Regards:
Tamás

Boot Failed, Single User FSCK couldn't load, mounting Macintosh HD failed, repair and verify returns no errors, and i need to transfer my data before starting over - HELP!!!!

Lets break down the facts here: My machine is an Intel-Based iMac running Mavericks - 1TB Hitachi Hard Drive
1. Was running an initial baseline image with Time Machine when the computer froze - waited hours - nothing got better and no functions were possible (force quit, etc.)
2. Hard Reboot
3. Upon reboot, the iMac was unable to load the log-in screen. The image was a folder with a "?" on it.
4. Rebooted with option key held down and selected Macintosh HD - Boot Failed
5. Restarted and Rebooted with Command R held down
6. Ran Disk Verify and Disk Repair - returned errors round one.
7. Ran Disk Verify and Disk Repair - Returned no Errors
8. Restart - Boot failed - the "NO" symbol replaced the apple symbol
9. Reboot with Command R
10. Attempt to mount Macintosh HD
11. Mount Failed.
12. Shutdown
13. Connect Firwire to Host computer and Target Computer
14. Boot with Command T
15. TDM entered - Host Machine cannot read Target Hard Drive
16. Shutdown
17. Boot with Command S
18. Endless loop created - Multiple errors including:
     - failed to open create the journal retval 0
     - could not read 512 bytes for the journal header - Return 22
     - Errorno 19
     - hfs_mounterror return: 22
Short of springing for a software online, I have no idea what the next steps are to getting my data moved from the Macintosh HD to my external so I can just reformat and install the OS again. Any help would be greatly appreciated, this is is a serious headache and I cannot lose my data - Thats what I was backing it up for in the first place!!!!

You may not have the luxury of having another Mac but you must know someone who does. You need to boot your Mac into target disk mode. This is going to be your best bet as far as saving your files. Keep in mind that everytime you mess with this computer you are further endangering your data. Also, once your Mac is booted as a target disk, it may be possible to mount it on a windoze computer just to copy your files to another drive. I used to have one here and if i still did I would try this for you but I "offed" it in favor on running windoze (Parallels) on my MBP. But, one way or another, you need to get next to another computer.

Satellite A660 - Will not boot up and HDD boot fail

Hi,
firstly thanks for your time.
Model: Satellite A660 (PSAW3A-07U00R)
The problem started yesterday, the computer was going slow as an application closed, so I held the off button untill the pc turned off. When I restarded the laptop it went to a screen saying: Start windows normally or repair Windows (recomended)
When started normally it just hangs at a blank screen, the repair Windows recommends a system restore to earlier point which didnt work. As it just hangs again. I tried pressing F8 and starting in safe mode but again it just hangs. Then after a few times trying safe mode and another system restore the computer then hangs when I press F8. After this the computer goes past the Toshiba logo screen with F2 and F12 options (which both still work), and then it comes up boot failed then goes blank and comes with boot failed bootfailed with some numbers and letters, then it goes to a small box titled boot menu with 4 options.These are
HDD/SSD Toshiba MK6465GSX
CD/DVD MAT****ABD-CMB UJ141ES
FDD
LAN
If I press ESC it goes through the bootfailed loop and ends up at same screen, if I press enter on "HDD/SSD Toshiba MK6465GSX" then it quickly comes back to screen and at the bottom it says [HDD/SSD Toshiba MK6465GSX] is failed.
I dont understand why it got worse over time. Can anyone think of why this has happend and more importantly how can I get my pc working again? Note: holding 0 then starting does nothing for me atm
regards, Matthew

All you people looking here on this dead thread.....
Toshiba A660 laptops are renowned for having hard drive fails and boot up problems after grinding to a halt.
My solution (after losing 3 hard drives [and a terabyte of family treasured times]) is the following.
Use MALWAREBYTES (free download and use for 28 days)
Scan and fix. Mine found over 300 trojans that 2013 Norton 360 could not find.
Re-boot into safe mode.
SCAN again.
Re-boot and empty the malwarebytes repair files it retains...
Run Norton/McAfee (whichever you have) and you should still have no issues.
Make a back-up repair disc. Ooooops......no you cant...........at least my laptop can`t.
I don`t know why.....
Tell me tosh..... why does windows x64 refuse to allow me to make a system boot disc (even though the laptop is all driver updated and Windows updated)?
Uninstall MalwareBytes when Norton/McAfee tells you there will be a conflict between the two programs.
It tells you to re-boot after uninstalling it.
Then when it re-boots you get a black screen. You cannot even get to bios. You think ytour laptop is turned into a brick frisbee. You pull out the battery in frustration after five minutes.
You replace and re-boot....but again you get no bios or boot up.... you think its destroyed the Bios or graphics somehow....youo can hear the hard-drive but you have no clue whats going on..
Around this time you shake the laptop in frustration.....
Calm down.
Switch on and leave FIFTEEN MINUTES....Ten of which will be a Black nothing screen with maybe a single white underscore line in the top left corner.LEAVE IT ALONE.
Make a sunday dinner for ten people....When you go back to the computer it will be up and running.
When you re-boot again, it will be dead black for five minutes...then boots up... you still think it has a problem... LEAVE IT.
When you reboot again it should work perfect (assuming you have not been overheating it by using it on a cushion on your lap and overheating the insides [use a laptop fan tray]) if you have not shaken your hard drive or caused scrambled damage by pulling the power fifty times like some people do.
I have lost three hard drives and thousands of Gigabytes of treasured family memories discovering the secret the hard way.
Enjoy.
Buy a different brand next time.
ALL Windows system files should be on a SWITCHED (to update) version of Windows.
Spinning drives should be for Data only.

[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)

New Error - Unable to Create Any Backups (com.adobe.versioncue.boot - Failed to start com.adobe.vers

A new error just started showing up in my Vc logs: com.adobe.versioncue.boot - Failed to start com.adobe.versioncue.backup.schedule.
Since the report of this error, I am unable to create any kind of Version Cue backups. Has anyone else seen this error?
I had hoped that a simple reboot would alleviate the problem, but it didn't. The error occurs during Vc startup (boot). It's a little odd that Vc was mostly fine until I rescheduled my Windows Backup (ntbackup.exe) to run 90 minutes earlier, and failed to tell Diskeeper to also not auto-defrag 90 minutes earlier. (In other words, it's possible that Diskeeper did its thing the same time ntbackup was running.)
Running Windows XP SP3. I'm going to try a repair install of Vc in a few moments.

Update 2: ntbackup restore of System State to day before last successful Vc backup failed to correct the problem. I can't even run a manual backup.
Can anyone tell me how to determine the ClassPath used by Vc?
There is no stack trace from this error - the exception is caught and handled, so Vc continues to run after creating the single log entry posted in Msg-1 above. By knowing the ClassPath, I may be able to restore the corrupted Java JARs, if that is the root of this problem.
I'd really hate to have to (ntbackup) restore the whole computer back to last Monday...

Boot failed: solaris server does not boot

Hi All,
one of my support person who has administrator previlages tried move the contents of root to trash directory, in the middle it got hung,and he had restrted the server.
Now the solaris does not boot. It says
boot failed
Enter Filename [platform/sun4v/kernel/sparcv9/unix]
and what ever we enter there it says boot cannot read.
Please suggest some workaround, nearly 200 users are down, actually it is our licnese server.

Hi,
What you could try is the following :
Boot the system from the solaris cd into single user mode.
Find out what the disk is you need to mount and mount it under /a
After you have done this you can see if you can move back the stuff that was moved from the root directory to the trash.
If that works then you could try and boot again from the disk to see if everything works again.
Nico

Cannot make Bumblebee (systemd-logind failed)

I had bought an Dell Inspiron 14 notebook and now I'm now I'm trying to use Arch Linux, but I can't make the graphic interfaces work.
I'm getting continuosly this error,
[ERROR]Cannot access secondary GPU - error: [XORG] (EE) systemd-logind: failed to get session: PID XXX does not belong to any known session
[ERROR]Aborting because fallback start is disabled.
when I use
primusrun glxspheres64
, I had already put
MODULES="i915 bbswitch" to my /etc/mkinitcpio.conf
My bootloader is Grub and I already had append
rcutree.rcu_idle_gp_delay=1
to it.
Outside then I hadn't touch any other bumblebee configuration.
Other informations that maybe are relevant: I'm trying to use bumblebee with the nvidia driver.
Thanks for reading that and sorry for bad english.

Got very similar problem, with "fresh" install on Lenovo G50 laptop: Intel and Ati cards. I noticed using sftp transfer or conky's curl I am logged out from my session back to lightdm.
From dmesg:
[ 966.843057] Chrome_ChildThr[1348]: segfault at 0 ip 00007f88d9d36391 sp 00007f88c5a8d500 error 6 in libmozalloc.so[7f88d9d35000+2000]
and Xorg.log
[ 1209.395] (EE) systemd-logind: failed to get session: PID 1955 does not belong to any known session
[ 1209.398] (EE) Failed to load module "modesetting" (module does not exist, 0)
[ 1209.398] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 1209.398] (EE) Failed to load module "vesa" (module does not exist, 0)
Is it something similar to this bug? Anything else seems to work OK.

Systemd boot fails

Similar Messages

Maybe you are looking for