Joined: 15 Aug 2004
|Posted: Thu Jun 29, 2017 12:39 pm Post subject: udev conflicting device mode
I have a laptop with two drives. One is a none volatile memory express (nvme) and the other is sata.
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sdb 8:16 1 7.2G 0 disk
└─sdb1 8:17 1 7.2G 0 part
sda 8:0 0 931.5G 0 disk
└─sda1 8:1 0 931.5G 0 part
└─crypt2 253:1 0 931.5G 0 crypt
nvme0n1 259:0 0 477G 0 disk
├─nvme0n1p1 259:1 0 512M 0 part
└─nvme0n1p2 259:2 0 476.4G 0 part
└─crypt1 253:0 0 476.4G 0 crypt
I use a custom initramfs that I create in a cpio archive. The initramfs has a script that I use to decrypt the two drives. I then use zfs to import the pool.
The Problem: I find the following via dmesg after booting into the system
|[ 144.358409] udevd: conflicting device node '/dev/mapper/crypt1' found, link to '/dev/dm-0' will not be created
[ 144.359223] udevd: conflicting device node '/dev/mapper/crypt2' found, link to '/dev/dm-1' will not be created
[ 144.441465] udevd: conflicting device node '/dev/mapper/crypt1' found, link to '/dev/dm-0' will not be created
[ 144.441694] udevd: conflicting device node '/dev/mapper/crypt2' found, link to '/dev/dm-1' will not be created
It seems to be trying to map the devices multiple times. Note that everything seems to be working normally. The drives are correctly mapped and I am able to import the pool and load gentoo, but for some reason it is trying to map the devices after having already mapped the devices in the initramfs. I have been looking through the kernel for an option that might explain this behaviour, but I am guessing it is a udev issue. I am guessing I have to somehow tell udev not to try and map these devices because it has already been done?
Does anyone know what the solution is? In the meantime I am going to start learning something about udev since this is an area I know very little about. Thanks.
Unanswered Post Initiative: