"Unsupported manifest format" error, likely corrupt store
Hello, Yesterday my PC lost power and when I turned it back on I started getting the error "guix package: unsupported manifest format". I have tried using "guix time-machine" to revert to a working commit and try again but this does not work. I have also tried a roll-back. I then can see that my ~/.guix-profile/manifest is empty, thus I think it is safe to say that this is where the issue is originating, however I am unable to rewrite this file, so I was wondering if there was any fix to this? I have tried everything that I can think of to repopulate this file, running guix pull as well as pulling certain past commits that worked, however nothing is fixing this error. Running pull works without errors, but the problem persists. I think that my store must be corrupt, as if I run guix gc --verify=contents I get a lot of path was modified, expected hash x, got y errors. I have tried fixing this using repair flag for gc but it is unable to repair these. I also used the command "guix refresh" and saw that many packages needed to be refreshed, however I cannot finish this command as I get the following error: Backtrace: 13 (primitive-load "/home/tyler/.config/guix/current/bin/g…") In guix/ui.scm: 2275:7 12 (run-guix . _) 2238:10 11 (run-guix-command _ . _) In ice-9/boot-9.scm: 1752:10 10 (with-exception-handler _ _ #:unwind? _ # _) 1752:10 9 (with-exception-handler _ _ #:unwind? _ # _) In guix/store.scm: 661:37 8 (thunk) 2170:25 7 (run-with-store # …) In guix/scripts/refresh.scm: 567:14 6 (_ _) In srfi/srfi-1.scm: 634:9 5 (for-each # …) In guix/scripts/refresh.scm: 367:10 4 (check-for-package-update # …) In srfi/srfi-1.scm: 858:15 3 (any1 # …) In guix/gnu-maintenance.scm: 842:10 2 (_ _ . _) In ice-9/boot-9.scm: 1685:16 1 (raise-exception _ #:continuable? _) 1685:16 0 (raise-exception _ #:continuable? _) Any help would be greatly appreciated. Thanks,Tyler Wolf
SSD keeps being lost, power source must be replugged to fix
Hi! This is my first time using a mailing list, so apologies if any formatting is weird. I have an SSD connected to my system that uses f2fs, my config, which shows how it is mounted, can be found [here](https://codeberg.org/tylerwolf/dotfiles/src/commit/0eaa8430170c30360fc85e09f0e32b62f249f619/etc/config.scm#L98-L103) (this drive is labelled "S70 Blade"). Every once in a while, typically after I upgrade packages or reconfigure system or home, my SSD is lost. I still see the name in Thunar but I cannot open it, as I get an input/output error and if I run lsblk I do not see my SSD. This SSD is not my boot drive, so my system keeps working for the moment, yet I no longer have access to this drive. If I reboot my system, I will receive an error that the filesystem is broken, as the machine still cannot read the SSD, however this is fixed if I remove the power source from my computer and plug it back in. While I don't think it makes a difference in this case, my computer only has one M.2 SSD slot, so I use a PCIe adapter to use two. Initially I thought this might be the problem, but the drive that I am having trouble with is the one plugged directly into my motherboard, Does anyone know how to fix this? Is this a hardware problem? A Guix problem? Or perhaps a problem with f2fs. Any help is appreciated. Thanks, Tyler Wolf
