From: Tyler Wolf via <help-guix@gnu.org>
To: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: SSD keeps being lost, power source must be replugged to fix
Date: Mon, 14 Nov 2022 17:50:49 +0000 [thread overview]
Message-ID: <kpq27ZK_gYbJBD0xXupbibatlW2Dn0U8Y7DQ_jH5A7cFpOBBiEB_S0BLYnYG80MV5uIpo1c_iPghhujitPxblWprRgqaEDG6qpOC4wXoyos=@twolf.io> (raw)
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
reply other threads:[~2022-11-15 13:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='kpq27ZK_gYbJBD0xXupbibatlW2Dn0U8Y7DQ_jH5A7cFpOBBiEB_S0BLYnYG80MV5uIpo1c_iPghhujitPxblWprRgqaEDG6qpOC4wXoyos=@twolf.io' \
--to=help-guix@gnu.org \
--cc=tyler@twolf.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).