Jump to content

kuhnamatata

Members
  • Content Count

    74
  • Joined

  • Last visited

Community Reputation

0 Neutral

About kuhnamatata

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed
  1. Thank's for all your work, upgrade went well
  2. Updated from 6.7 everything looks good, thanks for all the work much appreciated
  3. Thanks Squid, that worked. After re-booting I opened the sabnzbd docker to edit and saw that the extra parameter field was filled in and the corresponding cores were highlighted in the gui, deleted the extra parameters, saved and restarted but this time the extra parameters came up blank (finally) only a single xml file now, no more (1) version.
  4. Same problem here with my-SABnzbd.xml there are two files with one named my-sabnzbd (1).xml being the most recent, the older file has the <ExtraParams>--cpuset-cpus=0,4</ExtraParams> the the most recent (1) version has a blank <ExtraParams/> line.
  5. Upgraded from 6.5.3 with no issue, I did have to remove cpu pinning from extra parameters on dockers and apply through gui and restart a VM though, gui looks great thanks for all the work
  6. Another Samsung SSD 850 EVO 500GB temp reading error, both of mine now have a 74C overheat warning and never went over 30C before update.
  7. Upgraded to RC8 from RC7 with no issues. Had to click Provision a few times to get it to work. Great to see the green lock and https in the browser now, nice work thanks
  8. 32GB (4*8GB) Maxed out my Supermicro - X10SL7-F, I run multiple VMs and dockers, typical usage 38%
  9. Anyone download the smc_read.zip lately listed on gridrunners YouTube video 'How to read OSK KEY....) I have downloaded it multiple times and if it doesn't say it's a corrupted file it has all the text shown in the video without the OSK key. I'd appreciate it someone else would give it a try and see if they have the same problem, I have everything set to go except for the key, Thanks
  10. Updated from 6.1.9 no problems, just had to rebuild docker image file
  11. If you still have PLEXPASS Set to 1 in your variables you need to remove it, won't update to BETA if it's still there
  12. ashman Pretty sure I got the upgrade executable from here https://www.microsoft.com/en-us/software-download/windows10
  13. My Windows 10 anniversary upgrade installed with no problems, I'm on 6.1.9 set to 1 core and used Windows10Upgrade9252.exe to upgrade, I suspect that you do need 20GB for the upgrade