How to restore backup files to /etc folder on zfs rpool

cmrho

New Member
Nov 4, 2024
24
5
3
So. I did a bonehead thing and had to reinstall pve. Fortunately, I had a backup of the /etc and /var/lib folders. I reinstalled a fresh pve installation, then scp'd the /etc files from the backup onto the new rpool. It mostly worked to restore my pve server. However, ever since then, I cannot ssh back into it.

(1) I tried to mount the old zfs rpool on a separate system, but can't seem to access where the /etc folder is located. All I see is ROOT, data, and var-lib folders. Does anyone know how to restore backed up host files to the mounted zfs pool?

(2) Or, this new installation will work, but I need to get ssh back up and running. I've checked the ssh.config and sshd.config files but they are largely the default settings.

Here's what the service status outputs

[ssh.service - OpenBSD Secure Shell server
Loaded: loaded (/lib/systemd/system/ssh.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Sat 2025-02-08 16:23:55 CST; 4h 8min ago
Docs: man:sshd(8)
man:sshd_config(5)
Process: 11904 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=1/FAILURE)
CPU: 6ms

Feb 08 16:23:55 pve systemd[1]: ssh.service: Scheduled restart job, restart counter is at 5.
Feb 08 16:23:55 pve systemd[1]: Stopped ssh.service - OpenBSD Secure Shell server.
Feb 08 16:23:55 pve systemd[1]: ssh.service: Start request repeated too quickly.
Feb 08 16:23:55 pve systemd[1]: ssh.service: Failed with result 'exit-code'.
Feb 08 16:23:55 pve systemd[1]: Failed to start ssh.service - OpenBSD Secure Shell server.
Feb 08 16:24:03 pve systemd[1]: ssh.service: Start request repeated too quickly.
Feb 08 16:24:03 pve systemd[1]: ssh.service: Failed with result 'exit-code'.
Feb 08 16:24:03 pve systemd[1]: Failed to start ssh.service - OpenBSD Secure Shell server.]


Other things I've checked:

- network interface(s) are good
- I can ssh TO other systems, I just can't ssh INTO the pve system

Thanks all!
 
So. I did a bonehead thing and had to reinstall pve. Fortunately, I had a backup of the /etc and /var/lib folders. I reinstalled a fresh pve installation, then scp'd the /etc files from the backup onto the new rpool. It mostly worked to restore my pve server. However, ever since then, I cannot ssh back into it.

(1) I tried to mount the old zfs rpool on a separate system, but can't seem to access where the /etc folder is located. All I see is ROOT, data, and var-lib folders. Does anyone know how to restore backed up host files to the mounted zfs pool?

(2) Or, this new installation will work, but I need to get ssh back up and running. I've checked the ssh.config and sshd.config files but they are largely the default settings.

Here's what the service status outputs

[ssh.service - OpenBSD Secure Shell server
Loaded: loaded (/lib/systemd/system/ssh.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Sat 2025-02-08 16:23:55 CST; 4h 8min ago
Docs: man:sshd(8)
man:sshd_config(5)
Process: 11904 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=1/FAILURE)
CPU: 6ms

Feb 08 16:23:55 pve systemd[1]: ssh.service: Scheduled restart job, restart counter is at 5.
Feb 08 16:23:55 pve systemd[1]: Stopped ssh.service - OpenBSD Secure Shell server.
Feb 08 16:23:55 pve systemd[1]: ssh.service: Start request repeated too quickly.
Feb 08 16:23:55 pve systemd[1]: ssh.service: Failed with result 'exit-code'.
Feb 08 16:23:55 pve systemd[1]: Failed to start ssh.service - OpenBSD Secure Shell server.
Feb 08 16:24:03 pve systemd[1]: ssh.service: Start request repeated too quickly.
Feb 08 16:24:03 pve systemd[1]: ssh.service: Failed with result 'exit-code'.
Feb 08 16:24:03 pve systemd[1]: Failed to start ssh.service - OpenBSD Secure Shell server.]


Other things I've checked:

- network interface(s) are good
- I can ssh TO other systems, I just can't ssh INTO the pve system

Thanks all!
Answering my own post as a record. I fixed this. The issue was that the ssh keys were too open. I found the issue(s) by running

Code:
/usr/sbin/sshd -T

It displayed the keys that were too open. I changed the access for those keys by using 'chmod 600 KEYNAME'

I then restarted ssh.