GNU bug report logs - #68905
Boot fails when symlink exists

Previous Next

To reply to this bug, email your comments to 68905 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Pierre Neidhardt <vabagot <at> disroot.org>
To: bug-guix <at> gnu.org
Subject: Boot fails when symlink exists
Date: Fri, 02 Feb 2024 18:55:58 +0100

Today my Guix System crashed during the boot process for external
reasons.

Upon restart, booting a system would drop into the REPL right after the
following line:

--8<---------------cut here---------------start------------->8---
making '/var/...' the current system...
--8<---------------cut here---------------end--------------->8---

complaining that the symlink already exists.

I checked gnu/build/activation.scm (activate-current-system), and there
is this:

--8<---------------cut here---------------start------------->8---
  ;; Atomically make SYSTEM current.
  (let ((new (string-append %current-system ".new")))
    (symlink system new)
    (rename-file new %current-system)))
--8<---------------cut here---------------end--------------->8---

And indeed, there was a dangling /run/current-system.new file on my
disk.
After removing it (from a live USB, didn't know how to do this from the
Guile REPL), the system succeeded to boot.

The fix should be easy: ensure that (symlink system new) overwrites any
potentially existing file.

Cheers!
Pierre

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.