• Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Anton

  • Rank


  • Gender
  1. That is perfectly normal. Please look at this post: The answer from ken-ji describes what happens during boot time and solved exact the same problem for me! So don't panic, it will work
  2. Instead of generating: Cleaning /boot/config/ssh and /config/ssh and rebooting helps. Uninstalled the plugin as ssh is available without it (if the keys are not 0).
  3. Stop array for reboot, ... - 1/2 of the times my cache drives are unassigned after that. If not, they are unassigned after the reboot. This is really annoying... What do I have to do to save my drive configuration for the cache drives??? Thank you very much in advance!
  4. at least ... helpful .. children Can live with that
  5. Solved - Got an old IPMI card, made things a lot easier Space, etc. more than enough, but the ssh keys in /boot/config/ssh were all 0 bytes long. Delted them there, rebooted the system and... got valid ssh keys on both locations. No idea what happened to the /boot/config/ssh (as I did not have any idea how this was working until your very useful information here). TNX a lot!
  6. Sorry for the late answer and TNX for all the help! Learned some Slackware basics, checked port 22 - not listening, cleared up the /etc/ssh directory, started sshd: sshd generates a ssh_config (which looks good to me) and a lot of 0 byte long invalid keys which it is complaining about after (key_load_public: invalid format; Could not load host key ...) - all keys the same. How can I let unraid generate valid key pairs? Or do I have to do that manually? (I can generate them, but I do not think that is the planned way to setup unraid...)
  7. maybe?
  8. Thanks for the info! That's funny. Installed the trial, got too many drives, installed the bought key. tried ssh (not working). After that docker, installed the the ssh config tool to get ssh support, installation without any problems, but it said "ssh daemon not running", tried to start it, no error messages, nothing - some other people seem to have the same problem if you google for that tool, so ssh does not seem to work for "everyone else" - uninstalled it. Didnt' came to the ppk stuff as standard ssh was not working and the keyboard. So after your answer it is a con
  9. Thank you for your answer. That was fast No, it's not - was the first thing I tried (actually 2nd, 1st: change root password, 2nd check sssh, change to using ppks, disable root ssh, ... - normal for every linux system I install) "ssh: connect to host port 22: Connection refused"
  10. Googled. A lot. ssh support is built in in v6. There are plugins that enable ssh (why? thought it is built in), where you can even change a lot of setting, but they are not able to start the ssh daemon and are unmaintained (problem known, many months not a single reply, not to talk about fixes). Readme, manual, ... - not even a single word about ssh (not about how to enable it - it is used in vm setups, ... - but nobody is ever talking about how to get it running). So: Am I completely blind or is unraid not usable without it's own keyboard and monitor any more, as a NAS. I mean that
  11. Asking questions that only native english speakers that watch a lot of movies can know is the MOST STUPID verification method I ever seen since the beginning of the internet! Could anybody invest 5 minutes and use some standard captcha? Like the "i am no robot". Works in a fraction of a second for every user everywhere and saves a lot of time googling in movie databases...
  12. Same here. This plugin only adds some settings, ssh can not be started, no error messages, nothing. Seems like it is not maintained any more (since months)? P.S.: Asking questions that only native english speakers tha watch a lot of movies can know is the MOST SILLY verification method I ever seen since the beginning of the internet!