Disk device disappears before installer can mount it

  • Done
  • quality assurance status badge
Details
4 participants
  • Graham Lee
  • Graham Lee
  • Ludovic Courtès
  • zimoun
Owner
unassigned
Submitted by
Graham Lee
Severity
normal

Debbugs page

G
G
Graham Lee wrote on 21 May 2019 16:20
(address . bug-guix@gnu.org)
CB17F322-B140-48EC-A8E2-1AECD8CAE231@iamleeg.com
Hi everyone,

I’ve retried installation using the 1.0.1 ISO (you may remember me from such bug reports as “Filesystem error in the installer”). The good news is that the FAT16 EFI partition no longer confuses the partition editor. The bad news…

To recap, I’m choosing the guided partition scheme, with everything in a single partition. The installer proposes a reasonable scheme: it keeps my EFI partition, then a big e4fs, then a Linux swap partition. I accept that, and go through connecting to a network, setting root password, adding a user, and choosing desktop and daemon packages. Then the next error.

Toggle quote (2 lines)
> In procedure mount: mount “/dev/sda1” on “/mnt/boot/efi”: No such device

Indeed if I press OK and rerun to the installer, then the next time it gets to the partition page it won’t see the SSD. It doesn’t get detected again until a reboot.

The SSD is Samsung SSD PM871 mSATA 256GB

I will try to replicate this by partitioning the disk at the manual installer shell, to capture dmesg output.

Thanks,
Graham.
Attachment: file
Attachment: IMG_0185.jpeg
G
G
Graham Lee wrote on 22 May 2019 01:34
Bug 35852
(address . 35852@debbugs.gnu.org)
A5E28571-A878-4442-9038-3F6D365F3493@gmail.com
I was unable to reproduce the problem with the command line installer (I used parted to set up partitions on the SSD). I was able to at least get to the “guix system init” stage, which is currently still running.

Graham.
L
L
Ludovic Courtès wrote on 25 May 2019 10:28
Re: bug#35852: Disk device disappears before installer can mount it
(name . Graham Lee)(address . graham@iamleeg.com)(address . 35852@debbugs.gnu.org)
87zhnapho0.fsf@gnu.org
Hello Graham,

Graham Lee <graham@iamleeg.com> skribis:

Toggle quote (9 lines)
> To recap, I’m choosing the guided partition scheme, with everything in a single partition. The installer proposes a reasonable scheme: it keeps my EFI partition, then a big e4fs, then a Linux swap partition.
> I accept that, and go through connecting to a network, setting root password, adding a user, and choosing desktop and daemon packages. Then the next error.
>
>> In procedure mount: mount “/dev/sda1” on “/mnt/boot/efi”: No such device
>
> Indeed if I press OK and rerun to the installer, then the next time it gets to the partition page it won’t see the SSD. It doesn’t get detected again until a reboot.
>
> The SSD is Samsung SSD PM871 mSATA 256GB

So IIUC, the SSD is initially detected correctly, which allows you to
partition it, but later on /dev/sda1 “disappears”, right?

Could it be that “/dev/sda1” is actually the wrong device name? What
does ‘mount’ and ‘fdisk -l /dev/sda’ show, once you’ve got the error
message?

Thanks,
Ludo’.
L
L
Ludovic Courtès wrote on 25 Apr 2021 13:12
control message for bug #35852
(address . control@debbugs.gnu.org)
87r1iyf7iz.fsf@gnu.org
tags 35852 + moreinfo
quit
Z
Z
zimoun wrote on 25 Nov 2021 17:26
Re: bug#35852: Bug 35852
(name . Graham Lee)(address . iamleeg@gmail.com)(address . 35852-done@debbugs.gnu.org)
86y25br9la.fsf@gmail.com
Hi,

On Wed, 22 May 2019 at 09:34, Graham Lee <iamleeg@gmail.com> wrote:

Toggle quote (4 lines)
> I was unable to reproduce the problem with the command line installer (I used
> parted to set up partitions on the SSD). I was able to at least get to the
> “guix system init” stage, which is currently still running.

The bug is marked ’moreinfo’ since Apr. 2021. The submitter has not
provided more info after 2019. So closing. If I miss something, feel
free to reopen.


Cheers,
simon
Closed
?
Your comment

This issue is archived.

To comment on this conversation send an email to 35852@patchwise.org

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