Unexpected problem during install of Guix System 1.3.0

  • Done
  • quality assurance status badge
Details
3 participants
  • Bengt Richter
  • Matthias Cullmann
  • Mathieu Othacehe
Owner
unassigned
Submitted by
Matthias Cullmann
Severity
normal
M
M
Matthias Cullmann wrote on 14 May 2021 16:50
(address . bug-guix@gnu.org)
2ffb0d75-fa20-9354-bd0f-43c0b6f74015@gmail.com
Hi there,

I am trying to install Guix System 1.3.0 on an Asus ZenBook UX305 using
the wizard.

After the partitioning I get the error in the attached screen shot.

( mount "/dev/sda1" on "mnt/boot/ef" : No such device)

I had Linux installed already on this computer and would not need to
re-partition.

Any ideas how to fix this?

Thx & regards,

Matthias
Attachment: 20210514_164026.jpg
B
B
Bengt Richter wrote on 15 May 2021 11:35
(name . Matthias Cullmann)(address . matthias.cullmann@gmail.com)(address . 48419@debbugs.gnu.org)
20210515093506.GA2673@LionPure
Hi,

On +2021-05-14 16:50:48 +0200, Matthias Cullmann wrote:
Toggle quote (18 lines)
> Hi there,
>
> I am trying to install Guix System 1.3.0 on an Asus ZenBook UX305 using the
> wizard.
>
> After the partitioning I get the error in the attached screen shot.
>
> ( mount "/dev/sda1" on "mnt/boot/ef" : No such device)
>
> I had Linux installed already on this computer and would not need to
> re-partition.
>
> Any ideas how to fix this?
>
> Thx & regards,
>
> Matthias
>
what does this output?
Toggle snippet (3 lines)
$ ls /dev/disk/by-id/*|xargs file

Maybe you have nve disk that does not get translated to /dev/sdaX ?

If you have linux running, try
Toggle snippet (3 lines)
$ lsblk -f

Maybe you will see something like

nvme0n1
??nvme0n1p1 ...
??nvme0n1p2 ...

which would suggest that your
/dev/sda1
maybe should be
/dev/nvme0n1p1

but in general, IMO device references without unique id's are bloody feet waiting to happen.

I would suggest looking at uuid's for file systems, partitions, or devices,
such as you can view with lsblk

--
Regards,
Bengt Richter
M
M
Matthias Cullmann wrote on 18 May 2021 07:29
Fwd: bug#48419: Unexpected problem during install of Guix System 1.3.0
(address . 48419@debbugs.gnu.org)
CAGtLdtET6xXhKdHyJLcbEaYjY79d5QRa6YsrNOcurrShvHaPRg@mail.gmail.com
( I'm forwarding this to the list - forgot to reply all )

---------- Forwarded message ---------
From: Matthias Cullmann <matthias.cullmann@gmail.com>
Date: Sat, 15 May 2021 at 15:31
Subject: Re: bug#48419: Unexpected problem during install of Guix System
1.3.0
To: Bengt Richter <bokr@bokr.com>


Hi Bengt,

here is what I get ( now under MX linux on the same box ).

$ ls /dev/disk/by-id/*|xargs file
/dev/disk/by-id/ata-Micron_M600_MTFDDAV256MBF_154010B93F27: symbolic
link to ../../sda
/dev/disk/by-id/ata-Micron_M600_MTFDDAV256MBF_154010B93F27-part1: symbolic
link to ../../sda1
/dev/disk/by-id/ata-Micron_M600_MTFDDAV256MBF_154010B93F27-part2: symbolic
link to ../../sda2
/dev/disk/by-id/ata-Micron_M600_MTFDDAV256MBF_154010B93F27-part3: symbolic
link to ../../sda3
/dev/disk/by-id/wwn-0x500a075110b93f27: symbolic
link to ../../sda
/dev/disk/by-id/wwn-0x500a075110b93f27-part1: symbolic
link to ../../sda1
/dev/disk/by-id/wwn-0x500a075110b93f27-part2: symbolic
link to ../../sda2
/dev/disk/by-id/wwn-0x500a075110b93f27-part3: symbolic
link to ../../sda3

$ lsblk -f
NAME FSTYPE LABEL UUID FSAVAIL FSUSE%
MOUNTPOINT
sda
??sda1 vfat 7C99-13AE 251.8M 0%
/boot/efi
??sda2 ext4 rootMX19 90aa2c4f-5266-47bc-9b73-228c524b2790 211.2G 4% /
??sda3 swap swapMX bf24ea70-f3e5-4023-9367-98bcc1c464ac
[SWAP]

To me it looks quite standard?
Thx & regards.
Matthias


On Sat, 15 May 2021 at 11:35, Bengt Richter <bokr@bokr.com> wrote:

Toggle quote (55 lines)
> Hi,
>
> On +2021-05-14 16:50:48 +0200, Matthias Cullmann wrote:
> > Hi there,
> >
> > I am trying to install Guix System 1.3.0 on an Asus ZenBook UX305 using
> the
> > wizard.
> >
> > After the partitioning I get the error in the attached screen shot.
> >
> > ( mount "/dev/sda1" on "mnt/boot/ef" : No such device)
> >
> > I had Linux installed already on this computer and would not need to
> > re-partition.
> >
> > Any ideas how to fix this?
> >
> > Thx & regards,
> >
> > Matthias
> >
> what does this output?
> --8<---------------cut here---------------start------------->8---
> $ ls /dev/disk/by-id/*|xargs file
> --8<---------------cut here---------------end--------------->8---
>
> Maybe you have nve disk that does not get translated to /dev/sdaX ?
>
> If you have linux running, try
> --8<---------------cut here---------------start------------->8---
> $ lsblk -f
> --8<---------------cut here---------------end--------------->8---
>
> Maybe you will see something like
>
> nvme0n1
> ??nvme0n1p1 ...
> ??nvme0n1p2 ...
>
> which would suggest that your
> /dev/sda1
> maybe should be
> /dev/nvme0n1p1
>
> but in general, IMO device references without unique id's are bloody feet
> waiting to happen.
>
> I would suggest looking at uuid's for file systems, partitions, or devices,
> such as you can view with lsblk
>
> --
> Regards,
> Bengt Richter
>
Attachment: file
M
M
Mathieu Othacehe wrote on 13 Jun 2021 14:20
Re: bug#48419: Unexpected problem during install of Guix System 1.3.0
(name . Matthias Cullmann)(address . matthias.cullmann@gmail.com)(address . 48419@debbugs.gnu.org)
87fsxmgdmr.fsf@gnu.org
Hello Matthias,

Toggle quote (5 lines)
> I had Linux installed already on this computer and would not need to
> re-partition.
>
> Any ideas how to fix this?

Thanks for the report. This should be fixed with:
245cab2abc1fd74d1df489e500432c66c88f6b25. The issue was that the
installer could not mount FAT16 partitions.

Could you regenerate an installation image by running the following
command:

Toggle snippet (3 lines)
./pre-inst-env guix system image -t uncompressed-iso9660 gnu/system/install.scm

and confirm that it fixes your issue?

Thanks,

Mathieu
M
M
Matthias Cullmann wrote on 16 Jun 2021 21:01
(name . Mathieu Othacehe)(address . othacehe@gnu.org)(address . 48419@debbugs.gnu.org)
2d7ab241-aef4-fd20-27f7-b40a814033d0@gmail.com
Hello Mathieu,

thanks for you help.
I built the iso from commit 245cab2abc1fd74d1df489e500432c66c88f6b25 and
confirm that the partitioning works now.
Only need to figure out how to get my wifi running and soon I'll be
booting ;-)

Best regards,
Matthias

On 13.06.21 14:20, Mathieu Othacehe wrote:
Toggle quote (22 lines)
> Hello Matthias,
>
>> I had Linux installed already on this computer and would not need to
>> re-partition.
>>
>> Any ideas how to fix this?
> Thanks for the report. This should be fixed with:
> 245cab2abc1fd74d1df489e500432c66c88f6b25. The issue was that the
> installer could not mount FAT16 partitions.
>
> Could you regenerate an installation image by running the following
> command:
>
> --8<---------------cut here---------------start------------->8---
> ./pre-inst-env guix system image -t uncompressed-iso9660 gnu/system/install.scm
> --8<---------------cut here---------------end--------------->8---
>
> and confirm that it fixes your issue?
>
> Thanks,
>
> Mathieu
M
M
Mathieu Othacehe wrote on 17 Jun 2021 10:04
(name . Matthias Cullmann)(address . matthias.cullmann@gmail.com)(address . 48419-done@debbugs.gnu.org)
871r90lxx3.fsf@gnu.org
Hello Matthias,

Toggle quote (4 lines)
> I built the iso from commit 245cab2abc1fd74d1df489e500432c66c88f6b25 and
> confirm that the partitioning works now.
> Only need to figure out how to get my wifi running and soon I'll be booting

That's great to hear, thanks for testing! Regarding Wifi support, you
can have a look to:

Closing this one,

Thanks,

Mathieu
Closed
?
Your comment

This issue is archived.

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

To respond to this issue using the mumi CLI, first switch to it
mumi current 48419
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