You are not logged in.
I am facing an issue after attempting to install a new PCIE network card. The card itself works fine, however I noticed that /var is being created by my system (only when network card is installed) prior to my systems actual /var being mounted, causing a conflict. System boots fine and is fully functional when this happens, however all my docker containers etc are gone as a result of this issue, causing this to be a blocker for using my new card.
Details:
- /(root) is on ZFS, with `/var` being within its own dataset in the pool
- boot hooks are used to decrypt, partprobe the LUKs encrypted partition(s) which contain my ZFS filesystem
- ZFS is mounted via cachefile
My main ask here is if there is a way to disable my system from creating /var or if there is a way to influence the order so that my boot hooks run and mount my pool(s) prior to this occurring during boot? I attempted to blacklist the card however that doesn't prevent the creation of /var.
mkinitcpio.conf:
HOOKS="base udev autodetect modconf block keyboard encrypt load_part zfs filesystems"The custom load_part hook is simply running partprobe so the system can then see/import my pool(s) after decryption.
Last edited by Oskrg_Rst (2020-07-12 23:10:49)
Offline
I over-complicated this issue.. the fix was with ZFS the whole time, simply running:
zfs set overlay=on zroot/varThis resolved the problem. Able to boot into my system's natural state even though the erroneous/blank /var is getting created by just allowing ZFS to mount with the overlay option for the dataset containing /var
Offline