From: ihameed <ihameed@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: After recent upgrade, void lands at `dracut>` prompt
Date: Thu, 30 Jun 2022 23:38:36 +0200 [thread overview]
Message-ID: <20220630213836.hq5zCnnT02VaSs5euoOFJbW1pLKA3c_jtIR-ZLO3kxc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37757@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 971 bytes --]
New comment by ihameed on void-packages repository
https://github.com/void-linux/void-packages/issues/37757#issuecomment-1171703273
Comment:
> This is definitely a duplicate of #37667. Unfortunately, the only way to fix your initramfs is to grab a live image (I prefer [hrmpf](https://github.com/leahneukirchen/hrmpf)), mount your root and `/boot`, chroot in, add the change to the Dracut configuration, and then regenerate all initramfs images. (The easiest way to do that is `xbps-reconfigure -f zfs`.)
I had (and worked around locally before discovering https://github.com/void-linux/void-packages/issues/37667) this same problem. I didn't have any spare bootable media handy to use for a recovery image. Another way to get your full multi-user setup running so that you can rebuild this initramfs shell script convolution is to manually `mount /dev/path/to/my/root/volume /sysroot` in the dracut recovery shell. Then type `exit`. Startup should resume normally.
prev parent reply other threads:[~2022-06-30 21:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 11:04 [ISSUE] " zenny
2022-06-30 11:25 ` ahesford
2022-06-30 11:25 ` [ISSUE] [CLOSED] " ahesford
2022-06-30 11:45 ` zenny
2022-06-30 11:52 ` ahesford
2022-06-30 14:17 ` zenny
2022-06-30 21:38 ` ihameed [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=20220630213836.hq5zCnnT02VaSs5euoOFJbW1pLKA3c_jtIR-ZLO3kxc@z \
--to=ihameed@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).