How to get installer to select its SSD target?

[Haines]

I added a second SSD to a desktop machine and want to install the OS to it.

BIOS sees both SSDs. When I install the new SSD, $ lsblk indicates that the new and old SSD device names get swapped. My old SSD was originally /dev/nvme0, but with the insertion the new SSD it becomes /dev/nvme1. The new SSD is giiven the name /dev/nvme0. How do I tell the installer to install to the new SSD (now /dev/nvmw0)? It automatically tries to install the the old SSD (now /dev/nvme1). I used to simply detach the SATA able from HDs, but can't do that with SSDs

[Aki]

You can open a shell in the installer and blkid program to identify which device name identifies your older and newer disk during installation (before partitioning).

[Haines]

The problem was that I feared I was getting close to partitioning without having first selected its target. I now boldly go ahead, and eventually there does pop up a list of all accessible devices. So my question is answered. I then selected from the list the root partition of the new SSD (the SSD was already partitioned because I started to do a cross install and so partitioned it). Having done this I'm then told the EFI partition will be /dev/nvme0n1p2 and the installation will be to /devnvme1n1p2. The device /dev/nvme0n1p2 is the /boot/efi partition on my OLD SSD, while /dev/nvme1n1p2 is /root on the new SSD. I had thought a gpart would create /boot/efi/ automatically on the new SSD. Putting it instead on the OLD SSD makes it sound like I'll not be able to boot to the new SSD.

[arzgi]

I have only used expert install for a long time, and choose to partition myself, at least that enables to set the drive/partition bootable. I would guess it would be possible in other install methods.

[Aki]

[..] So my question is answered. [..]

Please mark the discussion as solved manually adding the tag [Solved] at the beginning of the first post.