An update.
After several more attempted reboots changing the
command line parameters failed, I logged in and
found that several commands, notably "systemctl"
failed with the message:
Failed to connect to bus: No such file or directory
What bus (dbus?) and why is it missing?
jl
On Sat, Dec 01, 2018 at 02:47:08PM -0500, Jon LaBadie wrote:
> My primary system was still running Fedora 26 and I'm in the process of
> updating stepwise using the dnf-system-upgrade plugin.
>
> The download and update to F27 seemed to go fine. But reboots fail
> and put me in "emergency/rescue" mode.
>
> Once I've logged in as root and su'ed to my personal account, I can
> turn networking on, run startx or mate-session for a desktop session.
> VirtualBox also works in the desktop.
>
> Hardware if pertainent:
> MB Gigabyte X79-UP4
> CPU Intel 3930K at 3.8GHz
> MEM 32GB
> VID nVidia GTX 660 Ti
> DISK 4, Mix of SSD and rotating,
> all but /boot managed by LVM
> KERN 4.18.19-100.fc27.x86_64
>
> I've cut and pasted the error messages from 'journalctl -b' (i.e.,
> the ones colored red) and include a little context on some.
>
> I do not see the problem, hopefully others will.
>
> Error output from "journalctl -b".
>
> There were 12 pairs of these messages varying only in the string
"_SB.C00X".
> The "X" was hex 0-B.
> Fedora 24, 25, and 26 gave these same messages but ran ok.
>
> Nov 30 18:29:22
cyber.jgcomp.com kernel: ACPI BIOS Error (bug): Could not resolve
[\TST0], AE_NOT_FOUND (20180531/psargs-330)
> Nov 30 18:29:22
cyber.jgcomp.com kernel: ACPI Error: Method parse/execution failed
\_SB.C000._TPC, AE_NOT_FOUND (20180531/psparse-516)
>
>
> The vbox modules mentioned in these message were loaded into the kernel
> at another point. VirtualBox (Windows 7) runs ok.
>
> Nov 30 18:29:22
cyber.jgcomp.com systemd-modules-load[304]: Failed to find module
vboxdrv
> Nov 30 18:29:22
cyber.jgcomp.com systemd-modules-load[304]: Failed to find module
vboxnetflt
> Nov 30 18:29:22
cyber.jgcomp.com systemd-modules-load[304]: Failed to find module
vboxnetadp
> Nov 30 18:29:22
cyber.jgcomp.com systemd-modules-load[304]: Failed to find module
vboxpci
>
>
> Nov 30 18:29:24
cyber.jgcomp.com systemd-udevd[825]: Specified group plugdev unknown
>
>
> These messages are correct, I'm not using ECC memory.
> Fedora 26 had same messages but worked fine.
>
> Nov 30 18:29:25
cyber.jgcomp.com kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel
#0 has DIMMs, but ECC is disabled
> Nov 30 18:29:25
cyber.jgcomp.com kernel: EDAC sbridge: Couldn't find mci handler
> Nov 30 18:29:25
cyber.jgcomp.com kernel: EDAC sbridge: Failed to register device with
error -19.
> ...
> Nov 30 18:29:25
cyber.jgcomp.com kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel
#0 has DIMMs, but ECC is disabled
> Nov 30 18:29:25
cyber.jgcomp.com kernel: EDAC sbridge: Couldn't find mci handler
> Nov 30 18:29:25
cyber.jgcomp.com kernel: EDAC sbridge: Failed to register device with
error -19.
>
>
> Only last line colored red by 'journalctl (hold queue overflow)'
>
> Nov 30 18:29:30
cyber.jgcomp.com kernel: kauditd_printk_skb: 115 callbacks
suppressed
> Nov 30 18:29:30
cyber.jgcomp.com kernel: audit: type=1131 audit(1543620570.726:96):
pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
msg='unit=
> Nov 30 18:29:30
cyber.jgcomp.com kernel: audit: audit_lost=38 audit_rate_limit=0
audit_backlog_limit=64
> Nov 30 18:29:30
cyber.jgcomp.com kernel: audit: kauditd hold queue overflow
>
>
> As above, only the "hold queue overflow" lines were colored
>
> Nov 30 18:29:34
cyber.jgcomp.com audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295
ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dracut-shutdown
comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=?
terminal=? res=success'
> Nov 30 18:29:34
cyber.jgcomp.com kernel: audit: type=1130 audit(1543620574.804:97):
pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
msg='unit=dracut-shutdown comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
> Nov 30 18:29:34
cyber.jgcomp.com kernel: audit: audit_lost=39 audit_rate_limit=0
audit_backlog_limit=64
> Nov 30 18:29:34
cyber.jgcomp.com kernel: audit: kauditd hold queue overflow
> Nov 30 18:29:34
cyber.jgcomp.com audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295
ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=plymouth-read-write
comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=?
terminal=? res=success'
> Nov 30 18:29:34
cyber.jgcomp.com kernel: audit: type=1130 audit(1543620574.816:98):
pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
msg='unit=plymouth-read-write comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
> Nov 30 18:29:34
cyber.jgcomp.com kernel: audit: audit_lost=40 audit_rate_limit=0
audit_backlog_limit=64
> Nov 30 18:29:34
cyber.jgcomp.com kernel: audit: kauditd hold queue overflow
> Nov 30 18:29:34
cyber.jgcomp.com kernel: audit: type=1131 audit(1543620574.816:99):
pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
msg='unit=plymouth-read-write comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
>
>
> This may be after login as root to "rescue mode" and "su-ing to my
personal account.
>
> Nov 30 18:29:54
cyber.jgcomp.com su[1727]: pam_systemd(su-l:session): Failed to
connect to system bus: No such file or directory
>
>
> Any ideas?
>
> Jon
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
https://getfedora.org/code-of-conduct.html
> List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org