| View previous topic :: View next topic |
| Author |
Message |
NewB
Apprentice
Joined: 08 Feb 2004
Posts: 224
|
 Posted: Sun Feb 19, 2006 9:59 pm Post subject: [Solved] boot fails after update |
 |
|
Hi,
I have a big problem after updating my system (I also removed gentoo-sources since I use nitro sources now). The boot fails when it starts trying to start the init scripts with the following error:
| Code: |
ERROR: <something cannot be run> until sysinit completes!
|
I realy need help on this one.... I have no idea how I can fix this. I remember that in the update was glibc, don't know if this has an influence on my problem...
thnx for your help...
Last edited by NewB on Sun Feb 19, 2006 11:35 pm; edited 1 time in total |
|
| Back to top |
|
 |
NewB
Apprentice
Joined: 08 Feb 2004
Posts: 224
|
| Posted: Sun Feb 19, 2006 10:10 pm Post subject: |
|
|
here are the package updated in my system update (the new version are listed):
app-shells/bash-3.1_p8
x11-libs/gtk+-2.8.12
media-video/mplayer-1.0.20060217
net-www/mplayerplug-in-3.21
media-video/spca5xx-20060202
sys-libs/glibc-2.3.6-r3
x11-misc/xchm-1.2
media-fonts/dejavu-2.0
media-sound/amarok-1.3.8
net-firewall/shorewall-3.0.4
app-cdr/gnomebaker-0.5.1-r2
app-laptop/thinkpad-5.9
sys-apps/baselayout-1.12.0_pre16-r1
x11-apps/ati-drivers-extra-8.22.5 |
|
| Back to top |
|
|
dgaffuri
Advocate
Joined: 05 Jun 2005
Posts: 2078
Location: Italy
|
| Posted: Sun Feb 19, 2006 10:23 pm Post subject: |
|
|
It's baselayout, when udev starts it creates a /dev/.rcsysinit which is later removed by /sbin/rc, but before starting scripts. That's intended to block network scripts starting too early (with fs not mounted rw) because of autoloaded modules and hotplug. Don't know why it's not removed in your case, anyway. Which version of udev are you running?
_________________
Adopt an unanswered post
If you feel that your problem has been solved please edit the top post and add [solved] to the subject |
|
| Back to top |
|
|
NewB
Apprentice
Joined: 08 Feb 2004
Posts: 224
|
| Posted: Sun Feb 19, 2006 10:26 pm Post subject: |
|
|
| I'm running udev version 084 |
|
| Back to top |
|
|
dgaffuri
Advocate
Joined: 05 Jun 2005
Posts: 2078
Location: Italy
|
| Posted: Sun Feb 19, 2006 10:37 pm Post subject: |
|
|
It's working fine here with udev-079-r1, but I've never heard of similar problems even with 084. Which scripts fail exactly? They should be only the critical ones, that is
| Code: | | checkroot hostname modules checkfs localmount clock bootmisc |
unless you have listed something different in
| Code: | | /etc/runlevels/boot/.critical |
_________________
Adopt an unanswered post
If you feel that your problem has been solved please edit the top post and add [solved] to the subject |
|
| Back to top |
|
|
NewB
Apprentice
Joined: 08 Feb 2004
Posts: 224
|
| Posted: Sun Feb 19, 2006 10:41 pm Post subject: |
|
|
| I didn't specify anything in /etc/runlevels/boot/.critical. I just downgraded baselayout now and reboot. If I still have the problem I will write down which scripts fails exactly... |
|
| Back to top |
|
|
NewB
Apprentice
Joined: 08 Feb 2004
Posts: 224
|
| Posted: Sun Feb 19, 2006 10:58 pm Post subject: |
|
|
the boot stops just after "caching service dependencies and everything fails after: checkroot, hostname, modules, checkfs, localmount, clock, bootmisc, alsasound,.... (this was in the order of the errors)
-> baselayout downgrade didn't help |
|
| Back to top |
|
|
dgaffuri
Advocate
Joined: 05 Jun 2005
Posts: 2078
Location: Italy
|
| Posted: Sun Feb 19, 2006 11:18 pm Post subject: |
|
|
It's strange. Looking better, critical services are directly sourced from /sbin/rc and don't use /sbin/runscript, so they should not give that error (it's at line 26 of /sbin/runscript.sh). Besides this on first fail of a critical service the system would su to a prompt and then reboot. I'll try to upgrade udev to 084 to see if I'm able to reproduce the problem.
Edit: it works well with 084 too, which kernel are you running?
_________________
Adopt an unanswered post
If you feel that your problem has been solved please edit the top post and add [solved] to the subject
Last edited by dgaffuri on Sun Feb 19, 2006 11:26 pm; edited 1 time in total |
|
| Back to top |
|
|
NewB
Apprentice
Joined: 08 Feb 2004
Posts: 224
|
| Posted: Sun Feb 19, 2006 11:25 pm Post subject: |
|
|
Thank you for your help!
I'm currently downgrading udev and glibc to the latest stable version of portage (since I did that with baselayout already). Will see if this helps... |
|
| Back to top |
|
|
dgaffuri
Advocate
Joined: 05 Jun 2005
Posts: 2078
Location: Italy
|
| Posted: Sun Feb 19, 2006 11:26 pm Post subject: |
|
|
I would exclude that glibc have something to do with this.
_________________
Adopt an unanswered post
If you feel that your problem has been solved please edit the top post and add [solved] to the subject |
|
| Back to top |
|
|
NewB
Apprentice
Joined: 08 Feb 2004
Posts: 224
|
| Posted: Sun Feb 19, 2006 11:34 pm Post subject: |
|
|
Ok back to normal, after downgrading udev to version 079-r1 everthing works again. But I'm still wondering why I had this problem since I was running udev version 084 for a while without any problems!
-> I'm running nitro-sources 2.6.14-nitro2 |
|
| Back to top |
|
|
dgaffuri
Advocate
Joined: 05 Jun 2005
Posts: 2078
Location: Italy
|
| Posted: Sun Feb 19, 2006 11:54 pm Post subject: |
|
|
Don't know really, I'm running now with udev-084 and baselayout-1.12.0_pre16-r1 with no problems (except that after upgrading baselayout dhcp will not work anymore for my ipw2200 if I use iwconfig, but that's another story). The kernel version is different, I'm using vanilla 2.6.16-rc4.
_________________
Adopt an unanswered post
If you feel that your problem has been solved please edit the top post and add [solved] to the subject |
|
| Back to top |
|
|
shimbob
Tux's lil' helper
Joined: 13 Sep 2003
Posts: 136
|
| Posted: Thu Mar 16, 2006 6:57 am Post subject: ditto |
|
|
This problem just happened to me during a fresh installation.
I dont think I had initially installed udev 84, but reemerging udev 79 and baselayout cleared the problem
wierd, whatever. |
|
| Back to top |
|
|
kluge
n00b
Joined: 20 Mar 2006
Posts: 1
|
| Posted: Mon Mar 20, 2006 7:15 am Post subject: |
|
|
| This also happened to me during a fresh install with standard udev 79 and baselayout. It appears that order matters here! I emerged baselayout then udev, and ran into the problem. When I emerged udev and then baselayout, the errors went away. |
|
| Back to top |
|
|
elabdel
n00b
Joined: 19 Apr 2004
Posts: 71
Location: France
|
| Posted: Sun Apr 02, 2006 10:55 am Post subject: |
|
|
Hello
I had the same problem after the fresh install on my laptop, and I have just solved this problem by removing /dev/.rcsysinit
I don't if this have any other effects but my system works well. |
|
| Back to top |
|
|
Arvernux
n00b
Joined: 20 May 2005
Posts: 30
Location: Loire, France
|
| Posted: Wed Apr 26, 2006 8:04 am Post subject: |
|
|
I had the same problem after a fresh install, but I could not see the .rcsysinit file.
I removed all the /dev and restart computer.
The /dev fix at the restart recreated the /dev, and it works.
_________________
Arvernux's boxes
Core i7 ; 12Go ; Nvidia GeForce 210
XP2500+ ; 512Mo ; NVidia GeForce 6200
portable targa visionnary XP2400
Comité de lutte contre le langage sms et les fautes volontaires |
|
| Back to top |
|
|
SilverDirk
n00b
Joined: 06 Aug 2004
Posts: 32
|
| Posted: Wed Jan 03, 2007 2:53 am Post subject: Also ran into it |
|
|
Just did a fresh install off 2006.1 and ran into this. Found this thread, checked my system and sure enough, I had the file /dev/.rcsysinit, and it was contained in the root partition, as seen by
| Code: | mkdir /tmp/root
mount --bind / /tmp/root
cd /tmp/root/dev
ls -l .r* |
Also, the dev tree was polluted with all the conceivable dev entries. As my whole goal in reinstalling was to go "pure udev" and write my own fun udev rules to make my system usable, I just (in addition to above)
| Code: | rm -r /tmp/root/dev
mkdir /tmp/root/dev
cp -a /dev/console /dev/null /dev/tty1 /tmp/root/dev/ |
and everything is working again.
If you didn't want to go "pure udev", removing the .rcsysinit would probably work. but strange things can happen with files underneath mount points of other filesystems. Or rather, very deterministic things for which I don't know the rules. What would happen if both the root fs and the dev fs contained a file named ".rcsysinit" and then you "rm /dev/.rcsysinit"? Does it get deleted from both filesystems? |
|
| Back to top |
|
|
|
Portage & Programming
