public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Larry the Plumber <dzjfqy7ioz@ol1y.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] biosdevname or equivalent for disks: did the order change on a specific, recent, kernel version?
Date: Wed, 11 Sep 2024 14:15:44 +0100	[thread overview]
Message-ID: <CAJZjf_w5mWdizPVmCS4rSaixQE0u-SmL1b2VmsXduF09jLg30A@mail.gmail.com> (raw)

Hi!
A bit of history first: my Fedora, then (after reinstall) my openSUSE
then (after reinstall) my Gentoo failed during boot. I thought it was
something related to dracut so I've been adding `hostonly = false` to
dracut.conf on all my home machines.

In summary, yesterday it failed on my Gentoo so I had to investigate.
* I had enable `unstable` use flags for the kernel only.
* I hadn't double-check the boot entries created.
* Power went off (no UPS yet) so I booted the new kernel.
* It didn't boot. I fixed two things: changed the partition id of
LUKSed swap from swap id to LVM id, to prevent systemd attempting to
mount it at boot (and failing). Secondly, I checked the fstab and
noticed all dev nodes were wrong (I have two SSD).
* After fixing the dev nodes in fstab the system booted properly.

This probably explains the Gentoo failure, since other distros (and
me, starting some day) use UUID in fstab.

So, my question is:
Has anyone any input on mysterious failures across several distros,
including Gentoo, around kernel 6.9.x <> 6.10.x?


             reply	other threads:[~2024-09-11 13:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-11 13:15 Larry the Plumber [this message]
2024-09-11 13:27 ` [gentoo-user] biosdevname or equivalent for disks: did the order change on a specific, recent, kernel version? Alan J. Wylie
2024-10-08 11:06   ` Larry the Plumber
2024-10-08 11:23     ` Alan J. Wylie

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=CAJZjf_w5mWdizPVmCS4rSaixQE0u-SmL1b2VmsXduF09jLg30A@mail.gmail.com \
    --to=dzjfqy7ioz@ol1y.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