Install stuck for hours with 100% CPU usage #402
Comments
|
This problem seems to occur only in configurations where I use ZFS. If I change it to use F2FS, everything works fine. Perhaps I've made a mistake with ZFS, but both vmWithDisko and --vm-test seem to work fine. |
|
why are you auto-gc'ing so much == thats so crazy |
I dunno, am I supposed not to? |
|
it looks like you're running out of space during install |
|
I'm not sure that's the case, because an otherwise equivalent install using F2FS works. I'll try to make a minimal reproducible example |
Seems like you're right, because this little situation with unresponsive VPS happens at the same step as previously even if I disable garbage collection. But how can I check what causes this though? |
|
I would use disko-install to configure the storage with the disko config you are using and verify the sizes you think you are specifying are what ends up happening. I would not use nixos-anywhere until i knew my disko config was working as intended. verify that /nix/store is not too small. maybe share your disko config, and the output of you may consider getting on the nixos matrix chat if you want suggestions in real time |
Yeah, you're right, guessing the cause of the problem from my info so far is next to impossible :) Thanks, I'll try matrix |
|
This is the output of It makes sense that |
|
I am having a similar problem on a VPS with 1GB of RAM. I can I did the same on the same VPC ~1 month ago and it worked, I am not sure what changed. |
When using
nixos-anywhereto install, at one point the installation process gets stuck, VPS becomes highly unresponsive and CPU usage goes to the moon. I've tried to wait, but it doesn't seem to move further:The text was updated successfully, but these errors were encountered: