bootup failure with F14(Aug-27 tree) with systemd (after adding the symlinks & reboot)

Kashyap Chamarthy kashyapc at fedoraproject.org
Sat Aug 28 10:46:23 UTC 2010


Hi,

I still notice fresh F14(Aug27-build)  install(a kvm guest) doesn't boot into runlevel-3 
with systemd.


I added these two symlink's from Lennart's email, and rebooted without any special kernel 
parameters
-----------------------------
# ln -s /lib/systemd/system/multi-user.target /etc/systemd/system/default.target)

# ln -sf /lib/systemd/system/multi-user.target /etc/systemd/system/default.target
-----------------------------



What I see on the console:
##################################################################################################
EXT3-fs (sda3): mounted filesystem with ordered data mode
SELinux: initialized (dev sda3, type ext3), uses xattr
[  OK  ]
Enabling local filesystem quotas:  [  OK  ]
Enabling /etc/fstab swaps:  [  OK  ]
SELinux: initialized (dev binfmt_misc, type binfmt_misc), uses genfs_contexts
rc.sysinit used greatest stack depth: 3552 bytes left
Starting LSB: processor frequency scaling support...
Starting LSB: Moves the generated persistent udev rules to /etc/udev/rules.d...
Starting Rescue Shell...
Welcome to rescue mode. Use "systemctl default" to activate default mode.
Retrigger failed udev eventsStarting D-Bus System Message Bus...
[  OK  ]
Give root password for maintenance
(or type Control-D to continue):
###############################################################################
Attempt to go to init3 after reboo
------------------------------------------------------------------------------
init[1]: prefdm.service: main process exited, code=exited, status=1
init[1]: prefdm.service holdoff time over, scheduling restart.
init[1]: Unit prefdm.service entered maintenance state.
Starting Display Manager...
[  OK  ]
Starting LSB: The rpcbind utility is a server that converts RPC program numbers into 
universal addresses. It must be running on the host to be able to make RPC calls on a 
server on that machine....
Starting rpcbind: Starting Display Manager...
[  OK  ]
Starting LSB: Starts the RPCSEC GSS client daemon...
Starting LSB: Start and stop the MD software RAID monitor...
Starting LSB: Moves the generated persistent udev rules to /etc/udev/rules.d...
Starting LSB: Start up the NFS file locking sevice...
Starting LSB: Mount and unmount network filesystems....
Starting LSB: Starts the NFSv4 id mapping daemon...
Retrigger failed udev eventsStarting mdmonitor: [  OK  ]
[  OK  ]
Starting NFS statd: Starting RPC idmapd: Starting Display Manager...
[  OK  ]
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
SELinux: initialized (dev rpc_pipefs, type rpc_pipefs), uses genfs_contexts
[  OK  ]
Starting Display Manager...
Starting Display Manager...
Starting Display Manager failed.
Mounting other filesystems:  [  OK  ]
Starting LSB: This is a daemon for collecting and maintaing information about hardware 
from several sources. See http://www.freedesktop.org/Software/hal...
Starting HAL daemon: [  OK  ]
Starting LSB: Start up the OpenSSH server daemon...
Starting LSB: run cron daemon...
Starting LSB: Starts/stop the "at" daemon...
Starting LSB: start and stop sendmail...
Starting /etc/rc.local Compatibility...
Starting Getty on tty6...
Starting Getty on tty5...
Starting crond: Starting Getty on tty2...
Starting sshd: Starting Getty on tty3...
Starting Getty on tty4...
Starting LSB: Daemon to access a smart card using PC/SC...
[  OK  ]
Starting sendmail: Starting PC/SC smart card daemon (pcscd): Starting atd: [  OK  ]
[  OK  ]
[  OK  ]
Starting sm-client: [  OK  ]
[  OK  ]
Starting ACPI Event Daemon failed.

##############################################################################################

Note: But I later booted into the machine with init=/sbin/upstart


Is there anything still I'm missing?

/kashyap


More information about the test mailing list