Hi Tanguy
"Tanguy Le Carrour" <tan...@bioneland.org> writes: > or "the day I lost my `head`" > or "happy ever after only lasts 6 years" > > Hi Guix, > > TL;DR my Guix System refuses to boot and I’m left with a "scheme screen of > death". It’s a single system+data encrypted partition. How am I supposed to > fix > that? > > This morning, I turned on my computer and… everything went I usual! I logged > in > and did what I had been happily doing weekly for the last six years: > > ``` > $ sudo guix system delete-generations; and guix home delete-generations; and > guix pull --delete-generations; and guix gc; and guix pull > ``` > > Everything went as usual. After that, I started working and quickly realized > that something was awfully wrong: basic commands like `head` were missing. > It’s > the first one I noticed, but `env` was also missing for instance. > > So I did what any act-and-think-later person would have done: I took a deep > breath… and rebooted! You know… "Have you tried to turn it off and on again" > kind of thinking. > > After having typed my encryption passphrase twice (actually, it was three > times, > for I never managed to type it right the first time), I ended up on the > "scheme > screen of death": > > ``` > making `/var…` the current system… > populating /etc from /gnu… > ice-9/boot-9.scm… > in procedure symlink: File exists Let me guess, you have /etc/guix/acl file pointing to a non existing store location. See https://issues.guix.gnu.org/77201, there is a bug with that that has the same symptom as you're experiencing. To fix it, delete this file in a live iso, and you should be good to go further. I am not sure in what state your system is, so I can't tell you if you will be able to boot. The commands you shared definitely should not cause the issues you are experiencing normally, something must've went wrong. If you still won't be able to boot, it's possible your generation is still somehow corrupted. In that case, it's probably easiest to boot into a live iso and reconfigure from a chroot. See the manual for instructions. (12.1 Chrooting into an existing system) > … > scheme@(guile-user)> > ``` > > As I `system delete-gererations`-ed few minutes ago, I have no way to boot on > the previous-now-gone system. Anyway, it was apparently broken. > Had it been a system only partition like the one I have at home, I would have > reinstalled it right away. But it’s not! It’s a single system+data encrypted > partition. > > I guess there a way to fix this somehow. But the only thing I can thing of is > to > reinstall on another disk and copy my data over, which sounds suboptimal. > > Can someone think of a clever way to fix it from the "scheme screen of death" > or a way to voodoo-cross reinstall without wiping out the data. You can reinstall(reinit) guix system without losing any data, you can always delete /gnu/store and /var/guix, and run guix system init from a live iso. That way you won't lose any data. But there might not be the need to do this for you, first try what I suggested above. (but note that since of the bug I outlined, you will still need to remove /etc/guix/acl) Just to make stuff faster in case it's not /etc/guix/acl, check also for special files (/bin/sh and /usr/bin/env by default, maybe you have more in your config), and see if there is file in the folder, but with .new extension. This is one other think that can cause symlink: File exists (but the log should look differently from what you sent, so I don't think that's it) Good luck, Rutherther
