• Posts

  • Joined

  • Last visited

Everything posted by jmbrnt

  1. Just wanted to say thanks to @ich777 - I put an old GTX 960 into my Dell R720 and now Plex transcoding is all being done so smoothly (particularly subtitled shows). Amazing instructions, all worked first time. Beautiful work.
  2. Cool thanks, I got it working when I used the literal username in question in /home/*username*/upload
  3. First up thanks @MarkusMcNugen for the efforts. In SFTP my goal is to share a directory from my unraid array with a friend. I create him a user and he can SFTP connect fine, but so far no amount of trial and error has successfully shared the files with him. What do I need to add to the container under Unraid to make this work? Say I wanted him to log in and see the content of my /mnt/users/videos dir? Cheers
  4. Bit late to the party, But I am using the librenms/librenms version of the container from CA. Before starting the librenms container, create a new MariaDB container (I am using the linuxserver/mariadb one). Once that is loaded, use the CLI for that container to build your database, and allow access from another host: CREATE DATABASE librenms CHARACTER SET utf8 COLLATE utf8_unicode_ci; CREATE USER 'librenms'@'localhost' IDENTIFIED BY 'librenms'; CREATE USER 'librenms'@'%' IDENTIFIED BY 'librenms'; GRANT ALL PRIVILEGES ON librenms.* TO 'librenms'@'localhost'; GRANT ALL PRIVILEGES ON librenms.* TO 'librenms'@'%'; FLUSH PRIVILEGES; exit Now, when you configure the LibreNMS container, point the DBhost to be the IP of the container (in my case, the same IP as the unraid box itself, as I'm using bridged networks for the containers). After a couple of minutes you can open the LibreNMS GUI and get cracking.
  5. Thanks @broadcastthebadger - this gives me some hope at 1:40am... I have recently brought my (encrypted) Unraid server across the ocean, and when it came time to boot up I was getting all sorts of kernel panic messages (about sync..). Doing it all from the iDrac terminal made gathering logs tricky, but I thought I would try and recover my config files from the existing USB stick (which had been working well for 2+ years) and go with a new stick.. Several hours later and still no boot - the closest I got to that nice blue syslinux menu was using UEFI, which doesn't seem to work with my Dell R720.. Can you share what settings you used in Rufus to make your bootable stick? Tonight I've tried: - 3 different USB (2, 2, 3) sticks - UEFI/BIOS - Creating the sticks using the Unraid tool on Mac, PC - Creating the stick by hand using Mac, PC, Linux - Booting the stick in another PC (which worked) - Drinking
  6. Hey @A75G - thanks for all your efforts. I have installed your LibreNMS container, and setup a MariaDB on the same host librenms/librenms/librenms all the way down - but it can never connect. The log doesn't give much away - any tips for getting this to work? The IPs/ports etc all match.
  7. Ah well at least the symptom makes sense. Not so sure if the cause does. I could understand a restart or reload... cheers
  8. Bit of a weird issue for me. I started up Dynamix' Wireguard plugin, following the blogpost on Worked perfectly with my Macbook, using the `Remote Tunneled Access` mode. Great. Then I went and added another peer (I wanted to use my phone too). After clicking 'Add peer' and generating the keys, I clicked Apply or whatever and... Lost access. No go at all. Can't even connect back to the server to undo what I did. Is that expected behavior? Note, I only generated new keys for the new peer, so I didn't expect to get locked out. Any suggestions welcomed - and thanks for building such a simple/great system!
  9. I have only seen this DRM message on Linux (Budgie 20.20) using Firefox. Still gives me the heebie jeebies
  10. I admit I don't really know what 'DRM features' in Firefox actually means, but here is this:
  11. Today when I went to use the web interface for Plex, Firefox asked me to enable DRM features. Yuck. Not keen at all. Apparently it's something to do with Plex partnering with Warner Bros. I am increasingly aware that Plex isn't the media streaming solution for me any more - but where can I go? What do you use, if not Plex, and how does it compare? I use Plex mainly on iPad, PS4 and the PC (web) very rarely.
  12. Thanks I am now running a scrub, thanks for the tip. Scrub looks OK
  13. Hi Woke up this morning to no DNS (I run unbound on my Unraid server).. Checked and most of my containers had died. Tried to stop and start, no go. Followed a quick Google and tried to remove and re-generate docker.img, which seems to have given me some grace (all containers deleted from GUI, but I can re-add them easily and the data persists...)... However, it seems the problem is one of my cache drives. It's not showing errors on the GUI, but btrfs commands show errors galore. It's a Dell R720, so I don't think it's a SAS cable as many of the other drives would be affected - possibly the SSD has just carked it - it's nearly 4 years old. I have attached diagnostics from prior to a reboot. I also see a lot of these: The cache is a pool of 2 drives - would I be best to remove /dev/sdi and replace it? Thanks
  14. This might be unrelated, as I am running the official Plex docker container (rather than binhex or linuxserver) - but - without doing a thing, the past couple of days/weeks my Plex has been wack. 1) The port that was set to be fwd via my firewall spontaneously changed (had been stable for 2 years) 2) Something seems to have changed with TLS - my PS4 lost the ability to talk to Plex, as did some external folks who share my library. I had to tweak the TLS settings under Settings > Network and change secure settings to preferred. Somehow it had defaulted to strict TLS settings - I could eventually browse to my server on [unraid-ip]:32400, as long as I put in HTTPS:// first... Bloody bananas! Working now though.
  15. Something seems really broken with this container, or at least the job F@H is sending me. It folds for a couple of seconds, then dies. Log below. 21:21:13:WU00:FS00:0xa7:ERROR:------------------------------------------------------- 21:21:13:WU00:FS00:0xa7:ERROR:Program GROMACS, VERSION 5.0.4-20191026-456f0d636-unknown 21:21:13:WU00:FS00:0xa7:ERROR:Source code file: /host/debian-stable-64bit-core-a7-avx-release/gromacs-core/build/gromacs/src/gromacs/mdlib/domdec.c, line: 6902 21:21:13:WU00:FS00:0xa7:ERROR: 21:21:13:WU00:FS00:0xa7:ERROR:Fatal error: 21:21:13:WU00:FS00:0xa7:ERROR:There is no domain decomposition for 25 ranks that is compatible with the given box and a minimum cell size of 1.37225 nm 21:21:13:WU00:FS00:0xa7:ERROR:Change the number of ranks or mdrun option -rcon or -dds or your LINCS settings 21:21:13:WU00:FS00:0xa7:ERROR:Look in the log file for details on the domain decomposition 21:21:13:WU00:FS00:0xa7:ERROR:For more information and tips for troubleshooting, please check the GROMACS 21:21:13:WU00:FS00:0xa7:ERROR:website at 21:21:13:WU00:FS00:0xa7:ERROR:------------------------------------------------------- 21:21:18:WU00:FS00:0xa7:WARNING:Unexpected exit() call 21:21:18:WU00:FS00:0xa7:WARNING:Unexpected exit from science code 21:21:18:WU00:FS00:0xa7:Saving result file ../logfile_01.txt 21:21:18:WU00:FS00:0xa7:Saving result file md.log 21:21:18:WU00:FS00:0xa7:Saving result file science.log 21:21:18:WU00:FS00:FahCore returned: INTERRUPTED (102 = 0x66) 21:22:13:WU00:FS00:Starting 21:22:13:WU00:FS00:Removing old file './work/00/logfile_01-20200326-205104.txt' 21:22:13:WU00:FS00:Running FahCore: /app/usr/bin/FAHCoreWrapper /config/cores/ -dir 00 -suffix 01 -version 705 -lifeline 258 -checkpoint 15 -np 31 Edit: talking to someone with more F@H experience, this seems like a dud WU. Will re-install the container.
  16. Thanks Squid. I have 96 cores running this dang thing, didn't want to miss the boat
  17. Anyone know how to force this to fold for covid-19? I have updated the container and no go...
  18. Thanks for checking that. You can see which driver your NICs have under Settings > Network Settings > Interface rules. The driver name is in parentheses. I am wondering if there are variants (or older/incompatible versions) of the driver on Unraid in use that don't play nice with a Centos VM. Narrowing down the problem in lieu of any advice from the Unraid developers might take a few shots. For the record, I don't think it's a problem with Unraid 6.8.2 or Centos, as it works flawlessly for me, without needing to pass through the PCI device - simply setting the VM to use br0 works. Would be great to solve this problem as it must be affecting a few people.
  19. The driver I'm referring to is on the unraid host system, nothing to do with the VM. My theory based on comparing a working and non-working system was due to a difference in broadcom drivers seen in Unraid OS itself. I also suggested some XML edits you were asking about to try, did they have any effect?
  20. Hi @eds I have just had a look at this issue. The XML for my test Centos 8 VM I just fired up (on Unraid 6.8.1)... <interface type='bridge'> <mac address='52:54:00:e0:a3:3c'/> <source bridge='br0'/> <target dev='vnet1'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> That is the default, generated by Unraid on my behalf (I selected br0 is my NIC to pass to the VM, as per usual). As itimpi said, there are a variety of NIC models you can use in kvm/qemu.. I have tested the following as working: - e1000, virtio, vmxnet3 You just edit the model type='X' parameter above. In my experience, e1000 has the best compatibility, vmxnet3 has the best performance (ony matters 10G and above, again, in my experience). Are you able to try making that change and see how it goes? Edit - note, it's worth mentioning my server is a Dell R730, using 1G broadcom based NICs. I am using the tg3 driver (as seen under settings>network settings> interface rules). It might be worth checking which driver you have. I know a chap with bnx2 drivers and he has trouble with Centos VMs too... Upgrading the variant of driver your NIC uses might be a solution in itself.
  21. You beaut, that seems to have solved it. Thanks very much.
  22. I just changed it to point at /mnt/disk1, and Docker is all go again. Should I just wipe the cache out and re-add it, copy the stuff from /mnt/disk1 back to the cache? The logic here is I did set it to /mnt/cache and still didn't work.
  23. OK - I thought they were on the cache... I'm still not sure why anything changed though, was all working before I fixed the xfs. I'll give it a shot moving to /mnt/disk1 and see..
  24. For example: root@unraid-2:~# find /mnt -name docker.img /mnt/user/system/docker/docker.img /mnt/user0/system/docker/docker.img /mnt/cache/system/docker/docker.img /mnt/disk1/system/docker/docker.img With this in mind I went to the Docker settings, changed the location of appdata and docker.img to the 'cache' variant, but no dice - still no containers showing up when re-enabling Docker. Do I need to do some other reconfig? Thanks again
  25. Cool - and thanks for the quick reply - but just to clarify - what am I looking for a duplicate copy of? I can see for example that there is a copy of docker.img on both the /mnt/cache and /mnt/user, but to be fair I am quite in the dark when it comes to the innards of Unraid