Jump to content

jbrodriguez

Community Developer
  • Posts

    2,089
  • Joined

  • Last visited

  • Days Won

    4

Everything posted by jbrodriguez

  1. That's right, I need to look into that.
  2. Hmm, so it doesn't delete the source. I'll check that part of the code.
  3. I'm changing working directory, but I'll double check.
  4. Could you send me the log ? And tell me which folders you had to manually delete ?
  5. Thanks. The log looks clean. I've added some logging to the app showing whether dry-run is on/off when starting an operation. I can't think of a reason why it ran so fast. How much ram do you have ? Can you update the app to 3.3.1 and try again with full verbosity (change it in the settings page) and dry-run ?
  6. v3.3.1 is available ! 2017-08-18 - 3.3.1 - Add dry-run logging - Add bitcoin address to the support fund
  7. Thank you for the kind comments ! Yes, I will add a bitcoin option
  8. Logs are located at /boot/logs/unbalance.log
  9. Hi wreave, you didn't send the whole log, but what I can see it's only transferring 4.68gb, it does seem like it's running a dry-run. Can you send the first part of the log, with the calculate section ?
  10. v3.3.0 is now available ! 2017-08-14 - 3.3.0 GATHER operation is now implemented !! Consolidate folders from your user shares into a single drive, always checking that enough space is available for the operation. Also, as soon as any transfer operation gets underway, a notification is sent showing which rsync commands will be executed (this happens after you click Move, Copy or Proceed). Additionally, the following changes were made: - Verbosity setting controls permission issue logging - Fix issue with console panel not allowing mouse scroll - Drive sizes in logs are shown in 'base 1000' - Update internal components The underlying transfer is the exact same as the one used for SCATTER. Let me know how it works for you. The next planned changes are: - Implement an operation history - Run docker safe new permissions (at the source folder level) (needs discussion with Squid
  11. Ok, well looks like the plugin is doing what it's supposed to Not sure how to proceed though, knowing your disk is in 'bad' shape as you mention. rsync will probably generate some error and interrupt any operation you run. Since you have enough space in at least one disk, why don't you run rsync from a (tmux/screen) command line, so you can monitor progress more closely.
  12. Can you run a quick $ tail -f /boot/logs/unbalance.log Just to check what it's doing. If you already stopped the process, then just check the end of the log.
  13. v2.10.2 is available as an over-the-air release ! - Fix crash with power on command
  14. Ok, in any case, I'll check why the operations section doesn't 'wrap' (the way ERRORS did).
  15. No, that section has never been scrollable. But also note that ERRORS text is split in two 'rows'. Is it possible that you increased the text size in the display & brightness settings of your iphone ? If that's the case, you can decrease the text size in the app (to small) so that it 'fits' the screen. Or reset the iphone's text size (restart the app if you do that) and set the app's text size to normal.
  16. v2.10.1 is available as an over-the-air release ! - Fix issue with cpu load display This should correctly display the avg cpu load of the server I'm still looking into the indicator appearing/disappearing.
  17. That E5-2670 has like virtual cores ?? I guess it's showing data until cpu16 ? I haven't tested rc7a, but it looks like the cpu load format changed. I'll check some more.
  18. 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.
  19. 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.
  20. 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.
  21. 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.
  22. 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
×
×
  • Create New...