Re: systemd intermittent startup
On Sun, Nov 18, 2012 at 11:07 PM, Zenaan Harkness <zen@freedbms.net> wrote:
>
> First, systemd worked.
> Now it hangs on bootup, with the following messages:
> Loading, please wait...
> systemd-fsck[249]: /dev/sda5: clean, ...
> plus one similar fsck msg.
>
> After a minute or two it asks me for root pwd or to Ctrl-D for normal
> bootup. I can get a root prompt, but normal bootup just appears to
> hang again...
>
> So I now edit grub entry and use /sbin/init to log in to post this.
>
> Looking at syslog, I get these sorts of red-colored entries (when
> viewed with vim):
>
> Nov 19 14:31:12 localhost kernel: [ 0.045814] x2apic not enabled,
> IRQ remapping init failed
> Nov 19 14:31:12 localhost kernel: [ 0.723077] pci0000:00: ACPI
> _OSC request failed (AE_SUPPORT), returned control mask: 0x0d
> Nov 19 14:31:12 localhost kernel: [ 4.793539] iwlwifi 0000:03:00.0:
> request for firmware file 'iwlwifi-6000g2a-5.ucode' failed.
> Nov 19 14:31:12 localhost kernel: [ 4.811507] [drm] MTRR allocation
> failed. Graphics performance may suffer.
> Nov 19 14:31:12 localhost kernel: [ 7.202959] EXT4-fs (sda5):
> re-mounted. Opts: errors=remount-ro
>
> Nov 19 14:31:12 localhost named[2353]: error (network unreachable)
> resolving './DNSKEY/IN': 192.33.4.12#53
> Nov 19 14:31:12 localhost named[2353]: error (network unreachable)
> resolving './NS/IN': 192.33.4.12#53
> Nov 19 14:31:12 localhost named[2353]: error (network unreachable)
> resolving './DNSKEY/IN': 2001:500:1::803f:235#53
> Nov 19 14:31:12 localhost named[2353]: error (network unreachable)
> resolving './NS/IN': 2001:500:1::803f:235#53
> Nov 19 14:31:12 localhost named[2353]: error (network unreachable)
> resolving './DNSKEY/IN': 192.36.148.17#53
> Nov 19 14:31:12 localhost named[2353]: error (network unreachable)
> resolving './NS/IN': 192.36.148.17#53
> N
> ...
> Nov 19 14:31:12 localhost named[2353]: error (network unreachable)
> resolving 'B.ROOT-SERVERS.NET/AAAA/IN': 192.33.4.12#53
> Nov 19 14:31:12 localhost named[2353]: error (network unreachable)
> resolving 'B.ROOT-SERVERS.NET/AAAA/IN': 2001:500:1::803f:235#53
> Nov 19 14:31:12 localhost named[2353]: error (network unreachable)
> resolving 'D.ROOT-SERVERS.NET/AAAA/IN': 2001:500:1::803f:235#53
> Nov 19 14:31:12 localhost named[2353]: error (network unreachable)
> resolving 'C.ROOT-SERVERS.NET/AAAA/IN': 192.33.4.12#53
> Nov 19 14:31:12 localhost named[2353]: error (network unreachable)
> resolving 'D.ROOT-SERVERS.NET/AAAA/IN': 192.36.148.17#53
> Nov
> ...
>
> Then there's it gets into time gap territory - of about 12s first,
> then 20s, then 5s etc as seen from this point:
> Nov 19 14:31:15 localhost dbus[2425]: [system] Successfully activated
> service 'org.freedesktop.UPower'
> Nov 19 14:31:27 localhost acpid: client 2946[0:0] has disconnected
> Nov 19 14:31:46 localhost acpid: client connected from 2946[0:0]
> Nov 19 14:31:46 localhost acpid: 1 client rule loaded
> Nov 19 14:31:51 localhost dbus[2425]: [system] Activating service
> name='org.freedesktop.UDisks' (using servicehelper)
> Nov 19 14:31:51 localhost dbus[2425]: [system] Successfully activated
> service 'org.freedesktop.UDisks'
> Nov 19 14:32:05 localhost kernel: [ 62.696092] usb 3-1.4: new
> full-speed USB device number 5 using ehci_hcd
>
> Perhaps it's too early for systemd and its bootup time improvements
> (of course, not booting up takes a lot longer :) ??
It works fine.
You might need to fsck your disk but beyond that you're encountering
delays because your NIC's firmware isn't loading so you network's not
coming up and named is acting up.
Reply to: