GNU bug report logs -
#35852
Disk device disappears before installer can mount it
Previous Next
Reported by: Graham Lee <graham <at> iamleeg.com>
Date: Tue, 21 May 2019 23:21:01 UTC
Severity: normal
Tags: moreinfo
Done: zimoun <zimon.toutoune <at> gmail.com>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 35852 in the body.
You can then email your comments to 35852 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-guix <at> gnu.org
:
bug#35852
; Package
guix
.
(Tue, 21 May 2019 23:21:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Graham Lee <graham <at> iamleeg.com>
:
New bug report received and forwarded. Copy sent to
bug-guix <at> gnu.org
.
(Tue, 21 May 2019 23:21:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
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.
[Message part 2 (text/html, inline)]
[IMG_0185.jpeg (image/jpeg, inline)]
Information forwarded
to
bug-guix <at> gnu.org
:
bug#35852
; Package
guix
.
(Wed, 22 May 2019 13:31:03 GMT)
Full text and
rfc822 format available.
Message #8 received at 35852 <at> debbugs.gnu.org (full text, mbox):
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.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#35852
; Package
guix
.
(Sat, 25 May 2019 17:30:02 GMT)
Full text and
rfc822 format available.
Message #11 received at 35852 <at> debbugs.gnu.org (full text, mbox):
Hello Graham,
Graham Lee <graham <at> iamleeg.com> skribis:
> 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’.
Added tag(s) moreinfo.
Request was from
Ludovic Courtès <ludo <at> gnu.org>
to
control <at> debbugs.gnu.org
.
(Sun, 25 Apr 2021 20:13:02 GMT)
Full text and
rfc822 format available.
Reply sent
to
zimoun <zimon.toutoune <at> gmail.com>
:
You have taken responsibility.
(Fri, 26 Nov 2021 01:33:03 GMT)
Full text and
rfc822 format available.
Notification sent
to
Graham Lee <graham <at> iamleeg.com>
:
bug acknowledged by developer.
(Fri, 26 Nov 2021 01:33:03 GMT)
Full text and
rfc822 format available.
Message #18 received at 35852-done <at> debbugs.gnu.org (full text, mbox):
Hi,
On Wed, 22 May 2019 at 09:34, Graham Lee <iamleeg <at> gmail.com> wrote:
> 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.
<http://issues.guix.gnu.org/issue/35852>
Cheers,
simon
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Fri, 24 Dec 2021 12:24:06 GMT)
Full text and
rfc822 format available.
This bug report was last modified 2 years and 95 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.