From mboxrd@z Thu Jan 1 00:00:00 1970 From: myglc2 Subject: bug#23072: GuixSD SSD install hangs at clocksource Date: Tue, 24 Jan 2017 14:15:04 -0500 Message-ID: <86vat41d8n.fsf@gmail.com> References: <87oaa853ex.fsf@gmail.com> <56EF0EED.5010102@gmx.net> <87d1qorln8.fsf@gmail.com> <877f61ut2v.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:34930) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cW6ZZ-0000JQ-Vr for bug-guix@gnu.org; Tue, 24 Jan 2017 14:16:10 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cW6ZW-0000P1-K2 for bug-guix@gnu.org; Tue, 24 Jan 2017 14:16:05 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:42457) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cW6ZW-0000On-H5 for bug-guix@gnu.org; Tue, 24 Jan 2017 14:16:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1cW6ZW-0006Lv-9T for bug-guix@gnu.org; Tue, 24 Jan 2017 14:16:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <877f61ut2v.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Wed, 11 Jan 2017 23:31:36 +0100") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 23072@debbugs.gnu.org On 01/11/2017 at 23:31 Ludovic Court=C3=A8s writes: > myglc2 skribis: > >> Florian Paul Schmidt writes: >> >>> On 20.03.2016 20:56, myglc2 wrote: >>> >>>> - I did a near-identical install to a SSD (Kingston ssdnow300), see >>>> "c06system-ssd.scm.log". If installed on the 1st server this shows >>>> Guix welcome screen, loads the keyboard & mouse drivers, then hangs >>>> showing: >>>>=20 >>>> "clocksource: Switched to clocksource tsc" >>> >>> This is just a shot in the dark, but I use SSD systems, too, and I >>> noticed that the first boot of a guixsd installation hangs for a while >>> collecting entropy before displaying a corresponding message IIRC and I >>> faintly remember the "switching to clocksource" message. Did you try >>> banging the keyboard? Maybe that's not possible on a headless server >>> though. Did you let it sit for a while? >>> >>> Flo >> Thanks Flo. Can't test that theory at the moment. But I do have a >> display attached (which is how I saw the "clocksource..." message). >> >> FWIW, in the HD install there is a prompt for keyboard input. It seems >> like the SSD install hung before it reached that. - George > > Any update on this bug? > > http://bugs.gnu.org/23072 > > Ludo=E2=80=99. Hi Ludo, I did experiments and I now see that this happens when the boot drive ID has changed from what was specified as the grub-configuration device in the most recent 'system init' or 'system reconfigure' operation. This can happen, for example, when one moves drives around or when one inserts a new drive in an empty lower SATA slot below drives holding GuixSD. This seemed like a bug to me because the doc says ... =E2=80=A2 Make sure the =E2=80=98grub-configuration=E2=80=99 form refers= to the device you want to install GRUB on. ... but there is no mention that it affects boot operation. Also I assumed, possibly wrongly, that GuixSD does not need the config to tell it which device grub is on at boot because it is already running on the boot device ;-) So, I don't know ... Is this a bug or is this expected behavior. If it is not a bug it seems like an opportunity to reduce the fragility of GuixSD configurations. HTH - George