ceyo14

Members
  • Posts

    140
  • Joined

  • Last visited

Everything posted by ceyo14

  1. I wanted to follow up and get your opinion... I just finished a Parity Check and It found 8345 errors, should I rerun parity and fix the errors or what should I do? I haven't changed anything physically since the last post about the parity write finishing. nas-diagnostics-20200620-2013.zip
  2. I JUST saw what you meant, this does help a lot... I selected what I wanted but it is not saving it, seems to be some limit I am hitting, IDK, I am unslecting them instead, that seems to like it better.
  3. To make matters worse, I just selected the remaining ones and clicked Apply and it didn't apply them, just erased the ones I just selected...
  4. I had already selected cores per Docker so it would stay ones I switched the CPUs, so I either select or deselect at least half of them...
  5. So, I am grateful to even have this issue, or annoyance I guess... and would love to have an easier or faster way to select the CPU Pinnings... See, I had Dual 6 core CPUs and had some things on a few cores and a VM on a whole CPU with Isolated cores... thats great but the issue is, I upgraded to Dual 12 Cores with HT thats 48 cores in total. So now all the CPU Pinnings are moved around and everything was only using physical cores and had to reselect my CPU Pinnings for the 39 Dockers and 4 VMs... So with a simple math, of 39 Dockers and 4 VMs, I now have 2,064 dots that I need to select one by one and it has to be with the mouse, no way to use the keyboard... no way to select a bunch in a row, or all in a docker or all in a row... or select a template or anything, and to make it worse sometimes you get the timing wrong and when you clicked you just missed the dot by a pixel and you adjust to reclick it and it stays gray then click again to select it.... I would love something different to what is there now.... something a bit more intuitive. IDK, I'd like to see what you guys think
  6. OK, Parity Rebuild finished successfully, everything is good now, thanks for the help, will be changing some cables and changing a sata power splitter too just in case. afraid to even touch it now.... but I do have some upgrades waiting for it...
  7. ok, it looks like it... I'll try that and update later, Thanks for all your help!
  8. @johnnie.black I am 60.5% in to the parity check but I am at 668960 parity errors, 1182 read or drive errors in the Parity Drive, and from 8 pending sectors (from 176 before they were "fixed") it is now reporting 104 pending with 2100 reported uncorrect and 24 reallocated sectors... Should I just remove it and start the parity on the other good 8TB drive? all other drives have not given me any more issues...
  9. I played around a bit more with the cables ( I am going to order a full set of cables, too many issues and don't want to keep the same ones...) , and the parity did a full read and repair using HD Sentinel (a bunch were like dark green, maybe weak? but at the end it said they were all good), the other 2 I had most issues with completed some test successfully... and was finally able to start the array... I am going to perform a read check now after I reinstall all memory and run a memtest. (had a bootup issue and only booted after I removed all memory and once I installed one in, it booted I left it like that, only 4gb right now) and will update later. Update: memtest already finished, all good there. Will start Read Check now and update later. Diags as of now. nas-diagnostics-20200611-1533.zip
  10. I have replaced the cable a few times, last time it even hard locked the server, rebooted, and it came up but still have read errors, tried changing to the other controller, tried like 4 cables in different ports too... what do you recommend? nas-diagnostics-20200602-1849.zip
  11. I have a new (to me, good) 8TB drive that I want to use for parity, and the parity drive to use as a data drive... I did have an issue with the parity drive but I believe it was a cable or something as the server was bumped and haven't seen any more issues... well I finally got the drive and started having issues with a 4TB drive (MB4000GCWDC_S1Z1GTFQ) it would show as unmountable: no file system, started playing around with the cables, had a few spares, not too conviced it was the cables or whatever... I did try a disk check on another machine and it worked great... so eventually it did pick up the partition and stayed mounted after running one of the xfs_repair commands... I removed the parity and put the new drive in parity sync started giving me errors..... put back old drive and it was considered new, did the newconfig and checked parity is valid and got it back to how it was, I had a spare 3TB drive and decided to change the 4TB drive and started to free up space on the 4TB to try and replace with the 3TB... but I actually started having issues with the other 4TB drive and the other 8TB Data drive already installed... I have not been able to fix this as of today, I am stuck I don't know what to do.... I have the following in my server... ParityST8000DM004-2CX188_ZCT04EXV - 8 TB (sdg)*0.0 B/s0.0 B/s0 Disk 1ST5000DM000-1FK178_W4J0AEZW - 5 TB (sdb)*0.0 B/s0.0 B/s0xfs5 TB Disk 2MB4000GCWDC_S1Z1GTFQ - 4 TB (sdf)*61.4 KB/s0.0 B/s0xfs4 TB Disk 3MB4000GDUPB_8433K012F - 4 TB (sde)*0.0 B/s0.0 B/s0xfsUnmountable: No file system Disk 4WDC_WD40EFRX-68WT0N0_WD-WCC4E5UZUJK5 - 4 TB (sdc)*0.0 B/s0.0 B/s0xfs4 TB Disk 5HGST_HUH728080ALE600_2EGLHPRX - 8 TB (sdd)*0.0 B/s0.0 B/s25xfs8 TB I have another 8TB HGST drive and a 3TB Toshiba drive (this is the first one to give errors but has checked out to be good with HD Sentinel and test performed). I do have CrashPlan backups, but I believe I would have to wipe everything and restore as I don't have a way to know what is in what disk... the info on the array has not changed much since I've had issues, if anything its not too important. but the fact that I don't know what is in the drive thats unmountable scares me. any way I can force emulated that drive? IDK, thought and suggestion please. everything I have read and tried has not worked, didn't find secondary block on the drive... nas-diagnostics-20200601-1311.zip
  12. Hey, I just installed Graylog but can't seem to login to it, says invalid credential. I installed but didn't do anything else with MongoDB or Elasticsearch... Do I have to do something with them? I am trying using admin with the (16 character) password specified in the Graylog Docker config... changed it and removed special characters but still not working...
  13. ok, So for anyone else who might want to do this how I did it, I was able to setup Rocket TLS with only the following on the Extra Parameters in the advanced tab Extra Parameters: -e ROCKET_TLS='{certs="/data/ssl/fullchain.pem",key="/data/ssl/privkey.pem"}' -e ROCKET_PORT=443 Then in unraid Terminal I typed the following to copy the corresponding Letsencrypt Certs from Nginx Proxy Manager (update the port [443] and scheme [https] on NPM too): scp /mnt/user/appdata/NginxProxyManager/letsencrypt/live/npm-14/fullchain.pem /mnt/user/appdata/bitwarden/ssl/ scp /mnt/user/appdata/NginxProxyManager/letsencrypt/live/npm-14/privkey.pem /mnt/user/appdata/bitwarden/ssl/ Then make sure to change your WebUI HTTP Port to 443 and I also changed the WebUI Link for when you right click on the Dashboard and want to be taken to Bitwarden. I guess I would need to make sure bitwarden copies the cert files on a schedule so when the certs change they are update... not sure how to do this one yet... Any ideas? Also @Roxedus what I forgot earlier is that on the emails I get the Reverse Proxies IP instead of the actual IP, I read somewhere that NPM supports the X-Real-IP $remote_addr; stuff, but I am not sure if it does or what needs to be fixed....
  14. Just tried this but still a no go... I am reverting and trying the Rocket TLS things... Apart from this I had another question, but I'll update about this when I remember...
  15. But how? My DNS (pihole) and or router (untangle) know my domain and automatically resolve it. I erased static DNS Entries and it still resolves to local. Flushed DNS too...
  16. Ok so try this for local... Can I keep the rest how it is for external and it should work right?
  17. Straight to local. Nslookup bw.mydomain.com returns 192.168.2.15. Tracert to bw.mydomain.com only 192.168.2.15 is shown. Does not go to router or reverse proxy first... So app cant login locally because it expects 443 but docker is only 80...
  18. It resolves to BW local IP... If I do nslookup my DNS replies the local IP which only supports HTTP... and app only looks for HTTPS... Externally obviously it works fine. But if I am at home on WiFi its offline only...
  19. I am at a loss with using the app on WiFi... I am using Ngonx Proxy Manager and can reach bitwarden externally... I can reach BW using IP locally on port 80. But if I try to login using the app it looks for port 443 by default and I cant login if connected to WiFi... How come the docker only uses port 80 and not both? What can I do to fix this...?
  20. OMG... so simple yet I've spent so much time on trying to see what is wrong here..... I thought it was either my router or a DNS issue..... (I'm using pi-hole and Untangle) Damn Hidden Advanced Setting, I always forget to open them...
  21. Can you specify what you did. I believe it is exactly my scenario...
  22. I was changing a docker from Bridge to Custom to assign it an IP, but instead of just putting the IP, I put the IP with the Mask (192.168.1.15/24). Obviously this is an invalid IP address and it failed, but when I returned to the dashboard the docker was no longer there... I just redownloaded it and remade it (was starting out with the docker anyways and appdata still there) but wouldn't have thought that to happen, I would have thought it would revert to how it was... I just think this mistake should not erase the docker...
  23. How long have previous build taken to build? not that it is indicative of this build... just curious... Obviously I know there are several factors that affect this regardless...