This is on unraid 7.2.4
I use a nvme raid card as a single cache drive fromatted with xfs (it holds 4 x m2 nvme drives in a pcie 16x slot type card - a marvell nvme controller).
The card works perfectly fine with the stock unraid kernel.
after upgrading to the kernel from this repo, the drive still gets detected after a reboot, but it is not in the cache drive slot. doing the usual fix of setting the cache pool to zero slots and starting the array without the drive, stopping it and adding the drive does not help - the GUI simply will not show the drive as an available cache pool device.
Even when creating a new config, the GUI will not allow to add the drive as a cache pool despite it getting detected as nvme01 by the unassigned devices plugin.
Any idea what the issue could be? does unraid check for some identifier to exclude certain devices from being used as a cache pool device? Is there a config file I can edit to force the drive to an allowed cache pool device?
The only thing I noticed is that the stock unraid kernel detects the drive as "eui.xxxxx" whereas the kernel from this repo has an empty identifier for it. Maybe that is why the GUI will not allow the drive to be used?
This is on unraid 7.2.4
I use a nvme raid card as a single cache drive fromatted with xfs (it holds 4 x m2 nvme drives in a pcie 16x slot type card - a marvell nvme controller).
The card works perfectly fine with the stock unraid kernel.
after upgrading to the kernel from this repo, the drive still gets detected after a reboot, but it is not in the cache drive slot. doing the usual fix of setting the cache pool to zero slots and starting the array without the drive, stopping it and adding the drive does not help - the GUI simply will not show the drive as an available cache pool device.
Even when creating a new config, the GUI will not allow to add the drive as a cache pool despite it getting detected as nvme01 by the unassigned devices plugin.
Any idea what the issue could be? does unraid check for some identifier to exclude certain devices from being used as a cache pool device? Is there a config file I can edit to force the drive to an allowed cache pool device?
The only thing I noticed is that the stock unraid kernel detects the drive as "eui.xxxxx" whereas the kernel from this repo has an empty identifier for it. Maybe that is why the GUI will not allow the drive to be used?