lucid boot error, open /dev/null failed

[sosaited]

I got this error today when I enabled ACPI 2.0 in my Bios and reverted another ACPI related setting to a previous setting. Before that a change of an ACPI in bios had caused my Ubuntu 9.10 and 10.04 to connect to the Internet, but I couldn't browse. And XP failed to load at all.

[gavin_attoe]

Edit: I've had variations on this error at startup. I'm not running a dual boot, just straight-up Ubuntu 10.04, upgraded from a previous version of Ubuntu installed about a year ago.

udevd-work[332]: opening directory /dev/null failed: no such file or directory

to

udevd-work[340]: opening directory /dev/null failed: no such file or directory

and now

udevd-work[349]: opening directory /dev/null failed: no such file or directory

There seem to be a lot of people with this bug, and there's a workaround listed with the bug issue Bug #575333

I'd still really like to know what causes it - seems to be trying to read from the DVD/CD Rom from what was said about the issue.

[radec]

i'm getting this error now as well. just did a fresh install of 10.10. pretty sure it happened right after added discard to /etc/fstab. not sure if its related and its possible this error was showing before and I just didn't notice it because I hadn't rebooted that many times and it still boots up fine and well under 10seconds.

-rad

[mlnease]

'Reply to Thread' page has no link to 'SOLVED' that I can find. Seems like it should have, to me. BIG button, maybe? I'm not too bright.

I stopped having this problem when I unplugged my USB external hard drive and camera.

Hope this helps someone.

mike

[drs305]

'Reply to Thread' page has no link to 'SOLVED' that I can find. Seems like it should have, to me. BIG button, maybe? I'm not too bright.

Only the original poster can mark a thread solved. It's done via the 'Thread Tools' link at the top right of the first post.

An individual who didn't initiate the thread could alter the title of his/her response by manually adding 'Solved' at the start of the individual post if desired, although it would not be reflected in the thread title.

[mlnease]

Of course, thanks--sorry for my misunderstanding.

[drs305]

Of course, thanks--sorry for my misunderstanding.

No harm in asking. We wish more users would use the "Solved" tag when the issue no longer requires help. It assists others looking for threads with a known solution and allows 'helpers' to concentrate on unresolved problems.

We don't advertise the 'SOLVED' link often enough, so we are happy to bring it to the attention of forumites when asked about it.

[krige]

I have the same problem under 10.10 64bit on an HP workstation.

* upate-grub didn't solve the problem;

* I don't have a DVD in the tray during boot;

* I don't have any USB external hard drive nor camera during boot;

* free -m gives the following output:

             total       used       free     shared    buffers     cached
Mem:          2000       1349        651          0         54        578
-/+ buffers/cache:        716       1284
Swap:         5860          0       5860

[krige]

I have disabled the floppy disk, the serial and parallel ports in the bios (I never use either of them), and the error disappeared.

[J@n]

Kudos to krige

Had the same problem and it started to irritate me. I got the udevd-work error after switching from a normal HDD to an SSD (restoring an image).

Turned of serial and parallel in BIOS and presto....error disappeared.

Now my SSD is really showing what it's worth

Greetz,

J@n

EDIT: Darn....a cold boot resulted in re-appearing of the error. Should have tested that