On 1/15/24 14:56, gene heskett wrote:
root@coyote:~# for j in /dev/disk/by-id/* ; do printf '%s\t%s\n'
"$(realpath "$j")" "$j" ; done
/dev/sr0 /dev/disk/by-id/ata-ATAPI_iHAS424_B_3524253_327133504865
/dev/sdi /dev/disk/by-id/ata-Gigastone_SSD_GST02TBG221146
/dev/sdj1 /dev/disk/by-id/ata-Gigastone_SSD_GST02TBG221146-part1
/dev/sdh /dev/disk/by-id/ata-Gigastone_SSD_GSTD02TB230102
/dev/sdh1 /dev/disk/by-id/ata-Gigastone_SSD_GSTD02TB230102-part1
/dev/sdk /dev/disk/by-id/ata-Gigastone_SSD_GSTG02TB230206
/dev/sdk1 /dev/disk/by-id/ata-Gigastone_SSD_GSTG02TB230206-part1
/dev/sdf /dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302498T
... 2 pairs with identical "serial numbers", ...
Are you certain that it is not two drives that fail to connect at boot?
You previously posted smartctl reports indicating a bad SATA connection.
If you disconnect everything except one Gigastone SSD, connect it to a
known good motherboard SATA port using a known good SATA cable, connect
it to a known good PSU power cable, boot live media into a rescue shell,
examine the Gigastone, write down the serial number, shutdown, and
repeat for the four other Gigastone drives, can you confirm the
duplicate serial numbers?
David
