No, it wasn't. For me it's often like this.
1. Non-working boot with runlevel N 2.
2. Reboot. Non-working boot. runlevel unknown.
3. Reboot. Non-working boot. runlevel unknown.
4. Reboot. Working boot. Runlevel N 2
--
Some services not started on boot, runlevel returns unknown
cat /var/log/boot.log
fsck from util-linux-ng 2.17.2
fsck from util-linux-ng 2.17.2
udevd[345]: BUS= will be removed in a future udev version, please use
SUBSYSTEM= to match the event device, or SUBSYSTEMS= to match a parent device,
in /lib/udev/rules.d/40-alsa-firmware-loaders.rules:9
runlevel
N 2
initctl list
alsa-mixer-save stop/waiting
avahi-daemon start/running, process 753
mountall-net stop/waiting
nmbd start/running, process 995
rc stop/waiting
rsyslog start/running, process 697
tty4 start/running, process 794
udev start/running, process 353
upstart-udev-bridge
And now, after another restart, I get: runlevel: unknown
--
Some services not started on boot, runlevel returns unknown
https://bugs.launchpad.net/bugs/543506
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I am experiencing the exact same problem (well different services, but
the same symptoms). some of the services in rc2 is starting, sometimes
all of them sometimes just a few.
Runlevel outputs:
runlevel 'unknown'
If I change to runlevel 2 by issuing init 2, the services starts.
Both tried an
