December 8, 201510 yr Hey guys, TL;DR: Always check your memory before starting a project I've been experiencing this annoyance where during long file transfers the machine is all but shutting down. Steps below to reproduce. Now my speeds aren't fantastic, about 11mbps writing. I haven't had a chance to test if this is happening when it's reading a large file as no file has completed uploading. What I mean by "All but shutting down": All mapped drives lose connection WebUI becomes unresponsive (will not load) As far as I have been able to figure out, I have to hard shut own my machine and turn it back on in order to get it to come back up. What I suspect: Honestly, I don't know much about this stuff. But I have a feeling it has to do with keeping a connection open that long instead of the actual amount of data being transferred. Reproduce: 1. Connect to NAS via mapped drive on windows. 2. Upload any file that will take a long time to upload. 3. Wait for "File transfer has been interrupted" prompt. Log during the crash can be found at http://pastebin.com/deaUGATQ I've attached a diagnostic log as the sticky has asked. I've put a lot of time into this already and I'd really like to figure out what the hell is going on. Please someone help erebus-diagnostics-20151208-1626.zip
December 9, 201510 yr You should post your complete diagnostics (Tools / Diagnostics). Quick guess is memory problem (based upon the segfaults when the kernel is trying to swap memory. I'm also assuming that you're running unMenu (since some of the segfaults are referencing awk). If you updated from v5, did you remove all the previous packages that you had installed via unMenu?
December 9, 201510 yr Author You should post your complete diagnostics (Tools / Diagnostics). Quick guess is memory problem (based upon the segfaults when the kernel is trying to swap memory. Sure, let me get a fresh one from right after the issue (Be back with that in about 5 minutes). In the mean time, all of my parts are brand new except for the SSD. Just to make sure by memory, you do mean RAM, correct? I'm also assuming that you're running unMenu (since some of the segfaults are referencing awk). If you updated from v5, did you remove all the previous packages that you had installed via unMenu? This install is a fresh install of 6.1.6 as of 10 hours ago. I did have the plugin linked before installed but this issue occurred before that. http://lime-technology.com/forum/index.php?topic=40262.0
Archived
This topic is now archived and is closed to further replies.