SCSI

Members
  • Posts

    252
  • Joined

  • Last visited

Everything posted by SCSI

  1. The "Update Stack" does not update the application for me for some reason. I had to manually run "docker-compose pull && docker-compose up -d" to update the application.
  2. I just started using docker compose and took me a bit to figure out how to update the containers added with compose. Any updates on adding a docker-compose pull feature?
  3. After I upgraded from 6.10.2 to 6.10.3 on an Unraid VM on ESXi, all hard drives connected to a LSI SAS2008 HBA in IT Mode being passthrough are no longer detected. Reverting back to 6.10.2 from the "previous" folder did not fix the issue. Will work more on diagnosing this issue. Update: Restarting the ESXi host fixed the issue and HBA was still detected after upgrading to 6.10.3.
  4. Upgraded from RC3 without issues. I had to update my pfsense DNS resolver custom options to the following to get around the DNS rebinding protection enabled message when enabling SSL for the management access. server: private-domain: "myunraid.net"
  5. No I have not changed the root password prior to upgrading.
  6. Encountered "Invalid Username or Password" when login in with root to the web GUI after the upgrade on one of my servers. SSH still works when login in as root. I had no issues with the other server. I have to add that I had to do a scan and repair the USB drive prior to upgrading to 6.10.0-rc1 since it was not writable.
  7. Been trying to move from v2 to v3 but during database conversion, it keeps erroring out on the following. Deleting the database gets Sonarr v3 to properly start. Restoring the database fails with the same error. Still searching on a way to fix this issue. 20-12-16 23:32:43.2|Info|MigrationLogger|*** 139: add_download_history migrating *** 20-12-16 23:32:43.2|Info|add_download_history|Starting migration to 139 20-12-16 23:32:43.3|Error|MigrationLogger|Newtonsoft.Json.JsonReaderException: After parsing a value an unexpected character was encountered: a. Path 'downloadUrl', line 12, position 3. (Json snippet ' "<--error-->audioLanguages": "En') ---> Newtonsoft.Json.JsonReaderException: After parsing a value an unexpected character was encountered: a. Path 'downloadUrl', line 12, position 3. at Newtonsoft.Json.JsonTextReader.ParsePostValue (System.Boolean ignoreComments) [0x0019a] in <d47de75a7e3f422ca4ca64a654c80495>:0 at Newtonsoft.Json.JsonTextReader.Read () [0x0005a] in <d47de75a7e3f422ca4ca64a654c80495>:0
  8. Thank you for maintaining this plugin. I am still on unraid 6.9 beta 22 with the 2020.7.01 openvm plugin and have not seen the "ioctl" error in the syslog since the initial install 9 days ago. I also have not gone to the settings page. I saw your release notes for the newer openvm releases and having the "ioctl" message show up only a few times upon installation is good enough for me. Thanks again.
  9. Thank you for working on this issue.
  10. What version of ESXI are you using for testing? I just updated my host to the latest ESXi 7.0b and installed the latest version of openvmtools_compiled and I am not seeing the errors in the log since I restarted the server 5 hours ago. I was using the ESXI 7.0 GA release prior to updating. Update: Ok the errors appeared 10 minutes after I posted this. It looks like 7 error messages gets written every time I refresh the openVMTools_compiled setting page.
  11. After updating to 6.9.0-beta22 with the latest openVMTools_compiled plugin, the following started appearing in the logs every 5 minutes: Jun 30 20:05:00 unraid-server kernel: Unknown ioctl 1976 Removing the openvm plugin and rebooting the server, the messages above no longer appear in the syslog.
  12. Upgraded from 6.8.3 successfully and all is working but I am getting "kernel: Unknown ioctl 1976" in the syslogs. Still tracking what causing this. Reverting to 6.8.3 does not show that error. Update: The "kernel: Unknown ioctl 1976" in the syslog is related to the openvmtools_compiled plugin. The following errors does not occur when the openvm plugin is removed.
  13. I also had this issue. Also my unifi docker lost its network setting (none) and failed to start. I had to change it back to Custom:br0 and applied its static IP. I upgraded from rc1 to rc5. Errors: Nov 1 19:02:23 Frank-Server rc.docker: unifi-controller: Error response from daemon: user specified IP address is supported on user defined networks only Nov 1 19:02:23 Frank-Server rc.docker: Error: failed to start containers: unifi-controller.
  14. I upgraded two unraid servers (one on Esxi and the other baremetal) last night running 6.7.3 rc2 to 6.8 rc1 and no issues encountered so far. I was able to get wireguard working on the baremetal but not on the unraid running on Esxi. Still trying to troubleshoot my wireguard issue. My two servers are located in two different houses and the wireguard issue is behind a PFsense firewall.
  15. Updated two servers and no issues except no Open-VPN connection on one of the servers. I changed the Open-VPN network type from HOST to Bridge and I already have interface set to ETH0. The fix suggested by Stef-dk works. Thanks! Awesome new dashboard!! Great job guys!
  16. Upgraded two servers with no issues. Drank a beer for each update. I need to have more Unraid server so I can drink more beer :)
  17. Thanks for another great tutorial. Is there a way to disable the Letsencrypt welcome page to hide the service even more? I currently use subfolders that is named differently than the dockers pointed to them.
  18. Upgrade went without a hitch on two servers. Thank you team!
  19. No upgrade issues from 6.5.1. Awesome additions by bonienl.
  20. Just migrated to Tautulli from PlexPy. Thanks guys!
  21. Yes they are. The three disks spun down are 2TB and the other two active drives are 3 and 4 TB. If that is how parity is normally done with different sized drives then I apologize for not noticing it much sooner.
  22. unRAID 6.5.0-rc5 related question since the rc5 thread was locked: Any changes in how parity checks are done? This morning, I noticed that parity-check is still in progress but 3 of the 5 are spun-down. A parity check was started last night due to unclean shutdown since I had to manually shutdown the server since it was not rebooting after the RC4 to RC5 update. I will update to RC6 after the parity check is finished.
  23. My only complaint on the rapid releases lately is that my server uptime went down the drain. lol!
  24. Upgraded with no issues so far. AWESOMESAUCE indeed for the addition of a web-based Terminal application thanks to eschultz . Great work guys!
  25. Going to test this v2 on my main unraid server with Plex data on it and see how long it will take. Been wishing for a way to store Plex data in a container or an image file so that only one file needs to be backup instead of numerous small files. This v2 worked very well on my secondary unraid server. Thanks for this awesome plugin.