| 13 Aug 2024 |
SigmaSquadron | Redacted or Malformed Event | 22:06:55 |
SigmaSquadron | Redacted or Malformed Event | 22:07:28 |
| 14 Aug 2024 |
| ·☽•Nameless☆•777 · ± joined the room. | 08:57:07 |
matthewcroughan | I can confirm the issue with nixos-install running out of memory still happens even with the latest disko and nix tooilng
evaluating derivation 'git+file:///home/matthew/git/nixcfg#nixosConfigurations.bpi-r4.config.syerror: build of '/nix/store/g952ci9c1fhdn61ybb71xd7yngspsbdk-homerouter-disko-images.drv' on 'ssh-ng://matthewcroughan@aarch64.nixos.community' failed: builder for '/nix/store/g952ci9c1fhdn61ybb71xd7yngspsbdk-homerouter-disko-images.drv' failed with exit code 123;
last 10 log lines:
> cp: cannot access '/nix/store/h60m1fwahjd2mv6gsg77ji3vb4gpj4dk-source/pkgs/applications/misc/tui-journal': Cannot allocate memory
> cp: cannot access '/nix/store/h60m1fwahjd2mv6gsg77ji3vb4gpj4dk-source/pkgs/applications/misc/tuir': Cannot allocate memory
> cp: cannot access '/nix/store/h60m1fwahjd2mv6gsg77ji3vb4gpj4dk-source/pkgs/applications/misc/tut': Cannot allocate memory
> cp: cannot access '/nix/store/h60m1fwahjd2mv6gsg77ji3vb4gpj4dk-source/pkgs/applications/misc/tuxclocker': Cannot allocate memory
> cp: cannot access '/nix/store/ia3ymz0pcg0w31091fb3w9jld3qa1kgp-util-linux-2.39.4-lib/share/locale/de/LC_MESSAGES': Cannot allocate memory
> cp: cannot access '/nix/store/ia3ymz0pcg0w31091fb3w9jld3qa1kgp-util-linux-2.39.4-lib/share/locale/es': Cannot allocate memory
> cp: cannot access '/nix/store/ia3ymz0pcg0w31091fb3w9jld3qa1kgp-util-linux-2.39.4-lib/share/locale/et': Cannot allocate memory
> cp: cannot access '/nix/store/kgdz4hwrdf6mir55xzmgmdnf9z75jm3l-tzdata-2024a/share/zoneinfo/right/Mexico': Cannot allocate memory
> cp: cannot access '/nix/store/l7gmwp99pwx2s20hy3hzhva0vxzpcwa9-systemd-minimal-256.2/share/dbus-1/services': Cannot allocate memory
> [ 152.515840] reboot: Power down
For full logs, run 'nix log /nix/store/g952ci9c1fhdn61ybb71xd7yngspsbdk-homerouter-disko-images.drv'.
| 17:58:10 |
matthewcroughan | All that can really be done in this scenario is trying again until it works | 17:58:30 |
matthewcroughan | It doesn't happen every time | 17:58:38 |
SigmaSquadron | Hi all. Is there a way to ensure a certain disk is processed first in a disko configuration? I have a detached-header LUKS setup that encrypts my internal disks and writes their headers to an USB device. Disko does encrypt both devices, but it processes the USB last, and it does so by deleting the headers and repartitioning. Is there a way to ensure it formats the USB before installing the headers? | 21:06:50 |
SigmaSquadron | * Hi all. Is there a way to ensure a certain disk is processed first in a disko configuration? I have a detached-header LUKS setup that encrypts my internal disks and writes their headers to an USB device. Disko does encrypt both devices, but it processes the USB last, and it does so by deleting the headers and repartitioning. Is there a way to ensure it formats the USB before installing the headers?
Sorry, I was looking for the priority option. | 21:12:26 |
SigmaSquadron | * Hi all. Is there a way to ensure a certain disk is processed first in a disko configuration? I have a detached-header LUKS setup that encrypts my internal disks and writes their headers to an USB device. Disko does encrypt both devices, but it processes the USB last, and it does so by deleting the headers and repartitioning. Is there a way to ensure it formats the USB before installing the headers?
Sorry, I was looking for the priority option.
| 21:20:39 |
SigmaSquadron | * Hi all. Is there a way to ensure a certain disk is processed first in a disko configuration? I have a detached-header LUKS setup that encrypts my internal disks and writes their headers to an USB device. Disko does encrypt both devices, but it processes the USB last, and it does so by deleting the headers and repartitioning. Is there a way to ensure it formats the USB before installing the headers?
Sorry, I was looking for the priority option.
| 21:20:49 |
SigmaSquadron | So, the priority option doesn't seem to reorder disk partitioning, only the partition creation order. | 21:22:24 |
SigmaSquadron | actually, it might not be a partitioning issue, just some disk weirdness: | 21:50:31 |