oblib
May 7th, 2010, 04:14 PM
I did an upgrade from 9.10 to 10.04 and something broke the init scripts. When I boot, most of the startup scripts don't run (cron, anacron, courier imap, apache, lirc, smbd, for example), and 'runlevel' reports "Unknown." However, if I run 'sudo init 2' everything starts up just fine.
In an effort to fix the problem, I did a clean 10.04 install on another partition and installed all my packages. Everything seemed to be working, but I didn't check thoroughly because I thought it should. I then went ahead and compiled and installed ffmpeg, mplayer, lirc, and mythtv and added my custom init scripts and rebooted.
It failed init again. So I figured it must be one of my init scripts. So I removed them again and rebooted. Everything started again, so I started testing one script at a time. What I discovered was that even with none of my scripts installed (so basically a virgin /etc/init.d/), every once in a while, the init process would still fail.
On the new partition, when it failed, modules would fail to load as well, so I had no sound or video capture devices. This is not fixed by "sudo init 2".
This does not happen on my original partition. It fails every time on the original, but I always have all of my devices.
I'm willing to admit that it's something wrong I did, but the system worked perfectly under 9.10, so something happened with 10.04 to break it. I just don't know how to debug it.
What is the easiest way to find out what's happening with the init sequence? Why would it fail to acheive runlevel 2?
BTW, it seems similar to this thread: http://ubuntuforums.org/showthread.php?t=1471004 which is where I learned to do 'init 2' to band-aid it.
Thanks in advance.
In an effort to fix the problem, I did a clean 10.04 install on another partition and installed all my packages. Everything seemed to be working, but I didn't check thoroughly because I thought it should. I then went ahead and compiled and installed ffmpeg, mplayer, lirc, and mythtv and added my custom init scripts and rebooted.
It failed init again. So I figured it must be one of my init scripts. So I removed them again and rebooted. Everything started again, so I started testing one script at a time. What I discovered was that even with none of my scripts installed (so basically a virgin /etc/init.d/), every once in a while, the init process would still fail.
On the new partition, when it failed, modules would fail to load as well, so I had no sound or video capture devices. This is not fixed by "sudo init 2".
This does not happen on my original partition. It fails every time on the original, but I always have all of my devices.
I'm willing to admit that it's something wrong I did, but the system worked perfectly under 9.10, so something happened with 10.04 to break it. I just don't know how to debug it.
What is the easiest way to find out what's happening with the init sequence? Why would it fail to acheive runlevel 2?
BTW, it seems similar to this thread: http://ubuntuforums.org/showthread.php?t=1471004 which is where I learned to do 'init 2' to band-aid it.
Thanks in advance.