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

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 

Maybe try to turn it off yourself instead of the sleep plugin and see if the same thing happens?

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 

For the purposes of testing a free Trial licence will suffice. Then, if you need to, you can transfer the licence as @zin105 points out. Since you're getting corruption of your USB device that you're having to fix with a Windows PC and since you've been using the same USB port "forever" and also possibly the same USB flash in it it might well be beginning to fail.