Hey everyone, I’m running into some trouble while trying to setup a new install of F43 Silverblue with 2x 128GB SSDs and 2x 6TB HDDs (each in RAID1) with the SSDs serving as cache for the spinning disks. Would like to have /efi/boot and /boot on the SSD raid array with 100GB allocated as cache, however I’m only seeing options for LVM2 with allocating the entire disks; I feel like I’m missing something obvious but not sure what. Any ideas?
An update; was able to partition /boot/efi and /boot on the SSD and added the HDD to a LVM group but there doesn’t appear to be a way to create LVM cache. Has anyone been able to do so?
Hello,
I expect, that you have the HW RAID controller. Are you able to see SSD in install GUI? If yes you could continue for example via: Fresh Fedora 43 WS installation does not support LVM, EXT4? - #8 by vzak11 . There is not necessary to do it manually, there is “Storage editor”. But for me was more easy to do it manually.
But your SPOC is HW controller…
Repair: SPOC is my typing error, it should by SPOF. It means Single Point Of Failure. If your HW controller failure you would have nothing. No OS, no data. I don’t think, that your model is good idea…
Hey Vladimir,
I’m using Intel VROC for RAID and can indeed see both RAID1 arrays for the SSD and HDD in the Blivet-GUI setup. The issue is that there does not appear to be a way to create LVM-cache for a partition (in this case for the SSD RAID array) nor to add a partition to the newly created LVM (from the HDD RAID array).
Unfortunately blivet-gui currently doesn’t support LVM cache so your only option is to add it manually after the installation (or create a cached LV before the installation and reuse it).
(blivet-gui used to support LVM cache in the past, but the support was removed many years ago)
Thank you for the confirmation, Vojtěch.
As an aside are there any plans to reintroduce the ability in the future?
Yes, unfortunately I don’t have as much time to work on blivet-gui as I wished, but I am slowly working on a new major release and LVM cache support is one of the features I’d like to add (or return in this case).