unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Graham Lee <graham@iamleeg.com>
To: 35852@debbugs.gnu.org
Subject: bug#35852: Disk device disappears before installer can mount it
Date: Wed, 22 May 2019 00:20:15 +0100	[thread overview]
Message-ID: <CB17F322-B140-48EC-A8E2-1AECD8CAE231@iamleeg.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1063 bytes --]

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.

> 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 #2.1: Type: text/html, Size: 1806 bytes --]

[-- Attachment #2.2: IMG_0185.jpeg --]
[-- Type: image/jpeg, Size: 397204 bytes --]

             reply	other threads:[~2019-05-21 23:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-21 23:20 Graham Lee [this message]
2019-05-22  8:34 ` bug#35852: Bug 35852 Graham Lee
2021-11-26  1:26   ` zimoun
2019-05-25 17:28 ` bug#35852: Disk device disappears before installer can mount it Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CB17F322-B140-48EC-A8E2-1AECD8CAE231@iamleeg.com \
    --to=graham@iamleeg.com \
    --cc=35852@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).