EOS Gemini-2024.04.20.iso -- not working?

Is there an issue with calamares on this ISO ?

I cannot get an install started.

l have the logs from the install attempt, just am not certain how to attach them to a post.

If I followed the instructions correctly, the following are the logs from my install attempt

[liveuser@eos-2024.04.20 ~]$ inxi -Fxxc0z | eos-sendlog

Try unplugging some of those USB drives if you don’t need them for the install.

1 Like

What @dalto said. I always unplug all USB devices except keyboard and mouse when installing any distro.

will try with two USB devices pulled

I need the one that holds the ISO stick

still does not open calamares w the two USB devices unplugged

Before launching the installer, try deleting the partitions that you were planning to replace. For some reason, Calamares doesn’t see that any disk space is available.

currently the partition I would delete is labeled: /dev/nvme0n1p7

will that partition keep the “dev/nvme0n1p7” designation or need to be reformatted or?

I am hesitant to delete that partition without knowing calamares will recognize it as empty and available for an install. Prior to the advice to unplug unused USB devices, I had a near empty 900 GB SSD plugged in and that did not seem to be recognized by calamares as free space. ____ (the 900 GB SSD is formatted fat32, might that be part of the problem? also it is designated as /dev/sdb1 )

you could show the current partitions:
sudo fdisk -l | eos-sendlog
this will show all partitions and formats plus details about disk scheme

If you delete it, it will turn into open space. Calamares can use the open space with the “Replace Partition” option.

1 Like

And no there is no general issue with calamares on Gemini :wink:
We do test every release internal with a group of testers to make sure it does work properly.

1 Like
Disk /dev/nvme0n1: 476.94 GiB, 512110190592 bytes, 1000215216 sectors
Disk model: Micron MTFDKBA512TFH                    
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: A49168DC-16E6-4306-8837-805134E05C54

Device             Start        End   Sectors   Size Type
/dev/nvme0n1p1      2048     534527    532480   260M EFI System
/dev/nvme0n1p2    534528     567295     32768    16M Microsoft reserved
/dev/nvme0n1p3    567296  175783935 175216640  83.5G Microsoft basic data
/dev/nvme0n1p4 996118528 1000214527   4096000     2G Windows recovery environment
/dev/nvme0n1p5 175785984  261101567  85315584  40.7G Linux filesystem
/dev/nvme0n1p6 261107712  446332927 185225216  88.3G Linux filesystem
/dev/nvme0n1p7 446334976  651956223 205621248    98G Linux filesystem
/dev/nvme0n1p8 651956224  713218047  61261824  29.2G Linux swap
/dev/nvme0n1p9 713220096  996118527 282898432 134.9G Linux filesystem

Partition table entries are not in disk order.

Disk /dev/sda: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: PSSD T7 Shield  
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 33553920 bytes
Disklabel type: dos
Disk identifier: 0x1957c1df

Device     Boot     Start       End   Sectors   Size Id Type
/dev/sda1            2048 519921663 519919616 247.9G  b W95 FAT32
/dev/sda2       519921664 704487423 184565760    88G 83 Linux
/dev/sda3       704487424 930177023 225689600 107.6G 83 Linux

Disk /dev/sdb: 14.84 GiB, 15938355200 bytes, 31129600 sectors
Disk model: STORE N GO      
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: 0x07bc774a

Device     Boot Start      End  Sectors  Size Id Type
/dev/sdb1        8064 31129599 31121536 14.8G  c W95 FAT32 (LBA)

Disk /dev/sdc: 7.36 GiB, 7897874432 bytes, 15425536 sectors
Disk model: Transcend 8GB   
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: 0x7498467c

Device     Boot   Start     End Sectors  Size Id Type
/dev/sdc1  *         64 5249887 5249824  2.5G  0 Empty
/dev/sdc2       5249888 5575519  325632  159M ef EFI (FAT-12/16/32)

I notice the installed drive is labeled “gpt” and the USB connected drive is labeled “dos”

Also, KDEpartition manager does not recognize the USB connected drive – no valid partition table

joekamprad, might you have a suggestion or solution based on the eos sendlog?

(I gather all the variables of software and hardware introduce fairly unique operational quirks.)

That is normal

Often, USB drives don’t have a partition table

Have you tried the solution proposed above with deleting the partition?

1 Like

this one should be usable to install with the replace partition option, as dalto suggested… You can try erasing the partition only this one before starting installer and check it after choosing replace partition.

You could also post the link to an installer log also it does not start it will include some hint on where it is failing. You can try start installer and send it via log tool or from command line:
cat ~/endeavour-install.log | eos-sendlog


this one?

     Required  storage B: 6442450944 "(5.5GiB)" 
     Available storage B: 1048576 "(0GiB)" 
    ..  Partition "/dev/nvme0n1p7" authorized for resize + autopartition install. 
    .. contains resizable "/dev/nvme0n1p7" 
    ..  Checking if "/dev/nvme0n1p7" can be replaced. 
    ..  Partition "/dev/nvme0n1p7" authorized for replace install. 
    .. contains replaceable "/dev/nvme0n1p7"

i do see all drives and partitions are detected and marked to be available for install, there is no free space (empty) but you should be able to replace partition /dev/nvme0n1p7

Neither GParted or KDE partition manager appear to allow resizing or deletion.