--- Begin Message ---
|
Subject: |
root: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY |
|
Date: |
Sun, 07 Feb 2016 16:21:35 -0500 |
I've been bitten by this once before, and a user on #guix did as well.
When there are problems in the root filesystem that fsck doesn't want to
fix automatically, the user is dumped into a guile prompt where PATH is
not set, and it's very inconvenient to run fsck manually.
This is what I just suggested that the user type, with apologies:
(use-modules (ice-9 ftw) (srfi srfi-26))
(define dirs (scandir "/gnu/store" (cut string-suffix? "e2fsprogs-1.42.13"
<>)))
(define e2fsck (string-append "/gnu/store/" (car dirs) "/sbin/e2fsck"))
(system* e2fsck "/dev/XXX")
Is there a better way?
Speaking from personal experience, it's very painful to do anything
non-trivial in that REPL. Even just adding readline would help a lot.
Maybe we should at least set PATH to include the available /bin and
/sbin directories before entering the REPL.
We should probably also handle errors from fsck specially.
Thoughts?
Mark
--- End Message ---
--- Begin Message ---
|
Subject: |
Re: bug#22588: root: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY |
|
Date: |
Mon, 08 Feb 2016 23:49:06 +0100 |
|
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) |
Mark H Weaver <address@hidden> skribis:
> Okay, I must admit that's a pretty great little hack, and a nice demo of
> how easy it is to hack something together like this in Guile.
It’s fun to think we have a compiler from a subset of Bourne shell to
the Guile VM. :-)
> Let's do it :)
Done in 6eb4390!
Thanks,
Ludo’.
--- End Message ---