Hello,
I want to inform about issue reported as #77086. I thought this e-mail won't be necessary as it seemed the issue is fixed, but according to recent information from yesterday, it is still a problem. Currently Guix System faces a bug where your root file system might not be unmounted cleanly. The exact cause is unknown and it seems only some systems are affected. You can know if you are affected by seing automatic fsck repair on (every) boot. Of course this applies only if other causes are absent, ie. if you experienced power outage, hard shutdown or your disk is broken. The file corruption is most obvious when rebooting right after reconfigure where people's system in the store can get corrupted, see: https://issues.guix.gnu.org/76959 If you are affected, one way you can do to prevent file corruptions is to close your session manually and then call `sync` in a tty before turning your computer off. Another way is to use the sysrq magic: https://boilingsteam.com/kill-magic/ (Alt-SysRq s, u, b to sync, mount as read-only, reboot), but keep in mind this should be ran only if you have exited your programs manually, otherwise you're possibly risking more than gaining, since the programs won't be able to save to disk anymore. It is not completely clear if the issue happens only on reboots, or even on shutdown. If you've got more information, please share it. Regards, Rutherther More info about the issue&updates: https://issues.guix.gnu.org/77086 TL;DR symptom: fsck ran on boots often to be safe from corruption: shut down session manually, `sync` in tty, `reboot` then
