Unexpected problem with Guix System installer

  • Open
  • quality assurance status badge
Details
3 participants
  • Julien Lepiller
  • Mathieu
  • Mathieu Othacehe
Owner
unassigned
Submitted by
Mathieu
Severity
normal
M
M
Mathieu wrote on 24 Dec 2021 02:46
(address . bug-guix@gnu.org)
nmail.3.39.61c5268f.180115be.4062@debian-sid
Hey,

Trying to install Guix on a 32GB thum drive, I get the attached backtrace.

The partition table is gpt with 500MB for ESP, 20GB for /, 2GB for swap and remaining space for /home. I have tried btrfs and ext4 for / and /home but got backtraces related to either mkfs.btrfs or mkfs.ext4 in both cases. I also have tried encryption or no encryption, but still got backtraces. The partitions are created to the drive because I can see they are still there when I restart the installer.

This is not the drive that was used to boot the Guix installer in the first place.

Thanks, hope someone can understand what the issue is.
Attachment: 20211224_022912.jpg
J
J
Julien Lepiller wrote on 24 Dec 2021 12:15
7256B498-306F-4476-890C-738B3A8B2888@lepiller.eu
From the backtrace I can't tell you more than this. The installer tried to run "mkfs.btrfs -f /dev/napper/crypt" but the command ended with status 1 (error). Unfortunately guix didn't capture the error. Next time you try, could you run the failid command (you'll find the exact one at the bottom) from another tty and report any error message?

Le 23 décembre 2021 20:46:55 GMT-05:00, Mathieu <matf@disr.it> a écrit :
Toggle quote (9 lines)
>Hey,
>
>Trying to install Guix on a 32GB thum drive, I get the attached backtrace.
>
>The partition table is gpt with 500MB for ESP, 20GB for /, 2GB for swap and remaining space for /home. I have tried btrfs and ext4 for / and /home but got backtraces related to either mkfs.btrfs or mkfs.ext4 in both cases. I also have tried encryption or no encryption, but still got backtraces. The partitions are created to the drive because I can see they are still there when I restart the installer.
>
>This is not the drive that was used to boot the Guix installer in the first place.
>
>Thanks, hope someone can understand what the issue is.
Attachment: file
M
M
Mathieu Othacehe wrote on 12 Nov 2022 17:35
(name . Mathieu)(address . matf@disr.it)(address . 52767@debbugs.gnu.org)
87y1sguo4n.fsf@gnu.org
Hello Mathieu,

Toggle quote (5 lines)
> This is not the drive that was used to boot the Guix installer in the
> first place.
>
> Thanks, hope someone can understand what the issue is.

Sorry for the very late reply. We recently added a bunch of error
reporting features to the installer. Any chance you still have the
hardware around and would be able to test again using the latest
installation image available here:

That would be super useful for us :)

Thanks,

Mathieu
M
M
Mathieu wrote on 12 Nov 2022 23:51
(name . Mathieu Othacehe)(address . othacehe@gnu.org)(address . 52767@debbugs.gnu.org)
aeb9ae3e-050a-44df-8d5f-438e3519af1f@disroot.org
Hi Mathieu,

Good news about the new features of the installer, thanks for your work! I rarely use that machine but I am now wondering if I haven't managed to install Guix on it, in the end. If that is correct, and working fine, I doubt I will reinstall from scratch, but if it is not running Guix already, then I will let you know when I try again (it may be in weeks or months though).

That machine was supposed to be my test bed before deciding if I could migrate my main hardware to Guix, which I did a few months later.

Cheers,

Mathieu

On 2022-11-12 17:35 Mathieu Othacehe <othacehe@gnu.org> wrote:

Toggle quote (20 lines)
>
> Hello Mathieu,
>
>> This is not the drive that was used to boot the Guix installer in
>> the
>> first place.
>>
>> Thanks, hope someone can understand what the issue is.
>
> Sorry for the very late reply. We recently added a bunch of error
> reporting features to the installer. Any chance you still have the
> hardware around and would be able to test again using the latest
> installation image available here:
> https://guix.gnu.org/en/download/latest/?
>
> That would be super useful for us :)
>
> Thanks,
>
> Mathieu
?