Page MenuHomeSolus
Create Task
Maniphest T8767

Solus 4.1 Installation freezes on "examining local storage devices"
Open, Needs More InfoPublic
Actions

Description

As discussed here https://discuss.getsol.us/d/2789-installation-freezes-on-examining-local-storage-devices/ please fix this with solus 4.2.

I can do quick tests if needed.

I have a completely new system where this error happens with 1 TB nvme SSD (windows preinstalled).
Iso file is KDE 4.1 on USB (created with dd command) that I installed before without issues on another system with 256 GB SSD.
When this is fixed, I will finally be able to install solus on the 1 TB nvme. Now I'm using my old 256 GB SSD which i brought over from my last system.

Event Timeline

logTom created this task.Feb 25 2020, 8:02 AM
Herald added a project: Lacks Project. · View Herald TranscriptFeb 25 2020, 8:02 AM
DataDrake triaged this task as Needs More Info priority.Feb 25 2020, 4:03 PM
DataDrake edited projects, added Installation; removed Lacks Project.
DataDrake added a subscriber: DataDrake.

I need to know what drives you have, make and model.

logTom added a comment.Feb 25 2020, 4:09 PM

Yeah, here is the nvme:

SAMSUNG MZVLB1T0HBLR-000L7 at nvme0n1

lshw output:
*-storage

     description: SATA controller
     product: Cannon Lake PCH SATA AHCI Controller
     vendor: Intel Corporation
     physical id: 17
     bus info: pci@0000:00:17.0
     version: 10
     width: 32 bits
     clock: 66MHz
     capabilities: storage msi pm ahci_1.0 bus_master cap_list
     configuration: driver=ahci latency=0
     resources: irq:133 memory:d2434000-d2435fff memory:d243b000-d243b0ff ioport:4050(size=8) ioport:4040(size=4) ioport:4020(size=32) memory:d243a000-d243a7ff
*-pci:1
     description: PCI bridge
     product: Cannon Lake PCH PCI Express Root Port #21
     vendor: Intel Corporation
     physical id: 1b
     bus info: pci@0000:00:1b.0
     version: f0
     width: 32 bits
     clock: 33MHz
     capabilities: pci pciexpress msi pm normal_decode bus_master cap_list
     configuration: driver=pcieport
     resources: irq:122 memory:d2200000-d22fffff
   *-storage
        description: Non-Volatile memory controller
        product: NVMe SSD Controller SM981/PM981
        vendor: Samsung Electronics Co Ltd
        physical id: 0
        bus info: pci@0000:02:00.0
        version: 00
        width: 64 bits
        clock: 33MHz
        capabilities: storage pm msi pciexpress msix nvm_express bus_master cap_list
        configuration: driver=nvme latency=0
        resources: irq:16 memory:d2200000-d2203fff
logTom added a comment.EditedFeb 25 2020, 4:12 PM

I also have this 2 drives in this machine. I was able to install Solus KDE 4.1 on the 840 when it was in another PC.
Samsung SSD 850 PRO 256GB at sdb
Samsung SSD 840 PRO Series at sda

logTom added a comment.Feb 28 2020, 8:25 AM

Please let me know if you need even more info.

cbednarski added a subscriber: cbednarski.Mar 22 2020, 6:37 PM

I also ran into this problem. Following the advice here I was able to move past this simply by restarting the Install OS application.

Here's my output from fdisk -l. Of note, I have an existing Linux installation (Ubuntu) and Windows 10, with the 2tb drive mounted at specific mount point in Windows (i.e. mounted as a specified folder, not a drive letter like D:).

/dev/sdb is my Solus install target and I was able to successfully install after restarting the Install OS application. I don't see any logs to attach.

Disk /dev/nvme0n1: 477 GiB, 512110190592 bytes, 1000215216 sectors
Disk model: Samsung SSD 950 PRO 512GB               
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: FE4E7A01-012C-4084-9110-92B76B68C074

Device             Start        End   Sectors   Size Type
/dev/nvme0n1p1      2048     923647    921600   450M Windows recovery environment
/dev/nvme0n1p2    923648    1128447    204800   100M EFI System
/dev/nvme0n1p3   1128448    1161215     32768    16M Microsoft reserved
/dev/nvme0n1p4   1161216  999167176 998005961 475.9G Microsoft basic data
/dev/nvme0n1p5 999168000 1000212479   1044480   510M Windows recovery environment


Disk /dev/sda: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: Samsung SSD 860 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 2909B0C7-F37A-421A-9F14-9009B2D7B826

Device     Start        End    Sectors  Size Type
/dev/sda1     34      32767      32734   16M Microsoft reserved
/dev/sda2  32768 3907026943 3906994176  1.8T Microsoft basic data


Disk /dev/sdb: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Disk model: Samsung SSD 850 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: A83883E9-4307-4840-9009-D3322A548F58

Device       Start       End   Sectors   Size Type
/dev/sdb1     2048    999423    997376   487M EFI System
/dev/sdb2   999424   3999743   3000320   1.4G Linux filesystem
/dev/sdb3  3999744 976771071 972771328 463.9G Linux filesystem






Disk /dev/sdc: 14.6 GiB, 15610576896 bytes, 30489408 sectors
Disk model: DataTraveler SE9
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x107a5823

Device     Boot Start     End Sectors  Size Id Type
/dev/sdc1  *        0 3466623 3466624  1.7G  0 Empty
/dev/sdc2         136  123015  122880   60M ef EFI (FAT-12/16/32)


Disk /dev/mapper/live-base: 6.2 GiB, 6614667264 bytes, 12919272 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

I snipped a bunch of ramdisks (16) and loops (3) since I htink they're not relevant, e.g:

Disk /dev/ram0: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/loop0: 1.6 GiB, 1668644864 bytes, 3259072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Prambler added a subscriber: Prambler.Aug 24 2020, 1:10 PM

I had this same issue as well. My storage devices are an NVME SSD, 2 SATA SSDs and 1 HDD. I had Manjaro previously installed on one of the SSDs.

When this happened to me, I opened GParted and deleted all the partitions on the SSD with Manjaro on it and then restarted the installer. It went through the 'Disks' page of the installer without batting an eyelid. My guess is that it had some issues with seeing swap or other partitions made by another linux install?

Copyright © 2015-2021 Solus Project. The Solus logo is Copyright © 2016-2021 Solus Project. All Rights Reserved.