Jump to content

jjslegacy

Members
  • Content Count

    96
  • Joined

  • Last visited

Community Reputation

1 Neutral

About jjslegacy

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

  1. you got me - I didn't even notice the nice - multitask failing - thanks!
  2. 4 cores 8 threads - Intel® Xeon® CPU E3-1280 V2 @ 3.60GHz
  3. 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.
  4. 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.
  5. 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
  6. 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
  7. 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
  8. 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
  9. 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
  10. I use the dynamix sleep plugin to do it automatically.
  11. 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
  12. 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