qos-scheduler pending/NodeAffinity after cluster restart

When restarting the control plane of the K3s cluster (in our case, an AMD64 laptop), the cluster restarts and almost all pods are running except for the ones below.

qos-scheduler (Pending/NodeAffinity):

Events:                                                                                                                                                  │
│   Type     Reason                           Age                    From     Message                                                                      │
│   ----     ------                           ----                   ----     -------                                                                      │
│   Warning  FailedToRetrieveImagePullSecret  19m (x169 over 3h50m)  kubelet  Unable to retrieve some image pull secrets (qos-registry-access); attempting │
│  to pull the image may not succeed.                                                                                                                      │
│   Warning  NodeAffinity                     12m                    kubelet  Predicate NodeAffinity failed: node(s) didn't match Pod's node affinity/sele │
│ ctor                                                                                                                                                     │
│   Warning  FailedMount                      12m (x2 over 12m)      kubelet  MountVolume.SetUp failed for volume "scheduler-configmap" : object "kube-sys │
│ tem"/"qosscheduler-config" not registered