Well I guess I can try reseating it, good idea.
Unfortunately this server is remote from me, so might as well collect ideas
before driving over.
On Sun, Jan 16, 2022, 3:00 PM Joe Zeff <joe(a)zeff.us> wrote:
On 1/16/22 11:44 AM, Neal Becker wrote:
> Now it's dead again. I can ssh to the machine. I can cat
> /proc/partitions and no nvme shown. I can only issue a couple of
> commands (I guess whatever is builtin to bash?), but almost all just
> give I/O error. no sudo or journatctl.
>
I presume that you're logged in as yourself, so you might try this:
source .bashrc
Source is a bash builtin so will work and this should get back your
normal CLI environment. It shouldn't really be needed, but might help.
> The machine is only used for compute, not heavy I/O so not caused by ssd
> wear (and smartctl showed no wear at all).
I'm no hardware geek, but it sounds like the connections to the drive
are bad.
It just occurred to me that /home might be on that drive. If so, source
won't do any good and that will explain why you can't get much done
through ssh.
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure