got exception while creating partitions

  • Open
  • quality assurance status badge
Details
3 participants
  • John Kehayias
  • Evgenii Lepikhin
  • Maxim Cournoyer
Owner
unassigned
Submitted by
Evgenii Lepikhin
Severity
normal
E
E
Evgenii Lepikhin wrote on 11 Aug 2021 07:11
(address . bug-guix@gnu.org)
CAHjPQwNQ5OVHRJsTTXdNmgy4b_JnMAS8x-8Aptuy-78H244QHQ@mail.gmail.com
Hi there,

I've got following exception while trying to install Guix (see attachment).
Two partitions were configured manually:

Device: /dev/sda1
MP: /
name: root
FS: ext4

Device: /dev/sdb1
MP: /data
name: <not set>
FS: ext4
Attachment: file
Attachment: PXL_20210811_050548369.MP.jpg
J
J
John Kehayias wrote on 17 Aug 2021 05:13
(name . 50004@debbugs.gnu.org)(address . 50004@debbugs.gnu.org)
6QWSWLeVCdLiqtNW45gVkmcldzhwozr86pBGhK5GBSHGLm6RaL98zT0A_0EZ6rEM9QhdeL9qytQHVP6_kj8vPafeES503LEoITCq03ig9Ro=@protonmail.com
Hi,

Thanks for filing this, I actually hit I think the same error when using the installer a week or 2 ago (built fresh from the main branch, not 1.3.0 which I found even flakier). This was on a nvme drive, also trying to just do the default ext4 partitions.

In general, it seems the partitioner is brittle: it didn't like some partially created partitions from a previous run, once made /boot an ext4 partition (rather than fat32), didn't like my messing with manual configuration.

In the end, I made sure to start with a clean (no partitions drive) and then it worked. I wish I had more detailed info, but for obvious reasons can't reproduce it now. I think I have some photos available, but looked like the same error I remember seeing.

Oh, and when there is a problem with partitions the installer kicks you back to the very beginning, which makes for a more tedious process in figuring out how to make it work.

Hope this is helpful!

John
M
M
Maxim Cournoyer wrote on 30 Aug 2021 22:51
(name . John Kehayias)(address . john.kehayias@protonmail.com)(name . 50004@debbugs.gnu.org)(address . 50004@debbugs.gnu.org)
87k0k2k66a.fsf@gmail.com
Hello,

John Kehayias <john.kehayias@protonmail.com> writes:

Toggle quote (23 lines)
> Hi,
>
> Thanks for filing this, I actually hit I think the same error when
> using the installer a week or 2 ago (built fresh from the main branch,
> not 1.3.0 which I found even flakier). This was on a nvme drive, also
> trying to just do the default ext4 partitions.
>
> In general, it seems the partitioner is brittle: it didn't like some
> partially created partitions from a previous run, once made /boot an
> ext4 partition (rather than fat32), didn't like my messing with manual
> configuration.
>
> In the end, I made sure to start with a clean (no partitions drive)
> and then it worked. I wish I had more detailed info, but for obvious
> reasons can't reproduce it now. I think I have some photos available,
> but looked like the same error I remember seeing.
>
> Oh, and when there is a problem with partitions the installer kicks
> you back to the very beginning, which makes for a more tedious process
> in figuring out how to make it work.
>
> Hope this is helpful!

This user experience is very valuable indeed. Thank you for taking the
time to send it here!

Maxim
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 50004@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 50004
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch