jbrodriguez

Ok, I found the issue. It's actually a minor bug, it can be fixed via an OTA release. The app 'should' be showing only the average cpu load, not each of the cores. Eventually, I could make it show all the cores, if requested.

That looks awful !!!! My 6.4-rc6 server has an i3-4130T (dual-core), while your AMD A8-7600 is a quad-core. But the cpu load data comes up completely different. Let me pm you to ask you for that cpu load data.

v2.10.0 is now available on Play Store and App Store ! - Server indicators are presented via a scrolling marquee !!! (If the content exceeds the width of the screen, otherwise it will be static) - Board & cpu temperature, system load and fan rpms indicators are available. (Dynamix System Plugin required for version prior to 6.4.x) - Temperature unit is obtained from unRAID settings. (ControlR plugin v2.2.0+ must be installed for this to work) - Timeouts are now applied when pinging the server. Settings are reset to 1000ms (1s) for both automatic and manual timeouts. Adjust accordingly as needed. Additional changes: - Fix display on iPads - Fix UI issues on Android (excessive space, wrong circular progress) - Use native Switch component (Ops tab) - Fix issue with Back hardware button (Android) This is a very important release, because showing server indicators had me blocked for a long time. Now that I was finally able to get it working, new features should come in faster. The next release will most likely refactor the data (servers) storage structure, which will probably require an app reinstall, but I'll try to convert data to new structure first.

No, they're not enabled by default. In any case, this gives me the idea to implement a history (similar to the parity history) in an upcoming release.

Mmm, that's definitely not good Not sure if your notifications were enabled, but you'd have been able to read that the transfer was interrupted

Ok, I checked the logs There were two separate errors transferring files The first one I: 2017/08/06 07:27:43 core.go:740: Running Move operation ... I: 2017/08/06 07:27:43 core.go:857: Command Started: rsync -avPRX "Media/movies" "/mnt/disk5/" W: 2017/08/06 12:39:00 server.go:259: closing socket (&{id: ws:0xc4200e4240 onMessage:0x6cf050 onClose:0x6cf0a0}): EOF I: 2017/08/06 16:15:34 core.go:939: Command Finished I: 2017/08/06 16:15:34 core.go:945: Current progress: 64.79% done ~ 4h46m52s left (39.78 MB/s) I: 2017/08/06 16:15:34 core.go:957: Removing: rm -rf "/mnt/disk2/Media/movies" W: 2017/08/06 16:15:34 shell.go:53: transferProgress:: rm: cannot remove '/mnt/disk2/Media/movies/Cake (2014)/Cake (2014) 720p.mkv': Permission denied W: 2017/08/06 16:15:35 shell.go:101: transferProgress:: waitError: signal: broken pipe W: 2017/08/06 16:15:35 core.go:968: Unable to remove source folder (/mnt/disk2/Media/movies): signal: broken pipe It fully copied "Media/movies" to disk5, but failed to delete the source folder (/mnt/disk2/Media/movies), due to a permission issue. In this case, the "Media/movies" data is in disk 5. Run $ ls -al /mnt/disk5/Media/movies to list the files. After you've double checked that, you can delete the files from disk2 (rm -rf "/mnt/disk2/Media/movies"), so you can further debug the permission issue. The second error I: 2017/08/06 16:15:35 core.go:857: Command Started: rsync -avPRX "Media/shows" "/mnt/disk5/" I: 2017/08/06 17:00:16 core.go:143: Sending config W: 2017/08/06 19:57:57 server.go:259: closing socket (&{id: ws:0xc4201841b0 onMessage:0x6cf050 onClose:0x6cf0a0}): EOF I: 2017/08/06 19:57:58 core.go:143: Sending config W: 2017/08/06 20:16:13 server.go:259: closing socket (&{id: ws:0xc4201842d0 onMessage:0x6cf050 onClose:0x6cf0a0}): EOF I: 2017/08/06 20:16:14 core.go:143: Sending config W: 2017/08/06 20:22:59 core.go:929: Command Interrupted: rsync -avPRX "Media/shows" "/mnt/disk5/" (exit status 23 : Partial transfer due to error) I: 2017/08/06 20:22:59 core.go:1039: unBALANCE - MOVE operation INTERRUPTED Started: Aug 6, 2017 07:27:43 Ended: Aug 6, 2017 20:22:59 Elapsed: 12h55m16.176s Command Interrupted: rsync -avPRX "Media/shows" "/mnt/disk5/" (exit status 23 : Partial transfer due to error) happened while transferring "Media/shows", so in this case the data still exists whole in disk2. Run $ ls -al /mnt/disk2/Media/shows After you've checked that, you can delete the incomplete transfer on disk5 As for the other share (Backup), the app didn't get to transfer it (because of the previous error), so the files are still present in disk2. Check that by running $ ls -al /mnt/disk2/Backup Not sure what you mention about crashplan, but the data in the raw disk should be there as per above. Also is it possible that you were receiving crashplan data at the same time as the app was running ? The app calculated these sizes for the folders you've shown in the screenshot, while the screenshot shows biggers folder sizes ? [64.9G] /mnt/disk2/Backup/./Pictures [40.4G] /mnt/disk2/Backup/./Documents [263.2M] /mnt/disk2/Backup/./Videos

It should be ready sometime next week, if there are no issues in the mean time

What about taking a look at the disk itself ? $ ls -al /mnt/disk2/share I understand disk2 is where data is supposed to be now. You could also check the log (/boot/logs/unbalance.log) or send it over (pm if you want).

Honestly ... that's too damn bad !!!

You're in for a treat with Game Of Thrones. If you can avoid spoilers (as I believe you have), wait until it's over to binge it.

329TB (assembled) !! Man !!

v2.2.0 has been published ! 2017-08-02 - 2.2.0 - Enable ControlR app to get temperature unit from server's GUI preferences This will become available in an upcoming ControlR app release

Thanks ! I've found the issue with the app not using the full screen on iPads. The fix will be included in the next release.

Since it's coming along pretty well, I figured I might as well post a teaser screenshot for the GATHER op There's still some work to be done, but it's not that far away now !

Ok, use port 80 in the app. It should work (unless you've set a custom emhttp port in the /boot/config/go file). The app uses the same port as the unRAID webGUI's, it doesn't use the plugin's port defined in the plugin's settings.

Hi, a couple of things to check - Make sure you're connecting to the unRAID webGUI's port (most likely 80) - Make sure you can access the webGUI from a browser on your device - Make sure you don't have an adblocker/firewall rule/etc preventing access to the webGUI from your device If none of the above applies, let me know to further troubleshoot.

v2.8.2 is available as an over-the-air (OTA) release ! 2.8.2 - Restore log functionality This fixes a minor bug that was preventing logs to be shown.

MacDaddy/wgstarks, thanks for bringing this up ! It's a minor bug in the app itself. I'll publish either an ota or full store release later

Thanks johnnie.black, followed these steps and parity rebuild has already finished. All is good now

I have 4544 errors on the parity drive. Diagnostics are attached, where I can see a LOT of read errors on the parity drive. Time to replace it right ? I can't find the procedure to replace a parity drive on the wiki, is it similar to the one for a new data drive ? Stop the array Unassign the parity drive if still assigned (to unassign, set it to No Device) Power down [ Optional ] Pull the parity drive (you may want to leave it installed for Preclearing or testing) Install the new drive Power on Assign the new drive in the slot of the parity drive Go to the Main -> Array Operation section Put a check in the Yes, I'm sure checkbox (next to the information indicating the drive will be rebuilt), and click the Start button (or similar) The rebuild will begin, with hefty disk activity on all drives, lots of writes on the new drive and lots of reads on all other drives wopr-diagnostics-20170720-0446.zip

v2.8.1 is now available ! 2.8.1 Initial support for 6.4.x's https. It's still subject to pending changes in unRAID. Additionally: - Updated screen navigation component - General improvements and other bug fixes This should enable you to connect to an unRAID server via https, provided the server is configured to do so. Also install the latest ControlR plugin for full compatibility. Let me know of any issues.

I can tell you what GATHER will do with an example. Let's say you have Breaking Bad's season 1/2 on disk2, season 3/4 on disk3, season 5 on disk4. GATHER will help you consolidate all 5 seasons in a single disk. It will let you choose to consolidate on disk2, disk3 or disk4 (provided there's enough available space) or any other disk that has enough space. What it won't do is fill an empty disk to "rebalance" the space among all available disks. Hope it makes it a bit clearer.

P.S.: Turbo Write really helps with write speeds, at the expense of having all of your disks spun up.

Ok, you're not running the latest unBALANCE version (which is 3.2.0, it would have logged which transfer operation you ran: move/copy). Yeah, rsync's error 23 (Partial transfer due to error) is almost like a catch-all But it's generally associated with permission errors or date-time issues with some of your files/folders. Did you get any permission issues during the calculate phase ?

Thanks for the comments ! It should run at approx the same speed as copying data to a parity protected drive. Can you check what the log says (/boot/logs/unbalance.log) ? Send a pm if you prefer.