jjslegacy

Members
  • Posts

    103
  • Joined

  • Last visited

Everything posted by jjslegacy

  1. Thanks! Looks all fixed now.
  2. I am having some troubles upgrading to the latest beta rclone. Anyone else? ##### Note that closing this window will abort the execution of this script ##### Updating rclone Archive: /boot/config/plugins/rclone/install/rclone.zip inflating: /boot/config/plugins/rclone/install/rclone ------------------------------------------------------------------- Update failed - Please try again -------------------------------------------------------------------
  3. He’s trying to use this one I assume and should ask for support there: https://github.com/riftbit/docker-serviio
  4. Why don’t you open an issue on the docker GitHub? You want get much help here I imagine.
  5. 100% on this - no real reason this should even exist (so thankful it does) but I am very surprised Limetech isn't looking to pick this up natively. There is a great use case for Unraid to me
  6. need to do more analysis but seems like I am having drive spindown issues with rc5 (as in not spinning down after XX minutes ) - anyone else? Will look into it more but something doesn't seem quite right
  7. you got me - I didn't even notice the nice - multitask failing - thanks!
  8. 4 cores 8 threads - Intel® Xeon® CPU E3-1280 V2 @ 3.60GHz
  9. had some other stuff running so it's not perfect but you can see mprime using 400% CPU and top reporting it wrong in the totals.
  10. I am noticing that the dashboard is correct and top is wrong. Example. I am running mprime which is maxing out my machine and the dashboard is correct. Top shows CPU usage at <3% busy.
  11. I have confirmed my two parity disks and one of my other disks will not spin down unless done manually. It says it does it from the log but the disks are always spinning which won't let the machine shutoff during the schedule. I just see this over and over May 2 17:31:59 MJMS kernel: mdcmd (61): spindown 0 May 2 17:32:00 MJMS kernel: mdcmd (62): spindown 8 May 2 17:32:00 MJMS kernel: mdcmd (63): spindown 29 This was working fine on all versions before 6.5.1 mjms-diagnostics-20180502-1733.zip
  12. On 6.5.1 my drives don’t appear to be spinning g down like they did before so now server won’t shutdown automatically as it should. Seems there is is always a few drives stuck spinning. Will have to dig in more later
  13. I am getting some php errors on the main page: Warning: Use of undefined constant byte11h - assumed 'byte11h' (this will throw an Error in a future version of PHP) in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 208 Warning: Use of undefined constant byte10h - assumed 'byte10h' (this will throw an Error in a future version of PHP) in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 208 ................................... Seems nobody else is seeing them? If I wrap the byte11h, byte10h in single quotes they go away but seems odd only I am seeing this. mjms-diagnostics-20180315-1308.zip
  14. Looking at this: Dec 29 08:35:07 MJMS kernel: usb 1-1.4: device descriptor read/64, error -110 It appears to be a power issue - wondering if something is done differently in the later kernel that is causing some dip in power. I am using the on-board internal USB port which I have been using forever. Will dig more into it later I guess
  15. I could try that if Limetech wants to grant my licenses to a new USB stick but seems rather odd to me that it works perfectly fine in all other versions besides 6.4
  16. I use the dynamix sleep plugin to do it automatically.
  17. I posted in the 18f thread but should probably make a new thread so here it is... I have an interesting problem I am not quite sure how to debug. I have tried a few versions of 6.4 and all ended the same way. At first I thought maybe it was my USB but it only does this with 6.4. My server gets turned off fully nightly as some days it doesn't get used so no need to run it all the time and the hardware doesn't have a sleep option. More often than not when I boot with 6.4 my USB drive drops off during plugin install and I have to take it out and fix the errors on a windows box. It doesn't do it every time but almost always. I go back to 6.3 and never see this issue. I can't run diagnostics since it tries to write to /boot but I suppose I could look into the code and modify it but not sure what else it tries to pull. I have manually pulled some logs and will add the syslog. Any ideas on how else to debug this? syslog
  18. I have an interesting problem I am not quite sure how to debug. I have tried a few versions of 6.4 and all ended the same way. At first I thought maybe it was my USB but it only does this with 6.4. My server gets turned off fully nightly as some days it doesn't get used so no need to run it all the time and the hardware doesn't have a sleep option. More often than not when I boot with 6.4 my USB drive drops off during plugin install and I have to take it out and fix the errors on a windows box. It doesn't do it every time but almost always. I go back to 6.3 and never see this issue. I can't run diagnostics since it tries to write to /boot but I suppose I could look into the code and modify it but not sure what else it tries to pull. I have manually pulled some logs and will add the syslog. Any ideas on how else to debug this? *edit - started a new thread for this also* syslog
  19. twice with this latest build my machine hasn't been able to boot and ends up in a UEFI shell. The USB drive has needed repaired on my windows box both times. Not really sure where to begin - usb drive going bad? bad luck?
  20. Safe mode did indeed let me add the disk - thanks! although now I can't format it. Will gather some log info Had to reboot into normal mode to get it to format - odd
  21. Actually tried again and now I see that token error Aug 11 13:15:15 MJMS emhttpd: error: changeDevice: missing csrf_token Aug 11 13:15:18 MJMS emhttpd: req (40): slotId.9=Hitachi_HUS724030ALE641_P8HP8WVP&csrf_token=EDDA1A93016334A3 Aug 11 13:15:19 MJMS emhttpd: req (41): slotId.9=Hitachi_HUS724030ALE641_P8HP8WVP&csrf_token=EDDA1A93016334A3 Aug 11 13:15:21 MJMS emhttpd: req (42): slotId.9=Hitachi_HUS724030ALE641_P8HP8WVP&csrf_token=EDDA1A93016334A3 Aug 11 13:15:22 MJMS emhttpd: req (43): slotId.9=Hitachi_HUS724030ALE641_P8HP8WVP&csrf_token=EDDA1A93016334A3 Aug 11 13:15:24 MJMS emhttpd: req (44): slotId.9=Hitachi_HUS724030ALE641_P8HP8WVP&csrf_token=EDDA1A93016334A3 Aug 11 13:15:25 MJMS emhttpd: req (45): slotId.9=Hitachi_HUS724030ALE641_P8HP8WVP&csrf_token=EDDA1A93016334A3 Aug 11 13:15:26 MJMS emhttpd: req (46): slotId.9=Hitachi_HUS724030ALE641_P8HP8WVP&csrf_token=EDDA1A93016334A3 Aug 11 13:15:27 MJMS emhttpd: req (47): slotId.9=Hitachi_HUS724030ALE641_P8HP8WVP&csrf_token=EDDA1A93016334A3 Aug 11 13:15:29 MJMS emhttpd: req (48): slotId.9=Hitachi_HUS724030ALE641_P8HP8WVP&csrf_token=EDDA1A93016334A3 Aug 11 13:17:53 MJMS emhttpd: req (49): changeDevice=Apply&slotId.9=Hitachi_HUS724030ALE641_P8HP8WVP Aug 11 13:17:53 MJMS emhttpd: error: changeDevice: missing csrf_token Aug 11 13:17:55 MJMS emhttpd: req (50): slotId.9=Hitachi_HUS724030ALE641_P8HP8WVP&csrf_token=EDDA1A93016334A3 Aug 11 13:17:57 MJMS emhttpd: req (51): slotId.9=Hitachi_HUS724030ALE641_P8J77NJP&csrf_token=EDDA1A93016334A3 Aug 11 13:17:58 MJMS emhttpd: req (52): slotId.10=Hitachi_HUS724030ALE641_P8HP8WVP&csrf_token=EDDA1A93016334A3 Aug 11 13:17:59 MJMS emhttpd: req (53): slotId.11=Hitachi_HUS724030ALE641_P8HP8WVP&csrf_token=EDDA1A93016334A3 Aug 11 13:18:02 MJMS emhttpd: req (54): slotId.13=Hitachi_HUS724030ALE641_P8HP8WVP&csrf_token=EDDA1A93016334A3 Aug 11 13:18:04 MJMS emhttpd: req (55): slotId.16=Hitachi_HUS724030ALE641_P8HP8WVP&csrf_token=EDDA1A93016334A3 Aug 11 13:18:07 MJMS emhttpd: req (56): slotId.22=Hitachi_HUS724030ALE641_P8J77NJP&csrf_token=EDDA1A93016334A3