Jump to content

GroxyPod

Members
  • Content Count

    118
  • Joined

  • Last visited

Community Reputation

9 Neutral

About GroxyPod

  • Rank
    Advanced Member

Converted

  • Gender
    Male
  • Location
    California, USA

Recent Profile Visitors

615 profile views
  1. Per their own docker hub at: https://hub.docker.com/r/plexinc/pms-docker they're supposed to have separate tagging: latest, plexpass, and public however they haven't updated the plexpass or public one in over a year. Safe to assume you're on the public (regular) version and not plex pass. To utilize plexpass versions (so long as you're a plex pass holder), you'll likely need to use another docker container like linuxserver where they keep it more up to date.
  2. You'll likely need to have a secondary router setup with VPN connectivity that sits behind your main router for it's internet source.
  3. I use that card in my setup. You need to have a motherboard that supports splitting the PCIe lane into 4x4x4x4 in order to utilize all 4 slots. 2 slots should be fine though I believe.
  4. Dec 10 22:35:04 MediaServer kernel: mce: [Hardware Error]: Machine check events logged Dec 10 22:35:04 MediaServer kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 4: e600000000020408 Dec 10 22:35:04 MediaServer kernel: mce: [Hardware Error]: TSC 0 ADDR fef13dc0 Dec 10 22:35:04 MediaServer kernel: mce: [Hardware Error]: PROCESSOR 0:506c9 TIME 1576017266 SOCKET 0 APIC 0 microcode 38 Looks like you might need to test your memory with memtest86 (available when booting up unRAID)
  5. It would help if the specs of your setup were included and the actual USB drive manufacturers/models were provided. For all we know, you can be using drives you got off Wish. I've been using unRAID for almost 4 years now, never had a single issue with the flash drive dying and I'm using a SanDIsk Cruzer Fit 16GB flash drive.
  6. You might want to look into user scripts. I think you'd have to use bash, but if you're looking to do a re-occurring script, it might be a better solution.
  7. As testdasi said, it is likely a bad DIMM. I just had to deal with this myself and it isn't fun. Best thing to do would to run memtest86 with all memory installed until you start seeing memory errors. Once you see these errors, take a picture / write down where they occur (eg: test 2, test 3, etc..) and how many. That way you only have to run up to those tests and not have to go through the entire testing to find the bad stick. Once you've found out which test you seem to have failures at, remove all but the minimum amount of memory required by your system and then run the test past the test # you were previously getting errors at. Then you just swap one stick in at a time, retest up to the test # after and repeat until you find the bad stick. After you've eliminated the last stick, run through the full memory test gambit to ensure everything checks out.
  8. Nov 20 13:29:36 Tower kernel: mce: [Hardware Error]: Machine check events logged Nov 20 13:29:36 Tower kernel: EDAC sbridge MC1: HANDLING MCE MEMORY ERROR Nov 20 13:29:36 Tower kernel: EDAC sbridge MC1: CPU 0: Machine Check Event: 0 Bank 11: 8c00004a000800c2 Nov 20 13:29:36 Tower kernel: EDAC sbridge MC1: TSC 7cc2532c5a4c6 Nov 20 13:29:36 Tower kernel: EDAC sbridge MC1: ADDR 44721c000 Nov 20 13:29:36 Tower kernel: EDAC sbridge MC1: MISC 90840080008148c Nov 20 13:29:36 Tower kernel: EDAC sbridge MC1: PROCESSOR 0:406f1 TIME 1574278176 SOCKET 0 APIC 0 Nov 20 13:29:36 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) Looks like you've got a memory module that might be starting to fail. I would look into running memtest86, find out which one it is and replace it if you start getting more frequent errors or have system instability.
  9. I am not having data corruption issues running a single cache drive using /mnt/cache/appdata for all dockers. All SQLite DBs are on the cache drive. Specs are in my signature as follows: unRAID Server Pro v6.7.2 | Array: 112TB | Parity: 10TBx2 | Cache: Samsung 970 EVO Plus 500GB NVMe | Flash Drive: SanDisk Cruzer Fit 16GB Case: Norco-4220 | MB: ASRock EP2C602-4L/D16 | PSU: Corsair RM1000i | RAM: IBM RDIMM 256GB (16GBx16) DDR3 1.5v Controllers: ASUS HYPER M.2 X16 | LSI 9201-16i | LSI 9210-8i Docker Containers: Guacamole | Jackett | Lidarr | Let's Encrypt | NetData | NZBGet | Ombi | Plex | Radarr | rTorrentVPN | Sonarr | Tautulli | Unifi Controller Plugins: Dynamix System Statistics | CA Auto Update Applications | Community Applications | Dev Tools | Dynamix SSD TRIM | Dynamix System Information | Fix Common Problems | Nerd Tools | Preclear Disks | rclone | Recycle Bin | Tips and Tweaks | Unassigned Devices | unBALANCE | User Scripts
  10. Anyone else having an issue with all torrents showing timed out on trackers with the latest update (assuming 1.1.r42.g37c9d4b-1-04)? Just backed down to 1.1.r42.g37c9d4b-1-03 and my torrents no longer show time out.
  11. Recently replaced my cache drive and noticed the BTRFS Filesystem DF reporting the wrong size. I ran btrfs fi usage /mnt/cache and noticed that my cache drive has a large unallocated spot which is likely what is causing my issue. btrfs fi usage /mnt/cache Overall: Device size: 465.76GiB Device allocated: 171.03GiB Device unallocated: 294.73GiB Device missing: 0.00B Used: 167.42GiB Free (estimated): 297.08GiB (min: 297.08GiB) Data ratio: 1.00 Metadata ratio: 1.00 Global reserve: 260.03MiB (used: 0.00B) Data,single: Size:168.00GiB, Used:165.65GiB /dev/nvme0n1p1 168.00GiB Metadata,single: Size:3.00GiB, Used:1.76GiB /dev/nvme0n1p1 3.00GiB System,single: Size:32.00MiB, Used:48.00KiB /dev/nvme0n1p1 32.00MiB Unallocated: /dev/nvme0n1p1 294.73GiB I looked on the googles and found that there is a btrfs filesystem resize max command that looks like it could correct the issue, but I would like to know if are any requirements to do this since it would be expanding the volume. I'm assuming the best practice would be to stop the array, backup the data, then do the command: btrfs filesystem resize max /mnt/cache and then bobs your uncle. Just wanted some clarification in case I need to format the cache drive instead. Thanks in advance! smalls-diagnostics-20190731-2102.zip
  12. I believe this is functioning as designed. They don't want your unraid.net address accessible outside of your own network. As far as disabling SSL, you should be able to change the Use SSL/TLS option to no within the Identification setting.
  13. I don't mean to send someone down a rabbit hole that doesn't need to be gone down; but after reading this thread, one question jumped out at me. Does anyone who is experiencing this corruption have a setup involving raid cards (LSI or other)? From what I'm seeing (with the limited listing of hardware specs provided thus far), it seems to be impacting people who directly connect drives to their motherboard. Not sure if this actually matters or not but just a thought.
  14. So I upgraded my memory from 128GB to 256GB and now the reported 'max memory' is up to 256GB. Looks like it can be pushed to the full 512GB On my way! lol