Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

8 Neutral

About GroxyPod

  • Rank
    Advanced Member


  • Gender
  • Location
    California, USA

Recent Profile Visitors

510 profile views
  1. 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
  2. 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.
  3. 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
  4. 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.
  5. 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.
  6. 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
  7. Ah that makes sense. I have dual E5-2670s in place right now. The max showing on ARK is 384GB per CPU. Guess I'll just have to try
  8. Can you upload your diagnostics? That will help speed up the process for those who can assist
  9. Forgive me if this has been asked/answered but my searching-fu of google, reddit, and this forum has failed me if that is the case. I noticed on the unRAID dashboard, it has the following: installed: 128 GB Multi-bit ECC max. installable capacity 192 GB The manual for the motherboard reports the following: Capacity- 16x 240-pin DDR3 DIMM slots - Support up to 512GB DDR3 R/LR DIMM ; 128GB ECC/non-ECC unbuffered UDIMM I'm looking to max out the memory with RDIMMS potentially and wanted to make sure there wasn't some limitation for this in unRAID. Thanks in advance!
  10. Thanks for looking into this Benson, I appreciate it! I figured that was the culprit. I went ahead and swapped the SATAIII port from SATAIII_0 to SATAIII_1 to see if that improves anything. Keeping an eye on it for possible bad port or cable. Booting up UnRAID did not produce the issue that was occurring above so we shall see. Fantastic. I'd prefer to just use PCIe power if that's the case anyway. Less cables to run across the board. Gotcha. So it sounds like I'd be stuck with a 3 card setup regardless. My last parity run (06/01/2019) was: Duration: 23 hours, 59 minutes, 35 seconds. Average speed: 115.8 MB/sec. When Parity starts, its usually in the 160 MB/sec range until it reaches the edge of one of the disks. I've got a mixture of 4TB/6TB/8TB disks in the array at the moment. As far as bottlenecks go, I'm not necessarily experiencing any other than an issue with slow DB messages on the Plex docker. Given that the cache drive was the subject to that error, it could of been related. I will continue to monitor and work on updating my disk tunables if that turns out not to resolve the issue.
  11. Hey everyone, Running through my syslogs, I came across this line multiple times (example pulled from syslog.2.txt): Apr 8 23:53:22 Smalls kernel: ata1.00: Enabling discard_zeroes_data Apr 8 23:53:22 Smalls kernel: sd 2:0:0:0: [sdj] Attached SCSI disk Apr 8 23:53:22 Smalls kernel: ata14: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Apr 8 23:53:22 Smalls kernel: ata14.00: ATAPI: MARVELL VIRTUALL, , 1.09, max UDMA/66 So my concern is 2 parts: 1) Does that mean sdj is the device that is only pulling the 1.5Gbps link? If so, that is my cache drive 2) It mentions MARVELL below it (hisssssss), does that mean it is on the MARVELL sata port? I double checked it compared to the board and the cache drive is plugged in to SATAIII_0 which should be the Intel SATAIII port. Potential Improvements: Currently I'm running LSI 9210-8i x3 cards (IT Mode) in PCIE5/PCIE4/PCIE3. I was looking in to getting a RAID expander card and saw an ebay posting for: (E91267 E91267-202 E91267-203 INTEL RAID EXPANDER STORAGE CONTROLLER). So, a couple questions came from that: 1) Does the version of the card matter for unraid? E91267 vs -202 vs -203 2) Does anything extra need to be done to the card to get it to work with unraid, like something similar to IT Mode or a specific firmware? ^ - Unfortunately I have never used a RAID EXPANDER card before, so that drives additional questions: 1) Does a card like this require an additional power connector? 2) Does the card work like this: I plug in my 5 bays in to 5 of the connectors on the card, then the 6th connector goes to the LSI 9210-8i via mini-sas to mini-sas cable? If that is the case, does the cable location matter on the expander card? Thanks in advance for your time! Diagnostics attached smalls-diagnostics-20190604-1904.zip