Hiccups installing GNU Guix 1.4.0rc2 system

  • Open
  • quality assurance status badge
Details
2 participants
  • J. Sims
  • Ludovic Courtès
Owner
unassigned
Submitted by
J. Sims
Severity
normal
J
J
J. Sims wrote on 15 Dec 2022 22:24
(name . bug-guix@gnu.org)(address . bug-guix@gnu.org)
HYrGixFgcpyQyYQuRS3IY-weWbaouFJZKmx3L8BasxMSfYxrYYxXYZN33pWbnAW_5FTbe8W_XpD4QunmR-56irnpKgqZsYq1s_ZDA7bWzes=@protonmail.com
Hey there,

I managed to successfully install the GNU Guix 1.4.0rc2 system iso on an HP Dev One laptop (with help from USB stuff for networking). Everything mostly went as expected, except after the installation I got a screen saying crypttab couldn't find a specific partition. I assume this was something left over from a previous OS installation since wiping the partitions with cfdisk and then installing worked fine. Note that while my initial install attempts did use encryption, the final (successful) one did not; I don't think this has any effect one way or the other on the viability of installation since I ran into the same issue both with and without an encrypted Guix installation before wiping the partitions.

Hopefully it should be simple enough to just completely rewrite the partition table during installation and sidestep this issue.

Thanks,
Juli
Attachment: file
L
L
Ludovic Courtès wrote on 15 Dec 2022 23:51
(name . J. Sims)(address . jtsims@protonmail.com)(address . 60104@debbugs.gnu.org)
87ilicl1qn.fsf@gnu.org
Hi,

"J. Sims" <jtsims@protonmail.com> skribis:

Toggle quote (6 lines)
> I managed to successfully install the GNU Guix 1.4.0rc2 system iso on
> an HP Dev One laptop (with help from USB stuff for
> networking). Everything mostly went as expected, except after the
> installation I got a screen saying crypttab couldn't find a specific
> partition.

What’s crypttab? At which point exactly does this screen appears:
before GRUB, after GRUB, once the Linux kernel has booted?

Toggle quote (8 lines)
> I assume this was something left over from a previous OS installation
> since wiping the partitions with cfdisk and then installing worked
> fine. Note that while my initial install attempts did use encryption,
> the final (successful) one did not; I don't think this has any effect
> one way or the other on the viability of installation since I ran into
> the same issue both with and without an encrypted Guix installation
> before wiping the partitions.

OK.

Toggle quote (2 lines)
> Hopefully it should be simple enough to just completely rewrite the partition table during installation and sidestep this issue.

Normally the installer will rewrite the partition table, unless (I
think) you choose to keep things unchanged.

Thanks,
Ludo’.
J
J
J. Sims wrote on 16 Dec 2022 20:15
lefLHY2vYpY59XPoXBfXbI-zguyFjxAu9qP_XyV9kQe1pSrRNlrwG2NN6AsLjS7ApJWvowP_0tZqx7S64GuOgHso2TYJ_obHqevjcDJsOsc=@protonmail.com
Hey,

Ludovic Courtès <ludo@gnu.org> wrote:

Toggle quote (3 lines)
> What’s crypttab? At which point exactly does this screen appears:
> before GRUB, after GRUB, once the Linux kernel has booted?

crypttab is some part of the LUKS encryption stuff. This appears to be a manpage for it: https://www.man7.org/linux/man-pages/man5/crypttab.5.html

The screen appears before GRUB.

I forgot to mention that the UUID of the partition it was looking for did not exist on-disk after completing the Guix installation process. Given the above manpage, I assume this means the crypttab file used in the encryption process wasn't fully replaced. Perhaps the file in question is appended to with Guix data rather than overwritten? Or perhaps it's not used at all for the way Guix does encryption and just gets left behind?

Toggle quote (3 lines)
> Normally the installer will rewrite the partition table, unless (I
> think) you choose to keep things unchanged.

Interesting... I did the full-disk guided installation method, so that should have done the trick, then.

This reminds me, I noticed that it didn't rewrite specifically the boot partition. When it showed the partition scheme at the end of the partitioning stage, it only showed it changing nvme0np2 (and nvme0np3 with encryption disabled - it only created swap with encryption disabled), while the boot was nvme0np1. After wiping the table, it showed all three.

Hopefully this helps.

Thanks,
Juli
L
L
Ludovic Courtès wrote on 17 Dec 2022 13:01
(name . J. Sims)(address . jtsims@protonmail.com)(name . 60104@debbugs.gnu.org)(address . 60104@debbugs.gnu.org)
875yeai6ie.fsf@gnu.org
Hi,

"J. Sims" <jtsims@protonmail.com> skribis:

Toggle quote (7 lines)
> Ludovic Courtès <ludo@gnu.org> wrote:
>
>> What’s crypttab? At which point exactly does this screen appears:
>> before GRUB, after GRUB, once the Linux kernel has booted?
>
> crypttab is some part of the LUKS encryption stuff. This appears to be a manpage for it: https://www.man7.org/linux/man-pages/man5/crypttab.5.html

Oh OK; Guix system doesn’t use that file.

Toggle quote (4 lines)
> The screen appears before GRUB.
>
> I forgot to mention that the UUID of the partition it was looking for did not exist on-disk after completing the Guix installation process. Given the above manpage, I assume this means the crypttab file used in the encryption process wasn't fully replaced. Perhaps the file in question is appended to with Guix data rather than overwritten? Or perhaps it's not used at all for the way Guix does encryption and just gets left behind?

‘guix system init’ and related commands error out if the config
specifies a file system UUID, a LUKS UUID, etc. that do not correspond
to an existing thing. So it’s unlikely that you managed to install Guix
System with a wrong UUID; likewise, the graphical installer is unlikely
to generate a config file with an incorrect UUID.

So the problem may be elsewhere.

Toggle quote (7 lines)
>> Normally the installer will rewrite the partition table, unless (I
>> think) you choose to keep things unchanged.
>
> Interesting... I did the full-disk guided installation method, so that should have done the trick, then.
>
> This reminds me, I noticed that it didn't rewrite specifically the boot partition. When it showed the partition scheme at the end of the partitioning stage, it only showed it changing nvme0np2 (and nvme0np3 with encryption disabled - it only created swap with encryption disabled), while the boot was nvme0np1. After wiping the table, it showed all three.

OK.

I’m afraid I’m not sure what happened. :-/

If you grab more details from your investigations, please share them.

Thanks for reporting the issue!

Ludo’.
?