From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marius Bakke Subject: Re: failed to resolve partition =?utf-8?B?4oCcbXktcm9vdOKAnQ==?= Date: Wed, 28 Jun 2017 23:54:40 +0200 Message-ID: <87o9t7n5gf.fsf@fastmail.com> References: <87injhe0cn.fsf@elephly.net> <87fueldyyz.fsf@mdc-berlin.de> <8760fg9ieq.fsf@elephly.net> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:58317) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dQKvA-0007WH-Ul for help-guix@gnu.org; Wed, 28 Jun 2017 17:54:49 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dQKv6-0005zy-2r for help-guix@gnu.org; Wed, 28 Jun 2017 17:54:49 -0400 Received: from out5-smtp.messagingengine.com ([66.111.4.29]:60511) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1dQKv5-0005yx-Gx for help-guix@gnu.org; Wed, 28 Jun 2017 17:54:44 -0400 In-Reply-To: <8760fg9ieq.fsf@elephly.net> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: Ricardo Wurmus , help-guix --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Ricardo Wurmus writes: > Ricardo Wurmus writes: > >> Ricardo Wurmus writes: >> >>> Linux appears to boot but then fails with =E2=80=9Cfailed to resolve pa= rtition >>> "my-root"=E2=80=9D. I suspect that something in (gnu build file-system= s) is >>> broken. koosha on IRC previously reported a similar problem. >> >> =E2=80=9Ccat /proc/partitions=E2=80=9D shows that only the ram* devices = are listed. >> None of the hard disk partitions are listed. Also, in the rescue REPL I >> don=E2=80=99t 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=E2=80=99m guessing that it=E2=80=99s a problem with the initrd; some m= issing kernel >> module maybe. Is there a way to regenerate the initrd without having to >> reinstall the whole system? I=E2=80=99m willing to fall back to my old = ways of >> manipulating things in the store just to get this thing booted soon. >> (I=E2=80=99ll 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. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAllUJaAACgkQoqBt8qM6 VPoZswf9GHKBX5J334Kzt8rTRNyGCWL8yMU6IDne/NxD2qkIpNLpttgoWIPWMJU5 tOajY95BElrSJEFMVcpL+7vAW0vXLzgOjLTOWbBY+/CNPBgQUqma8oxHwi27Lu6r k/ekjJZyLQlrxSPo1J2zih8YAZSoq/EyBzZcyiHD1ffXs4I+rbblJLdr9vR6oyT2 z90deij4eDM0tNKAbf4Auta1A8OBzMhW00nBkFX/qG1ERQBwTI8OtZNP4sBBtWxo VtfExxbEg0vhl36IYCnmmnAZO8GUyRq8OMbuUVSFYTrX3kEcayTeW1dOJMvw2o9S LjFOuCyKHE6VsxcRD+eylZaiFf2clw== =+SBc -----END PGP SIGNATURE----- --=-=-=--