I'm glad it was helpful for you. That failure tripped me up for quite a while when I first encountered it. Thanks for watching!

I can try to help. I have yet to delve into impermanence much myself at this point so my knowledge is somewhat limited. The first thing I would check is that you have your age/access `keys.txt` files stored in directories that are set to persist. In the video and my nix-config repo, the hosts-level access key is stored at the default location '/var/lib/sops-nix/key.txt' and that path is declared in the `hosts/common/core/sops.nix` module. The home-level dev access key is stored at `/home//.config/sops/age/keys.txt` and the path for that is declared in the `home//common/optional/sops.nix` module. You could either persist those locations (assuming you used the same paths as I did) or move the keys and declared paths to a location that you prefer and that you are declaring as persistent. In the case of the host-level keys.txt path, since it is auto generated when required, you should be able to just change the declared path and it will generate the keys to that location based on the hosts ssh key. Considering the key is auto-generated that leads to the other potential issue. You may need to use the `neededForBoot` to ensure the related partitions are mounted early enough and also ensure that sops activation occurs after impermanence does its thing. There is an issue open issue on the sops-nix repo that goes into more detail on all of the above: github.com/Mic92/sops-nix/issues/149 The first several comments address the first bit and the `neededForBoot` and activation order are addressed in this comment: github.com/Mic92/sops-nix/issues/149#issuecomment-1596029524 I hope that points you in the right direction. Let me know how it goes and thanks for watching!

​@@Emergent_Mind Thanks, ' fileSystems."/pathOf/sops-nix-key".neededForBoot = true; ' fixed the problem. really appriciate your help

Excellent, glad I could help.