Leaderboard

Popular Content

Showing content with the highest reputation on 04/08/20 in all areas

  1. To work around this add a variable like below. Just use the latest image. edit: https://nginxproxymanager.com/advanced-config/
    2 points
  2. I literally have about 50 tabs open, but this was probably the one that I ended up following: https://tfahl.com/2017/08/04/graphing_snmp_data_with_prometheus_and_grafana.html Thanks to him and you, I have both Prometheus and the Prometheus SNMP exporter running in (separate) containers, talking to each other, collecting data..... and I've produced graphs in Grafana, also in a separate container. So, success! Thanks GilbN!
    1 point
  3. Yep because, i think the Forge server doesn't run that's why no screen can be found, please look in the logfile for Forge itself (i also tried to run a Forge server, it rund fine for a week or so and then it won't start so i switched over to Spigot/Bukkit). Yep totaly understandable but like i've said this game is designed without linux in mind... Is that a Ryzen specific problem? On my Xeon it works just fine. What are your Extra Parameters that you've entered (can you give me your full startup command)? This link that you provided says that the -Xms and -Xmx commands should be bevor the -jar and they are. Yep, many people don't run actually the vanialla server in my container and everyone who want's to update the server or run another version have to place the file manually in the server directory but i changed that already and a new container is available (the above issue is not solved and i would advice you to not update since it will delete your above fix). Yep, that's only if someone needs it and an entry can easily be created by clicking on 'Add another Path, Port, Variable, Label or Device' then selecting 'Variable' enter the correseponding variable from the docker file in the 'Key' section (in this case 'EXTRA_JVM_PARAMS') and enter your paramaters at 'Value' ('Name' can be empty or what you want), click 'Add' and then 'Apply' the container will now start with your extra java startup parameters. I think you are using the GAME_PARAMS wrong you should create this variable like i said above and use it like that (some minecraft jre's can also use command line switches and that are the GAME_PARAMS look for example at spigot: Click). The EXTRA_JVM_PARAMS is for example for something like this: '-XX:G1NewSizePercent=20 -XX:G1ReservePercent=20 -XX:MaxGCPauseMillis=50 -XX:G1HeapRegionSize=32M'.
    1 point
  4. Edit the apcupsd configuration file on the windows box UPSTYPE net DEVICE <unraidip>:3551
    1 point
  5. Thanks for the feedback, I tried to mount it manually but without any changes. Here is the log with auto-mount. I have only been testing unRaid for a few days and then switch completely from Proxmox. Real good software. Regards Maggi tower-diagnostics-20200408-1958.zip
    1 point
  6. If after a correcting check you get more sync errors (without an unclean shutdown) first thing to do is to run memtest.
    1 point
  7. Sorry, no idea then, I use multiple connections, but form a single Windows desktop to multiple Unraid servers, and some servers connect to my desktop with one port and to another Unraid server with the other.
    1 point
  8. In this case both mirros are corrupt, or it would be automatically fixed. That looks more like corrupt metadata, but any corrupt data can be identified by a scrub, it will also result in an i/o error if you try to read/copy that file.
    1 point
  9. One of the worst SMART reports I have ever seen. Replace ASAP.
    1 point
  10. That is a good start. It would be enough for me and the way I use cache.
    1 point
  11. 1 point
  12. Did you format the disks? You can also post the diagnostics: Tools -> Diagnostics
    1 point
  13. It would be great if the folder does not belong to the "root" group. Set chown to nobody:users. You can do that in your normal terminal ssh to your unraid. drwxrwx--- 1 nobody users 240 Apr 8 11:10 data/ If you are working with GUID etc. it will work. Otherwise it maybe throws some error. Cheers
    1 point
  14. There are checksum errors on the pool, and possibly because of that it's failing to remove the missing device, you can reboot to try again, if it still doesn't work best bet is to backup, re-format and restore the data.
    1 point
  15. Had this issue too, but finally figured it out. Despite you setting the folders in the Docker Setup, you also need to tell SAB to use the data folder in it's configuration menu because for some reason it is set by default to save to the config folder there.
    1 point
  16. Good day everyone, Just want to say thanks to the unraid team, spaceinvaderone and everyone on the forums for all their work and love for this beautiful software that is UNRAID. I'm a noob Unraider. I recently built my first system. I enjoy the learning process and setting up cool dockers for eg media streaming and downloading, etc. However having become a dad recently my time is very limited now. My question is will the unraid team ever consider a subscription service with video tutorials (like spaceinvader, I appreciate his work and very grateful for it but sometimes feel I'd prefer to get guidance from the ppl that designed the os) or individuals authorized by unraid from the community to assist noob users in getting more advanced dockers or features set up quickly? Will there by any changes to the license tiers in the future? Will unriad team ever release an official app for ios and Android?. (There are options out there but I'm not really impressed by it, some features don't work as I would like them to) How important is ecc ram for unraid software compared to ZFS. Does it make a SIGNIFICANT difference the way the file systems are set up having ECC ram for unriad os. Or will I have relatively the same protection using normal hardware that doesn't support? Best regards, Shane. Sent from my iPhone using Tapatalk
    1 point
  17. for rj45 i recommend a Dell HN10N Broadcom 57810 Dual-Port 10 Base-T on ebay you can get it for $25 and its 10gb
    1 point
  18. Two sentences: 1. http://$IP:$PORT/install.php 2. Me idiot. Never mind, stay healthy and thank you for your hard work!
    1 point
  19. found the problem i run the docker without the stem username and password and it immediately update
    1 point
  20. I figured it out and its working. But what flag do i put so i can see what Rclone is doing while its syncing? I need to just keep searching. Figured it out as well. Thanks
    1 point
  21. Seems to be going normally, write speed to the array is close to 40MB/s, which is about right for default writing mode, and at those speeds it should move more than 100GB per hour, are most files similar sized media files or do you some time move smaller files? Smaller files can take much longer to copy/move. Also and just in case you're not familiar with it, if you enable turbo write mover should go much faster, at around 300/400GB per hour, at the expense of all drives spinning up.
    1 point
  22. nothing wrong with the docker image, see q10:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md edit @brimnac you also have this issue.
    1 point
  23. hopefully not, SMART looks fine JB ( ↓ ) is the resident expert on hardware, FS corruption, etc, below are a few threads where he's discussed how to handle this type of thing. I'm by no means an expert so do your due diligence but what I get from the first thread is that you should run xfs_repair without -n, and use -L if needed (you may end up with a lost and found of recovered files). Then verify that the emulated files are all intact before attempting to rebuild. Only rebuild to the same disk if you're positive the disk is good, which I believe it is. The next post "XFS File System Corruption - Safest way to Fix?" talks about using UFSExplorer to recover data from formatted XFS disks if necessary, also the OP discusses repairing the corruption outside of unRaid in Fedora where the xfs_repair is native. also mentioned in the next post... The last thread is probably less relevant but discusses possible causes such as bad ram... So you actually have the original disk intact, ultimately that could prove to be less corrupt make sure you don't clear it until this is all resolved.
    1 point
  24. Hi, I'm running a Ryzen build on Asus ROG Crosshair Hero VIII X570 chipset. I initially had ECC memory and had no issues with it, however I can't prove if it correct errors or not. ECC I used wasn't expensive at all compared to OC memory for gamers, but the thing is that only unbuffered ECC is supported and not many manufacturers offers it. And you'll be limited to stock frequency 2666Mhz that means your Ryzen infinity bus will run at 1333 which means worse performance. I then switched to Kingston DDR4 32Gb (2x16Gb) 3466 MHz pc-27700 HyperX FURY Black . My gaming VM benchmarks merely showed 1-2 FPS improvement . So you can easily game on ECC as well.
    1 point
  25. Windows has a feature (more like a flaw) where it always caches credentials, so if you've accessed a share previously when it was public and then switch the share to private, Windows will keep sending the original credentials (ie: none) and be denied access. Clear the credentials in Windows. Also, a wealth of common problems affecting windows and all NAS systems is here Try the Tips & Tweaks plugin What parts of it? If you need to access the GUI remotely, then a VPN (wireguard or openvpn) or a reverse-proxy (Let's Encrypt) is what you want. If you need to access the GUI of certain applications running, then once again the above If you simply want to expose the ports for Plex, then go ahead and do that on your router. Expose the minimum required for the app to operate (ie: 32400). If you want to expose your entire server by tossing it into a DMZ on the router, then don't do that unless you know and understand and can properly secure your network SpaceInvader One's youtube channel is usually pretty good.
    1 point
  26. You may need to open a cmd prompt as administrator and run: ipconfig /flushdns Once you get pfsense up, you'll be able to watch the bandwidth usage on the status page to you can see if you are using the internet or the cache server as well.
    1 point
  27. Hi guys, Just wanted to drop in and say I managed to solve this! I noticed when booting in Windows, that it would fail to find enough resources to allocate to PCI devices, resulting in error 12 on maybe a PCI-E root port or, at times, the 1080 ti graphics card! Looking at the Unraid logs, I found the same kind of thing happening there that I had missed when debugging the logs last time: Mar 27 14:57:47 gnznas kernel: pci 0000:04:00.0: PCI bridge to [bus 05] Mar 27 14:57:47 gnznas kernel: pci 0000:04:00.0: bridge window [mem 0xf2100000-0xf21fffff] Mar 27 14:57:47 gnznas kernel: pci 0000:06:00.0: BAR 15: no space for [mem size 0x18000000 64bit pref] Mar 27 14:57:47 gnznas kernel: pci 0000:06:00.0: BAR 15: failed to assign [mem size 0x18000000 64bit pref] Mar 27 14:57:47 gnznas kernel: pci 0000:06:00.0: BAR 14: assigned [mem 0xe7800000-0xe8ffffff] Mar 27 14:57:47 gnznas kernel: pci 0000:06:00.0: BAR 13: assigned [io 0xc000-0xcfff] Mar 27 14:57:47 gnznas kernel: pci 0000:07:01.0: BAR 15: no space for [mem size 0x18000000 64bit pref] Mar 27 14:57:47 gnznas kernel: pci 0000:07:01.0: BAR 15: failed to assign [mem size 0x18000000 64bit pref] Mar 27 14:57:47 gnznas kernel: pci 0000:07:01.0: BAR 14: assigned [mem 0xe7800000-0xe8ffffff] Mar 27 14:57:47 gnznas kernel: pci 0000:07:01.0: BAR 13: assigned [io 0xc000-0xcfff] Mar 27 14:57:47 gnznas kernel: pci 0000:08:00.0: BAR 1: no space for [mem size 0x10000000 64bit pref] Mar 27 14:57:47 gnznas kernel: pci 0000:08:00.0: BAR 1: failed to assign [mem size 0x10000000 64bit pref] Mar 27 14:57:47 gnznas kernel: pci 0000:08:00.0: BAR 3: no space for [mem size 0x02000000 64bit pref] Mar 27 14:57:47 gnznas kernel: pci 0000:08:00.0: BAR 3: failed to assign [mem size 0x02000000 64bit pref] In baremetal Windows, there are a number of options you can go through to fix this issue outlined here: https://egpu.io/forums/pc-setup/fix-dsdt-override-to-correct-error-12/. You can do a DSDT patch with Clover and remove a PCI-E root port that you don't care about (which can completely disable visibility of a 2nd graphics card (I also have an AMD RX580 and Nvidia GT 710 in there too) from the Windows OS). I thought maybe also this might work: https://khronokernel-4.gitbook.io/disable-unsupported-gpus/ Neither of those things I could get working, but I did find an acceptable workaround for now.. which is to press F11 at boot, and when the boot selection menu comes up, re-plug the eGPU box back into thunderbolt port. Then boot into Unraid afterwards. This now shows the devices in the PCI list as follows: +-01.2-[01-2f]----00.0-[02-2f]--+-01.0-[03-22]----00.0-[04-22]--+-00.0-[05]----00.0 Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan Ridge 4C 2018] | | +-01.0-[06-13]----00.0-[07-08]----01.0-[08]--+-00.0 NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] | | | \-00.1 NVIDIA Corporation GP102 HDMI Audio Controller | | +-02.0-[14]----00.0 Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 4C 2018] | | \-04.0-[15-22]-- ... +-03.1-[31]--+-00.0 NVIDIA Corporation GK208B [GeForce GT 710] | \-00.1 NVIDIA Corporation GK208 HDMI/DP Audio Controller +-03.2-[32]--+-00.0 Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] | \-00.1 Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590] But when I passthrough the 1080ti to a Windows 10 VM, the device won't start because error 43, which is something SpaceInvaderOne has documented very well in his Youtube videos (check them out if you haven't already they're all really good!) So I went through all of his suggestions, and _still_ it didn't work. Looking at the logs again, there are still some PCI devices whose BAR is failing to start. After much digging around Linux kernel man pages I found that adding `pci=realloc` to the boot args of Flash USB, the resource accounting is sorted out completely on the next boot and all PCI devices find resources and start successfully! yay Make sure you also have CSM disabled and above 4G enabled in your BIOS, and use a VBIOS ROM in your libvirt xml (all documented by SpaceInvaderOne) .. I also set 'Above 4G MMIO` to 36 bit as well (I thought that was related to the 36bit large memory that the egpu.io page was trying to set up, but not sure if it bears any relevance over the other Above 4G setting in CSM area). I also set PCIE Devices Power On to enabled in BIOS too. Hope this helps someone. I now have a working Mac and Windows VMs running simultaneously with their own separate graphics cards!
    1 point
  28. Well, I figured this out and thought i would come back and let you know. I initially grabbed windows iso from the windows website, at the time of this post that was version 1909. When this failed to install i decided to grab an older version so i went for 1809, this installed perfectly. strange but true!
    1 point
  29. hmm not working for me - is it still working for you guys? EDIT: its gone http://www.docs.influxdata.com/influxdb/v1.5/tools/web_admin/ As of version 1.3, the web admin interface is no longer available in InfluxDB. The interface does not run on port 8083 and InfluxDB ignores the [admin] section in the configuration file if that section is present. Chronograf replaces the web admin interface with improved tooling for querying data, writing data, and database management. See Chronograf’s transition guide for more information.
    1 point
  30. I have an unmountable BTRFS filesystem disk or pool, what can I do to recover my data? Unlike most other file systems, btrfs fsck (check --repair) should only be used as a last resort. While it's much better in the latest kernels/btrfs-tools, it can still make things worse. So before doing that, these are the steps you should try in this order: Note: if using encryption you need to adjust the path, e.g., instead of /dev/sdX1 it should be /dev/mapper/sdX1 1) Mount filesystem read only (safe to use) Create a temporary mount point, e.g.: mkdir /temp Now attempt to mount the filesystem read-only. v6.9.2 and older use: mount -o usebackuproot,ro /dev/sdX1 /temp v6.10-rc1 and newer use: mount -o rescue=all,ro /dev/sdX1 /temp For a single device: replace X with actual device, don't forget the 1 in the end, e.g., /dev/sdf1 For a pool: replace X with any of the devices from the pool to mount the whole pool (as long as there are no devices missing), don't forget the 1 in the end, e.g., /dev/sdf1, if the normal read only recovery mount doesn't work, e.g., because there's a damaged or missing device you should use instead the option below. v6.9.2 and older use: mount -o degraded,usebackuproot,ro /dev/sdX1 /temp v6.10-rc1 and newer use: mount -o degraded,rescue=all,ro /dev/sdX1 /temp Replace X with any of the remaining pool devices to mount the whole pool, don't forget the 1 in the end, e.g., /dev/sdf1, if all devices are present and it doesn't mount with the first device you tried use the other(s), filesystem on one of them may be more damaged then the other(s). Note that if there are more devices missing than the profile permits for redundancy it may still mount but there will be some data missing, e.g., mounting a 4 device raid1 pool with 2 devices missing will result in missing data. With v6.9.2 and older, these additional options might also help in certain cases (with or without usebackuproot and degraded), with v6.10-rc1 and newer rescue=all already uses all theses options and more. mount -o ro,notreelog,nologreplay /dev/sdX1 /temp If it mounts copy all the data from /x to another destination, like an array disk, you can use Midnight Command (mc on the console/SSH) or your favorite tool, after all data is copied format the device or pool and restore data. 2) BTRFS restore (safe to use) If mounting read-only fails try btrfs restore, it will try to copy all data to another disk, you need to create the destination folder before, e.g., create a folder named restore on disk2 and then: btrfs restore -v /dev/sdX1 /mnt/disk2/restore For a single device: replace X with actual device, don't forget the 1 in the end, e.g., /dev/sdf1 For a pool: replace X with any of the devices from the pool to recover the whole pool, don't forget the 1 in the end, e.g., /dev/sdf1, if it doesn't work with the first device you tried use the other(s). If restoring from an unmountbale array device use mdX, where X is the disk number, e.g. to restore disk3: btrfs restore -v /dev/md3 /mnt/disk2/restore If the restore aborts due an error you can try adding -i to the command to skip errors, e.g.: btrfs restore -vi /dev/sdX1 /mnt/disk2/restore If it works check that restored data is OK, then format the original btrfs device or pool and restore data. 3) BTRFS check --repair (dangerous to use) If all else fails ask for help on the btrfs mailing list or #btrfs on libera.chat, if you don't want to do that and as a last resort you can try check --repair: If it's an array disk first start the array in maintenance mode and use mdX, where X is the disk number, e.g., for disk5: btrfs check --repair /dev/md5 For a cache device (or pool) stop the array and use sdX: btrfs check --repair /dev/sdX1 Replace X with actual device (use cache1 for a pool), don't forget the 1 in the end, e.g., /dev/sdf1
    1 point