Hi Raghav,

On Mon, 31 Aug 2020 05:48:30 -0400
Raghav Gururajan <raghavgururajan@disroot.org> wrote:

> Hello Guix!
> 
> [1] Out of no where, when I did `guix environment foo`, I got:
> 
> \note: build failure may have been caused by lack of free disk space
> builder for `/gnu/store/2ajnpcblwpgzjdhx3050qapy3li31pr5-profile.drv'
> failed with exit code 1
> 
> [2] When I redid the command 2nd time, I got:
> 
> error (ignored): cannot unlink `/tmp/guix-build-profile.drv-0':
> Read-only file system
> error (ignored): cannot unlink
> `/gnu/store/2ajnpcblwpgzjdhx3050qapy3li31pr5-profile.drv.chroot/tmp/guix-build-profile.drv-0':
> Read-only file system
> guix environment: error: cannot link
> `/gnu/store/.links/1jd7y4xvj853m4aygnyixci5h2y7a1py6iavp9kwzvcinyniqwbd' to
> `/gnu/store/3klrs2bkcmypwnmx61q24rc7csgk19f8-profile/share/icons/Adwaita/64x64/emotes/face-smile-big
> symbolic.symbolic.png': Read-only file system

Usually that means file-system corruption, which very likely was caused by a
hardware (disk) problem.  I've had it before, and shortly after the disk died.

What does "sudo dmesg" show around the time it made it read-only?