unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Danny Milosavljevic <dannym@scratchpost.org>
To: Bryan Ferris <saffsnail@gmail.com>
Cc: 33999@debbugs.gnu.org
Subject: bug#33999: CP437: Invalid Argument on init
Date: Thu, 10 Jan 2019 18:59:05 +0100	[thread overview]
Message-ID: <20190110185905.413ce912@scratchpost.org> (raw)
In-Reply-To: <CABkR=SUnpHJ+-brA5k40t3gvcOf2DuU8+UKEseTiee25Vuy1rg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3160 bytes --]

Hi,

On Thu, 10 Jan 2019 07:15:10 -0800
Bryan Ferris <saffsnail@gmail.com> wrote:

> I've linked to two videos here, one of the boot (the screen with the GNU
> logo and "100% freedom" on it) and one of the init (where Shepherd reports
> errors,

Thanks!  I've viewed those.

>I think it's dmesg?).

It depends.  On early boot it's dmesg and once syslog is up it's syslog.

> Boot:
> https://drive.google.com/file/d/1YMbCI3BvznhMI_eYYTxMvxJC2SKlNqSJ/view?usp=sharing
> Init:
> https://drive.google.com/file/d/1CZov16Xrpy9D8DMN9eHeANjR7UHh2WpL/view?usp=sharing

Maybe the CP437 is not harmless after all.

Please try adding the unquoted part below at the indicated place:

> >> >   (file-systems (cons*
> >> >                   (file-system
> >> >                     (device (file-system-label "ESP"))
> >> >                     (mount-point "/boot/efi")
> >> >                     (type "fat")  
> >>

 (check? #f)

> >> >                   )  

Then invoke

  guix system reconfigure /etc/config.scm

as root in order for it to be applied and reboot.

This prevents fsck.fat from being invoked - so we hopefully also doesn't
need CP437 any more.

If that doesn't help, try this (it's kinda dangerous :( ):

> >> >   (file-systems (cons*
> >> >                   (file-system
> >> >                     (device (file-system-label "ESP"))
> >> >                     (mount-point "/boot/efi")
> >> >                     (type "fat")  
> >>

(check? #f)
(needed-for-boot? #f)

> >> >                   )  

Then invoke

  guix system reconfigure /etc/config.scm

as root in order for it to be applied and reboot.

This prevents fsck.fat from being invoked and it also prevents the
initial ram disk (a very early tiny GNU system which runs right after the kernel
starts up and before init) from trying to mount /boot/efi .  The real system
will still mount /boot/efi later.

It would be interesting if 

(1) This fixes the problem (I don't think so), or
(2) It reduces the number of error messages and makes it less bad.

After all this, if it still doesn't work:

Try adding the unquoted part:

> >> >   (file-systems (cons*
> >> >                   (file-system
> >> >                     (device (file-system-label "ESP"))
> >> >                     (mount-point "/boot/efi")
> >> >                     (type "fat")  
> >>

(check? #f)
(needed-for-boot? #f)
(mount? #f)

> >> >                   )  

Then invoke

  guix system reconfigure /etc/config.scm

as root in order for it to be applied and reboot.

This prevents mounting of /boot/efi entirely (it's pretty dangerous).

Should your system not boot any more you can select the older generation
in the grub boot menu.  It's also possible that you can't run

  guix system reconfigure /etc/config.scm

anymore after this.  If so, please invoke

  mount /boot/efi

as root.  Then you can invoke

  guix system reconfigure /etc/config.scm

once.

It's likely that the latter will be a successful workaround to
the original problem.
It would still be good if we got to the root cause later.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2019-01-10 18:00 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-06 19:34 bug#33999: CP437: Invalid Argument on init Bryan Ferris
2019-01-09 19:08 ` Danny Milosavljevic
2019-01-09 21:18   ` Bryan Ferris
     [not found]     ` <CABkR=SUyCV7d6sR1Zyy4Aj4Cp5raS_Tn-Akji3k0fQPeneErFg@mail.gmail.com>
2019-01-10 15:15       ` Bryan Ferris
2019-01-10 17:59         ` Danny Milosavljevic [this message]
2019-01-10 20:37           ` Bryan Ferris
2019-01-16 11:00   ` Ludovic Courtès
2019-01-18 22:59     ` Danny Milosavljevic
2019-01-19 10:19       ` Ludovic Courtès
2019-01-21  0:40       ` Danny Milosavljevic
2019-01-21  8:41         ` Danny Milosavljevic
2019-01-21  9:50         ` Ludovic Courtès
2019-01-21 10:16           ` Danny Milosavljevic
2019-01-21 10:51             ` Ludovic Courtès
2019-01-23 15:42             ` Bryan Ferris
2019-01-26 17:32               ` Bryan Ferris
2019-01-10 18:21 ` Danny Milosavljevic
2019-01-16 15:43   ` Bryan Ferris
2019-01-18 19:00     ` Bryan Ferris
2019-01-18 22:48       ` Danny Milosavljevic
     [not found]         ` <CABkR=SWtHUA+G50fR_QiU-tGU6TatQ7wnKWW+n6LdFexSYJZRA@mail.gmail.com>
     [not found]           ` <20190120031949.2bb81997@scratchpost.org>
2019-01-20 14:34             ` Bryan Ferris
2019-01-20 22:48               ` Danny Milosavljevic
2019-01-20 22:49                 ` Danny Milosavljevic

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=20190110185905.413ce912@scratchpost.org \
    --to=dannym@scratchpost.org \
    --cc=33999@debbugs.gnu.org \
    --cc=saffsnail@gmail.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).