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) Nicolas Graves <ngra...@ngraves.fr> writes: > Possibly but I'm not 100% sure as I'm only able to diagnose it after the > fact. > > Here it happened as a side-effect of another bug (probably 76554, laptop > screen blank after kexec reboot). It hangs indefinitely so at some > point I have to force halt the computer from the power button. Maybe > that was the cause of the corruption I observe at reboot. So you are using luks, typed in your password, got a black screen so forced shutdown? 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. 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. > > It started to happen to me as soon as november / december. > I'm running shepherd 1.0.3 now so it doesn't seem fixed by that. 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. Regards, Rutherther
