SSH problem on Ultra 2

If you download the logs what do the lines look like that include SSH in services.conf

Thank you for the quick response.

It states SSH=1

@mdgm thank you for your help offer, I've been away from the device for the last couple of days, will do if I go there.

But I discovered this:

Feb 16 17:48:58 vega sshd[6050]: error: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
Feb 16 17:48:58 vega sshd[6050]: error: @ WARNING: UNPROTECTED PRIVATE KEY FILE! @
Feb 16 17:48:58 vega sshd[6050]: error: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
Feb 16 17:48:58 vega sshd[6050]: error: Permissions 0670 for '/etc/ssh/ssh_host_rsa_key' are too open.
Feb 16 17:48:58 vega sshd[6050]: error: It is recommended that your private key files are NOT accessible by others.
Feb 16 17:48:58 vega sshd[6050]: error: This private key will be ignored.
Feb 16 17:48:58 vega sshd[6050]: error: bad permissions: ignore key: /etc/ssh/ssh_host_rsa_key
Feb 16 17:48:58 vega sshd[6050]: error: Could not load host key: /etc/ssh/ssh_host_rsa_key
Feb 16 17:48:58 vega sshd[6050]: error: Could not load host key: /etc/ssh/ssh_host_dsa_key

I think I know how it happened, I was trying to change the permissions of a file, but I most probably did it too generic. This was also the reason that I did a OS reinstall as well.

Any ideas on how to fix it?

Problem solved. Let me write the steps that I did for future reference:

- the problem -- ssh lockdown due to too open RSA key, permissions messed up by the user

- the solution: *****do it at your own risk*****
1. put the ReadyNAS into tech support mode
2. telnet over port 23
3. log in with root username and password (google this password, it is easy to find)
4. mount the regular boot partition of the device as follows
echo DEVICE partitions > /etc/mdadm.conf
mdadm --examine --scan >> /etc/mdadm.conf
mdadm --assemble --scan
mount /dev/md0 /mnt
5. go to /etc/ssh/
6. rename the key files ssh_host_dsa_key and ssh_host_dsa_key.pub to another name for backup purposes using mv command
7. reboot the device
8. if you are using terminal, you should sudo the ssh or delete the keys on your computer prior to connection attempt

you should be good to go..

thanks to mdgm for the inspiration, some steps are copied from: http://onlyblueatwork.wordpress.com/201 ... -recovery/

As a faster alternative to step #4 - by mdgm

On RAIDiator: # /bin/start_raid.sh

On ReadyNAS OS 6: # rnutil start_raids

The mount command would still be needed (at least on RAIDiator).