zer0zer0

I just wanted to say thank you and also add my script so maybe someone can find it when they're searching for fan control for the Asustor AS5402T 😎 I added more temps and speeds as 90 was really high for the fans pwm speeds and had the fan spinning at 1912 rpm. I changed the ARRAY_FAN to match the correct pwm path #!/bin/bash TEMPS=(0 55 60 65 70 75 80) SPEEDS=(45 60 75 90 130 170 255) # Fan device. Depends on your system. pwmconfig can help with finding this out. # pwm1 is usually the cpu fan. You can "cat /sys/class/hwmon/hwmon0/device/fan1_input" # or fan2_input and so on to see the current rpm of the fan. If 0 then fan is off or # there is no fan connected or motherboard can't read rpm of fan. ARRAY_FAN=/sys/devices/platform/asustor_it87.2608/hwmon/hwmon1/pwm1 #REPLACE HD TEMP WITH CPU TEMP FROM SENSORS HIGHEST_TEMP=$(/usr/bin/sensors | grep "CPU Temp" | cut -d"+" -f2 | cut -c1-2) for i in ${!TEMPS[@]}; do CHECKTEMP=${TEMPS[$i]} #echo "loop " $i $CHECKTEMP if [ "$HIGHEST_TEMP" -le "$CHECKTEMP" ]; then break fi LASTTEMP=${TEMPS[$i]} FANSET=${SPEEDS[$i]} done echo "Temp " $HIGHEST_TEMP " >= " $LASTTEMP "Setting fan to " $FANSET echo $FANSET > $ARRAY_FAN

I'm excited to see this container, but it doesn't want to come up on my server Just gets stuck at 12/11/202311:31:59 AM API: Starting... 12/11/202311:32:00 AM PROXY: Starting...

So, it won't rebuild from parity? That data is only recoverable using testdisk or similar?

Hmm, all of the other disks also start at 8? Device Start End Sectors Size Type /dev/sdb1 8 2441609210 2441609203 9.1T Linux filesystem /dev/sdc1 8 2441609210 2441609203 9.1T Linux filesystem /dev/sdd1 8 2441609210 2441609203 9.1T Linux filesystem /dev/sde1 8 2441609210 2441609203 9.1T Linux filesystem /dev/sdf1 8 2441609210 2441609203 9.1T Linux filesystem

It was definitely formatted with xfs and then all of a sudden just threw that error root@DARKSTOR:~# fdisk -l /dev/sde Disk /dev/sde: 9.1 TiB, 10000831348736 bytes, 2441609216 sectors Disk model: HUH721010AL4204 Units: sectors of 1 * 4096 = 4096 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 14CEF3CF-1F72-48D2-8C97-83C61932AE02 Device Start End Sectors Size Type /dev/sde1 8 2441609210 2441609203 9.1T Linux filesystem

Same result unfortunately Sorry, could not find valid secondary super block

It’s going to take a while 😃 why /dev/md4p1 and not /dev/sde?

All of a sudden one of my disks gave me the dreaded error of unmountable, no supported file system Disk 4 - HUH721010AL4204_7PH0NGHC (sde) Check xfs filesystem is totally missing from the gui for this disk, but there for all the other array disks? Running a check from the CLI comes back with could not find a valid secondary superblock Where do I go from here apart from just replacing the drive? Diagnostics zip attached darkstor-diagnostics-20230810-2128.zip

While I'm waiting I flashed the latest firmware and the drive is now reporting no smart issues, passes the tests and is ripping at 220-250MB/sec. Very weird, but I'll take it while I wait for a replacement to arrive. Haha

As far as I can tell all of the drives are operating as expected and all connections are fine. It might start our at ~28MB/sec and then it will drop under 10 🙃 I do get a weird result for smart test on the parity drive - Background short Failed in segment --> 3 But it reports are healthy at the same time? Diagnostics file attached Diskspeed tests are also good when benchmarking the drives But, as you can see here the parity drive is only being written really slowly unraid-diagnostics-20230522-1659.zip

I'm not sure what's up, but I'm on 6.10.0-rc8 and I'm not seeing it no matter what I search for in community apps (version 2022.05.15) Searching for "docker folder" comes up with totally irrelevant results and searching for your repo only shows your other awesome work!!

Hmm, apt installing python3 and then running those whitelist scripts works perfectly for me... sudo apt update sudo apt install python3

I made things as simple as possible and I'm just using /torrents as my path mapping, so I don't think that's the issue. Yes the file gets downloaded and I can see it sitting in the /torrents directory and it starts seeding I've also run DockerSafeNewPerms a few times, but that hasn't changed anything. I can get around it by using nzbToMedia scripts for the time being, but it's weird I can't get it working natively

Anyone else having issues getting torrents to complete with Sonarr? I have paths mapped properly, and have tried qbittorrent, rtorrent, deluge, etc. without any luck Sonarr sends torrents perfectly, and the torrent clients download them perfectly Then the completion just doesn't happen and there's no logs

Are you sure you’re forcing it to transcode? can you see the nvidia card if you run nvidia-smi from inside the docker terminal?

I've seen times when nvidia-smi doesn't show anything but it is actually transcoding. You should be sure you are forcing a transcode and then check in your Plex dashboard for the (hw) text like this...

binhex plexpass container is working well for me

I talked to @StevenD and dropped back to UnRAID version 6.9.0-beta35 like he's running, and this issue is resolved

To follow up on my issues, I can boot if I choose just one cpu, so it's probably not an issue with this plugin specifically. It is more likely to be UnRAID itself. If I set one cpu and also hypervisor.cpuid.v0 = FALSE in the vmx file I can get it to boot and the plugin appears to be working as expected. @ich777- if you can think of any logs etc. to get this resolved let me know

That's weird that yours is working and mine isn't. I also just tested that it works as expected with a plain Ubuntu 20.10 instance with hypervisor.cpuid.v0 = FALSE set. No problems at all. Mine was working great with linuxserver.io nvidia builds. So it’s definitely not a hardware or esxi issue. I have the following setup: ESXi 6.7 with the latest patches UnRAID 6.9.0-rc2 Nvidia Quadro P400 Passing through both the nvidia card and audio device. Other passed through devices like sas hba, and nvme drives work perfectly. Without any flags in the vex file I can boot the UnRAID virtual machine and can see the Nvidia card root@XXXX:~# lspci | grep NV 03:00.0 VGA compatible controller: NVIDIA Corporation GP107GL [Quadro P400] (rev a1) 03:00.1 Audio device: NVIDIA Corporation GP107GL High Definition Audio Controller (rev a1) But anything else has errors like root@XXXX:~# nvidia-smi Unable to determine the device handle for GPU 0000:03:00.0: Unknown Error Nvidia Driver Settings page gives me this error If I add the hypervisor.cpuid.v0 = FALSE variable to the vmx file it freezes after bzroot and won't boot

Just wanted to let you know that the ESXi logo is a bit messed up

Tried all of the different advanced variables, without any luck, so I gave up and did a bare metal UnRAID with a nested ESXi instead

Anyone have any luck getting this working with an UnRAID host running on ESXi 7 with pass through? Mine either freezes at boot time, or if I change some advanced variables around I can get it to boot, but get a message on the plugin page saying "unable to determine the device handle" I have tried the normal advanced settings you need for ESXi and nvidia passthrough like setting hypervisor.cpuid.v0 = “FALSE” and pciHole.start = “2048” but I'm not having much luck so far

Did iSCSI make it into the new 6.9 beta release, or will it hopefully make it's way into the RC?

So...I have Unraid running under ESXi 7.0 as well, but can't do PCI passthrough and also have Hardware Virtualization enabled so I can use VM Manager. If I try and enable it I get an error - "Failed - PCI passthrough devices cannot be added when Nested Hardware-Assisted Virtualization is enabled." Is there a hack to get this to work? Or has it always been the case that you can only choose one of the other?