Github messages for voidlinux
 help / color / mirror / Atom feed
From: dezifit <dezifit@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: dracut/initramfs: 6.6.54_1 fails to mount root partition
Date: Tue, 08 Oct 2024 15:24:56 +0200	[thread overview]
Message-ID: <20241008132456.E4DC82AC7E@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-52546@inbox.vuxu.org>

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

New comment by dezifit on void-packages repository

https://github.com/void-linux/void-packages/issues/52546#issuecomment-2399843162

Comment:
Some more testing shows that the dracut-emergency environment is able to mount another JFS partition just fine. Only the root partition fails, even after a forced filesystem check, which just confirms a valid superblock and clean filesystem.

I tried with kernel 6.11.2 (also fails to boot, same symptom), did a memcheck (passed without error) and finally switched back to the still working kernel 6.6.51 after running out of ideas.

It looks like a strange issue of the specific root partition, therefore I will close this ticket if there is no participation.

  reply	other threads:[~2024-10-08 13:24 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-07 16:16 [ISSUE] " dezifit
2024-10-08 13:24 ` dezifit [this message]
2024-10-09 12:19 ` witseid
2024-10-09 19:34 ` Katnjia
2024-10-09 19:37 ` Katnjia
2024-10-09 20:38 ` dkwo
2024-10-09 22:22 ` classabbyamp
2024-10-11 11:05 ` dezifit
2024-10-11 11:25 ` witseid
2024-10-11 11:30 ` witseid
2024-10-11 11:30 ` witseid
2024-10-11 11:34 ` witseid
2024-10-11 14:55 ` classabbyamp
2024-10-11 15:25 ` dezifit
2024-10-11 15:36 ` classabbyamp
2024-10-11 15:48 ` dezifit
2024-10-11 15:52 ` classabbyamp
2024-10-11 16:02 ` dezifit
2024-10-11 16:11 ` classabbyamp
2024-10-23  8:32 ` dezifit

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=20241008132456.E4DC82AC7E@inbox.vuxu.org \
    --to=dezifit@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).