I have 2 disks , one have win 11 and the other pop os. when i boot from the fedora iso to install fedora to the pop os disk it reads both disks as it should, but the “storage editor” to make custom partitions shows only the win 11 disk. i can install fedora outside the “storage editor” using for example the “use entire disk” option but i can’t make make custom partitions.
The problem exist even if i format the pop os disk and leave it unallocated. One time tho it show up the pop os/unallocated disk and and didn’t show up the win 11 disk. Either way it didn’t show up both disk not even a single time and i tried it many times with many combinations.
I tried many distros like ubuntu, manjaro kde, pop os, linux mint, zoris os and i can normally make custom partitions with them. Fedora 41 which have the older installation menu can show both disks tho on custom mode, so it must be storage editor’s problem with the newr versions.
As you can see this is on a vmware worksation but i’m planning to buy a real second small nvme to install fedora (with seperate bootloaders) to see how it’s running on a real h/w.
The disk selection seems to be misleading. This should work:
On the Destination page select the disk where you want to install Fedora. The doubling of checkboxes on the left and check-sign on the right is misleading as well, try leaving only one check-box checked (the one where Fedora should be installed, like in the example screenshot below).
Then launch the Storage Editor. The disk previously selected should be displayed.
The fact that you can see the disk on the older installer, made me think of the problem you could have.
You could use this ISO to install direct F43 with an old installer:
Or better make a GPT partition table on the second disk.
Do you EFI or legacy boot?
It doesn’t work either. If i only select the disk that have the pop os installed on the “select destination” then the storage editor will show nothing.
There you should be able to select the disk and delete the partitions you do not need anymore.
Just after you can go back to “Use entire disk” and it should appear now.
p.s.
please take also my other comment in account, not seeing second disk or not offer it to install, as long it has an MBR boot record.
Because I used to use one disk for efi, boot and root and another disk for /home. This was easily done with the Blivet editor during the installation. I can no longer do this during the install, since the storage editor only sees one disk. This a major regression of usability. Unless, I’m missing some other tiny UI element somewhere to click on.
I’ve noticed this too with Fedora 44. The storage manager in the Anaconda installer doesn’t seem to see more than 1 disk.
Ideally I’d like to follow this tutorial somewhat, but install /home on a second drive.
The benefit of all the subvolumes in btrfs is you can then elect to omit more things from snapper snapshots. reducing snapshot sizes, and retaining items such as logs. between rollbacks.
Additional items covered are the use of LUKS2, but then requires some other manual edits and running some script, which im not thrilled with.
As a comparison, CachyOS seems to have done a good job with incorporating this all into their installer. Perhaps that can be referenced.
My posted was made based off of testing fedora 44 and 43 fresh installations on a vm. (VMware workstation.) It’s been a few weeks but both cases I had 2 nvme virtual disks, and the installer only ever seemed to see the first nvme virtual disk listed. (Which prevented me from mapping /home to the second disk.)
