udev ( oops ) error at boottime ?!?!

[Nova00X]

Hi guys !

I was simply webbrowsing when X crashes ! gdm went back and i tried to login back ton X but it didn't work... So i decided to reboot ... and i had a strange error ! It blocks me during the boot process.

Here is my problem : At boot time i get this error message :

---------

* Mounting proc at /proc ......... ( ok )
* Mounting sysfs at /sys .......... ( ok )
* Mounting /dev for udev ......... ( ok )
* Populating /dev with saved device nodes ....
/sbin/rc: line 24: cannot redirect stadard input from /dev/null: No such fil or directory ( oops )

* The "tar" command failed with error:

This does not look like a tar archive
tar: Skipping to next header
tar: Archive contains obsolescent base-64 headers

bzip2: Data integrity error when decompressing.
input file = (stdin), output file = (stdout)

It is possible that the compressed file(s) have becom corrupted.
You can use the -tvv option to test integrity of such files.

You can use the 'bzip2recover' program to attempt to recover data from undamaged sections of corruptes files

tar: Child returned status 2
tar: Error exit delayed from previous errors

* Since this is a critical task, startup cannot continue


----------

I don't understand what's going on... i didn' changed anything. What's wrong with udev ? Can a hardware problem cause udev to fail populating devices ?

Thanks in advance for giving any direction to look to !

[wynn]

It looks as though you have the /dev directory saved in a tarball which is restored at every boot.

If you haven't got any special /dev nodes — if you don't know and you did the installation, you probably haven't — then the quick way round is the delete the tarball.

However, if you are the cautious sort, you will probably want to boot up the LiveCD and check the tarball as the error message suggests.

Unfortunately, I have been unable to find out what the tarball is called and where it is kept
_________________
The avatar is jorma, a "duck" from "Elephants Dream": the film and all the production materials have been made available under a Creative Commons Attribution 2.5 License, see orange.blender.org for details.

[Nova00X]

The problem was solved by updating udev to the actual stable version (087-r1). I was hoping it would somewhat regenerate files or something like that ... In fact it seems not but tests have changed ...

The first next reboot, same message appeared but was no more blocking.
Now at every reboot i got a huge message full of information about what would be every device in next tarball ... that's odd ...
However this is no more blocking the boot process

[wynn]

If you havn't got any exotic devices attached (coffee maker?) for which you have manually created the nodes in /dev then you can set