• Content Count

  • Joined

  • Last visited

Community Reputation

8 Neutral

About SnickySnacks

  • Rank


  • Gender

Recent Profile Visitors

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

  1. You aren't trying to access the smb share with the root user are you?
  2. Also, this is exactly what the log is telling you. A "CE memory read error" or "CE memory scrubbing error" is a "Correctable Error (CE)". It would be worse if you were getting "Uncorrectable Errors (UE)" My concern is that you've merely turned off the memory scrubbing and whatnot, hiding the errors rather than fixing them.
  3. Just to be clear, are you now running with ECC off? That seems like a bad idea. Doesn't that mean that instead of seeing the errors, it's just going to be failing silently and potentially corrupting the memory? (especially if you weren't seeing the errors in memtest in the first place)
  4. Is your server exposed to the internet? A few of those process names look suspiciously like malware. /tmp/kdevtmpfsi /var/tmp/kinsing
  5. It will be something like: 1) copy everything off the existing licensed USB onto a PC 2) delete everything off the licensed USB 3) copy everything from the trial USB to the licensed USB 4) Delete the trial key from the licensed USB 5) copy the licensed Unraid key file from the PC backup onto the licensed USB If you do it this way you should still have your trial USB and a backup copy of your licensed USB in case anything goes wrong.
  6. Why not just copy your new server config to your current USB? No transfer needed, then.
  7. It's my preference to stop them on Unraid since I don't have to manage individual computers (or guests!). If you notice any new files that need to be added to the veto list, please let the community know. At this point my shares are all read-only as a ransomware preventative measure except for 1 share that I stage files to, so nothing can really make files in the array anymore anyways.
  8. If you want Unraid itself to prevent these files from being created: 1. Stop array 2. Go to SMB Settings and add this to SMB Extra Configuration veto files = /._*/.DS_Store/.AppleDouble/.Trashes/.TemporaryItems/.Spotlight-V100/ delete veto files = yes
  9. Are the files that are having an issue all on the same disk? If so, which one? I'm also a bit curious if you've tried comparing with a hex editor or something to see what is being changed.
  10. Nobody is going to point out that he's running two emulated parity drives? That's got to slow you down a bit, I'd imagine, since writes are going to spin up and read the whole array. Am I wrong?
  11. Oh. So that NVME error wasn't so harmless. At least you got it figured out.
  12. Eh? Not that normal. I rarely if ever hit the spin down button and my disks always spin down normally after a reboot (once folder caching is done doing its thing). Flam3h: How sure are you that the drives aren't spinning down eventually? Fix Common Problems is running 10 minutes after your system comes up and you can see in the log that the system issues a spin down ~15 minutes after that, which generates a (likely harmless) error on an NVME drive: Oct 14 01:26:33 Tower emhttpd: shcmd (138): /usr/sbin/hdparm -y /dev/nvme0n1 Oct 14 01:26:33 Tower root: HDIO_DRI
  13. When you say "wire shelf" do you literally mean they are sitting exposed on a wire shelf and not in any sort of PC case?
  14. I don't know much about cache disks. Obvious suggestion is to fix the error on the disk and then enable plugins/dockers/VMs one at a time until you can determine which one is causing the problem, I suppose.
  15. At the time those diagnostics were created, were any CPUs showing 100% load? If so, which ones? Also, have you tried booting in safe mode and seeing if this occurs with no plugins/dockers/vms loaded? There does seem to be some corruption on one of your disks: Oct 7 23:56:33 Homebase kernel: BTRFS critical (device sdj1): corrupt leaf: root=5 block=1953586397184 slot=84, bad key order, prev (288230376157862467 96 4) current (6150723 96 5) ### [PREVIOUS LINE REPEATED 4 TIMES] ### Should probably run a check on that one, as it looks like it eventually causes a kernel fault: