GNU bug report logs -
#23072
GuixSD SSD install hangs at clocksource
Previous Next
Reported by: myglc2 <myglc2 <at> gmail.com>
Date: Sun, 20 Mar 2016 19:54:01 UTC
Severity: normal
Tags: moreinfo
Done: zimoun <zimon.toutoune <at> gmail.com>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 23072 in the body.
You can then email your comments to 23072 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-guix <at> gnu.org
:
bug#23072
; Package
guix
.
(Sun, 20 Mar 2016 19:54:01 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
myglc2 <myglc2 <at> gmail.com>
:
New bug report received and forwarded. Copy sent to
bug-guix <at> gnu.org
.
(Sun, 20 Mar 2016 19:54:01 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
I tried to upgrade my headless server running GuixSD from to HD to SSD.
First I shot myself in the foot doing 'guix init' on the SSD. Possibly
by labeling the SSD root using the same label as the system HD root, or
maybe I miss-specified the bootloader device?
Anyway, to dig myself out, I switched to a 2nd server running
Guix/Debian and ...
- reinstalled GuixSD to the 1st server's HD, see
"c06system.scm.log". This runs fine back in the 1st server.
- 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:
"clocksource: Switched to clocksource tsc"
So to summarize, ~identical install on HD runs fine, install on SSD
hangs.
Please see attached logs. - George
[c06system-ssd.scm.log (application/octet-stream, attachment)]
[c06system-sdd.scm.log (application/octet-stream, attachment)]
Information forwarded
to
bug-guix <at> gnu.org
:
bug#23072
; Package
guix
.
(Sun, 20 Mar 2016 20:59:01 GMT)
Full text and
rfc822 format available.
Message #8 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
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:
>
> "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
--
https://fps.io
[signature.asc (application/pgp-signature, attachment)]
Information forwarded
to
bug-guix <at> gnu.org
:
bug#23072
; Package
guix
.
(Mon, 21 Mar 2016 13:45:02 GMT)
Full text and
rfc822 format available.
Message #11 received at submit <at> debbugs.gnu.org (full text, mbox):
Florian Paul Schmidt <mista.tapas <at> gmx.net> 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:
>>
>> "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
Information forwarded
to
bug-guix <at> gnu.org
:
bug#23072
; Package
guix
.
(Wed, 09 Nov 2016 20:51:02 GMT)
Full text and
rfc822 format available.
Message #14 received at 23072 <at> debbugs.gnu.org (full text, mbox):
Hi,
myglc2 <myglc2 <at> gmail.com> skribis:
> Florian Paul Schmidt <mista.tapas <at> gmx.net> 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:
>>>
>>> "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’.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#23072
; Package
guix
.
(Wed, 11 Jan 2017 22:32:01 GMT)
Full text and
rfc822 format available.
Message #17 received at 23072 <at> debbugs.gnu.org (full text, mbox):
myglc2 <myglc2 <at> gmail.com> skribis:
> Florian Paul Schmidt <mista.tapas <at> gmx.net> 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:
>>>
>>> "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’.
Added tag(s) moreinfo.
Request was from
ludo <at> gnu.org (Ludovic Courtès)
to
control <at> debbugs.gnu.org
.
(Wed, 11 Jan 2017 22:32:02 GMT)
Full text and
rfc822 format available.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#23072
; Package
guix
.
(Tue, 24 Jan 2017 19:16:02 GMT)
Full text and
rfc822 format available.
Message #22 received at 23072 <at> debbugs.gnu.org (full text, mbox):
On 01/11/2017 at 23:31 Ludovic Courtès writes:
> myglc2 <myglc2 <at> gmail.com> skribis:
>
>> Florian Paul Schmidt <mista.tapas <at> gmx.net> 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:
>>>>
>>>> "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’.
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 ...
• Make sure the ‘grub-configuration’ 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
Information forwarded
to
bug-guix <at> gnu.org
:
bug#23072
; Package
guix
.
(Tue, 18 Feb 2020 14:10:02 GMT)
Full text and
rfc822 format available.
Message #25 received at 23072 <at> debbugs.gnu.org (full text, mbox):
Dear,
Any update about the bug#20372 [1]?
Since it is 3 years old, does it still happen with a recent Guix versions?
[1] https://debbugs.gnu.org/cgi/bugreport.cgi?bug=23072
All the best,
simon
Information forwarded
to
bug-guix <at> gnu.org
:
bug#23072
; Package
guix
.
(Thu, 20 Feb 2020 00:46:02 GMT)
Full text and
rfc822 format available.
Message #28 received at 23072 <at> debbugs.gnu.org (full text, mbox):
On Tue, 18 Feb 2020 at 17:00, zimoun <zimon.toutoune <at> gmail.com> wrote:
> On Tue, 18 Feb 2020 at 16:56, my glc2 <myglc2 <at> gmail.com> wrote:
> > I don't know. i haven't changed drive config since 2017, or, for that matter, upgraded since 2018.
>
> Ok.
> Keep in touch if you change something. :-)
>
> (I am in the process of triaging old bugs ;-))
For the record, line above why the bug is still open.
Reply sent
to
zimoun <zimon.toutoune <at> gmail.com>
:
You have taken responsibility.
(Fri, 26 Nov 2021 01:33:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
myglc2 <myglc2 <at> gmail.com>
:
bug acknowledged by developer.
(Fri, 26 Nov 2021 01:33:02 GMT)
Full text and
rfc822 format available.
Message #33 received at 23072-done <at> debbugs.gnu.org (full text, mbox):
Hi,
On Thu, 20 Feb 2020 at 01:45, zimoun <zimon.toutoune <at> gmail.com> wrote:
> On Tue, 18 Feb 2020 at 17:00, zimoun <zimon.toutoune <at> gmail.com> wrote:
>> On Tue, 18 Feb 2020 at 16:56, my glc2 <myglc2 <at> gmail.com> wrote:
>
>> > I don't know. i haven't changed drive config since 2017, or, for that matter, upgraded since 2018.
This old bug is open because an error back in 2016. Nothing change
since 2017 and last upgrade since 2018. A lot of thing has changes
since then. Therefore I am closing.
Feel free to reopen if you consider it is worth to keep it open and if
it could useful.
<http://issues.guix.gnu.org/issue/23072>
Cheers,
simon
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Fri, 24 Dec 2021 12:24:07 GMT)
Full text and
rfc822 format available.
This bug report was last modified 2 years and 85 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.