paaland

Members
  • Posts

    13
  • Joined

  • Days Won

    1

Everything posted by paaland

  1. It should also be possible to disable password authentication via SSH and only rely on SSH keys since that's tied to the web login (same username & password on both).
  2. I've been using the system temperatures plugin for some time with success. Yesterday I shut down my system to install a Nvidia Quadro P400 to use for HW transcoding. Boot the device back up (did not check if the temp plugin worked at this time), installed Nvidia Drivers, rebooted again. Now the Nvidia drivers are working, HW transcoding is working, but the only temp sensor the plugin detects are the NVME SSD. The CPU and mobo temp sensors I used to have are "gone". System is an AMD Ryzen 5 5600G CPU on a Asus TUF GAMING B550-PRO motherboard. Don't know if it has anything to do with the P400 or not, but that was the only change I did from working to not-working. This is what I find in the log: Sep 29 07:21:52 nasse root: +============================================================================== Sep 29 07:21:52 nasse root: | Installing new package /boot/config/plugins/dynamix.system.temp/dynamix.system.temp.txz Sep 29 07:21:52 nasse root: +============================================================================== Sep 29 07:21:52 nasse root: Sep 29 07:21:52 nasse root: Verifying package dynamix.system.temp.txz. Sep 29 07:21:52 nasse root: Installing package dynamix.system.temp.txz: Sep 29 07:21:52 nasse root: PACKAGE DESCRIPTION: Sep 29 07:21:52 nasse root: Package dynamix.system.temp.txz installed. Sep 29 07:21:52 nasse root: plugin: skipping: sensors-detect - Unraid version too high, requires at most version 6.7.2 Sep 29 07:21:52 nasse root: plugin: skipping: sensors-detect - Unraid version too high, requires at most version 6.7.2 Sep 29 07:21:52 nasse root: plugin: running: anonymous Sep 29 07:21:52 nasse kernel: nct6775: Found NCT6798D or compatible chip at 0x2e:0x290 Sep 29 07:21:52 nasse kernel: ACPI Warning: SystemIO range 0x0000000000000295-0x0000000000000296 conflicts with OpRegion 0x0000000000000290-0x0000000000000299 (\AMW0.SHWM) (20210331/utaddress-204) Sep 29 07:21:52 nasse kernel: ACPI: OSL: Resource conflict; ACPI support missing from driver? Sep 29 07:21:52 nasse root: Sep 29 07:21:52 nasse root: ----------------------------------------------------------- Sep 29 07:21:52 nasse root: Plugin dynamix.system.temp is installed. Sep 29 07:21:52 nasse root: This plugin requires Dynamix webGui to operate Sep 29 07:21:52 nasse root: Copyright 2021, Bergware International Sep 29 07:21:52 nasse root: Version: 2021.06.25 Sep 29 07:21:52 nasse root: ----------------------------------------------------------- Sep 29 07:21:52 nasse root: Sep 29 07:21:52 nasse root: plugin: dynamix.system.temp.plg installed Sep 29 07:21:52 nasse root: plugin: installing: /boot/config/plugins/dynamix.unraid.net.plg Sep 29 07:21:52 nasse root: plugin: running: anonymous Sep 29 07:21:52 nasse root: plugin: running: anonymous Sep 29 07:21:52 nasse root: plugin: running: anonymous Sep 29 07:21:52 nasse root: Downloading and installing API. Please wait… Sep 29 07:21:52 nasse root: plugin: skipping: /boot/config/plugins/dynamix.my.servers/dynamix.unraid.net.txz already exists Sep 29 07:21:52 nasse root: plugin: running: /boot/config/plugins/dynamix.my.servers/dynamix.unraid.net.txz Sep 29 07:21:52 nasse root:
  3. I've been using the system temperatures plugin for some time with success. Yesterday I shut down my system to install a Nvidia Quadro P400 to use for HW transcoding. Boot the device back up (did not check if the temp plugin worked at this time), install Nvidia Drivers, reboot. Now the Nvidia drivers are working, HW transcoding is working, but the only temp sensor the plugin detects are the NVME SSD. The CPU and mobo temp sensors are "gone". System is an AMD Ryzen 5 5600G CPU on a Asus TUF GAMING B550-PRO motherboard. Don't know if it has anything to do with the P400 or not, but that was the only change I did from working to not-working.
  4. I don't think that's possible. Only one of them can use it at any given time. That said, I too have an AMD APU (Ryzen 5 5600G). I've given up getting hardware transcoding in Plex, but Jellyfin should work, right? Problem is that all I get is errors if I try to use hardware transcoding. I'm running Unraid 6.10.0-rc1 with the AMDGPU drivers installed. I tried with the "Jellyfin AMD Intel Nvidia" docker image. What are you doing?
  5. Influx recently released v2. It's not directly compatible with the storage format used in v1.x. So if you use influxdb:latest as the docker image tag you would inadvertedly upgrade to v2.0. So change the tag to influxdb:1.8 to get latest v1.x. If you really want to upgrade to v2.0 you'll need to run a script to convert your database to v2 format. Read about that on InfluxDB's web site.
  6. You can run docker-compose via docker. Put this in your /boot/config/go file to create an alias docker-compose that downloads docker-compose and run it in docker. The benefit is that it's always running the latest version, so you don't even need to update it. alias docker-compose="docker run --rm \ -v /var/run/docker.sock:/var/run/docker.sock \ -v '$PWD:$PWD' \ -w='$PWD' \ docker/compose:latest"
  7. Immediately turn off you Windows 10 VM. If you really need to turn it on I'd remove it's network interface from the VM manager first. That way it cannot be reached, nor can it infect the rest of your network. Copy anything you really need to USB medium, take care not to copy anything that could be infected with anything. Then delete the VM. You also need to carefully examine and scan for virus any other computer on your network. Also scan the unraid server from a shell run: docker run --name ClamAV -v /mnt/user:/scan:ro tquinnelly/clamav-alpine -i This will download ClamAV, update it and run a full scan of everything in /mnt/user. You might want to scan /boot as well afterwards. As for security you should never expose neither Unraid or an VM to the internet directly. Never ever use DMZ. If you really need to expose a web service use a reverse proxy and setup port forwarding of single ports. Reverse proxies often have the option to protect against a lot of hacking attempts. Since a hacker managed to get into your Windows VM you either have exposed the whole thing, or you have exposed some unsecured or poorly protected service.
  8. After some more investigation it seems one of my SSD's in the cache pool has died. Tried btrfs scrub and there were a gazillion uncorrectable errors (no correctable ones). So I assume unraid was just serving from on of the SSD's. SMART status even failed to run on the disk. Should not unraid give me some warning about one of the SSD's in a pool having died?
  9. Seems sdg is the cache pool. It's mounted as: /dev/sdg1 on /mnt/cache type btrfs (rw,noatime,space_cache=v2,discard=async) I'll look into posting the diagnostics....
  10. [ 387.065682] sd 12:0:0:0: [sdg] tag#10 access beyond end of device [ 387.065694] sd 12:0:0:0: [sdg] tag#11 access beyond end of device [ 387.065700] sd 12:0:0:0: [sdg] tag#12 access beyond end of device [ 387.065708] sd 12:0:0:0: [sdg] tag#13 access beyond end of device [ 387.065724] sd 12:0:0:0: [sdg] tag#14 access beyond end of device [ 387.065730] sd 12:0:0:0: [sdg] tag#15 access beyond end of device [ 387.065735] sd 12:0:0:0: [sdg] tag#16 access beyond end of device [ 387.065755] sd 12:0:0:0: [sdg] tag#1 access beyond end of device [ 387.065764] sd 12:0:0:0: [sdg] tag#2 access beyond end of device After a reboot my log is filled to 100% in just a few minutes. The log is full of the message above. Except some boot issues where the server hangs on boot in about 50% of the attempts, it's up and running with no apparent ill effect. Running 6.9.2 on a homebuilt server. I have four disks (sda-sdd) and two SSDs (sde & sdf). Is sdg is a reference to a disk, I don't know what that is.
  11. I stopped the array and reformatted the cache, then did a new restore, this time linked files worked. So it must have been some issue with restoring on top of existing files or something like that.
  12. Needed my first backup today since one of my SSD's on my cache pool died. Apparently it does not backup symbolic links properly. All my linked files were restored as a 0 bytes large normal file. Big problem
  13. New to unRAID, but have used other NAS software like Qnap before. I have two data disks, one parity disk and a cache SSD. I've tried reading the FAQ, but I'm still not getting it. Of my shares, only isos and my home folder share is marked green and protected. These have use cache set to "yes" which I understand means that writes happens to the cache first, then the mover process moves them to the array when it runs. Other shares like appdata (docker), domains (vms) and system are marked "unprotected". These have also use cache set to "yes". Is the mover not able to move files if in use? Do I need to shut down containers and vms to move them? If so, what's really the point of the cache? What happens when the cache disk is full? Some kind of LRU or FIFO or will I start getting write errors?