From: Marius Bakke <mbakke@fastmail.com>
To: Ricardo Wurmus <rekado@elephly.net>, help-guix <help-guix@gnu.org>
Subject: Re: failed to resolve partition “my-root”
Date: Wed, 28 Jun 2017 23:54:40 +0200 [thread overview]
Message-ID: <87o9t7n5gf.fsf@fastmail.com> (raw)
In-Reply-To: <8760fg9ieq.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 1905 bytes --]
Ricardo Wurmus <rekado@elephly.net> writes:
> Ricardo Wurmus <rekado@elephly.net> writes:
>
>> Ricardo Wurmus <rekado@elephly.net> writes:
>>
>>> Linux appears to boot but then fails with “failed to resolve partition
>>> "my-root"”. I suspect that something in (gnu build file-systems) is
>>> broken. koosha on IRC previously reported a similar problem.
>>
>> “cat /proc/partitions” shows that only the ram* devices are listed.
>> None of the hard disk partitions are listed. Also, in the rescue REPL I
>> don’t see any disk under /dev/.
>>
>> So (gnu build file-systems) works as it should. Curious.
>>
>> When I boot with the USB stick, however, /dev/sda (the USB disk) and
>> /dev/sdb (the hard disk) both exist.
>>
>> I’m guessing that it’s a problem with the initrd; some missing kernel
>> module maybe. Is there a way to regenerate the initrd without having to
>> reinstall the whole system? I’m willing to fall back to my old ways of
>> manipulating things in the store just to get this thing booted soon.
>> (I’ll ask for forgiveness later.)
>
> I fixed this by re-init-ing the system with a tiny change to the
> operating system definition:
>
> --8<---------------cut here---------------start------------->8---
> (initrd (lambda (fs . args)
> (apply base-initrd fs
> #:extra-modules (list "sata_nv")
> args)))
> --8<---------------cut here---------------end--------------->8---
>
> The module is needed because this is an NVIDIA disk controller.
Maybe we could add all disk drivers to the base initrd image?
$ du -h $(guix build linux-libre 2>/dev/null)/lib/modules/*/kernel/drivers/ata
1.3M /gnu/store/b7nk7glwlrjk8fnw4g7zylzlx7g2f6jd-linux-libre-4.11.6/lib/modules/4.11.6-gnu/kernel/drivers/ata
That doesn't sound too much to me and will save many users some trouble.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2017-06-28 21:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-27 18:45 failed to resolve partition “my-root” Ricardo Wurmus
2017-06-27 19:15 ` Ricardo Wurmus
2017-06-28 16:38 ` Ricardo Wurmus
2017-06-28 21:54 ` Marius Bakke [this message]
2017-06-29 14:33 ` Ludovic Courtès
2017-06-29 20:51 ` Alex Kost
2017-06-30 12:45 ` Ludovic Courtès
2017-06-29 14:37 ` Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o9t7n5gf.fsf@fastmail.com \
--to=mbakke@fastmail.com \
--cc=help-guix@gnu.org \
--cc=rekado@elephly.net \
/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).