lordmarqui

Members
  • Posts

    34
  • Joined

  • Last visited

Recent Profile Visitors

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

lordmarqui's Achievements

Noob

Noob (1/14)

0

Reputation

1

Community Answers

  1. Thanks Will flip that on and report back.
  2. Need some advice. Just got done with a new build using an intel i13900k and gigabyte pro art mobo. New everything and server is seemingly in tip top shape. However it randomly shuts down (crashes?). After a day or so. I have it on its own ups, on its own outlet, which I which is on its own breaker. (This was happening before and I assumed it was a power issue so I had an electrician run dedicated lines to my server closet.) Server is water cooled and stays well with spec temp range. I just need some direction to troubleshoot this. Thoughts on where to go next debugging this? (I plan to post logs once I’m back home and can pull them off the server)
  3. As an update it turns out that my Unifi Controller was using 1TB!!! Which makes sense that everytime Mover ran, it would take data off the array and move back to the cache pool because that's how I set it to run (Cache Priority without a min amount of memory free). Deleted, ran trim and the server now hums. Thanks everyone!
  4. Woke up this morning and the cache pool is maxed to 511GB, where the Appdata share ballooned to fill it all... Not sure where to go next... I'm sure there's an obvious issue that I'm missing but can't seem to pin it down. Appreciate everyone's help ahead of time.
  5. Here are the Share utilizations per drive after clicking Compute: appdata 257GB total: Cache: 236 GB Disk 6: 14.0 GB Disk 7: 2.96 GB From my reading, appdata should at most be 10% of that. Any thoughts? I will post new log files below in case that's helpful. samson-diagnostics-20220106-0029.zip To reiterate, the downloads are going to a separate cache pool (called cache_ssd)... My appdata and system shares go to another cache pool, which are the drives that are getting filled obnoxiously fast at the moment and that I'm seeking advice on how to correct.
  6. I misspoke re the appdata share. It successfully moved to the array when I invoked mover prior to rebuilding everything. as far as now, can you clarify your advice? That is correct that I have the downloads share pointed to a separate ssd cache pool just for downloads. The other cache pool is where the system- and appdata are pointed to. does that help?
  7. thanks for the reply... so the initially i had a completely full cache drive to the tune of 500gb, where all 500gb were consumed by my docker image and appdata share... i deleted my docker image but the appdata folder was also incredibly large and i couldnt restart the docker service, so i changed the appdata share settings to No and invoked Mover to offload appdata. It appears it went to disk6. i then rebuilt docker and changed the share preference for appdata back to Prefer. Fast forward to now. I've rebuilt Docker and examined every path to ensure the mappings had the correct leading / when needed, etc... Testing out the downloads, which began this whole issue, I see that the problem persists... I just stopped docker services and attempted to run Mover, but nothing happened. Meaning, the cache drive didn't decompress... Sab's Docker Run is below: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='binhex-sabnzbd' --net='proxynet' -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -p '8181:8080/tcp' -p '8090:8090/tcp' -v '/mnt/user/downloads/':'/data':'rw,slave' -v '/mnt/user/appdata/binhex-sabnzbd':'/config':'rw' 'binhex/arch-sabnzbd' f9eca668b41adf5f4cb6dfed537f9150c005bd080334e69df97c40680fb202b3
  8. I'm having issues with my cache drive (where my appdata share is mapped to) filling up when I download files via Sabnzbd. I've poured over all the posts and videos I can find, which has helped me narrow the issue down to what I think is a "leaky" or maybe an improperly mapped path inside of the docker instance itself... That said, I new to this and only think that might be the issue and am here asking for some advice. I'm attaching my logs for some guidance. I would appreciate any help the community could offer. Thanks in advance! samson-diagnostics-20220105-2227.zip
  9. assuming this solves my ssd woes, what do you think the problem was related to?
  10. ok great... i connected two of the ssd's to this port this morning and have downloaded about 400gb and no issues so far... i'll report back in a few days and mark this issue as resolved if no trouble. thanks a lot!
  11. i mounted 2 ssd's as i mentioned above, ran downloads for about 4 hours but then the complete_downloads SSD dropped off, but the incomplete_downloads SSD remained mounted.... diagnostics are attached. thanks a lot for all the advice! samson-diagnostics-20190904-0027.zip
  12. i went ahead and placed 2 of my SSD's on 2 of the mobo's SAS ports... i started a few downloads and i'll report back soon.
  13. Thanks for the reply... Just so I’m sure, this is the layout of my mobo. The 2 cache drives are in the sata 6gb/s (which I assume is sata3) which leaves me with 3 empty “mini sas cable connectors.” I have 2 sata breakout cables (which plug into one of these mini sas ports and had 6 outputs) — this gives me a total of 12 drives to run off of two ports. I know those cables work. Would it be reasonable to try one drive per cable?
  14. i've done a few things (except for update the mobo firmware bc i'm afraid to brick my system). I bought a 6 port pcie sata 3 card, installed it and got everything working late last night. I moved my incomplete and complete download folders to individual SSD’s (and placed 2 additional SSD's for use once this test passes). I then downloaded a bunch of stuff as I went to sleep since all the quick tests on the mounted SSD's looked great... Woke up this morning and noticed the 4 newly installed SSD’s unmounted about 1 hour after the downloads began. (my 2 separate cache drives are connected directly the mobo and are thankfully fine). This is the same behavior as before. Is there something I’m doing wrong? Thus far I’ve tried directly wiring to the mobo via sata breakout cables, mounting in my Das, and now via this pcie sata3 expansion card — each time the drives unmount. Any thoughts at all? diagnostics attached. if this is truly a mobo firmware issue, do you have a 'hold-my-hand' tutorial so i don't destroy my setup, since this mobo is nowhere to be found anymore? samson-diagnostics-20190903-1802.zip
  15. thanks a lot for the reply... the firmware on this motherboard has been flashed to IT mode and as far as i'm aware of is the most up to date, but i'm clearly no expert. (build guide: https://www.serverbuilds.net/anniversary and flashing to IT mode: https://www.serverbuilds.net/flashing-onboard-sas-2008) i removed all ssd's that i recently installed (leaving my 2 cache drives)... got things back up and running... then i placed the ssd's into a 24-bay DAS unit that i built (similar build guide here: https://www.serverbuilds.net/16-bay-das) and then it all went down again... could the issues be related to the specific drives i'm putting in? they're the same drives that are in my cache (https://www.amazon.com/Silicon-Power-Performance-Internal-SP512GBSS3A55S25/dp/B07997QV4Z?psc=1&SubscriptionId=AKIAIA3UEVTLIG7AIKFA&tag=serverbuilds-20&linkCode=xm2&camp=2025&creative=165953&creativeASIN=B07997QV4Z)... there seemed to be odd behavior when i tried to mount the ssd -- occasionally the ssd's would all mount fine (i was trying to add 4 new ssd's as unassigned devices). occasionally 1 would unmount and then become unmountable. occasinally i would lose 2 of the ssd's off the UI entirely and one would stay mounted and another unmount but the mount button would be grayed out. does any of this make sense?