Destination storage device criteria for Fedora Silverblue 38 install?


I want to install Fedora Silverblue 38 onto my Crucial 2TB SATA SSD. The SSD is working fine in the Intel device, as I can boot into an NVME drive on that device, which has Windows 11 and see the 2TB Crucial SSD. Also, I can boot into Fedora Silverble 37 on a SSD that is connected to the device by USB cable, and that can see the Crucial 2TB SSD. The 2TB Crucial SSD is connected to the motherboard via SATA.

But when I boot into the Fedora Silverblue 38 installed USB device, it cannot see the Crucial 2TB SSD in order to pick it to install to. Is there a way I can make this work, or is the 2TB drive too large, or wrong in some other way?

Thank you

I just downloaded the Fedora Silverblue 37 media and created the bootable USB, and booted to that, and it also cannot see the 2TB Crucial SATA SSD. to install to.

Some more info: I created a Fedora Silverblue 37 installer USB storage device, and booted to that, still it cannot see the 2TB crucial drive I want to install to.

I then un-plugged the crucial SSD from SATA and connected it via USB to SATA cable. Still nope. I then booted into the Fedora Silverblue 37 USB media, and cholse to use Fedora, running from that USB, and ran lsblk, and there it is, the Crucial SSD 2TB is listed as sda. I then chose to install Fedora Silverblue from the activities menu, and it complains that there are no connected drives to install Fedora to.

For some reason, Fedora Silverblue does not deem the Crucial 2TB SATA SSD as a suitable destination drive, and I do not know why.

If you use the Fedora Workstation live install image, do you see the same behavior?

OK, more information. Using the Fedora Silverblue 37 Installer media, and just running it as a Fedora live, opening terminal, and running
sudo fdisk -l
the result is that the crucial MX500 disk is listed with these warnings in red.

partition 1 does not start on physical sector boundary.
GPT PMBR size mismatch (3979243 != 60063743) will be corrected by write.
The backup GPT table is not on the end of the device

I ‘fixed’ the first one by using fdisk to remove both partitions created by windows. I did not need those partitions, it was just a test.

I cannot figure out what the others mean, if they are important, or normal, if this disk is somehow counterfeit, or corrupted, or if it is normal and irrelevant. I will continue to research.

If you wiped out the partitions then it is simple to fix the errors by creating a totally new empty gpt partition table. The errors with partitioning may be causing the issue in visibility.

Leave the drive with no partitions and it should be available to install onto.