Your message dated Tue, 16 Mar 2021 02:35:33 +0100
with message-id <[email protected]>
and subject line Re: Bug#985255: Systemd initiates fsckd for no apparent reason
has caused the Debian Bug report #985255,
regarding Systemd initiates fsckd for no apparent reason
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
985255: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985255
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 247.3-1
Every few system restarts fsckd runs and fails with the following error message:
[TIME] timed out waiting for device /dev/sdb2
I am subsequently dropped into a terminal session (busybox?)
There are no problems with the filesystem or the hard disk (SSD) in question.
Pressing Ctl-Alt-Del almost always results in a successful reboot. Rarely,
the system will halt again with the same error message requiring yet
another reboot. In any case, the system eventually boots without error.
This problem first appeared on a hard disk that has since been replaced.
Manually initiating fsck on /dev/sdb2 has never resulted in an error
on either the old disk or the new one. Occasionally, systemd reports an
error indicating missing system files (/dev/sda1). Again, manually
running fsck against the referenced partition has never resulted in an error.
I tried sending this via reportbug, but I've never received an email reply
indicating it was received. I was previously running Debian Buster without
issue. I upgraded to Debian Bullseye several months ago, but did not
experience this problem until sometime after the initial upgrade.
If you require additional information, feel free to contact me with your
request.
--- End Message ---
--- Begin Message ---
[please always CC the bug report on replies]
Am 16.03.2021 um 01:20 schrieb haagmj:
Requested info attached. The exact error message was provided in my
initial report. In any case, I know of no way to take a screenshot from
within a terminal.
---- On Mon, 15 Mar 2021 18:37:05 +0800 *Michael Biebl
<[email protected]>* wrote ----
Control: tags -1 + moreinfo
Please provide your /etc/fstab, an exact error message (screenshot is
fine), the output of "udevadm info --export-db" and a "journalctl -alb"
from a failed boot.
Apparently /dev/sdb2 is not attached during boot, but you have listed it
in /etc/fstab. Therefore systemd is waiting for it.
You probably want noauto or nofail here, but not defaults.
Anyway, not a bug in systemd, thus closing
Regards,
Michael
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
