[[Support] HaveAGitGat - Tdarr: Audio/Video Library Analytics & Transcode Automation]

UPDATE: tdarr 2.00.14 is confirmed broken. Do not upgrade to this version until a fix is available!

[[Support] HaveAGitGat - Tdarr: Audio/Video Library Analytics & Transcode Automation]

37 minutes ago, NeoDude said:

Getting variations of this error on just about every transcode today. Has been previously working without issue, any ideas?

 

DURATION : 02:04:06.720000000

[h264_cuvid @ 0x5651f381a580]

Cannot load libnvcuvid.so.1

[h264_cuvid @ 0x5651f381a580]

Failed loading nvcuvid.

Stream mapping:

Stream #0:0 -> #0:0

(h264 (h264_cuvid) -> hevc (hevc_nvenc))

Stream #0:1 -> #0:1 (copy)

Stream #0:2 -> #0:2 (copy)

Stream #0:3 -> #0:3 (copy)

Stream #0:4 -> #0:4 (copy)

Stream #0:5 -> #0:5 (copy)

Error while opening decoder for input stream #0:0 : Operation not permitted

 

 

I'm having same issue. Seems like there was an update to Tdarr docker yesterday which has broken it. I'm posting an issue on Github now.

[[Support] Linuxserver.io - openssh-server]

I am trying to use this docker to set up a reverse SSH tunnel so I can access remote hosts that are behind NAT. But no matter what I always get this error and the tunnel is not created:

 

pi@piaware:~ $ ssh -i ~/.ssh/my_key -R 10022:localhost:2222 [email protected] -p 2222
Warning: remote port forwarding failed for listen port 10022
Welcome to OpenSSH Server

758869fae143:~$

 

I tested creating a reverse SSH tunnel to a normal Ubuntu host and it worked fine. Where I am I going wrong with the docker?

[[Plugin] Spin Down SAS Drives]

Definitely no I/O. No difference in the output when running the other commands either

[[Plugin] Spin Down SAS Drives]

13 hours ago, doron said:

Thanks for reporting, @absolute_badger.

Might be that this drive / controller combo ignores the spindown command.

 

Right after you spin down, say, /dev/sde, and get the "Spinning down" message from SAS Assist, can you issue, against the same device:

sdparm -C sense /dev/sde

and post the output?

 

 

Done:

 

Quote

root@heineken:~# sdparm -C sense /dev/sde
    /dev/sde: SEAGATE   ST33000650SS      0004

 

[[Plugin] Spin Down SAS Drives]

I have four Seagate ST33000650SS SAS drives in my array connected to LSI 9211-8i with latest IT firmware

 

Installed SAS spindown plugin

 

I click to spin down the drives, unraid shows them as spun down but they are definitely all still spinning (other SATA drives in my array spin down correctly)

 

Unraid logs:

 

Quote

Feb 21 05:48:48 heineken emhttpd: spinning down /dev/sde
Feb 21 05:48:48 heineken SAS Assist v0.85: Spinning down device /dev/sde
Feb 21 05:48:48 heineken emhttpd: spinning down /dev/sdk
Feb 21 05:48:48 heineken SAS Assist v0.85: Spinning down device /dev/sdk
Feb 21 05:48:48 heineken emhttpd: spinning down /dev/sdj
Feb 21 05:48:48 heineken SAS Assist v0.85: Spinning down device /dev/sdj
Feb 21 05:48:48 heineken emhttpd: spinning down /dev/sdi
Feb 21 05:48:48 heineken SAS Assist v0.85: Spinning down device /dev/sdi
Feb 21 05:48:48 heineken emhttpd: spinning down /dev/sdm

 

SAS util output:

 

Quote

SAS Spindown Utility (v20210201.01)

sde     | ST33000650SS  | 1000:0072:1000:3040   |  n/a  | 
sdi     | ST33000650SS  | 1000:0072:1000:3040   |  n/a  | 
sdj     | ST33000650SS  | 1000:0072:1000:3040   |  n/a  | 
sdk     | ST33000650SS  | 1000:0072:1000:3040   |  n/a  | 

 

/tmp/sas-util-out:

 

Quote

{
  "utility-run": {
    "date": "20210221-06:03 GMT",
    "version": "20210201.01",
    "Unraid version": "6.9.0-rc2",
    "message": "",
    "drives": [
      {
        "drive": {
          "model": "ST33000650SS",
          "sdparm-i": "/dev/sde: SEAGATE ST33000650SS 0004|Device identification VPD page:| Addressed logical unit:| designator type: NAA, code set: Binary| 0x5000c50055ce4473| Target port:| designator type: NAA, code set: Binary| transport: Serial Attached SCSI Protocol (SPL-4)| 0x5000c50055ce4471| designator type: Relative target port, code set: Binary| transport: Serial Attached SCSI Protocol (SPL-4)| Relative target port: 0x1| Target device that contains addressed lu:| designator type: NAA, code set: Binary| transport: Serial Attached SCSI Protocol (SPL-4)| 0x5000c50055ce4470| designator type: SCSI name string, code set: UTF-8| SCSI name string:| naa.5000C50055CE4470|RC=0",
          "controller-id": "1000:0072:1000:3040",
          "controller-slot": "02:00.2"
        }
      },
      {
        "drive": {
          "model": "ST33000650SS",
          "sdparm-i": "/dev/sdi: SEAGATE ST33000650SS 0004|Device identification VPD page:| Addressed logical unit:| designator type: NAA, code set: Binary| 0x5000c5005600b44b| Target port:| designator type: NAA, code set: Binary| transport: Serial Attached SCSI Protocol (SPL-4)| 0x5000c5005600b449| designator type: Relative target port, code set: Binary| transport: Serial Attached SCSI Protocol (SPL-4)| Relative target port: 0x1| Target device that contains addressed lu:| designator type: NAA, code set: Binary| transport: Serial Attached SCSI Protocol (SPL-4)| 0x5000c5005600b448| designator type: SCSI name string, code set: UTF-8| SCSI name string:| naa.5000C5005600B448|RC=0",
          "controller-id": "1000:0072:1000:3040",
          "controller-slot": "02:00.2"
        }
      },
      {
        "drive": {
          "model": "ST33000650SS",
          "sdparm-i": "/dev/sdj: SEAGATE ST33000650SS 0004|Device identification VPD page:| Addressed logical unit:| designator type: NAA, code set: Binary| 0x5000c50055ce340b| Target port:| designator type: NAA, code set: Binary| transport: Serial Attached SCSI Protocol (SPL-4)| 0x5000c50055ce3409| designator type: Relative target port, code set: Binary| transport: Serial Attached SCSI Protocol (SPL-4)| Relative target port: 0x1| Target device that contains addressed lu:| designator type: NAA, code set: Binary| transport: Serial Attached SCSI Protocol (SPL-4)| 0x5000c50055ce3408| designator type: SCSI name string, code set: UTF-8| SCSI name string:| naa.5000C50055CE3408|RC=0",
          "controller-id": "1000:0072:1000:3040",
          "controller-slot": "02:00.2"
        }
      },
      {
        "drive": {
          "model": "ST33000650SS",
          "sdparm-i": "/dev/sdk: SEAGATE ST33000650SS 0004|Device identification VPD page:| Addressed logical unit:| designator type: NAA, code set: Binary| 0x5000c50055ce28db| Target port:| designator type: NAA, code set: Binary| transport: Serial Attached SCSI Protocol (SPL-4)| 0x5000c50055ce28d9| designator type: Relative target port, code set: Binary| transport: Serial Attached SCSI Protocol (SPL-4)| Relative target port: 0x1| Target device that contains addressed lu:| designator type: NAA, code set: Binary| transport: Serial Attached SCSI Protocol (SPL-4)| 0x5000c50055ce28d8| designator type: SCSI name string, code set: UTF-8| SCSI name string:| naa.5000C50055CE28D8|RC=0",
          "controller-id": "1000:0072:1000:3040",
          "controller-slot": "02:00.2"
        }
      }
    ]
  }
}
{
  "controllers": [
    {
      "controller": {
        "Slot": "02:00.2",
        "Class": "PCI bridge [0604]",
        "Vendor": "Advanced Micro Devices, Inc. [AMD] [1022]",
        "Device": "400 Series Chipset PCIe Bridge [43c6]",
        "Rev": "01"
      }
    }
  ]
}

 

Is there anything else I can try?

[Spin down SAS drives]

Vote from me. Just built my new Unraid server to replace two old NAS boxes. 4x SAS drives and 4x SATA drives running on an LSI 9211-8i in IT mode. Unraid will spin down the SATA drives but not the SAS drives. Lots of unnecessary heat and power consumption with drives spinning away when they aren't in use 90% of the time!