From: Danny Milosavljevic <dannym@scratchpost.org>
To: "Ludovic Courtès" <ludo@gnu.org>, "Bryan Ferris" <saffsnail@gmail.com>
Cc: 33999@debbugs.gnu.org
Subject: bug#33999: CP437: Invalid Argument on init
Date: Mon, 21 Jan 2019 11:16:41 +0100 [thread overview]
Message-ID: <20190121111641.49665997@scratchpost.org> (raw)
In-Reply-To: <878szel4pa.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1556 bytes --]
Hi Ludo,
Hi Bryan,
On Mon, 21 Jan 2019 10:50:41 +0100
Ludovic Courtès <ludo@gnu.org> wrote:
> It’s not surprising to .lock files to be empty.
I agree. But I didn't filter them out because it would be confusing.
> But where are those
> files you’re talking about? Surely there’s no /gnu/store on the VFAT
> EFI partition, right?
Oh, these empty files are on the root partition Bryan provided - there
are lots and lots of empty files, including very important ones like the
pam configuration files and the elogind configuration files (which is why
the login didn't work).
It looks like something crashed or sync(2) wasn't called before reboot or
something.
Some flash storage devices like to lie about whether they synced something
(they'll say they did sync but they really didn't yet). If one then cuts
the power it leads to data loss. But that's all speculation.
@Bryan: Would you be up to doing the installation again but then before the
reboot do a manual invocation of "sync" and then wait 5 min before rebooting?
Is it flash storage?
I didn't check the contents of the ESP partition because they don't matter.
What matters is whether the ESP partition is dirty (it was) and whether a
manual invocation of "fsck.vfat" succeeds on it (it does).
Out of curiousity I checked ESP anyway now. It has:
EFI
EFI/GuixSD
EFI/GuixSD/grubx64.efi
$ ls -l EFI/GuixSD/grubx64.efi
-rwxr-xr-x 1 root root 155136 11. Jan 16:52 /mnt/tmp/EFI/GuixSD/grubx64.efi
That's all there is in the ESP partition.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-01-21 10:17 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
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 [this message]
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=20190121111641.49665997@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=33999@debbugs.gnu.org \
--cc=ludo@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).