From: Dan Egli <dan@newideatest.site>
To: gentoo-user@lists.gentoo.org, thelma@sys-concept.com
Subject: Re: [gentoo-user] fsck.fat 4.1 - File system couldn't be fixed
Date: Sat, 12 Dec 2020 17:04:25 -0700 [thread overview]
Message-ID: <7efaf7f6-ff4e-082f-4948-c461a691c562@newideatest.site> (raw)
In-Reply-To: <ed6aa63f-296d-04ce-275f-26696d4ddaaa@sys-concept.com>
You want to add it to the default command line in /etc/default/grub, if
it's needed. Frankly, as long as you have ext4 support built in to your
kernel (not a module) then I don't think you need it. I've gotten
similar warnings on my machines and they've never had a problem loading
the root FS. Oh, and it's not initframes, it is INIT RAM FS (no spaces,
of course). For Initial Ram Filesystem. :)
On 12/12/2020 12:47 PM, thelma@sys-concept.com wrote:
> I took care of this error, it was about cfg80211 enable wireless
> support (which I don't have) so I disable it in .config.
> But when I generate initframes I'm getting a warning:
>
> genkernel --install --kernel-config=/usr/src/linux/.config initramfs
>
> * WARNING... WARNING... WARNING...
> * Additional kernel parameters that *may* be required to boot properly:
> *
> * With support for several ext* filesystems available, it may be needed to
> * add "rootfstype=ext3" or "rootfstype=ext4" to the list of boot parameters.
>
> Which grub file I edit to add support for "rootfstype=ext4" ?
>
--
Dan Egli
From my Test Server
next prev parent reply other threads:[~2020-12-13 0:04 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-11 21:36 [gentoo-user] fsck.fat 4.1 - File system couldn't be fixed thelma
2020-12-11 22:06 ` Jack
2020-12-11 22:29 ` thelma
2020-12-11 23:50 ` Michael
2020-12-12 1:16 ` thelma
2020-12-12 7:32 ` Dan Egli
2020-12-12 18:48 ` thelma
2020-12-12 19:25 ` Dan Egli
2020-12-12 19:47 ` thelma
2020-12-13 0:04 ` Dan Egli [this message]
2020-12-12 20:24 ` thelma
2020-12-12 10:59 ` Tamer Higazi
2020-12-12 19:49 ` thelma
2020-12-13 0:06 ` Dan Egli
2020-12-12 22:40 ` Neil Bothwick
2020-12-13 3:07 ` [gentoo-user] [SOLVED] fsck.fat 4.1 - File system couldn't be fixed [SOLVED] thelma
2020-12-13 6:00 ` Victor Ivanov
2020-12-13 7:42 ` thelma
2020-12-13 7:57 ` [gentoo-user] How to config nullmailer bobwxc
2020-12-13 13:33 ` [gentoo-user] [SOLVED] fsck.fat 4.1 - File system couldn't be fixed [SOLVED] Victor Ivanov
2020-12-14 6:07 ` thelma
2020-12-14 12:06 ` Michael
2020-12-13 14:17 ` Michael
2020-12-13 14:33 ` Neil Bothwick
2020-12-13 15:02 ` Victor Ivanov
2020-12-13 16:52 ` Neil Bothwick
2020-12-14 5:41 ` Thomas Mueller
[not found] ` <20201214054146.415BCE0A03@pigeon.gentoo.org>
2020-12-14 10:02 ` Michael
[not found] ` <20201214054146.0CC61E09F5@pigeon.gentoo.org>
2020-12-14 10:09 ` Wols Lists
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=7efaf7f6-ff4e-082f-4948-c461a691c562@newideatest.site \
--to=dan@newideatest.site \
--cc=gentoo-user@lists.gentoo.org \
--cc=thelma@sys-concept.com \
/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