i92guboj
Bodhisattva
Joined: 30 Nov 2004
Posts: 10315
Location: Córdoba (Spain)
|
 Posted: Wed May 04, 2005 4:26 pm Post subject: [udev] - Power failure, unable to boot - (Solved) |
 |
|
Im bored of these things, they are driving me mad 
Five minutes ago a power failure in the same moment where I was soft rebooting my system has messed up something I cant figure out. I've tried reinstalling udev, no difference at all.
This is the lovely output when booting:
| Code: |
* Configuring system to use udev
* Populating /dev with device nodes
/sbin/rc: line 25: cannot redirect standard input from /dev/null: No such file or directory
* the tar command failed with error
(stdin) is not a bzip2 file
tar: Child returned status 2
tar: Error exit delayed from previous errors
* Since this is a critical task startup cannot continue
/dev/console: no such file of directory
Give root password for mainteinance
(or type Control-D for normal startup):
|
Of course, if I ctrl-d then the system reboots, if i give the password I boot into a minimal read-only environment. Looking into /dev I see, in fact, that all the related stuff is not there, only sysctl and a couple more files that I can't remember (not relevant thou).
In the other side, if I boot from a livecd and mount /dev/hda2 wich hold my root, I can see that /dev contains all the stuff it is supposed to, so I'm thinking that the trouble has something to do with udev, but I tried reinstalling it, even deleting all the config into /etc/udev and reinstalling again, do change.
Please, if anyone can help me I will be very thankfull. 
[edit]: Suspecting a filesystem corruption I run xfs_check /dev/hda2 and it reports nothing, as do fsck.xfs /dev/hda2. This is so strange, since all the udev settings has been rebooted. Should I completely remove the /dev directory and reemerge udev (or maybe something more)? Maybe the problem is in the dev nodes themselves... 
[second edit and fix]: Edited /etc/conf.d/rc and put RC_DEVICE_TARBALL="no" on it. That solved the issue. I'm still figuring what was happening, but, since this solved the issue I think that the tarball got corrupted with that hard crash. Anyway, I haven't been able to find how to restore it, so, if someone has any idea can post it here, even if this post is now closed. Thaks to all that read this, and I hope this will be usefull for anyone more in the future.  |
|
Kernel & Hardware
