BRiT

Members
  • Posts

    6399
  • Joined

  • Days Won

    9

Everything posted by BRiT

  1. Use the existing plugins for Python 2 and 3 that others have already made. Same for IPMITools if you need that. Search for them using Community Applications.
  2. cat /etc/slackware-version That should always give you your answer.
  3. I just updated my unRaid server to this card last week and it's detected and working for me on the latest official 6.10.3 series. I have it set as eth0 and marked all the other nice as down. No issues that I can see yet. Sounds like you got a bad card.
  4. You can use a Bridge network setup in unRaid and use Docker IPVLAN setting to assign specific IP address to each docker container then setup firewall rules on your router for that IP.
  5. It's possible through a slightly different means. Use IPVLAN for those dockers so they each have a unique IP. Setup dnsmasq on your router. Configure the hostname.local as entries for the specified IPs. I have emby.local, transmission.local, eggdrop.local, and speedtest.local pointing to the respective IP addresses.
  6. Unraid runs from RAM. Changes do not persist across reboots unless additional steps have been taken to persistent to the flash drive and reloaded on startup. Most users use the plugin "User Scripts" to run and manage customizations like that.
  7. No sound card drivers on the host server (unraid) so doubtful if getting an audio device to work with Docker especially if its a plug-in card like PCI / PCI Express. Probably easier to get it passed through to a VM and use it that way.
  8. I suggest you READ the previous post.
  9. I never update packages inside of a Docker container as that defeats the entire purpose of Dockers. That purpose is that Docker Creators manage the entire internal contents to ensure an exact and known working experience.
  10. I thought you can already get this by using BTRFS as your filesystem in your data drives. That way your array drives are parity protected and the contents of your files have Metadata checksums for the file contents.
  11. It doesn't work on the user filesystems, at least it didn't when I tried it 5 years ago. So use it on the actual filesystems such as /mnt/disk#/share/directory/file
  12. If you're still curious enough have a look at what exactly it stores. It's mounted so you can see everything that's inside of it.
  13. No need for all those complicated steps at all. As already posted, support for this is built into unraid since 6.9.2. I suggest reading and comprehending the following post:
  14. Everything I have seen with networking is to run both IPV4 and IPV6 at the same time, which is called dual stacked, or to run only IPV4. The attempts at only running IPV6 currently results in not being able to reach huge portions of the internet. The rest of the network world simply isn't ready yet.
  15. For files that are never supposed to change, look into marking them as immutable with, chattr +i filename . The only way the file can be changed is through removing the immutable attribute first with, chattr -i filename.
  16. Isn't there enough hardware level support in hard drives where they detect and correct bitrot from a sector perspective? I vaguely recall a post by Limetech (maybe?) that went into all the various levels of protection that is actually built into the storage hardware systems.
  17. Post your parity check history so one knows when it faltered. You do have it scheduled to run regularly, like monthly right? You can see this on the Web UI by looking at parity history and posting a screenshot of the window captured. I dint know where that info might be inside the diag file, otherwise I'd look there.
  18. Love to see these quick release series. Hope all goes smoothly.
  19. That's not the installed to directory. Look under /usr/local/emhttp/plugins/ hierarchy, that will have plugins installed.
  20. Run and finish Parity check at all of the following times: 1. before any server maintenance. 2. after any server maintenance 3. before moving a server 4. after moving a server But its your data and your server so feel free to take whatever risks you're comfortable with.
  21. I would not want to put any of my servers on the internet with DNS records pointing to them, so using CloudFlare as a security firewall proxy makes sense. But its your server and your data so take whatever highstakes risks that you are comfortable with.