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 Kernel
Packages, which is subscribed to linux in Ubuntu.

  [Trusty] fails to boot with kernels later than v3.11: systemd-
  udevd[133]: conflicting device node

Status in linux package in Ubuntu:
  In Progress

Bug description:
  I have a lab server named 'caddy' that is used for data recovery and
  forensics of disk drives. It has hot-swap drive bays for various disk
  interface types. Amongst others it has a Promise FasTrak TX2000 IDE
  'fake' RAID controller.

  It was upgraded from Saucy to Trusty. After the upgrade the server
  fails to boot using kernel version 3.13.0-24-generic during early udev
  whilst still in the initrd. Errors of the form:

  [    6.989549] systemd-udevd[137]: inotify_add_watch(7, /dev/sdi2, 10) 
failed: No such file or directory
  [    7.092733] systemd-udevd[133]: conflicting device node 
'/dev/mapper/pdc_ecjaiecgch1' found, link to '/dev/dm-2' will not be created

  are reported for some devices, usually the Promise 'fake' RAID

  The system hangs at that point without ever dropping to a busybox

  Starting with an earlier Saucy kernel version 3.11.0-12-generic allows
  the server to start successfully.

  After some research it appears that maybe this is due to an
  incompatibility between systemd-udevd and device-mapper and/or dmraid-
  activate. I read in a similar Fedora bug report a comment by Kay

  "Device-mapper seems to mknod() things in /dev, which just can not work
  correctly today.

  There is nothing udev can fix here, it will never touch any device
  node, which should not exist in the first place, that is in the way."

  I've tried breaking initrd, but unless it is done at 'top' udevd
  starts and the system hits this problem.

  Serial console logs of the failed and successful boot attempts are

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to