Am 07.03.19 um 08:32 schrieb Bob Tracy: > On Thu, Feb 28, 2019 at 07:36:37PM +0100, Michael Biebl wrote: >> Control: tags -1 + moreinfo >> >> Please attach the full output "journalctl -alb" output of such a failed >> boot. >> >> I'd also be interested in the output of >> udevadm info /sys/class/block/sda2
That output looks ok from what I can see.
I have no idea why you don't have a corresponding active
dev-sda2.device
> Apologies for the delay in responding. Wanted to wait for 5.0.0-final
> to be released, and then I had to wait another 48 hours for the build to
> finish.
>
> Requested command output attached. I ran "journalctl -alb" in emergency
> mode prior to performing any of the manual workaround steps I normally do
> to bring the system up multi-user. Only the first of the "failed to start"
> local file systems ("/dev/sda5", corresponding to "/tmp") showed up in the
> output.
>
> Several packages updated since original bug report. No change in symptoms.
> Current kernel is 5.0.0, systemd and udev are 241-1, and initramfs-tools*
> are 0.133. Curiously, I've been seeing syslog messages from
> "syslogd-fstab-generator" to the effect of "Running in a container, ignoring
> fstab device entry for /dev/sda4" (where "/dev/sda4" is my swap partition).
> Same log entry for the cdrom device (/dev/hda). No virtualization support
> of any kind has consciously been installed/configured, so where is this
> notion of running in a container coming from?
https://github.com/systemd/systemd/blob/master/src/fstab-generator/fstab-generator.c#L109
https://github.com/systemd/systemd/blob/master/src/basic/virt.c#L430
There are various tests used to determine if the system runs in a
container environment.
What does systemd-detect-virt say?
--
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
