From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] After recent upgrade, void lands at `dracut>` prompt
Date: Thu, 30 Jun 2022 13:25:59 +0200 [thread overview]
Message-ID: <20220630112559.R1Q7zNVoNTelXs5XL0dIuNaRvK2Lv_T5q3rdlnq9m9o@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: 1162 bytes --]
Closed issue by zenny on void-packages repository
https://github.com/void-linux/void-packages/issues/37757
Description:
Hi,
Context:
- Non-root-zfs (ext4) on a separate drive
- Mirrored zpool which is accessible
- The machine does not boot beyond dracut.
An upgrade two days back brought the kernel from booting and now inaccessible.
1. Prior to the `dracut` prompt it asks to enable `rd.debug`. I use the open sourced radeon driver for the graphics card as follows:
```
" $ lspci | grep VGA
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM]
```
How can I fix the issue?
2. However, it seems similar to https://github.com/void-linux/void-packages/issues/37667
But the machine is not accessible beyond the dracut prompt. How can one append `omit_dracutmodules+=" zfs "` to `/etc/dracut.conf.d/zfs.conf` (proposed by @zdykstra in https://github.com/void-linux/void-packages/issues/37667#issuecomment-1165599150 and endorsed by @ahesford in https://github.com/void-linux/void-packages/issues/37667#issuecomment-1165688484and regenerate the init file?
Cheers,
/z
next prev parent reply other threads:[~2022-06-30 11:25 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 ` ahesford [this message]
2022-06-30 11:45 ` zenny
2022-06-30 11:52 ` ahesford
2022-06-30 14:17 ` zenny
2022-06-30 21:38 ` ihameed
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=20220630112559.R1Q7zNVoNTelXs5XL0dIuNaRvK2Lv_T5q3rdlnq9m9o@z \
--to=ahesford@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).