From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Marusich Subject: Re: Bootloader trouble during installation Date: Thu, 06 Jul 2017 09:19:10 -0700 Message-ID: <87h8ypy1vl.fsf@gmail.com> References: <20170706133936.E133DA0155@smtp.hushmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:53417) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dT9Ut-000805-PD for guix-devel@gnu.org; Thu, 06 Jul 2017 12:19:20 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dT9Us-0000L6-Nx for guix-devel@gnu.org; Thu, 06 Jul 2017 12:19:19 -0400 Received: from mail-pg0-x233.google.com ([2607:f8b0:400e:c05::233]:35010) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dT9Us-0000KL-Hf for guix-devel@gnu.org; Thu, 06 Jul 2017 12:19:18 -0400 Received: by mail-pg0-x233.google.com with SMTP id j186so3318325pge.2 for ; Thu, 06 Jul 2017 09:19:18 -0700 (PDT) In-Reply-To: <20170706133936.E133DA0155@smtp.hushmail.com> (cinder's message of "Thu, 06 Jul 2017 09:39:36 -0400") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: cinder88@hushmail.com Cc: guix-devel@gnu.org --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable cinder88@hushmail.com writes: > Hello again, all. I've been trying to install GuixSD for the first time w= ith no success. Sorry to hear that! Hopefully we can help get it fixed. > The installation process seems to go smoothly, but my machine can't > detect the installation. Since the installation isn't detected, I > believe the problem is with the bootloader. How far along does the bootstrap process get? Are you receiving an error message at some point? If you can provide some more details about the problem, maybe it will point us towards the right solution. > For the bootloader, I am attempting to use legacy boot, not UEFI. I >realize that > fdisk below identifies /dev/sda2 as an EFI system, but this seems to auto= matically > happen when I set boot to on in parted. The reason that happens is because 'boot' is an alias for 'esp' in the case of GPT (see: info '(parted) set'). I'm not sure if it's correct to enable this flag on /dev/sda2, though. In Guix's system installation tests, which also use GPT, we enable the 'boot' flag on the bios_grub partition, which is /dev/sda1 in your case. Maybe you can try enabling the 'boot' flag on /dev/sda1 instead? > (file-systems (append > (list (file-system > (device "my-root") > (title 'label) > (mount-point "/") > (type "ext4"))) > (list (file-system > (device "my-boot") > (title 'label) > (mount-point "/boot") > (type "ext4"))) > %base-file-systems)) It might not be related to the issue at hand, but you might want to double check that the labels of your file systems actually matches labels you've specified here. There are many ways to view file system labels; one convenient way is to run 'blkid' (which is in the util-linux package). > Thank you for any and all help, Happy to assist! =2D-=20 Chris --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEy/WXVcvn5+/vGD+x3UCaFdgiRp0FAlleYv8ACgkQ3UCaFdgi Rp2+JQ/9F9kCEwlLt1bair6nSwkIIFHghgriC4REcLNGSNq4gJ1cCiEsga4bRBnf azJwDzmZv87Q03wrW/iLy4mAObkpuweHnIjS33KdP+qi1mQmbNSDd9ThtD8M69CC w4n+PPtelkvNCAsMHMYpZinofs3Cs1Q62p2xB38mbRRGGPHODWxmHtbMuuGo3dP/ o8UZlZMTfiUtiXyd1wRbzdRkmFhPqMYlgv2Vuc/chG1ephCWT0MFGU/mPPdQv2Qn C8R8Dgifp2D+MhiOUPMKIbzBbn2840UkgyKBCVRU4q/M0VGECXgM+pgz4stiNX80 1olsQqafOHhOEswGm+k4ObnbtVqUFKSGpMA8f1BT56aDiKuqyNLDXGX8lSPn4d9W A1P9gjz8fWd95sWUW12c71K3cpapvvSFp5oRrSY3jfs9FAB5E7jZsRLuTq/R0n0C h4iy+YJVzAPOIaFzTlnToLl2b3D6l21zOLxk3kJdtyW6kMtQpwPNqbUqiLga9PdR 5SAo06uiqsYhk8QcRNeG1vqTJDIWS9Jhb2z9CHLxzxCv82Ihr5Wfdj7UuhdGItUQ N0BozvJxXoT+LqEQ5ebNevCnOnxGHdLC9bzdTJUrrRgpwCfBAbKhiC4wNYrQ2/sE F9AcLfmFo0CdN+YlAD+RBjM68ENTuC0W6Z3J4Yw1hUQoVnCOj8Y= =7v4A -----END PGP SIGNATURE----- --=-=-=--