它昨晚工作了，从那以后我就没有重新启动服务器（它从一个 USB 硬盘驱动器复制几百 GB 到另一个 USB 硬盘驱动器，否则什么也不做），但现在我只能这样做：
aaron@aaron-VirtualDesktop:~$ ping 192.168.0.100
PING 192.168.0.100 (192.168.0.100) 56(84) bytes of data.
64 bytes from 192.168.0.100: icmp_seq=1 ttl=63 time=1.57 ms
64 bytes from 192.168.0.100: icmp_seq=2 ttl=63 time=2.60 ms
64 bytes from 192.168.0.100: icmp_seq=3 ttl=63 time=2.14 ms
64 bytes from 192.168.0.100: icmp_seq=4 ttl=63 time=2.56 ms
64 bytes from 192.168.0.100: icmp_seq=5 ttl=63 time=7.41 ms
^C
--- 192.168.0.100 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4007ms
rtt min/avg/max/mdev = 1.575/3.258/7.412/2.109 ms
aaron@aaron-VirtualDesktop:~$ ssh [email protected] -vvv
OpenSSH_7.2p2 Ubuntu-4ubuntu2.2, OpenSSL 1.0.2g 1 Mar 2016
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug2: resolving "192.168.0.100" port 22
debug2: ssh_connect_direct: needpriv 0
debug1: Connecting to 192.168.0.100 [192.168.0.100] port 22.
debug1: Connection established.
debug1: key_load_public: No such file or directory
debug1: identity file /home/aaron/.ssh/id_rsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/aaron/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/aaron/.ssh/id_dsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/aaron/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/aaron/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/aaron/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/aaron/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/aaron/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.2
ssh_exchange_identification: read: Connection reset by peer
aaron@aaron-VirtualDesktop:~$
我能找到的具有相同错误消息的唯一现有问题是这个，它在没有太多讨论且没有答案的情况下被删除： https://serverfault.com/q/799207
我真的不想拔掉插头并重新启动，那么有没有办法使用当前会话来解决这个问题？
答案1
感谢@derobert 帮助我解决这个问题。
事实证明，就我而言，系统驱动器以某种方式损坏，因此无法找到再次登录所需的文件。我比较了它正在复制的驱动器，看来复制进展顺利，我猜是因为当驱动器开始向南移动时，执行此操作所需的所有指令都已经在内存中了。
但看起来这里的解决方案是将系统从已知良好的备份重新映像到不同的驱动器上。 （这就是您进行备份的原因。）