demm , now it shows correctly the keyboard layout map; about the partitioning on calamares journalctl displayed errors with timestamp matching to the moment(s) when calamares crash choosing the Erase disk option:
Oct 30 16:48:10 localhost.localdomain kernel: squashfs: SQUASHFS error: Can't find a SQUASHFS superblock on sda3
Oct 30 16:48:10 localhost.localdomain kernel: EXT4-fs (sda3): unable to read superblock
Oct 30 16:48:10 localhost.localdomain kernel: EXT4-fs (sda3): unable to read superblock
Oct 30 16:48:10 localhost.localdomain kernel: EXT4-fs (sda3): unable to read superblock
Oct 30 16:48:10 localhost.localdomain kernel: FAT-fs (sda3): invalid media value (0x4c)
Oct 30 16:48:10 localhost.localdomain kernel: FAT-fs (sda3): invalid media value (0x4c)
Oct 30 16:48:10 localhost.localdomain kernel: ufs: You didn't specify the type of your ufs filesystem
mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ...
>>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
Oct 30 16:50:09 localhost.localdomain kernel: squashfs: SQUASHFS error: Can't find a SQUASHFS superblock on sda3
Oct 30 16:50:09 localhost.localdomain kernel: EXT4-fs (sda3): unable to read superblock
Oct 30 16:50:09 localhost.localdomain kernel: EXT4-fs (sda3): unable to read superblock
Oct 30 16:50:09 localhost.localdomain kernel: EXT4-fs (sda3): unable to read superblock
Oct 30 16:50:09 localhost.localdomain kernel: FAT-fs (sda3): invalid media value (0x4c)
Oct 30 16:50:09 localhost.localdomain kernel: FAT-fs (sda3): invalid media value (0x4c)
Oct 30 16:50:09 localhost.localdomain kernel: ufs: You didn't specify the type of your ufs filesystem
mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ...
>>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
Oct 30 16:55:59 localhost.localdomain kernel: squashfs: SQUASHFS error: Can't find a SQUASHFS superblock on sda3
Oct 30 16:55:59 localhost.localdomain kernel: EXT4-fs (sda3): unable to read superblock
Oct 30 16:55:59 localhost.localdomain kernel: EXT4-fs (sda3): unable to read superblock
Oct 30 16:55:59 localhost.localdomain kernel: EXT4-fs (sda3): unable to read superblock
Oct 30 16:55:59 localhost.localdomain kernel: FAT-fs (sda3): invalid media value (0x4c)
Oct 30 16:55:59 localhost.localdomain kernel: FAT-fs (sda3): invalid media value (0x4c)
Oct 30 16:55:59 localhost.localdomain kernel: ufs: You didn't specify the type of your ufs filesystem
mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ...
>>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
Oct 30 16:57:25 localhost.localdomain kernel: squashfs: SQUASHFS error: Can't find a SQUASHFS superblock on sda3
Oct 30 16:57:25 localhost.localdomain kernel: EXT4-fs (sda3): unable to read superblock
Oct 30 16:57:25 localhost.localdomain kernel: EXT4-fs (sda3): unable to read superblock
Oct 30 16:57:25 localhost.localdomain kernel: EXT4-fs (sda3): unable to read superblock
Oct 30 16:57:25 localhost.localdomain kernel: FAT-fs (sda3): invalid media value (0x4c)
Oct 30 16:57:25 localhost.localdomain kernel: FAT-fs (sda3): invalid media value (0x4c)
Oct 30 16:57:25 localhost.localdomain kernel: ufs: You didn't specify the type of your ufs filesystem
mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ...
>>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
All the logs and info come from a machine with a BIOS system using a MBR partitioning scheme, firstly I tested the live iso with a wiped out hardrive (previously backed up with clonezilla) and recently with my computer restored having 2 primary partitions (reserved to Windows) and 1 extended (which is sda3) with 2 distros, 2 swaps and 2 data partitions.