udevd[926] unable to open "/etc/udev/rules.d": no such file or directory.

Bug #318338 reported by Simon Allen on 2009-01-18
16
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu
Undecided
Unassigned

Bug Description

Hi.

Upon boot on my Asus m51sn (3G model) laptop running Ubuntu Jaunty, usplash appears and the boot proceeds as expected. However, after a few seconds the usplash boot image goes away and replaced by text. The first line of text on the screen seems to be an error message:

udevd[926] unable to open "/etc/udev/rules.d": no such file or directory.

Further down after a few other lines of text that appear normal (except for the fact that usplash seems to be broken) the following appears:

Loading hardware drivers
udev-event[2141] mknod/dev/pktcdvd/control

after the udev-event line, text follows along the lines of not found but I can't remember the exact wording, as my laptop just boots seemingly fine.

After taking a look at /etc/udev/rules.d I find that the directory does exist and contains three files:
70-persistent-cd.rules
70-persistent-net.rules
README

After doing a search for a folder named "pktcdvd" or "mknod" I find nothing except a few files or folders that don't have a file or folder named "control" in them.

Daniel T Chen (crimsun) wrote :

jaunty's udev now uses /lib/udev/rules.d, not /etc/udev/rules.d

OK, well I have many more files in /lib/udev/rules.d

Still doesn't explain why the error occurs.

2009/1/18 Daniel T Chen <email address hidden>

> jaunty's udev now uses /lib/udev/rules.d, not /etc/udev/rules.d
>
> ** Changed in: ubuntu
> Status: New => Incomplete
>
> --
> udevd[926] unable to open "/etc/udev/rules.d": no such file or directory.
> https://bugs.launchpad.net/bugs/318338
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Seems something in mkinitd ... on root filesystem, /etc/udev/rules.d is hardlinked to /lib/udev/rules.d, while on initrd image this is not the case. Again, this may be related to Bug #315979, which for me appeared on same update.
Maybe it is needed to check the initrd creation procedure, to reflect any relevant changes made to udev.

It appears on my ubuntu jaunty 64bit in early boot. Something different in initrd creation not reflecting udev changes? It came up together with Bug #318338 which is due to missing link /etc/udev/rules.d -> /lib/udev/rules.d in initrd. Is something missing for udev management in /usr/share/initramfs-tools/hooks/udev ?

k1dugar (k1dugar) wrote :

Error: unable to open "/etc/udev/rules.d": no such file or directory
I can confirm that this error occur in early boot of amd64 arch. system is not able to load nvidia driver, i guess its related to udev error.

James Schriver (dashua) wrote :

I am having this issue as well on an updated Jaunty 64 bit, updated from Intrepid 64 (update-manager -d).

Simon Allen (garfunkel) wrote :

Actually, the nvidia thing is a different issue, assuming the driver is
installed, you need to add the -ignoreABI option to /etc/X11/xorg.conf. When
I did that, nvidia works fine.

2009/1/20 k1dugar <email address hidden>

> Error: unable to open "/etc/udev/rules.d": no such file or directory
> I can confirm that this error occur in early boot of amd64 arch. system is
> not able to load nvidia driver, i guess its related to udev error.
>
> --
> udevd[926] unable to open "/etc/udev/rules.d": no such file or directory.
> https://bugs.launchpad.net/bugs/318338
> You received this bug notification because you are a direct subscriber
> of the bug.
>

kenzo (kenzo) wrote :

I can second that - for me, with 2.6.28 the system is not even booting up at all, as I'm using LUKS for file system encryption and the failing udev prevents this from working. I have to go back to 2.6.24 to have the system running at all.

Richard Verwayen (ys76) wrote :

I am running a custom 2.6.29-rc2 on a crypted-root machine, and as kenzo pointed out, it doesn't boot at all.
The machine was upgraded to jaunty from intrepid without any warnings or errors.

update-initramfs on a (old) working kernel/initrd causes this bug to appear, too.

Afer some time, the machine reboots.

Michael Rooney (mrooney) wrote :

I think I am getting this bug as well, after installing Jaunty 64bit Alpha 3. It displays what I believe is this error before usplash for me, beeps about 10-15 times, and then goes I think to a black screen. I tried then installing i386 instead and got a similar looking error, although it only beeps once and then continues booting quickly.

James Schriver (dashua) wrote :

udev (137-1) jaunty; urgency=low

  * New upstream release:
    - udevadm test no longer has force option.
    - udevd has --resolve-names=early|late|never option.
    - Group of IDE CD-ROM drives fixed. LP: #315997.
    - Group of DRI subsystem fixed. LP: #317430.
    - /etc/udev/rules.d not existing is not an error. LP: #315780.
    - Bug where device nodes would be replaced by symlinks on rename has been
      fixed. LP: #315979.

  * Use --resolve-names=never in the installer and initramfs, since we don't
    have a useful name service. LP: #319199.
  * Since we don't have to worry about group lookup, we may as well copy the
    default rules into the initramfs as well. This actually double-solves
    LP: #315979.
  * Make sure the root filesystem is writable before attempting to copy
    generated rules across. LP: #224870.
  * Remove /dev/MAKEDEV symlink; the FHS no longer requires it when /dev
    is automatically managed.

  * It is not permitted to call udevadm trigger or settle during an upgrade
    without depending on udev. Attempting this will fail.
  * Change /etc/init.d/udev restart to actually restart the daemon, with a
    bit of detection to print a warning if we missed events while the
    daemon was down.
  * Refreshing /dev is now /etc/init.d/udev refresh-devices
  * Restart udev daemon after upgrade. LP: #317944.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers