burtjr

Members
  • Content count

    316
  • Joined

  • Last visited

Community Reputation

5 Neutral

About burtjr

  • Rank
    Advanced Member

Converted

  • Gender
    Male
  • Location
    San Diego

Recent Profile Visitors

158 profile views
  1. Probably because with out pictures it's just a computer that is used as a server. When pictures are attached you will probably get some comments.
  2. Not sure why you would use the word unfair, but I am sure there was some research prior to them deciding on a price point. Email them and see what they say.
  3. Here is what I got from google..... autocutsel tracks changes in the server's cutbuffer and clipboard selection. When the clipboard is changed, it updates the cutbuffer. When the cutbuffer is changed, it owns the clipboard selection. The cutbuffer and clipboard selection are always synchronized. Since the VNC client synchronizes the Windows' clipboard and the server's cutbuffer, all three "clipboards" are always kept synchronized. When you copy some text in Windows, the cutbuffer and the clipboard selection are updated. When you copy text on the server using either the cutbuffer or the clipboard selection, the Windows's clipboard is always updated
  4. I have the LN4 version of that board had the same issue and the below worked for me 1) Make a backup copy of /boot/syslinux/syslinux.cfg --> /boot/syslinux/syslinux.cfg_bak 2) Download latest unRAID zip file from our Downloads section 3) Extract the syslinux/syslinux.cfg from within the zip and overwrite /boot/syslinux/syslinux.cfg 4) Reboot unRAID and try booting non-GUI mode Another option if the above doesn't work is to start in gui mode. On a side note this board does take a while to get through the start up.
  5. I would use it as a cache drive for dockers.
  6. Update the firmware on the SASLP. The last I looked and it was a while ago was up to .21. I don't have the SS-500, I have IStar's, but they worked flawlessly on the SALSLP with the .21 firmware.
  7. The wiki is updated by anyone not Lime Technologies. If you have time put the information together and update the wiki. There is a thread all be it rather long that should give you what you need to get a Ryzen build going. I haven't kept up to date on the 6.4 testing on the Ryzen platform, but was thought to fix some major issues.
  8. Personally I would always attempt merging before upgrading. They will usually get you by and you can determine from there exactly what you will need if in fact you do need to upgrade.
  9. I'm not sure how long you waited for the server to power down, but in my experience it could take hours for it to properly power down because of what ever went rouge to slow down or lock it up. Other than patience and tailing the log to see what caused the server to get to that point I can see that you could have done anything different.
  10. Run fix common problems in troubleshooting mode, then post the logs if/when it happens again.
  11. I found the below in your log, not sure if this would cause your problem, the only other thing I saw in your diagnostic was some warnings in your libvirt.txt file. Although others with more knowledge of dockers and VM's will chime in, I would check your docker and VM set ups, starting with the one using IP address 218.87.108.154 and if they look good to you, shut down all dockers and VMS, check for stability then introduce one at a time until you find the one causing the instability. Jun 1 19:53:00 Tower sshd[14274]: error: maximum authentication attempts exceeded for root from 218.87.109.154 port 52885 ssh2 [preauth] Jun 1 19:53:00 Tower sshd[14274]: Disconnecting: Too many authentication failures [preauth] Jun 1 19:53:02 Tower sshd[14416]: refused connect from 218.87.109.154 (218.87.109.154) Jun 1 19:53:19 Tower sshd[14503]: refused connect from 59.45.175.34 (59.45.175.34) Jun 1 19:53:29 Tower sshd[14545]: refused connect from 116.31.116.39 (116.31.116.39) Jun 1 19:54:03 Tower sshd[14776]: refused connect from 59.45.175.34 (59.45.175.34) Jun 1 19:54:27 Tower sshd[14888]: refused connect from 116.31.116.39 (116.31.116.39)
  12. Think of a VM like a regular computer that your building. If you want to play newer games at the highest frame rates then you buy a top of the line graphics card. In a VM you have a virtual computer using the same hardware as a bare metal box only it's in 1 box and you pass through the card so the VM can use it.
  13. Take a look at the motherboard manual, I think the M2 drive will up a PCIE slot, although not sure which one.
  14. You should read the whole thread, it is a living and breathing document. I think the main fix was concerning the c states.
Copyright © 2005-2017 Lime Technology, Inc. unRAIDĀ® is a registered trademark of Lime Technology, Inc.