You are not logged in.

#1 2012-08-13 07:59:12

fvsc
Member
From: Antwerp, Belgiun
Registered: 2009-10-31
Posts: 11

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)

Offline

#2 2012-08-14 07:44:14

fvsc
Member
From: Antwerp, Belgiun
Registered: 2009-10-31
Posts: 11

Re: systemd boot fails

Nobody able to help????

Or is this the wrong forum?

Offline

#3 2012-08-14 07:52:48

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 20,105
Website

Re: systemd boot fails

Your post is not clear (at least to me). You have to manually mount /boot and /home -- and they both seem to be called the same thing?

Do you have the correct modules in your mkintcpio.conf? When you build your initrd, is your mdadm.conf used? Is your fstab correct?


Arch + dwm   •   Mercurial repos  •   Github

Registered Linux User #482438

Offline

#4 2012-08-14 08:00:16

Zancarius
Member
From: NM, USA
Registered: 2012-05-06
Posts: 207

Re: systemd boot fails

fvsc wrote:

Nobody able to help????

Or is this the wrong forum?

Sometimes posts go unseen, so be patient. Failing responses here, sometimes it might be helpful to continue looking for a solution on your own.

I'm not sure this is the correct forum, unless your issue is specific to installation gone awry, but that's unlikely to be why you haven't received a response. For starters, it's only been 24 hours since your first post, and it's at the tail-end of a weekend in some timezones. In my particular case, I generally only glance through threads I've posted in for new replies or posts that are flagged as new since my last visit.

Anyway, the first thing you might want to do is post your /etc/fstab as it sounds like some partitions aren't correctly mounting. I suspect this might be because you forgot to add something to your initrd via /etc/mkinitcpio.conf, but since you didn't mention if your system boots without using systemd, I can't tell if this is a problem you're experiencing as a consequence of systemd alone.

If you're using a software raid setup with LVM, read this. I've never used RAID under Arch, but it appears to me that if you're using /dev/mapper, you're probably using software raid. If so, it's imperative that you have your /etc/mkinitcpio.conf configured with the correct hooks. If those hooks are missing or if you're not sure that your initrd was generated, you can always re-generate it using mkinitcpio -p linux.

Edit: Whoops! jasonwryan beat me to it!

Last edited by Zancarius (2012-08-14 08:01:53)


He who has no .plan has small finger.
~Confucius on UNIX.

Offline

#5 2012-08-14 09:20:17

fvsc
Member
From: Antwerp, Belgiun
Registered: 2009-10-31
Posts: 11

Re: systemd boot fails

jasonwryan wrote:

Your post is not clear (at least to me). You have to manually mount /boot and /home -- and they both seem to be called the same thing?

Do you have the correct modules in your mkintcpio.conf? When you build your initrd, is your mdadm.conf used? Is your fstab correct?


Booting without systemd works without any problem.

My mistake, I need to mount /home manually not /boot.
My home partition is on a SW raid.

After manually mounting the /home partition and using systemctl default the boot process continues and my system is working as of I booted without systemd.

By the way I' m using arch now for several years without problems so I suppose the setup is OK.

And second I have the same setup for my laptop, but without the SW raid for the /home partition, and there booting with systemd runs smoothly.

As far as I can see it is the combination of systemd and the /home partition on a SW raid

Last edited by fvsc (2012-08-14 09:21:32)

Offline

#6 2012-08-14 15:26:35

FlorianJW
Member
Registered: 2012-08-14
Posts: 2

Re: systemd boot fails

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 getty@tty1.service/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)

Offline

#7 2012-08-14 16:46:41

mukl
Member
From: Vienna, Austria
Registered: 2008-01-30
Posts: 39

Re: systemd boot fails

I don't know, if this is a related problem or the solution works for you, but i think my problem today was similar.

After an upgrade of linux and systemd[-tools] my notebook with a crypttool device and lvm won't boot anymore. It waited for the home-partition to mount.

I did several things this morning, but i think the solution was to chroot into the installation and install linux package again. The crucial part is the recreation of the initial ramdisk, I guess.

Offline

#8 2012-08-14 17:34:20

FlorianJW
Member
Registered: 2012-08-14
Posts: 2

Re: systemd boot fails

Your problem was propably exactly the same as mine and your tip worked for me perfect. Thank you for that.

So the easiest way to fix this, is propably to execute

pacman -S linux

So I guess we have a working solution and the topic can be closed.

Offline

#9 2012-08-14 17:40:44

Zancarius
Member
From: NM, USA
Registered: 2012-05-06
Posts: 207

Re: systemd boot fails

FlorianJW wrote:

Your problem was propably exactly the same as mine and your tip worked for me perfect. Thank you for that.

So the easiest way to fix this, is propably to execute

pacman -S linux

So I guess we have a working solution and the topic can be closed.

All that essentially does is uncompresses the archive and re-runs mkinitcpio. I'd bet just doing the latter (mkinitcpio -p linux) would work just fine.


He who has no .plan has small finger.
~Confucius on UNIX.

Offline

#10 2012-08-15 07:49:45

fvsc
Member
From: Antwerp, Belgiun
Registered: 2009-10-31
Posts: 11

Re: systemd boot fails

Zancarius wrote:
FlorianJW wrote:

Your problem was propably exactly the same as mine and your tip worked for me perfect. Thank you for that.

So the easiest way to fix this, is propably to execute

pacman -S linux

So I guess we have a working solution and the topic can be closed.

All that essentially does is uncompresses the archive and re-runs mkinitcpio. I'd bet just doing the latter (mkinitcpio -p linux) would work just fine.


This is not working for me.
After Pacman -S linux I have still the problem.

/home which is on a SW raid is not mounted (timed out) and after a manual mount and systemctl default the system comes online.

Any other ideas to solve this?

Offline

#11 2012-08-15 17:53:53

Zancarius
Member
From: NM, USA
Registered: 2012-05-06
Posts: 207

Re: systemd boot fails

When you re-run pacman -S linux, does it also run mkinitcpio?

Edit: Also, what's the output of

ls /dev/mapper

when your boot fails? Is your home partition listed in there?

Last edited by Zancarius (2012-08-15 17:59:45)


He who has no .plan has small finger.
~Confucius on UNIX.

Offline

#12 2012-08-15 22:18:16

Lanik
Member
Registered: 2012-08-15
Posts: 1

Re: systemd boot fails

Zancarius wrote:

I'd bet just doing the latter (mkinitcpio -p linux) would work just fine.

This worked for me.  Thanks!

Offline

#13 2012-08-16 03:37:07

falconindy
Developer
From: New York, USA
Registered: 2009-10-22
Posts: 4,097
Website

Offline

#14 2012-08-17 07:34:07

kodiak
Member
Registered: 2012-04-26
Posts: 61

Re: systemd boot fails

Hello, since yesterdays weekly update my system does not boot either and it seems pretty much related. I have my /boot on a seperate ext2 partition, / and /home are on a LVM.
I swapped from initscripts to systemd 2 weeks ago. The system hangs while it looks for /home: Thats the output (I took a picture since it hangs at the end)

...
[ OK ]  Mounted /boot.
[ TIME ] Time out wating for device dev-disk-by\x2uuid-and so on
[ DEPEND ] Dependency failed for /home
[ DEPEND ] Dependency failed for Local File Systems.
...
Welcome to emergency mode. Use "systemctl default" and so on

What I did until now: I´ve got a bootable snapshot from before the last update. I booted into, chroot into the old system and run the commands  pacman -S linux and mkinitcpio -p linux, no change. Than I followed the link of falconindy and tried to changed fstab from uuid to label for home (/dev/dm-5) which did not help either.

/etc/mkinitcpio.conf: HOOKS="base udev autodetect pata scsi sata lvm2 filesystems usbinput fsck"

pacman -Ss systemd
core/initscripts 2012.08.2-1 (base)
    System initialization/bootup scripts
core/libsystemd 188-2 [installed]
    systemd client libraries
core/systemd 188-2 [installed]
    system and service manager
core/systemd-sysvcompat 188-2 [installed]
    sysvinit compat for systemd
core/systemd-tools 188-2 [installed]
    standalone tools from systemd
community/systemd-arch-units 20120704-2 [installed]
    Arch specific Systemd unit files

I have no idea how to go on and rely on your help.

Last edited by kodiak (2012-08-17 07:35:17)

Offline

#15 2012-08-17 15:00:02

fvsc
Member
From: Antwerp, Belgiun
Registered: 2009-10-31
Posts: 11

Re: systemd boot fails

Zancarius wrote:

When you re-run pacman -S linux, does it also run mkinitcpio?

Edit: Also, what's the output of

ls /dev/mapper

when your boot fails? Is your home partition listed in there?


Yes mkinitcpio is run

/dev/mapper/nvidia_cjjcaiie
/dev/mapper/nvidia_cjjcaiiep1


when I do a manual mount
mount /dev/mapper/nvidia_cjjcaiiep1 /home
the home partition is mounted and I can do systemctl default and the boot process continues and the pc comes on line.

Offline

#16 2012-08-17 15:14:35

fvsc
Member
From: Antwerp, Belgiun
Registered: 2009-10-31
Posts: 11

Re: systemd boot fails


When I change in fstab the line
/dev/mapper/nvidia_cjjcaiiep1          /home                   ext3    defaults,acl            0       1

by
/dev/dm-7                                        /home                   ext3    defaults,acl            0       1

the pc boots without any problem.

output of ls -al /dev/mapper
total 0
drwxr-xr-x  2 root root      220 Aug 17 17:05 .
drwxr-xr-x 19 root root     3.7K Aug 17 17:07 ..
lrwxrwxrwx  1 root root        7 Aug 17 17:05 VolGroup00-lvolroot -> ../dm-0
lrwxrwxrwx  1 root root        7 Aug 17 17:05 VolGroup00-lvolswap -> ../dm-4
lrwxrwxrwx  1 root root        7 Aug 17 17:05 VolGroup00-lvoltmp -> ../dm-2
lrwxrwxrwx  1 root root        7 Aug 17 17:05 VolGroup00-lvolvar -> ../dm-1
lrwxrwxrwx  1 root root        7 Aug 17 17:05 VolGroup00-lvolvirt -> ../dm-3
lrwxrwxrwx  1 root root        7 Aug 17 17:05 VolGroup00-lvolweb -> ../dm-5
crw-------  1 root root  10, 236 Aug 17 17:05 control
brw-------  1 root root 254,   6 Aug 17 17:05 nvidia_cjjcaiie
brw-------  1 root root 254,   7 Aug 17 17:05 nvidia_cjjcaiiep1

Last edited by fvsc (2012-08-17 15:19:41)

Offline

#17 2012-08-18 11:03:41

gondsman
Member
Registered: 2009-07-27
Posts: 84

Re: systemd boot fails

I have the same problem here, except that my root is on the array, so I can't remove the dmraid hook. Changing fstab to point to /dev/mapper/* or /dev/dm-* doesn't make any difference.
Does it mean I'll never be able to use systemd? After not being able to use grub2 for the same reason? Why is fakeRAID support so bad on linux (I don't know if it's Arch-specific) when the kernel manages the array just fine?

Offline

#18 2012-08-18 16:53:00

nobody44
Member
Registered: 2011-08-25
Posts: 29

Re: systemd boot fails

Same problem here:

Aug 18 18:34:06 pokemon4ever systemd[1]: Job dev-dm\x2d3.device/start timed out.
Aug 18 18:34:06 pokemon4ever systemd[1]: Job local-fs.target/start failed with result 'dependency'.
Aug 18 18:34:06 pokemon4ever systemd[1]: Triggering OnFailure= dependencies of local-fs.target.
Aug 18 18:34:06 pokemon4ever systemd[1]: Job rescue.target/start failed with result 'dependency'.
Aug 18 18:34:06 pokemon4ever systemd[1]: Job home.mount/start failed with result 'dependency'.
Aug 18 18:34:06 pokemon4ever systemd[1]: Job dev-dm\x2d3.device/start failed with result 'timeout'.

My fstab:

devpts                 /dev/pts      devpts    defaults            0      0
shm                    /dev/shm      tmpfs     nodev,nosuid        0      0
/dev/dm-1 / ext4 defaults 0 1
/dev/dm-3 /home ext4 defaults 0 1
/dev/dm-2 swap swap defaults 0 0
/dev/sda1 /boot ext2 defaults 0 1

All I have to do in rescue mode is:

mount /dev/dm-3 /home
swapon /dev/dm-2
systemctl default

Thanks for any help :-).

Offtopic:
I start to hate systemd.

Edit:
Yeah thanks, I know my hostname is nice :-)!

Last edited by nobody44 (2012-08-18 16:53:57)

Offline

#19 2012-08-18 18:24:35

kenny96
Member
Registered: 2012-08-18
Posts: 17

Re: systemd boot fails

I had a similar problem with LVM+dmcrypt at top and this fstab:

# 
# /etc/fstab: static file system information
#
# <file system> <dir>   <type>  <options>       <dump>  <pass>
tmpfs           /tmp    tmpfs   nodev,nosuid    0       0
/dev/mapper/vgroup-home /home ext3 defaults 0 1
/dev/mapper/vgroup-root / ext3 defaults 0 1
/dev/mapper/vgroup-swap swap swap defaults 0 0
/dev/sda1 /boot ext2 defaults 0 1 

/root mounted correctly but /home and /swap no, timeout error appeared and i needed to manually mount /home and /swap
I have found this https://bugs.archlinux.org/task/30908 and
adding the lvm-on-crypt.service seems to solve my problem.

Offline

#20 2012-08-18 18:29:35

nobody44
Member
Registered: 2011-08-25
Posts: 29

Re: systemd boot fails

Nope. Doesn't work for me.

Offline

#21 2012-08-18 21:18:14

Zancarius
Member
From: NM, USA
Registered: 2012-05-06
Posts: 207

Re: systemd boot fails

I should add that I just ran into something similar today with my server (my third and final system converted to systemd). I'm not precisely sure what fixed it, but here's what I did:

1) Read this when the boot failed. I applied the systemd debugging args to the kernel, booted the system, and discovered that the problem actually began after my file systems were activated (lvchange) but before mount.
2) Merged in all pacnew files. I hadn't updated the server in a while, so there were a few sitting around. I didn't merge all of them, but the two remaining (CUPS and PHP) aren't critical services.
3) Re-ran mkinitcpio -p linux

The important part is to remove "quiet" on your kernel command line and add the appropriate lines for systemd debugging. It lead me to believe that it wasn't necessarily something wrong with file system mount points (although I did remove a tmpfs declaration for /tmp; I have /tmp mounted on a separate file system and systemd does NOT like doubled entries in /etc/fstab--be sure you don't have duplicates).

Again, I'm not exactly sure what I did to fix the problem I encountered. My server also runs LVM (as does my desktop) but mysteriously refused to boot with systemd until after a few fixes. Perhaps this will give you a few extra pointers. Also, make sure your system is completely up to date--but that probably goes without saying.


He who has no .plan has small finger.
~Confucius on UNIX.

Offline

#22 2012-08-19 09:36:46

k2s
Member
Registered: 2012-03-24
Posts: 9

Re: systemd boot fails

had exactly the same problem as described after last kernel/systemd update.

Solution was: sudo mkinitcpio -p linux

Offline

#23 2012-08-19 10:25:40

gondsman
Member
Registered: 2009-07-27
Posts: 84

Re: systemd boot fails

Oh, I should add this is indeed Arch-specific, as Fedora can boot just fine off the array.
EDIT: To try to make things clearer: the mkinitcpio solution doesn't work if you're on a fakeRAID (or bios RAID, however you want to call it). If you have the root partition on the array you need to have the dmraid hook otherwise the kernel won't boot.

Last edited by gondsman (2012-08-19 10:30:56)

Offline

#24 2012-08-21 18:15:01

gondsman
Member
Registered: 2009-07-27
Posts: 84

Re: systemd boot fails

I made a little progress in at least finding a workaround for this issue. If I remove /home and swap from my fstab (leaving only root) and then add mount and swapon commands in rc.local the system boots fine. My fear is that if something happens to the filesystem and it's flagged as "dirty" it will not perform a fsck and it will fail mounting it. Is there a way of replicating the behaviour of the init scripts as far as mounting goes (checking the filesystem every X mounts for example) and put it into rc.local?

Offline

#25 2012-08-22 19:33:28

gondsman
Member
Registered: 2009-07-27
Posts: 84

Re: systemd boot fails

Another bump to tell you that using mdadm instead of dmraid for the raid array (in the mkinitcpio.conf) leads to the exact same result (apart from changing the name of the devices from /dev/mapper/* to /dev/md126p*).

Offline

Board footer

Powered by FluxBB