From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Thompson Subject: Re: System installation from a USB stick Date: Thu, 24 Jul 2014 07:57:56 -0400 Message-ID: <87d2cv3r5n.fsf@izanagi.i-did-not-set--mail-host-address--so-tickle-me> References: <87y4xdhgn3.fsf@gnu.org> <877g3z2w60.fsf@gnu.org> <87r41jp2pa.fsf@gnu.org> <87bnslk4d6.fsf@gnu.org> <87vbqtfq0x.fsf@gnu.org> <87mwc5e2uj.fsf@gnu.org> <87k378be4g.fsf@gnu.org> <87pph09m4p.fsf@gnu.org> <87oawgvzhb.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:44201) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XAHey-000552-F7 for guix-devel@gnu.org; Thu, 24 Jul 2014 07:58:15 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XAHer-0003QD-UD for guix-devel@gnu.org; Thu, 24 Jul 2014 07:58:08 -0400 Received: from na3sys009aog102.obsmtp.com ([74.125.149.69]:45025) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XAHer-0003Pz-MR for guix-devel@gnu.org; Thu, 24 Jul 2014 07:58:01 -0400 Received: by mail-qa0-f47.google.com with SMTP id i13so2726262qae.20 for ; Thu, 24 Jul 2014 04:57:59 -0700 (PDT) In-Reply-To: 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-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: Adam Pribyl Cc: guix-devel Adam Pribyl writes: > I can not boot installed system, boot looks for /dev/sda1 which is not > present. It smells to me like the same problem with devtmpfs previously in > live USB... I found in grub the reference to /dev/sda1 (as LiveUSB now > with udev in devtmpfs and kernel 3.15.6 asigns the HDD /dev/sda) but it > looks like the kernel booting from HDD is not seeing it like this. This could be an instance of the problem that bit me last night. The version of Guix that gets installed (0.6, as you mentioned in your notes), uses an initrd that cannot see SATA hard disks. So, as a work-around, you must explicitly add the relevant kernel modules in your operating-system definition like so: (use-modules (gnu) (srfi srfi-26)) (define my-os (operating-system ... (initrd (cut base-initrd <> #:extra-modules '("libahci.ko" "ahci.ko"))) ...)) Additionally, as Ludovic has already mentioned, I find that using device labels is much better than hoping that the /dev nodes on the installation image are the same as the /dev nodes on the installed system. -- David Thompson Web Developer - Free Software Foundation - http://fsf.org GPG Key: 0FF1D807 Support the FSF: https://fsf.org/donate