I hope that someone can me assist me on this. I’ve tried to get rid off the problem for 2 weeks but didn’t find a solution myself.
...
updating GRUB 2 menu...
lsblk: /dev/mapper/no*[0-9]: kein blockorientiertes Gerät
lsblk: /dev/mapper/raid*[0-9]: kein blockorientiertes Gerät
lsblk: /dev/mapper/disks*[0-9]: kein blockorientiertes Gerät
Found Windows 10 on /dev/sda1
activating the configuration...
/nix/store/vmkijy3aslx3cn7ry0qj355ra1wxc5yb-nixos-system-nixos-20.03.2516.674ab2dffa5/activate: line 63: 6185 Killed /nix/store/sg42gk32rbx5b3klmw9ql2sy165rnq8v-perl-5.30.1/bin/perl -w -I/nix/store/8s02cl42y2xjn87bj12ckcf7jg6wzh7n-perl5.30.1-File-Slurp-9999.29/lib/perl5/site_perl -I/nix/store/blknnx27sq31hbqdzh1i3z06af8lkd93-perl5.30.1-JSON-4.02/lib/perl5/site_perl /nix/store/w5s7s1nnzsmzdqh06abysffrj2m0nrwf-update-users-groups.pl /nix/store/m5kaj04ly5x646580l2p0x42jiv106qr-users-groups.json
Activation script snippet 'users' failed (137)
setting up /etc...
reloading user units for root...
reloading user units for sddm...
reloading user units for guido...
setting up tmpfiles
reloading the following units: dbus.service
restarting the following units: polkit.service
warning: error(s) occurred while switching to the new configuration
I do get the same error in line 63 when “starting activation script” in stage #2 of the boot process. Booting needs now between 20 - 60 minutes (before 1 - 2 minutes I guess).
Memory consumption is high from nscd, polkit, file.so … So I’ve stopped some services. Still the rebuild fails. The perl script consumes up to 2 GB.
At the risk of sounding like a simpleton, is adding more swap temporarily an option? I understand that if there’s a memory leak in the perl script this won’t help, but if the script just needs a bit more space it might help. Even plugging in an old usb stick might do it.
I run this laptop without swap and it worked like a charm before this happened.
I’ve traced the memory allocation of the script and it allocated more than 2 GB (!!!). Even this is a time consuming task. Adding swap will only prolong this.
Yes, like in the first installation process, you can mount the drives and do the nixos-install again.
(That is very handy if you system freezes in booting process [after you did a garbage collection before reboot])