>
> Note: sudo guix gc --verify did not find things.

Upon this new information I don't think your store got corrupted, what
got corrupted was files in /etc only, and it would've gotten fixed
if you booted, but you didn't since the normal.mod was broken.

>
> Is it? I didn't have cp or cat, so no way of me reading what's in
> grub.cfg--and I'm not correctly guessing these hashes from my human memory:

Grub isn't using coreutils it has its own commands. Cat is one of them
though, you can use cat in grub. ls is also available.
If you want to see the file in parts, set pager to 1.

"In rescue mode, only the insmod (see insmod), ls (see ls), set (see set), and 
unset (see unset) commands are normally available. If you end up in rescue mode 
and do not know what to do, then see GRUB only offers a rescue shell. "
https://www.gnu.org/software/grub/manual/grub/grub.html#Commands

The only time they aren't available is if you were in rescue shell.
Since you had normal.mod corrupted, it makes sense you were in a rescue
shell, I didn't realize that. If normal.mod is corrupted, there isn't a
way to recover I am afraid. The only would be to find a different
normal.mod, ie. in the store, by looking through ls of /gnu/store for a
grub, and use that as a prefix.

> Next, for before I fixed it:
>
> So I guess we need /var/log/messages.1.zstd for the time before I rebooted.
>
> That one it said it rotated to messages.1 (no ".zstd")--which doesn't exist.
>
> grep for "Apr.*20" over all "messages"* (after uncompressing them)
> gave me: messages.1 (so from messages.1.zstd).  So I guess that one is
> meant.  That one starts at Apr 13 and ends at end of Apr 20.
>
> I copied messages* away so I will still have them.
>
> I checked the contents of messages.1 and at least it's easy to find the
> spot since there's a big block of damage in there, see end (note:
> I manually removed lines containing secret keys :P):

Are you sure this is part of the log after you issued reboot? If so,
there isn't anything left from it, so it probably got removed because of
the failed unmount.

Reply via email to