public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: fsck operational error
Date: Wed, 09 Apr 2025 23:08:37 +0100	[thread overview]
Message-ID: <1920315.tdWV9SEqCh@rogueboard> (raw)
In-Reply-To: <691540be-2caf-479f-b5e9-d4c43f61e54a@yahoo.com>

[-- Attachment #1: Type: text/plain, Size: 1062 bytes --]

On Wednesday, 9 April 2025 17:38:50 British Summer Time ralfconn wrote:
> Il 21/09/24 18:16, ralfconn ha scritto:
> > 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 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.
> 
> Old thread, no answer, but now I get the same message on another box,
> just after I reconfigured the kernel for hardening
> (https://kspp.github.io/Recommended_Settings), so it was not an OpenRC
> issue.
> 
> I'll update if I find the option that causes the issue, just to close
> the thread for the posterity :-).
> 
> raffaele

I don't run a hardened setup and don't have this problem.

Is your fsck service in boot level?

~ # rc-update -s -v | grep fsck
                 fsck | boot

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2025-04-09 22:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <41040b25-52a7-484a-9261-1f115f2d5818.ref@yahoo.com>
2024-09-21 16:16 ` [gentoo-user] fsck operational error ralfconn
2025-04-09 16:38   ` [gentoo-user] " ralfconn
2025-04-09 22:08     ` Michael [this message]
2025-05-22 17:16     ` yahoo
2025-05-22 18:13       ` Dale
2025-05-22 20:02         ` yahoo
2025-05-22 21:29           ` yahoo
2025-05-22 22:08             ` Dale

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=1920315.tdWV9SEqCh@rogueboard \
    --to=confabulate@kintzios.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