Am 20.03.2011 12:33, schrieb Florian Kriener: > Package: systemd > Version: 19-1 > Severity: normal > > --- Please enter the report below this line. --- > Today I wanted to take a look at systemd and was stopped early. At first > it look as if systemd hung after cryptsetup from initrd but after using > some kernel command line options to increase the verbosity of systemd I > found that systemd hung when starting rsyslog (if I interpret "Logging > Daemon" correctly"). Here are the last lines: > > Starting /tmp... > Starting Remoount API VFS... > Starting Runtime Directory... > Starting File System Check on Root Device... > Starting Lock Directory... > Starting Logging Daemon... > > I then pressed Ctrl-Alt-Del, which lead to console fonts and keymap > initialization and some error messages.
Do you have any special setup (cryptsetup, LVM, partition layout like /usr on a separate partition)? Could you boot with systemd.log_level=debug and systemd.log_target=kmsg please and check if that reveals more. It's most likely not a rsyslog related issue. "Logging Daemon" is systemd's internal logger service provided by systemd-logger.service. My guess is that systemd is waiting for some devices to show up. You could wait for at least a minute to wait for the timeout and check if the boot process continues. If you then can login, check the status with systemctl list-jobs and systemctl --full --all | grep failed. If you are able to connect to your system via a serial console to the a full log of the boot process, that would be most helpful. Michael Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
