udev error message and kernel panic

Bug #573615 reported by mattgyver83
82
This bug affects 15 people
Affects Status Importance Assigned to Milestone
initramfs-tools (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: grub2

1. Ubuntu 10.04 LTS (upgraded from 9.10)
2. grub-common 1.98-1ubuntu5
3. When performing a cold-start of the PC grub properly loads the OS and GDM without flashing any errors.

A vast majority of the startup's, about 4 of 10 starts show the following error message for a minute and then load the gdm normally; udev_work[XXX] open /dev/null failed: no such file or directory
On the last startup attempt i received two instances of that message.

In one instance I recieved a Kernel Panic hanging the machine;
Run_Init: nuking initramfs contents: Directory not empty
[ 3.230737] Kernel Panic - not synching : attempted to kill init!

I am able to use the machine and get into gnome and I dont seem to have any adverse effects caused by this error. I also only get this error from a cold start, I can reboot all night and day and not receive this message and I have only seen the kernel panic one one occasion.

http://ubuntuforums.org/showthread.php?t=1466745

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: grub-common 1.98-1ubuntu5
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic-pae 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic-pae i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Sun May 2 07:51:03 2010
ProcEnviron:
 LANGUAGE=
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: grub2

Revision history for this message
mattgyver83 (mattgyver83) wrote :
Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

I've seen a computer that gives a similar message but the machine does not panic. Again it was a machine that was updated from 9.10.

affects: grub2 (Ubuntu) → initramfs-tools (Ubuntu)
Revision history for this message
deactivated (deactivated-account) wrote :

I have the "udev_work[XXX] open /dev/null failed: no such file or directory" error on a clean install of 10.04 i386. No kernel panic and after a few seconds the boot completes. Seems to occur randomly on either cold boot or re-start.

Revision history for this message
petermolnar (petermolnar) wrote :

Mine is an updated version too, is gives a similar message, although no kernel panic, and it boots normally after this.

Revision history for this message
gthf (guybrush-t) wrote :

I have same problem but i made a new install (not update from 9.10).
I've change some mount points with 10.04 (/tmp /var), I have no swap, I use an SSD for root (/).
The problem occurs randomly or at least I do not understand when it fires.

Revision history for this message
Gio (giovanni-lenzi) wrote :

I think I have the same problem..

The error message is:
"run-init script, nuking intramfs. Directory not empty"

It occurs randomly both on cold booting and restarting.. It hangs the system up and it requires a button hold to power off the server.

Initially I thought it was a hardware related problem because of a disk failure: I have a dl365g5 with hp smart array controller p400 and 6 disks in raid 6 configuration (2 disk of redundancy). But now the disk has been correctly rebuilt and the problem continues to appear randomly...

The error displays after grub loading..

If I enter recovery mode, the problem disappears, even for next reboots in normal mode.

Maybe it can be related to modifications in /etc/fstab. I've added a lvm volume to mount at boot. Obviously, when I don't receive the error, the volume is mounted correctly..

Revision history for this message
SapphirePaw (sapphirepaw) wrote :

This started happening to me somewhat recently (i.e. sometime in 2011) on Ubuntu Lucid; in /var/log/apt I see an update of `linux-image-generic-lts-backport-maverick (2.6.35.22.34, 2.6.35.23.35)` which included the install of `linux-image-2.6.35-23-generic (2.6.35-23.41~lucid1)` and the corresponding headers on Feb 5. This upgrade also seems to have included grub-common (1.98-1ubuntu9, 1.98-1ubuntu10).

I can't find anything related to initramfs in history.log or history.*.gz (which goes back to 2010 Apr 30.) In the cases it has happened so far, the machine has been okay after reboot with the hardware reset button.

I have root as ext4 on LVM on an SSD; I'm using the Maverick backport kernel for its improved TRIM and barrier support. The machine was installed as Intrepid and has been upgraded through each release. I've stayed on Lucid because I finally got tired of fixing things after each upgrade.

Revision history for this message
Sean Clarke (sean-clarke) wrote :

Still present in 10.04.2 (2.6.32-32-generic-pae #62-Ubuntu SMP )

Changed in initramfs-tools (Ubuntu):
status: New → Confirmed
Revision history for this message
iLugo (isra) wrote :

If the main report is the #155689, then please change the status to "Confirmed" also there. I am having same issue in Ubuntu 10.10 .

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.