From: Dave Young <dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Alex <mysqlstudent-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Can't mount USB within initramfs
Date: Tue, 29 Sep 2015 16:04:02 +0800 [thread overview]
Message-ID: <20150929080402.GC30623@dhcp-129-73.nay.redhat.com> (raw)
In-Reply-To: <CAB1R3shGMbuAh8HKSFq086VegXo7vLh=f7EH-49wjoBd_p69BQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 09/13/15 at 02:50pm, Alex wrote:
> Hi,
>
> I have a fedora22 system with dracut-041-10 and initramfs created with
> it fails at "reached target basic system". I enabled some debugging,
> and it appears to just loop, unable to mount a root, until I get a
> dracut shell.
>
> It's created an sosreport, but I'm unable to mount a USB stick to copy
> it. It displays info about the device when it's inserted, but no
> device name is assigned to it. Is this a problem with how the
> initramfs was created, a bug, or am I doing something wrong?
>
> The only modules in /usr/lib/modules/drivers are gpu drivers,
> i2c/algos, and raid1 and raid456. The system has a RAID1 and a RAID5
> partition, but the kernel modules aren't loaded (have to load them
> manually), but then no devices are shown in /proc/mdstat there either.
>
> Is filesystem support compiled into the kernel or must that be added
> to the initramfs manually?
You can try add them manually like below, assume you are using vfat filesystem..
--add-drivers "usb_storage vfat"
Thanks
Dave
prev parent reply other threads:[~2015-09-29 8:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-13 18:50 Can't mount USB within initramfs Alex
[not found] ` <CAB1R3shGMbuAh8HKSFq086VegXo7vLh=f7EH-49wjoBd_p69BQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-09-29 8:04 ` Dave Young [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=20150929080402.GC30623@dhcp-129-73.nay.redhat.com \
--to=dyoung-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mysqlstudent-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 read-only IMAP folder(s) and NNTP newsgroup(s).