From: Christopher Baines <mail@cbaines.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: help-guix@gnu.org
Subject: Re: Kernel panic - not syncing: attempting to kill init! when booting GuixSD
Date: Tue, 30 May 2017 13:43:40 +0100 [thread overview]
Message-ID: <a4bb0046-81fa-4ed3-d880-380e1c771dfc@cbaines.net> (raw)
In-Reply-To: <87fufprngc.fsf@gnu.org>
[-- Attachment #1.1: Type: text/plain, Size: 1899 bytes --]
On 28/05/17 16:49, Ludovic Courtès wrote:
> Hi Christopher,
>
> Christopher Baines <mail@cbaines.net> skribis:
>
>> So I deleted some system generations from one of my GuixSD systems, then
>> rebooted. Unfortunately, I can no longer get it to boot. I think the
>> latest system generation should work, and at least one of the previous
>> generations should work.
>>
>> Excluding the generations that I removed, the others don't boot. All I
>> can really gather so far is a call stack, and the message:
>> Kernel panic - not syncing: Attempted to kill init!
>
> Weird. Is it because the root file system could not be found? Or
> something else? Like Ricardo wrote, could it be that the file system
> label changed or something?
Looking at the file system and configuration, it seems that this is
unlikely.
>> I'm going to try and make some time to see if I can get this system back
>> working again. I'm not sure how realistic this is, but I'm planning to
>> start by using the installation image, and somehow running guix system
>> reconfigure.
>
> I would suggest booting from an external medium such as the installation
> image, mounting the file system that holds /gnu/store, and inspecting
> there.
>
> Also worth trying: you could edit the command line in the GRUB menu to
> have it refer to /var/guix/profiles/system-NNN-link, where NNN is the
> number of a previous generation known to be on disk.
I don't have the right cables to attempt to get a serial connection to
see what is going on in the early boot, so I tried running guix system
init from some GuixSD installation media. I'm glad to say that it worked :)
After running guix system init, I had a working system generation to
boot with.
I'll try to setup some kind of serial connection, so that I can attempt
to debug further if this happens again.
Thanks,
Chris
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 858 bytes --]
next prev parent reply other threads:[~2017-05-30 12:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 15:26 Kernel panic - not syncing: attempting to kill init! when booting GuixSD Christopher Baines
2017-05-24 15:45 ` Ricardo Wurmus
2017-05-29 18:48 ` Christopher Baines
2017-05-28 15:49 ` Ludovic Courtès
2017-05-30 12:43 ` Christopher Baines [this message]
2017-05-30 4:06 ` Quiliro
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a4bb0046-81fa-4ed3-d880-380e1c771dfc@cbaines.net \
--to=mail@cbaines.net \
--cc=help-guix@gnu.org \
--cc=ludo@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).