On 2025-04-08 11:05, ruthert...@ditigal.xyz wrote: > Hello Nicolas, > > As for your original question 'how can that even happen?', it's quite > common for this to happen if disk is not unmounted cleanly, especially > right after reconfigure. It's actually quite easy to 'reproduce' this is > a VM by issuing reconfigure and then forcefully shutting it down. Since > people usually reboot after reconfigure, it's a problem when the > disks aren't unmounting cleanly... (ie the issue linked 77086)
I thought that because we were using copy-on-write, the files only were actually saved on the filesystem when they were properly produced, and thus properly recorded in the gc. So it's not possible to have stronger guarantees on that issue? > So you are using luks, typed in your password, got a black screen so > forced shutdown? I don't even have the screen to type my password on LUKS ; it's just plain blank when I hit `reboot --kexec` and it hangs indefinitely, no message or nothing. > > I am thinking that your system might not have actually shutdowned > properly, because otherwise it doesn't make sense to me your store files > would get corrupted. When I reboot without kexec, my system usually complains about unmounted /run/user/1000, but I don't know if that might have something to do with it. > If you actually booted after typing in your password, no store files > would be modified as there is no guix command issued. And what was > from previous boot was already saved. And if that's so, I don't think > the bug you're linking is related. But we will probably never know for > sure. > In case you're running into this regularly, > 1. check your disk with programs for that, to know if it's fine, > 2. if disk is fine, do ensure, especially after reconfigures, your disk > is synced, ie. issue `sync` command. Probably best to do it before any > shutdown to be safe and to not lose any work. Specifically you would > have to close programs manually, best the whole session, run sync and > only then halt/reboot. > > Also see https://issues.guix.gnu.org/76959 for instructions from others > on how to recover if you're unsure. Based on how much damage was done > you might have to boot to a previous generation and remove the newer+gc, or > even go to a live iso and delete more than that. Thanks for the advice, I'll check that out! > > Regards, > Rutherther -- Best regards, Nicolas Graves
