[Bug 1358491] Re: [Trusty] fails to boot with kernels later than v3.11: systemd-udevd[133]: conflicting device node
I worked around this by removing the long name /dev/isw_verylongname/p1 and replacing it with /dev/dm-1 in the /etc/fstab Interestingly, this is the 2nd raid in the system. The first one mounts with no problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1358491 Title: [Trusty] fails to boot with kernels later than v3.11: systemd- udevd[133]: conflicting device node To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1358491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1358491] Re: [Trusty] fails to boot with kernels later than v3.11: systemd-udevd[133]: conflicting device node
** Changed in: linux (Ubuntu) Assignee: TJ (tj) = (unassigned) ** Changed in: linux (Ubuntu) Status: In Progress = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1358491 Title: [Trusty] fails to boot with kernels later than v3.11: systemd- udevd[133]: conflicting device node To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1358491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1358491] Re: [Trusty] fails to boot with kernels later than v3.11: systemd-udevd[133]: conflicting device node
Have anyone found a solution? I have the same problem here.. conflicting device node '/dev/mapper/1sw_bchgjehgcf_biosraid6' found, link to '/dev/dm-6' will not be created -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1358491 Title: [Trusty] fails to boot with kernels later than v3.11: systemd- udevd[133]: conflicting device node To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1358491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1358491] Re: [Trusty] fails to boot with kernels later than v3.11: systemd-udevd[133]: conflicting device node
TJ, I have the same problem on my home system, a HP Z600 with hardware RAID. Looking at the results from 4 different reboots today: $ grep conflicting device node /var/log/syslog Mar 7 09:36:22 z600 kernel: [ 14.744525] systemd-udevd[738]: conflicting device node '/dev/mapper/isw_ciijhaceja_Volume0p4' found, link to '/dev/dm-4' will not be created Mar 7 09:36:22 z600 kernel: [ 14.923887] systemd-udevd[733]: conflicting device node '/dev/mapper/isw_ciijhaceja_Volume0p1' found, link to '/dev/dm-1' will not be created Mar 7 09:36:22 z600 kernel: [ 14.934934] systemd-udevd[741]: conflicting device node '/dev/mapper/isw_ciijhaceja_Volume0p2' found, link to '/dev/dm-2' will not be created Mar 7 09:36:22 z600 kernel: [ 15.412385] systemd-udevd[733]: conflicting device node '/dev/mapper/isw_ciijhaceja_Volume0p3' found, link to '/dev/dm-3' will not be created Mar 7 20:34:03 z600 kernel: [ 14.711869] systemd-udevd[742]: conflicting device node '/dev/mapper/isw_ciijhaceja_Volume0p1' found, link to '/dev/dm-1' will not be created Mar 7 20:34:03 z600 kernel: [ 14.737949] systemd-udevd[741]: conflicting device node '/dev/mapper/isw_ciijhaceja_Volume0p2' found, link to '/dev/dm-2' will not be created Mar 7 20:34:03 z600 kernel: [ 14.775406] systemd-udevd[742]: conflicting device node '/dev/mapper/isw_ciijhaceja_Volume0p4' found, link to '/dev/dm-4' will not be created Mar 7 20:34:03 z600 kernel: [ 14.775510] systemd-udevd[731]: conflicting device node '/dev/mapper/isw_ciijhaceja_Volume0p1' found, link to '/dev/dm-1' will not be created Mar 7 20:34:03 z600 kernel: [ 15.036880] systemd-udevd[741]: conflicting device node '/dev/mapper/isw_ciijhaceja_Volume0p3' found, link to '/dev/dm-3' will not be created Mar 7 20:34:03 z600 kernel: [ 15.275910] systemd-udevd[733]: conflicting device node '/dev/mapper/isw_ciijhaceja_Volume0p2' found, link to '/dev/dm-2' will not be created Mar 7 20:34:03 z600 kernel: [ 15.276606] systemd-udevd[730]: conflicting device node '/dev/mapper/isw_ciijhaceja_Volume0p5' found, link to '/dev/dm-5' will not be created Mar 7 20:34:03 z600 kernel: [ 15.461964] systemd-udevd[730]: conflicting device node '/dev/mapper/isw_ciijhaceja_Volume0p5' found, link to '/dev/dm-5' will not be created Mar 7 20:34:03 z600 kernel: [ 15.831112] systemd-udevd[731]: conflicting device node '/dev/mapper/isw_ciijhaceja_Volume0p6' found, link to '/dev/dm-6' will not be created Mar 7 20:34:03 z600 kernel: [ 15.875357] systemd-udevd[730]: conflicting device node '/dev/mapper/isw_ciijhaceja_Volume0p7' found, link to '/dev/dm-7' will not be created Mar 7 20:34:03 z600 kernel: [ 15.945102] systemd-udevd[733]: conflicting device node '/dev/mapper/isw_ciijhaceja_Volume0p8' found, link to '/dev/dm-8' will not be created Mar 7 21:03:39 z600 kernel: [ 18.100972] systemd-udevd[737]: conflicting device node '/dev/mapper/isw_ciijhaceja_Volume0p2' found, link to '/dev/dm-2' will not be created Mar 7 21:03:39 z600 kernel: [ 18.140472] systemd-udevd[745]: conflicting device node '/dev/mapper/isw_ciijhaceja_Volume0p5' found, link to '/dev/dm-5' will not be created Mar 7 21:03:39 z600 kernel: [ 18.677290] systemd-udevd[738]: conflicting device node '/dev/mapper/isw_ciijhaceja_Volume0p6' found, link to '/dev/dm-6' will not be created Mar 7 21:03:39 z600 kernel: [ 18.692634] systemd-udevd[738]: conflicting device node '/dev/mapper/isw_ciijhaceja_Volume0p9' found, link to '/dev/dm-9' will not be created Mar 7 21:03:39 z600 kernel: [ 18.716691] systemd-udevd[737]: conflicting device node '/dev/mapper/isw_ciijhaceja_Volume0p5' found, link to '/dev/dm-5' will not be created Mar 7 21:25:44 z600 kernel: [ 15.418372] systemd-udevd[842]: conflicting device node '/dev/mapper/isw_ciijhaceja_Volume0p2' found, link to '/dev/dm-2' will not be created Mar 7 21:25:44 z600 kernel: [ 15.487121] systemd-udevd[842]: conflicting device node '/dev/mapper/isw_ciijhaceja_Volume0p4' found, link to '/dev/dm-4' will not be created Mar 7 21:25:44 z600 kernel: [ 15.658368] systemd-udevd[832]: conflicting device node '/dev/mapper/isw_ciijhaceja_Volume0p6' found, link to '/dev/dm-6' will not be created Mar 7 21:25:44 z600 kernel: [ 15.802411] systemd-udevd[839]: conflicting device node '/dev/mapper/isw_ciijhaceja_Volume0p3' found, link to '/dev/dm-3' will not be created Mar 7 21:25:44 z600 kernel: [ 15.999608] systemd-udevd[838]: conflicting device node '/dev/mapper/isw_ciijhaceja_Volume0p7' found, link to '/dev/dm-7' will not be created Mar 7 21:25:44 z600 kernel: [ 16.158226] systemd-udevd[832]: conflicting device node '/dev/mapper/isw_ciijhaceja_Volume0p5' found, link to '/dev/dm-5' will not be created Mar 7 21:25:44 z600 kernel: [ 16.325655] systemd-udevd[832]: conflicting device node '/dev/mapper/isw_ciijhaceja_Volume0p9' found, link to '/dev/dm-9' will not be created $ cat /proc/cmdline BOOT_IMAGE=/vmlinuz-3.13.0-46-generic
[Bug 1358491] Re: [Trusty] fails to boot with kernels later than v3.11: systemd-udevd[133]: conflicting device node
blausand, I'm afraid I've not spent much time on this issue since I developed the work-around of moving the rootfs. As it only affected the forensics server when hot-swap disks with dmraid metadata were attached I've not re-visited this issue so far. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1358491 Title: [Trusty] fails to boot with kernels later than v3.11: systemd- udevd[133]: conflicting device node To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1358491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1358491] Re: [Trusty] fails to boot with kernels later than v3.11: systemd-udevd[133]: conflicting device node
I have the very same problem and it freaks me out because i cannot return to the much older kernel that woud boot. *I kindly request some guidance to a temporary manual fix.* The mapper-ID (isw_) seems to change from time to time. I don't know if that stems from the Ubuntu (Studio 14.04 LTS) installation or, possibly, from Intels RAID rebuild code that is launched via the Windows OS e.g. after power loss. _ blausand@Utopon ~ cat /proc/cmdline BOOT_IMAGE=/vmlinuz-3.2.0-67-generic root=UUID=57907805-da9f-4d85-9c49-71807a97c4c0 ro nosplash blausand@Utopon ~ cat /proc/version Linux version 3.2.0-67-generic (buildd@brownie) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #101-Ubuntu SMP Tue Jul 15 17:46:11 UTC 2014 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1358491 Title: [Trusty] fails to boot with kernels later than v3.11: systemd- udevd[133]: conflicting device node To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1358491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1358491] Re: [Trusty] fails to boot with kernels later than v3.11: systemd-udevd[133]: conflicting device node
The 'fake' RAID controller has two disks attached. Each is configured as separate RAID-0 stripe arrays - this is because the controller doesn't support JBOD pass-through. This issue is caused by the LVM volumes on a fake-RAID device failing to be ready because the LVM VG_CADDY/rootfs is not created since the VG's container partition /dev/mapper/pdc_ecjaiecgch4 does not get created: (initramfs) cat /proc/version Linux version 3.13.0-24-generic (buildd@panlong) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014 (initramfs) cat /proc/cmdline BOOT_IMAGE=/vmlinuz-3.13.0-24-generic root=/dev/mapper/VG_CADDY-rootfs ro debug bootdegraded=true libata.force=noncq console=tty0 console=ttyS0,115200n8 netconsole=@10.254.1.3/eth0,@10.254.1.51/ --debug --verbose break=top nomdmonddf nomdmonisw (initramfs) dmesg | grep -C2 sdb [ 97.610562] scsi 11:0:1:0: Direct-Access ATA ST380011A3.06 PQ: 0 ANSI: 5 [ 97.610762] sd 11:0:1:0: [sdb] 156299375 512-byte logical blocks: (80.0 GB/74.5 GiB) [ 97.610786] sd 11:0:1:0: Attached scsi generic sg2 type 0 [ 97.610893] sd 11:0:1:0: [sdb] Write Protect is off [ 97.610895] sd 11:0:1:0: [sdb] Mode Sense: 00 3a 00 00 [ 97.610942] sd 11:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 97.675153] sdb: sdb1 sdb2 sdb3 sdb4 [ 97.675669] sd 11:0:1:0: [sdb] Attached SCSI disk -- 27[ 100.196769] systemd-udevd[176]: inotify_add_watch(7, /dev/sdb3, 10) failed: No such file or directory 27[ 100.196845] systemd-udevd[168]: inotify_add_watch(7, /dev/sdb1, 10) failed: No such file or directory 27[ 100.197798] systemd-udevd[177]: inotify_add_watch(7, /dev/sdb4, 10) failed: No such file or directory 27[ 100.198351] systemd-udevd[175]: inotify_add_watch(7, /dev/sdb2, 10) failed: No such file or directory 27[ 100.198375] systemd-udevd[179]: inotify_add_watch(7, /dev/sdc2, 10) failed: No such file or directory 27[ 100.198911] systemd-udevd[180]: inotify_add_watch(7, /dev/sdc3, 10) failed: No such file or directory (initramfs) dmesg | grep 'too small' [ 100.346794] device-mapper: table: 252:13: dm-0 too small for target: start=13574144, len=142725198, dev_size=156298401 # fake RAID raw device (initramfs) kpartx -l /dev/sdb sdb1 : 0 2014 /dev/sdb 34 sdb2 : 0 1024000 /dev/sdb 2048 sdb3 : 0 12023809 /dev/sdb 1288192 sdb4 : 0 142725198 /dev/sdb 13574144 # same device through the device-mapper viewpoint (initramfs) kpartx -l /dev/mapper/pdc_ecjaiecgch Alternate GPT is invalid, using primary GPT. pdc_ecjaiecgch1 : 0 2014 /dev/mapper/pdc_ecjaiecgch 34 pdc_ecjaiecgch2 : 0 1024000 /dev/mapper/pdc_ecjaiecgch 2048 pdc_ecjaiecgch3 : 0 12023809 /dev/mapper/pdc_ecjaiecgch 1288192 pdc_ecjaiecgch4 : 0 142725198 /dev/mapper/pdc_ecjaiecgch 13574144 I've moved the VG to another disk on a plain PATA controller for now. I'll investigate more when I have time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1358491 Title: [Trusty] fails to boot with kernels later than v3.11: systemd- udevd[133]: conflicting device node To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1358491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1358491] Re: [Trusty] fails to boot with kernels later than v3.11: systemd-udevd[133]: conflicting device node
** Attachment added: Successful boot with kernel 3.11.0-12-generic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1358491/+attachment/4181112/+files/caddy-good.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1358491 Title: [Trusty] fails to boot with kernels later than v3.11: systemd- udevd[133]: conflicting device node To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1358491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1358491] Re: [Trusty] fails to boot with kernels later than v3.11: systemd-udevd[133]: conflicting device node
Due to bug 560246 Launchpad requires the REFERER header on form submission... apport-collect cannot send the system diagnostic data. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1358491 Title: [Trusty] fails to boot with kernels later than v3.11: systemd- udevd[133]: conflicting device node To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1358491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1358491] Re: [Trusty] fails to boot with kernels later than v3.11: systemd-udevd[133]: conflicting device node
Looking closer, the reason 3.11.x starts is that there are no dmraid device-mapper nodes created at all. I'm modifying the /init script so I can break in early, and re-run it to break-points of my choice, to do more diagnosis. ** Changed in: linux (Ubuntu) Assignee: (unassigned) = TJ (tj) ** Changed in: linux (Ubuntu) Status: Triaged = In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1358491 Title: [Trusty] fails to boot with kernels later than v3.11: systemd- udevd[133]: conflicting device node To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1358491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
