On 15/03/2021 02.38, David T-G wrote:
Hi, all --
I have an existing Leap 15.2 system with an nvme SSD, and I'm happy with how it boots. It does not, such that I have ever noticed, exhibit this behavior.
However, I have also just built another Leap 15.2
diskfarm:~ # grep . /etc/SUSE-brand /etc/os-release ; uname -a /etc/SUSE-brand:openSUSE /etc/SUSE-brand:VERSION = 15.2 /etc/os-release:NAME="openSUSE Leap" /etc/os-release:VERSION="15.2" /etc/os-release:ID="opensuse-leap" /etc/os-release:ID_LIKE="suse opensuse" /etc/os-release:VERSION_ID="15.2" /etc/os-release:PRETTY_NAME="openSUSE Leap 15.2" /etc/os-release:ANSI_COLOR="0;32" /etc/os-release:CPE_NAME="cpe:/o:opensuse:leap:15.2" /etc/os-release:BUG_REPORT_URL="https://bugs.opensuse.org" /etc/os-release:HOME_URL="https://www.opensuse.org/" Linux diskfarm 5.3.18-lp152.63-default #1 SMP Mon Feb 1 17:31:55 UTC 2021 (98caa86) x86_64 x86_64 x86_64 GNU/Linux
system on a single SATA SSD, and as it boots is reports
[ slider ] A start job is running for dev-disk-by\x2dlabel-System.device (nns / 1min 30s)
that always runs to the 90-second timeout and then fails. What is that, and how do I make it not?!? The behaviour is just that message, or is there a problem?
-- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)