• Posts

  • Joined

  • Last visited


  • Gender
  • Location
    San Diego

Recent Profile Visitors

1301 profile views

burtjr's Achievements


Contributor (5/14)



  1. Just made a quick VM and loaded up fine. See screen shots. The only thing I need to do was extract the image as it was a .gz and copy iy to my server. I didn't spend anytime with it, set it up with VNC as video. I should have stated I used the Linux template with no html edits and nothing passed through.
  2. Another option that worked for me to get Ethernet through the house was disconnecting the phone land line from the phone company, in my newish house (7yrs old) outside and installing a switch to the router and connected the phones lines inside the house to the switch. At least with mine I had CAT 5e already run for the phone lines and has worked perfect for 6 years. I have a line in every room albeit not in the location I would have chose, but gets me close. Now this will take away your land line phone, I used a VOIP service for a while, but ended up ditching it for my cell phone after never using the VOIP phone, not because it was bad, just wasn't as convenient.
  3. burtjr

    New build

    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.
  4. 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.
  5. 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
  6. 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.
  7. I would use it as a cache drive for dockers.
  8. 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.
  9. 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.
  10. 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.
  11. 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.
  12. Run fix common problems in troubleshooting mode, then post the logs if/when it happens again.
  13. 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 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 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 ( Jun 1 19:53:19 Tower sshd[14503]: refused connect from ( Jun 1 19:53:29 Tower sshd[14545]: refused connect from ( Jun 1 19:54:03 Tower sshd[14776]: refused connect from ( Jun 1 19:54:27 Tower sshd[14888]: refused connect from (
  14. 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.
  15. Take a look at the motherboard manual, I think the M2 drive will up a PCIE slot, although not sure which one.