Jump to content

Squid

Community Developer
  • Posts

    28,770
  • Joined

  • Last visited

  • Days Won

    314

Everything posted by Squid

  1. It appears that you're using an el-cheapo (or counterfeit) flash drive. Definitely corrupted. If it happens to be new, then I'd toss it.
  2. Does it work if you set it instead to /mnt/cache/appdata/...
  3. The "go" file is executed very early. Unless you have it execute another script in the background that waits for the array to start (or via the user scripts plugin), there is next to no hope that the array is started when your command executes
  4. Since the stats for Boinc (the official docker container) / Folding@Home (container from mobiusnine) will come out for CA later this week, here is an update on the LinuxServer containers which are still too new to CA to have them generate any graphs As of May 4th (4:36am EST), there are 161,170 total downloads As of May 4th (4:38am EST), there are 588,162 total downloads
  5. Apr 24 20:45:31 Tower kernel: EDAC sbridge MC1: HANDLING MCE MEMORY ERROR Apr 24 20:45:31 Tower kernel: EDAC MC1: 1 CE memory scrubbing error on CPU_SrcID#0_Ha#0_Chan#2_DIMM#0 (channel:2 slot:0 page:0x44721c offset:0x0 grain:32 syndrome:0x0 - area:DRAM err_code:0008:00c2 socket:0 ha:0 channel_mask:4 rank:1) Memory error. Check your system event log for more info.
  6. by cache drive, do you mean a mapping to /mnt/cache/... or to a cache only share via /mnt/user/...?
  7. Post in the support thread for docker folders
  8. Save the .key file within /config on the flash Delete everything else.
  9. Dropbox works fine. It just doesn't like a reference to /mnt/user/.... If you change it to /mnt/diskX/... or /mnt/cache/... there's no problems.
  10. Screenshot to convey better what you're describing would be a boon
  11. You probably never took off the "n" flag from the command
  12. Certain combinations of CPUs / motherboards / your astrology sign (Scorpio's have it the worst) will issue an MCE during startup up when initializing the cores. Probably due to microcode updates and can be safely ignored.
  13. Your cache drive dropped offline. Power down, reseat the cabling then go from there. The cause. SATA cabling is a piss-poor design, and breathing on them the wrong way causes poor connections.
  14. run the https://wiki.unraid.net/Check_Disk_Filesystems against disk 3
  15. It calls the update script to check for and install updates at the time the backup runs
  16. Question mark top right of the browser window.
  17. You have the parity disk set to never spin down. So when something does write to the array, it will spin up automatically, but never spin down. Main, click on parity to adjust
  18. Edit the /downloads and change it to /data on the template and it should work. https://forums.unraid.net/topic/57181-docker-faq/?tab=comments#comment-566086
  19. Which boils down to the 320MB/s meaning the build never completed due to a restart. @anonymous3759 Run another check. It should return zero errors (assuming that the one that had the million odd errors was a correcting check. If it wasn't, then make sure to check off "correcting" when kicking it off)
  20. Reboot, remove the docker folder plugin, reboot again and see if the same symptoms continue. If they don't then post in the docker folder support thread.
×
×
  • Create New...