Post-installation issue: Qubes attempts to "complete" configuration after every reboot

I rebooted again and this time rather than trying to recreate thin LV volumes, I picked existing (defaults were already there) and

salt.pillar [CRITICAL] Specified ext_pillar interface Y not available

Where Y is qvm_features, qvm_prefs, qvm_tags, the same as in this post except that I did not do any DIY steps or modifications.

sudo qubesctl state.highstate tells me there’s nothing to report and to check master log.

Salt logs:

  • minion - empty
  • minion.install - empty
  • master - empty
  • master.20240804.gz - contains empty master

One detail that may have been changed between successful installation in 1 and semi-successful 2, 3, 4 is I rechecked BIOS settings and could not boot with UEFI only meaning I’m in Legacy Mode now (I also can’t boot from install USB key with UEFI only), so I assume I couldn’t have done it before either so that should have been consistent throughout all attempts. I burned install file to ISO with dd during 1st install and Ubuntu USB Image Writer the 2nd time (and used that for 2, 3, 4).

Should I try to reinstall again? Not sure how many attempts it’d take to get a good one… I saw there’s a Community Guide for UEFI installation on ThinkPad - would that be worth a try?

Also spotted this about buggy Lenovo systems…