Everything posted by gerard6110
-
Dynamix - V6 Plugins
Dynamix WebGui On certain tabs the status bar at the bottom is not desiplayed correctly, where it is dropped out of view. This has been the case at least as of 6.1.9. This happens on the Tabs: Main and VMs. In itself not so important, except when stopping the array, it is impossible to follow what is going on, as part of the logging messages are invisible. Would be nice if this could be fixed.
-
Dynamix - V6 Plugins
System Buttons On my Elite TV Server its display behaviour is fine, however on my Stacker Media Server its behavious is odd, meaning that the buttons are located below the main menu bar, with a white background on certain Tab(-Subtabs). Both using Windows explorer and both with Tabbed Views. This happens on the Tab(-Subtab): Dashboard, Shares-User Shares, Settings, Plugins-Installed Plugins, Apps-Installed Apps, Stats-Disk Stats and Tools. It not a real problem; just annoying (to the nice layouts).
-
Dynamix - V6 Plugins
s3_sleep Thanks to Dynamix for (updating) the plugin - with the 2016.09.24 update at least the powerdown script is being executed, so shutdown works again. However, even before this update (but since moving to Unraid 6.2 stable) it was / is not detecting the HDD's spinning. Even immediately after spinning up all drives, it says the all monitored drives are spun down. The system checks all drives, except for the cache SSD's. As you know the minimum time before spinning down is 15 minutes. So after spinning up it should at least take 15 minutes for them to spin down. Log: Sep 25 12:13:34 Stacker s3_sleep: ---------------------------------------------- Sep 25 12:13:34 Stacker s3_sleep: killing s3_sleep process 18257 Sep 25 12:13:34 Stacker s3_sleep: ---------------------------------------------- Sep 25 12:13:34 Stacker s3_sleep: command-args=-C 2 -a -c -m 15 -e eth0 -N 0 -D 2 Sep 25 12:13:34 Stacker s3_sleep: action mode=shutdown Sep 25 12:13:34 Stacker s3_sleep: check disks status=yes Sep 25 12:13:34 Stacker s3_sleep: check network activity=no Sep 25 12:13:34 Stacker s3_sleep: check active devices=no Sep 25 12:13:34 Stacker s3_sleep: check local login=no Sep 25 12:13:34 Stacker s3_sleep: check remote login=no Sep 25 12:13:34 Stacker s3_sleep: version=3.0.4 Sep 25 12:13:34 Stacker s3_sleep: ---------------------------------------------- Sep 25 12:13:34 Stacker s3_sleep: included disks=sdb sde sdf sdg sdh sdi sdj sdk sdl sdm Sep 25 12:13:34 Stacker s3_sleep: excluded disks=sda sdc sdd Sep 25 12:13:34 Stacker s3_sleep: ---------------------------------------------- Sep 25 12:13:34 Stacker s3_sleep: s3_sleep process ID 18509 started, To terminate it, type: s3_sleep -q Sep 25 12:13:34 Stacker s3_sleep: All monitored HDDs are spun down Sep 25 12:13:34 Stacker s3_sleep: Extra delay period running: 15 minute(s) Sep 25 12:13:46 Stacker emhttp: Spinning up all drives... Sep 25 12:13:46 Stacker emhttp: shcmd (370): /usr/sbin/hdparm -S0 /dev/sdc &> /dev/null Sep 25 12:13:46 Stacker kernel: mdcmd (56): spinup 0 Sep 25 12:13:46 Stacker kernel: mdcmd (57): spinup 1 Sep 25 12:13:46 Stacker kernel: mdcmd (58): spinup 2 Sep 25 12:13:46 Stacker kernel: mdcmd (59): spinup 3 Sep 25 12:13:46 Stacker kernel: mdcmd (60): spinup 4 Sep 25 12:13:46 Stacker kernel: mdcmd (61): spinup 5 Sep 25 12:13:46 Stacker kernel: mdcmd (62): spinup 6 Sep 25 12:13:46 Stacker kernel: mdcmd (63): spinup 7 Sep 25 12:13:46 Stacker kernel: mdcmd (64): spinup 8 Sep 25 12:13:46 Stacker kernel: mdcmd (65): spinup 9 Sep 25 12:13:46 Stacker emhttp: shcmd (371): /usr/sbin/hdparm -S0 /dev/sdd &> /dev/null Sep 25 12:14:34 Stacker s3_sleep: All monitored HDDs are spun down Sep 25 12:14:34 Stacker s3_sleep: Extra delay period running: 14 minute(s) Sep 25 12:15:35 Stacker s3_sleep: All monitored HDDs are spun down Sep 25 12:15:35 Stacker s3_sleep: Extra delay period running: 13 minute(s) Sep 25 12:16:35 Stacker s3_sleep: All monitored HDDs are spun down Sep 25 12:16:35 Stacker s3_sleep: Extra delay period running: 12 minute(s) Sep 25 12:17:35 Stacker s3_sleep: All monitored HDDs are spun down Sep 25 12:17:35 Stacker s3_sleep: Extra delay period running: 11 minute(s) Sep 25 12:18:35 Stacker s3_sleep: All monitored HDDs are spun down Sep 25 12:18:35 Stacker s3_sleep: Extra delay period running: 10 minute(s) Would you please have a look. Thanks.
-
Dynamix - V6 Plugins
s3_sleep Since the upgrade to 6.2 stable (few days ago) my media server is not shutting down anymore automatically. Manually shutting down and WOL'ing is fine. The log says, something like: ... All drives spundown. Shutting down system. System woken up. Resetting timers ... Repeat ... It seems to me the shutdown or powerdown script is not found / executed. Please help, as the server is normally off, except when consuming content from it: movies, series, music.
-
Bergware's Dynamix S3 Sleep
Hi in my case after upgrading to 6.2 it is not shutting down anymore. It seems the powerdown scripts is not found by s3_sleep.
-
Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array
I'm not seeing this issue. Try clearing the browser cache and possibly a different browser to see if it continues. Indeed not seeing this issue with Google Chrome, but I prefer to keep on using IE 11+ for everything (old habits). BTW all tabs under Main have this issue; both in windowed mode as in full screen mode.
-
Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array
Hi, Maybe it's just my setup, but after installing this plugin, the main / array operation tab is somewhat corrupted at the bottom. The bottom line is a little bit of the page and when stopping / restarting the array, the progress tekst is not displayed fully. I know it's just esthetics, but just a little bit annoying and probably a very simple things to fix. Thanks.
-
VirtualBox Plugin for unRAID v5 and v6
I'm using the Apache webserver by dmacias72. As a direct plugin; not using a dockerized webserver.
-
VirtualBox Plugin for unRAID v5 and v6
Hi, Not sure where this message will end up ... Last couple of days / week tried several times to login with phpvirtualbox. To no avail, obviously. So what is wrong? Everything required is running (virtualbox, vboxwebsrv) and I get to he login page, but not even the default admin / admin works. Recovery.php (to reset the default admin / admin) does not work either. Setting var $noAuth = true; lets me in (without username / password, as expected). But I would prefer to really login. Any thoughts? Permissions issue?