jaybird2203

Members
  • Posts

    56
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

jaybird2203's Achievements

Rookie

Rookie (2/14)

1

Reputation

  1. Yeah, that sorted the issue on my setup - thanks for the direction! Always get cautious about a plugin that manages a driver and the direction given is to remove the driver lol
  2. @ich777 Had to go back awhile but did this step and driver has updated. Still seeing the same web error about trying to download the last listed version in the pop up as well as the php error on the left side. Guessing I'd need to remove the plugin, reboot, reinstall the plugin yeah? Don't see any steps on removing the driver itself.
  3. Nope, doesn't bother me in the slightest. Was simply thinking if other users were looking for that instant gratification of deleting and getting an immediate update on size they could use that approach of navigating to the share tab until both had the same functionality implemented. Sent from my SM-G975W using Tapatalk
  4. I have the update recycle bin in the background set as yes and noticed that if you manually navigate to the shares tab then delete the files from there instead of the main settings page the size is still updated almost instantly. I'm guessing the two locations to empty the recycle bin are handled differently in regards to the listed size? Any intention to bring the shares tab into that same approach?
  5. Thanks for the quick response Squid, I've moved the flash drive to another port on the motherboard. This time its specifically a USB2 port. I'll continue to monitor. Is there any validation/test that can be done on the flash drive to ensure its not in early stages of dying? Drive itself is less than a year old since being replaced from a previous flash drive I was using for unraid.
  6. I've been running 6.8.0 rc-9 with only one issue that's happened twice. First time I wasn't able to capture it but this time I did. Last time the server had ~30 days of run time, this time its 21 days. It appears that when the server gets into this state it's no longer detected on the network yet you can access it directly (if you use the network location \\Tower) to view folder structure and use Dockers (webpages direct like tower:8080) but as soon as you attempt to copy a file the connection will drop and the client PC will report 0x8007003B. Has happened on two different PC's. I've attached the diagnostics while its in this state as well as provided a few screenshots of the webpage (that should be dark) yet its clearly white. Any assistance is greatly appreciated. tower-diagnostics-20191229-1218.zip
  7. I've been running 6.8.0 rc-9 with only one issue that's happened twice. First time I wasn't able to capture it but this time I did. Last time the server had ~30 days of run time, this time its 21 days. It appears that when the server gets into this state it's no longer detected on the network yet you can access it directly (if you use the network location \\Tower) to view folder structure and use Dockers (webpages direct like tower:8080) but as soon as you attempt to copy a file the connection will drop and the client PC will report 0x8007003B. Has happened on two different PC's. I've attached the diagnostics while its in this state as well as provided a few screenshots of the webpage (that should be dark) yet its clearly white. Any assistance is greatly appreciated. tower-diagnostics-20191229-1218.zip
  8. Appreciate the quick response. OK, so the scenario is to be expected then. I swear I used to recall there was a time recently where you could trigger the mover and remain on that page at which point once the mover was finished the page/button would revert back to being able to trigger again (not that you would)
  9. Was running rc7 for ~40 days (upgraded to rc7 shortly after its release) until I had an issue with my system recently where the main web page background was completely white with the text being slightly grey despite my theme being set to black along with an inability to restart some dockers after a power outage running on UPS. Hard reboot of the system brought that back but ever since then things have been "off" from normal operations. Attached diagnostics are from ~20 mins prior to this post while running rc9 and reverting the majority of the issues I could correct easily. Core System specs: Asus Crosshair 6 w/3900x (7501 bios), 32 GB DDR4 ram. Now I may have other underlying issues that may be influencing this (and I'd love some assistance pointing out potential ones) but I just noticed that with both Chrome and Edge web browsers there are pages that are not updating automatically. One such page is when starting the Mover manually. It does not revert back to the Orange Move now but but stay with the greyed out Move Now button and "Disabled - Mover is running." message being shown. CPU dashboard is showing that its appears to be updating dynamically there but I'm at a loss for where to check/test next to address this. The file share functionality and the Dockers are still operating normally as best I can tell and a quick revert to rc7 didn't change this behavior. Any thoughts? (marking this as Minor to rule out other potential issues first but if its only webpage related then should be annoyance) tower-diagnostics-20191208-1547.zip
  10. Quick question that I may have missed so apologies in advance. Looking for the proper way to setup Radarr to use the standard unraid recycle bin plug-in by dlandon rather than pointing to a empty folder then manually deleting from there. Any assistance with this is greatly appreciated.
  11. Upgraded directly from 6.6.6 with no issues. Been running ~4 days no issues, Ryzen 1700 + Asus Crosshair mobo.
  12. Appreciate the quick turn around. Can report that the details do remain after the upgrade so that portion was addressed. Sent from my SM-T700 using Tapatalk
  13. Hi All, Having an issue with the recent linuxserver/openvpn-as repo build of Openvpn-as that I hope someone can shed some light. Running 6.7.0-rc-7 right now, haven't updated openVPN in ages (can't recall prior build but already did the network type = bridge and removal of "interface=eth0" modifications which all worked until I tried to change the network settings the clients could access) but decided to nuke the full install and start from scratch. As it stands now I'm able to install the docker, get into the GUI and add a new user although every time I attempt to stop/start the docker it appears the install reverts back to defaults. I mean my users details, as.conf settings and not sure what else all revert back to the defaults as if the file has been completely wiped. I've tried using the same app folder location and new app folder location but nothing appears to be retained. File permissions look correct (nobody/users) and the cache drive works for the other dockers just not this one. Any assistance is greatly appreciated. App run is as follows: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker create --name='OpenVPN' --net='bridge' --log-opt max-size='10m' --log-opt max-file='3' --privileged=true -e TZ="America/New_York" -e HOST_OS="Unraid" -e 'PGID'='100' -e 'PUID'='99' -p '943:943/tcp' -p '9443:9443/tcp' -p '1194:1194/udp' -v '/mnt/user/Dockers/openvpn':'/config':'rw' 'linuxserver/openvpn-as' 566e0951ece71323f6fa1a567f02a72ba1301036be09ca43ccd155914931f7b6 logs when the docker starts (up to EULA) are as follows: [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 10-adduser: executing... ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io We gratefully accept donations at: https://www.linuxserver.io/donate/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 20-time: executing... Current default time zone: 'America/New_York' Local time is now: Sat Apr 6 22:45:22 EDT 2019. Universal Time is now: Sun Apr 7 02:45:22 UTC 2019. [cont-init.d] 20-time: exited 0. [cont-init.d] 30-config: executing... existing data found, reinstalling openvpn-as backing up certs.db backing up cluster.db backing up config.db backing up config_local.db backing up log.db backing up notification.db backing up userprop.db backing up as.conf Selecting previously unselected package openvpn-as. (Reading database ... 11947 files and directories currently installed.) Preparing to unpack /openvpn/openvpn.deb ... Unpacking openvpn-as (2.7.3-05bc07c0-Ubuntu16) ... Setting up openvpn-as (2.7.3-05bc07c0-Ubuntu16) ... Automatic configuration failed, see /usr/local/openvpn_as/init.log You can configure manually using the /usr/local/openvpn_as/bin/ovpn-init tool. Automatic configuration failed, see /usr/local/openvpn_as/init.log You can configure manually using the /usr/local/openvpn_as/bin/ovpn-init tool. Beginning with OpenVPN AS 2.6.0 compression is disabled by default and on upgrades as security patch. restoring certs.db restoring cluster.db restoring config.db restoring config_local.db restoring log.db restoring certs.db restoring cluster.db restoring config.db restoring config_local.db restoring log.db restoring notification.db restoring userprop.db restoring as.conf [cont-init.d] 30-config: exited 0. [cont-init.d] 40-openvpn-init: executing... Detected an existing OpenVPN-AS configuration. Continuing will delete this configuration and restart from scratch. Please enter 'DELETE' to delete existing configuration: OpenVPN Access Server Initial Configuration Tool ------------------------------------------------------ OpenVPN Access Server End User License Agreement (OpenVPN-AS EULA)
  14. Sweet, just did the steps and looks like the cache drives are back to the pool. Just copying the files back. Here's the diagnostics for ref.
  15. Ok so ran the check disk filesystems using the scrub option given the btrfs and cache pool and it couldn't repair the error, specifically "error details: csum=1" Once that was completed I stopped array, unassigned the cache drives and restarted the array. Immediately got a message from the "fix common errors" about detecting hardware errors, so installed mcelog plugin via nerdpack then restarted complete tower. Didn't see the same error but pulled diagnostics and attached. Since then I've backup the contents of the cache drive and I'm open to completely destroying the pool and starting from scratch although I can't seem to find the location where I can reformat from the gui. I have the preclear plugin installed but didn't think that'd be the proper way to format the drives and start from scratch.