SnickySnacks

Members
  • Posts

    105
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

SnickySnacks's Achievements

Apprentice

Apprentice (3/14)

9

Reputation

  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_DRIVE_CMD(standby) failed: Inappropriate ioctl for device Oct 14 01:26:33 Tower root: Oct 14 01:26:33 Tower root: /dev/nvme0n1: Oct 14 01:26:33 Tower root: issuing standby command Oct 14 01:26:33 Tower emhttpd: shcmd (138): exit status: 25 Other than that, everything seems normal in the log.
  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: Oct 8 02:02:49 Homebase kernel: BUG: unable to handle kernel NULL pointer dereference at 0000000000000080 Oct 8 02:02:49 Homebase kernel: PGD 4ad0b1067 P4D 4ad0b1067 PUD 4ad0b0067 PMD 0 Oct 8 02:02:49 Homebase kernel: Oops: 0000 [#1] SMP NOPTI Oct 8 02:02:49 Homebase kernel: CPU: 15 PID: 1848 Comm: fstrim Tainted: P O 4.19.56-Unraid #1 Oct 8 02:02:49 Homebase kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X570 Taichi, BIOS P2.10 09/09/2019 Oct 8 02:02:49 Homebase kernel: RIP: 0010:btrfs_trim_fs+0x166/0x369 Oct 8 02:02:49 Homebase kernel: Code: 00 00 48 c7 44 24 38 00 00 00 00 49 8b 45 10 48 c7 44 24 40 00 00 00 00 48 c7 44 24 30 00 00 00 00 48 89 44 24 20 48 8b 43 68 <48> 8b 80 80 00 00 00 48 8b 80 f8 03 00 00 48 8b 80 a8 01 00 00 0f Oct 8 02:02:49 Homebase kernel: RSP: 0018:ffffc9001294fc90 EFLAGS: 00010297 Oct 8 02:02:49 Homebase kernel: RAX: 0000000000000000 RBX: ffff888f5db68200 RCX: ffff888fbf604878 Oct 8 02:02:49 Homebase kernel: RDX: ffff888cac98de80 RSI: ffff888f5d718c00 RDI: ffff888fbf604858 Oct 8 02:02:49 Homebase kernel: RBP: 0000000000000000 R08: ffff888f5911fa70 R09: ffff888f5911fa68 Oct 8 02:02:49 Homebase kernel: R10: ffffea0022918ec0 R11: ffff888ffe9e0b80 R12: ffff888fbfafe000 Oct 8 02:02:49 Homebase kernel: R13: ffffc9001294fd20 R14: 0000000000000000 R15: 0000000000000000 Oct 8 02:02:49 Homebase kernel: FS: 000014b7fa3ac780(0000) GS:ffff888ffe9c0000(0000) knlGS:0000000000000000 Oct 8 02:02:49 Homebase kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Oct 8 02:02:49 Homebase kernel: CR2: 0000000000000080 CR3: 00000001a6aa2000 CR4: 0000000000340ee0 Oct 8 02:02:49 Homebase kernel: Call Trace: Oct 8 02:02:49 Homebase kernel: ? dput.part.6+0x24/0xf6 Oct 8 02:02:49 Homebase kernel: btrfs_ioctl_fitrim.isra.7+0xfe/0x135 Oct 8 02:02:49 Homebase kernel: btrfs_ioctl+0x4f6/0x28ad Oct 8 02:02:49 Homebase kernel: ? queue_var_show+0x12/0x15 Oct 8 02:02:49 Homebase kernel: ? _copy_to_user+0x22/0x28 Oct 8 02:02:49 Homebase kernel: ? cp_new_stat+0x14b/0x17a Oct 8 02:02:49 Homebase kernel: ? vfs_ioctl+0x19/0x26 Oct 8 02:02:49 Homebase kernel: vfs_ioctl+0x19/0x26 Oct 8 02:02:49 Homebase kernel: do_vfs_ioctl+0x526/0x54e Oct 8 02:02:49 Homebase kernel: ? __se_sys_newfstat+0x3c/0x5f Oct 8 02:02:49 Homebase kernel: ksys_ioctl+0x39/0x58 Oct 8 02:02:49 Homebase kernel: __x64_sys_ioctl+0x11/0x14 Oct 8 02:02:49 Homebase kernel: do_syscall_64+0x57/0xf2 Oct 8 02:02:49 Homebase kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Oct 8 02:02:49 Homebase kernel: RIP: 0033:0x14b7fa4de397 Oct 8 02:02:49 Homebase kernel: Code: 00 00 90 48 8b 05 f9 2a 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c9 2a 0d 00 f7 d8 64 89 01 48 Oct 8 02:02:49 Homebase kernel: RSP: 002b:00007ffc52c9f358 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 Oct 8 02:02:49 Homebase kernel: RAX: ffffffffffffffda RBX: 00007ffc52c9f4b0 RCX: 000014b7fa4de397 Oct 8 02:02:49 Homebase kernel: RDX: 00007ffc52c9f360 RSI: 00000000c0185879 RDI: 0000000000000003 Oct 8 02:02:49 Homebase kernel: RBP: 0000000000000003 R08: 0000000000000000 R09: 0000000000415fd0 Oct 8 02:02:49 Homebase kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000415740 Oct 8 02:02:49 Homebase kernel: R13: 00000000004156c0 R14: 0000000000415740 R15: 000014b7fa3ac6b0 Oct 8 02:02:49 Homebase kernel: Modules linked in: veth xt_CHECKSUM ipt_REJECT ip6table_mangle ip6table_nat nf_nat_ipv6 iptable_mangle ip6table_filter ip6_tables vhost_net tun vhost tap macvlan xt_nat ipt_MASQUERADE iptable_nat nf_nat_ipv4 iptable_filter ip_tables nf_nat xfs dm_crypt algif_skcipher af_alg dm_mod dax md_mod bonding edac_mce_amd kvm_amd nvidia_drm(PO) nvidia_modeset(PO) nvidia(PO) drm_kms_helper btusb btrtl btbcm drm kvm btintel igb bluetooth agpgart syscopyarea sysfillrect crct10dif_pclmul sysimgblt fb_sys_fops crc32_pclmul crc32c_intel ghash_clmulni_intel i2c_piix4 i2c_algo_bit pcbc i2c_core aesni_intel aes_x86_64 crypto_simd wmi_bmof mxm_wmi ahci ecdh_generic cryptd ccp libahci glue_helper wmi button pcc_cpufreq acpi_cpufreq Oct 8 02:02:49 Homebase kernel: CR2: 0000000000000080 Oct 8 02:02:49 Homebase kernel: ---[ end trace 9bdd9e618dc0d9c2 ]--- Oct 8 02:02:49 Homebase kernel: RIP: 0010:btrfs_trim_fs+0x166/0x369 Oct 8 02:02:49 Homebase kernel: Code: 00 00 48 c7 44 24 38 00 00 00 00 49 8b 45 10 48 c7 44 24 40 00 00 00 00 48 c7 44 24 30 00 00 00 00 48 89 44 24 20 48 8b 43 68 <48> 8b 80 80 00 00 00 48 8b 80 f8 03 00 00 48 8b 80 a8 01 00 00 0f Oct 8 02:02:49 Homebase kernel: RSP: 0018:ffffc9001294fc90 EFLAGS: 00010297 Oct 8 02:02:49 Homebase kernel: RAX: 0000000000000000 RBX: ffff888f5db68200 RCX: ffff888fbf604878 Oct 8 02:02:49 Homebase kernel: RDX: ffff888cac98de80 RSI: ffff888f5d718c00 RDI: ffff888fbf604858 Oct 8 02:02:49 Homebase kernel: RBP: 0000000000000000 R08: ffff888f5911fa70 R09: ffff888f5911fa68 Oct 8 02:02:49 Homebase kernel: R10: ffffea0022918ec0 R11: ffff888ffe9e0b80 R12: ffff888fbfafe000 Oct 8 02:02:49 Homebase kernel: R13: ffffc9001294fd20 R14: 0000000000000000 R15: 0000000000000000 Oct 8 02:02:49 Homebase kernel: FS: 000014b7fa3ac780(0000) GS:ffff888ffe9c0000(0000) knlGS:0000000000000000 Oct 8 02:02:49 Homebase kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Oct 8 02:02:49 Homebase kernel: CR2: 0000000000000080 CR3: 00000001a6aa2000 CR4: 0000000000340ee0