Github messages for voidlinux
 help / color / mirror / Atom feed
From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] dracut/initramfs: 6.6.54_1 fails to mount root partition
Date: Wed, 20 Nov 2024 02:41:19 +0100	[thread overview]
Message-ID: <20241120014119.8BE612ED71@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: 1296 bytes --]

Closed issue by dezifit on void-packages repository

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

Description:
### Is this a new report?

Yes

### System Info

Void 6.6.54_1 x86_64 libc

### Package(s) Affected

linux-6.6_1

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

After updating the kernel from 6.6.51_1 to 6.6.54_1 the systems fails to mount the root partition and boots into the recovery console.

 `/run/initrunfs/rdsosreport.txt` shows:
 `dracut Warning: Failed to mount -t jfs -o ro,ro /dev/disk/ny-uuid/<correct uuid> /sysroot`

Manual invocation of `fsck /dev/sda1` gives `Filesystem is clean.`, but manual mount with `mkdir -p /mnt; mount /dev/sda1 /mnt` fails with:
`mount: /mnt: wrong fs type, bad option, bad superblock on /dev/sda1`

Choosing the last working kernel `6.6.51` in grub boots the (grub legacy bios) system without any issue. I have already recreated the initramfs with `dracut --force --kver $(uname --kernel-release)`, but it fails with the same same error. Are there JFS related changes in the kernel configuration? Any ideas?

### Expected behaviour

Regular system boot.

### Actual behaviour

Can't mount root partition.

### Steps to reproduce

100% reproducible on the failing system.

      parent reply	other threads:[~2024-11-20  1:41 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-07 16:16 [ISSUE] " dezifit
2024-10-08 13:24 ` dezifit
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
2024-11-20  1:37 ` jozzsi
2024-11-20  1:38 ` jozzsi
2024-11-20  1:41 ` classabbyamp
2024-11-20  1:41 ` classabbyamp [this message]

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=20241120014119.8BE612ED71@inbox.vuxu.org \
    --to=classabbyamp@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).