cannot boot beyond runlevel 1

Felix Miata mrmazda at earthlink.net
Sun Jan 2 17:37:43 UTC 2011


On 2011/01/01 20:57 (GMT-0700) Michal Jaegermann composed:

> On Sat, Jan 01, 2011 at 07:11:14PM -0500, Felix Miata wrote:

>>  I've never found the manual page explaining how to do
>>  with upstart the things I knew how to do with sysvinit.

> You have the same service scripts but if you moved up from F14 to
> rawhide then you will be using systemd.  Your /etc/inittab is likely
> replaced.  Check explanatory comments there.

They seem minimally useful. This is the entirety of inittab:
# inittab is no longer used when using systemd.
#
# ADDING CONFIGURATION HERE WILL HAVE NO EFFECT ON YOUR SYSTEM.
#
# Non-SysV tasks for individual runlevels live in 
/lib/systemd/system/runlevelX.target.wants
#
# Ctrl-Alt-Delete is handled by /etc/systemd/system/ctrl-alt-del.target
#
# To set a default runlevel <X>, run:
#
# ln -s /lib/systemd/system/runlevel<X>.target /etc/systemd/system/default.target

  >>  Investigate where?

> Where it gets stuck.  'sh -x /etc/init.d/network start' looks like a
> good beginning and you are following up from this.

If I boot to runlevel 1 and do that, network is up, Google is pingable.

On a normal boot to runlevel 3 it appears to proceed well beyond that. Maybe 
those logs are misleading? first line on screen after attempting runlevel 3 
boot is:
Starting Avahi mDNS/DNS-SD Stack...
following is a bunch of LSB: lines, last of which is:
Mount and umnount network filesystems....
Starting /etc/rc.local Compatibility...
Starting Terminate Plymouth Boot Screen...
Retrigger failed udev events
Starting cups: Starting sshd: Mounting other filesystems: Starting NFS statd: 
Starting RPC idmapd: [42.171289] RPC: Registered udp transport module.
...
starting rpcsvcgsse (via systemctl...
Initializing OpenCT smart card...
(some USB lines)
Starting LSB: Daemon to access a smart c...
Starting PC/SC smart c...
Starting HAL Hardware Manager...
[43.414506] Installing knfsd...
Starting NFS services:
Starting NFS daemon: [44.0996085] NFSD: Using /var/lib/nfs/v4recovery as the 
NFSv4 state recovery directory
[44.311521] NFSD: starting 90-second grace period
Starting NFS mountd:                                        [OK]
[44.708309] uhci_hcd 0000:00:1d.0: PCI INT A disabled
[44.724072] ehci_hcd 0000:00:1d.7: PCI INT B disabled
                                                             [OK]
[44.712166] uhci_hcd 0000:00:1d.1: PCI INT C disabled
[44.719190] uhci_hcd 0000:00:1d.2: PCI INT D disabled
                                                             [OK]

 From here, nothing more happens, no keyboard response, except to shift-PgUp 
or CAD.

 From the former, I see following "eth0: link becomes ready" four lines of:
grep: ifcfg-ifcfg-: No such file or directory, then:
Bringing up interface ifcfg-:
Starting LSB:...

Maybe that's about an unconfigured/unwanted/unneeded (onboard) eth1? eth0 is 
a configured PCI card.

The only instances of "failed" I see doing Shift-PgUps are:
Starting Recreate Volatile Files and Directories failed.
[33.849718] systemd[1]: Unit systemd-tempfiles-setup.service entered failed 
state.
...last write time is in the future...

until I get above mounting messages and see at least 9 lines of of invalid 
EDID....

then further up, 3 lines of failed to write '0' to /proc/sys/.../tables: no 
such...

I tried removing /etc/exports, /etc/nfs.conf and all lines containing NFS 
from /etc/fstab, but that didn't help either.

>>  I've got Rawhide running and yum updated further via chroot from Factory
>>  boot, but don't know what to look for as indicated above.

> If you booted to level 1 then 'chkconfig network off' and/or
> similar.  If you are just booting "normally" then you need to drop
> 'rhgb quiet' from a boot command and when a user space starts to

I've been stripping all instances of rhgb quiet from grub.conf for as long as 
they've been appearing there.

> show up you have a message on yor screen "For an interactive startup
> press I" or something pretty close.  It is pretty loud and clear.

I've been seeing that for a lot of years, but I don't see it now. Maybe it's 
getting lost in mode switches/switching, or maybe it's that little bit of 
illegible navy text on black background most of the way through init? How far 
along should it proceed before I try?
-- 
"How much better to get wisdom than gold, to choose
understanding rather than silver." Proverbs 16:16 NKJV

  Team OS/2 ** Reg. Linux User #211409

Felix Miata  ***  http://fm.no-ip.com/


More information about the test mailing list