Arch Linux

pgzh

Member

Registered: 2013-03-20

Posts: 19

System fails to boot with own kernel, dm_crypt/udev related?

Hi,

after running a pacman -Syu this week (I think it happend on March 13th), my Arch linux installation stopped booting with my self-compiled kernel.
I have 3 hard drives configured in a (md-)raid 5 (2 separate raids, one for the system partition and one for data). In both raid arrays is a dm_crypt (luks) encrypted partition.
I'm booting with cryptdevice=UUID=... on the command line, crypttab and fstab contain only UUIDs.

On booting I get the following error:
"A start job is running for dev-disk-by/..." for all my encrypted partitions (including swap) except for the system partition right after udev gets started.

'systemctl status' says

Mar 16 11:50:11 orion systemd[1]: Started udev Kernel Device Manager.
Mar 16 11:50:11 orion systemd-udevd[2479]:  conflicting device node '/dev/mapper/crypt_root' found, link to '/dev/dm-0' will not be created[0m

'journalctl -xb' contains

-- Unit systemd-udevd.service has finished starting up.
-- 
-- The start-up result is done.
Mar 16 11:50:11 orion systemd-udevd[2479]:  conflicting device node '/dev/mapper/crypt_root' found, link to '/dev/dm-0' will not be created
Mar 16 11:50:11 orion mtp-probe[2499]: checking bus 8, device 3: "/sys/devices/pci0000:00/0000:00:1d.2/usb8/8-2"
...
Mar 16 11:51:39 orion systemd[1]: [1;31mTimed out waiting for device dev-disk-by\x2duuid-0290e0db\x2dd7a3\x2d432d\x2d8fe9\x2db81d24ab4f6d.device.
-- Subject: Unit dev-disk-by\x2duuid-0290e0db\x2dd7a3\x2d432d\x2d8fe9\x2db81d24ab4f6d.device has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit dev-disk-by\x2duuid-0290e0db\x2dd7a3\x2d432d\x2d8fe9\x2db81d24ab4f6d.device has failed.
-- 
-- The result is timeout.
Mar 16 11:51:39 orion systemd[1]:  Dependency failed for /data.[0m
-- Subject: Unit data.mount has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit data.mount has failed.
-- 
-- The result is dependency.
Mar 16 11:51:39 orion systemd[1]:  Dependency failed for Local File Systems.
-- Subject: Unit local-fs.target has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit local-fs.target has failed.
-- 
-- The result is dependency.
...

The first mentioned UUID belongs to the unencrypted dm-crypt partition:

/dev/mapper/crypt_data: UUID="0290e0db-d7a3-432d-8fe9-b81d24ab4f6d" TYPE="xfs"

The underlying RAID5 was up and running according to /etc/mdstat.

Strangely, with the default Arch linux kernel, the system boots (with identical commandline options) without any problems.

Maybe someone here can help me shed some light onto this, I guess I have set a kernel option that is not set in the Arch kernel or vice versa. I already checked and changed to devfs auto-mount option in my kernel, but that did not make any difference. I don't have any clue where to look next.
Where can I start to look for the culprit?

Any help would be highly appreciated...

Last edited by pgzh (2014-03-16 11:09:22)

falconindy

Developer

From: New York, USA

Registered: 2009-10-22

Posts: 4,111

Website

Re: System fails to boot with own kernel, dm_crypt/udev related?

my self-compiled kernel.

Not the first thread on this topic. Your kernel lacks CONFIG_FHANDLE.

---

blog | ±github

pgzh

Member

Registered: 2013-03-20

Posts: 19

Re: System fails to boot with own kernel, dm_crypt/udev related?

Thank you very much falconindie!

Actually I've searched for different keywords and the error messages I found in the logs, but did not come across the solution myself. I'm sorry if a thread like this one already existed here.