But I've put another drive in, that I want to install a non efi system on too.
booted back to bullseye to id the drive, its this one: (from dmesg) [ 7.366909] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 7.374281] ata5.00: both IDENTIFYs aborted, assuming NODEV [ 7.686897] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 7.690699] ata5.00: failed to IDENTIFY (I/O error, err_mask=0x100) [ 13.126916] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 13.130587] ata5.00: failed to IDENTIFY (I/O error, err_mask=0x100) [ 13.130593] ata5: limiting SATA link speed to 3.0 Gbps [ 18.502913] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 320) [ 18.507502] ata5.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded [ 18.507509] ata5.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out [ 18.507513] ata5.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out [ 18.507890] ata5.00: supports DRM functions and may not be fully accessible [ 18.508532] ata5.00: disabling queued TRIM support =========== [ 18.508537] ata5.00: ATA-11: Samsung SSD 870 QVO 1TB, SVQ02B6Q, max UDMA/133 =========== [ 18.508541] ata5.00: 1953525168 sectors, multi 1: LBA48 NCQ (depth 32), AA [ 18.512287] ata5.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded [ 18.512294] ata5.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out [ 18.512298] ata5.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out [ 18.512707] ata5.00: supports DRM functions and may not be fully accessible [ 18.513368] ata5.00: disabling queued TRIM support [ 18.515302] ata5.00: configured for UDMA/133 The installer does not identify it by the same names, so how do I install to this drive w/o touching any of the other 6 samsung EVO series drives. I've never learn to love gnome, and the kde5 you offer is buggier than a 10 day old road kill in August, so this time is a text install to see if I can put TDE in for a desktop. How do I proceed? The partitioner does not identify the drives found adequatly. The drive is plugged into the mainboard controller, I think to port 5 of 6. I could label it, but the partitioner doesn't do labels. This drive is new, and has not anything written to it. blkid is no help because udev, in naming drives puts the stuff on a separate controller for a raid 10 with 3 partitions on 4 drives completely out of order. This too is less than helpful. And the raid10 is my existing /home partition & swap. Ideas as to how to proceed? Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
