From: ralfconn <mentadent47@yahoo.com>
To: "gentoo-user@lists.gentoo.org" <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] fsck operational error
Date: Sat, 21 Sep 2024 18:16:20 +0200 [thread overview]
Message-ID: <41040b25-52a7-484a-9261-1f115f2d5818@yahoo.com> (raw)
In-Reply-To: 41040b25-52a7-484a-9261-1f115f2d5818.ref@yahoo.com
Hello,
Upon boot OpenRc shows this warning:
fsck: checking local filesystem
fsck: fsck.ext4 device or resource busy while trying to open /dev/nvme0n1p6
fsck: filesystem mounted or opened exclusively by another program?
fsck: operational error
This is the root filesystem, and in fstab it is listed as:
UUID=xxxx-xxxx-xxxx / ext4 noatime,discard 0 1
/etc/conf.d/fsck contains only:
fsck_on_battery="YES"
fsck_shutdown="NO"
fsck_abort_on_errors="YES"
This started a week ago after a system update when I switched from
kernel 6.10.9 to 6.10.10 (~amd64). That day there was also an update of
OpenRc to version 0.55.
Has anybody seen the same?
thanks,
raf
parent reply other threads:[~2024-09-21 16:16 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <41040b25-52a7-484a-9261-1f115f2d5818.ref@yahoo.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41040b25-52a7-484a-9261-1f115f2d5818@yahoo.com \
--to=mentadent47@yahoo.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox