Arch Linux

SickToni

Member

Registered: 2011-08-26

Posts: 6

[SOLVED] Systemd freezes during boot

Hello guys,

I encountered yesterday a fatal problem on my notebook (Thinkpad T430). I wanted to boot into Arch which worked without any problems the day before and then it suddenly stop booting during the start of 'systemd'. I just see that

udev

and

lvm2

have been hooked.

Also I see that the volume group of lvm has been found and also all the volumes. I would guess that there is no problem with lvm.
I also tried to boot with:

systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M

This changes nothing it freezes everytime at the same position.

I hope you understood my problem, if not, then say something and I will post a screenshot of my output.

Any ideas how to solve the problem?

Thanks

Last edited by SickToni (2013-03-29 15:20:23)

s1ln7m4s7r

Member

Registered: 2013-02-22

Posts: 262

Re: [SOLVED] Systemd freezes during boot

Can you post what appears in your screen? It would help to see what's the problem.

SickToni

Member

Registered: 2011-08-26

Posts: 6

Re: [SOLVED] Systemd freezes during boot

I get this. I tried different kernel options trying to get in the debug/rescue-mode, but nothing helped.

s1ln7m4s7r

Member

Registered: 2013-02-22

Posts: 262

Re: [SOLVED] Systemd freezes during boot

What do you have as hooks and modules in mkinitcpio.conf? Also post your fstab!

Last edited by s1ln7m4s7r (2013-03-28 19:21:40)

SickToni

Member

Registered: 2011-08-26

Posts: 6

Re: [SOLVED] Systemd freezes during boot

the mkinitcpio.conf:

# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run.  Advanced users may wish to specify all system modules
# in this array.  For instance:
#     MODULES="piix ide_disk reiserfs"
MODULES=""

# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image.  This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=""

# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way.  This is useful for config files.
FILES=""

# HOOKS
# This is the most important setting in this file.  The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added.  Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
##   This setup specifies all modules in the MODULES setting above.
##   No raid, lvm2, or encrypted root is needed.
#    HOOKS="base"
#
##   This setup will autodetect all modules for your system and should
##   work as a sane default
#    HOOKS="base udev autodetect block filesystems"
#
##   This setup will generate a 'full' image which supports most systems.
##   No autodetection is done.
#    HOOKS="base udev block filesystems"
#
##   This setup assembles a pata mdadm array with an encrypted root FS.
##   Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
#    HOOKS="base udev block mdadm encrypt filesystems"
#
##   This setup loads an lvm2 volume group on a usb device.
#    HOOKS="base udev block lvm2 filesystems"
#
##   NOTE: If you have /usr on a separate partition, you MUST include the
#    usr, fsck and shutdown hooks.
HOOKS="base udev autodetect modconf block filesystems usbinput fsck lvm2"

# COMPRESSION
# Use this to compress the initramfs image. By default, gzip compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"

# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=""

the fstab:

# 
# /etc/fstab: static file system information
#
# <file system>	<dir>	<type>	<options>	<dump>	<pass>
# UUID=c0548d03-ac12-4594-92ed-1549cc67b78a
/dev/mapper/VolGroup00-lvolroot	/         	ext4      	rw,relatime,data=ordered	0 1

# UUID=77276fa3-f0d0-4efa-a9dc-1f917072247a
/dev/mapper/VolGroup00-lvolhome	/home     	ext4      	rw,relatime,data=ordered	0 2

I would guess that I could change some hooks, but I don't understand why ....

And also one small question. If I wish to change something, then I have to update it for my ArchLinux. I was thinking, I could get chroot-access same as for the installation. Right now I'm using a Ubuntu-LiveUSB to access to the Arch system and it's not possible to use chroot, right?

Last edited by SickToni (2013-03-29 11:27:04)

tumas

Member

Registered: 2012-02-08

Posts: 89

Re: [SOLVED] Systemd freezes during boot

I would guess that I could change some hooks, but I don't understand why ....

And also one small question. If I wish to change something, then I have to update it for my ArchLinux. I was thinking, I could get chroot-access same as for the installation. Right now I'm using a Ubuntu-LiveUSB to access to the Arch system and it's not possible to use chroot, right?

Yes that's right, u can chroot to your installation if u boot from the arch-installation-image from usb/cd and activate your lvm volume(s) with "vgchange -ay". After that u can mount your partitions just like u would do when installing arch.
I am not sure if that will solve your problem, but as https://wiki.archlinux.org/index.php/LV … tcpio.conf suggests, u could try to add the "lvm2" option between "block" and "filesystem" and then run "mkinitcpio -p linux" to reconfigure your kernel.

SickToni

Member

Registered: 2011-08-26

Posts: 6

Re: [SOLVED] Systemd freezes during boot

Yes that's right, u can chroot to your installation if u boot from the arch-installation-image from usb/cd and activate your lvm volume(s) with "vgchange -ay". After that u can mount your partitions just like u would do when installing arch.
I am not sure if that will solve your problem, but as https://wiki.archlinux.org/index.php/LV … tcpio.conf suggests, u could try to add the "lvm2" option between "block" and "filesystem" and then run "mkinitcpio -p linux" to reconfigure your kernel.

It helped. Thanks. Know I can boot into my system, but now I have some problems with the XServer.