deaerator

I have a Daily DVR Section on my plex server. It records the OTA Daily TV shows but they way plex is setup it keeps shows until its watched and then deleted. I don't know how to script but looking for someone to create a script. I want this to run at midnight and I wanted to delete all video files older than 24hours or have it flagged as watched and plex will delete automatically.

I'm having the same issue with my P2000 and the stuttering problem is with every file I play. Curious on how to fix also?

This script works fine and yes you have to do this every time you update the container.

With the new Unraid-Nvidia Plugin for leveraging GPU Acceleration, Currently I want to use it on Emby since it can Decode/Encode out of the box with the latest FFMPEG. But I am having trouble with playback. Every 5-7 seconds the it will stop playback for milliseonds making it real annoying. How do I troubleshoot this. Emby Logs attached. Log.txt Transcoder log.txt

I manually typed it this: --runtime=nvidia And now it works. I appreciate the hard work that went into this plugin also. Thank you

Having some trouble getting this to work with my Plex Media Server. Unraid version 6.6.6 This is my docker cmd root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='plex' --net='host' --cpuset-cpus='2,3,4,5,6,7,8,9,10,11,12,13,14,15,18,19,20,21,22,23,24,25,26,27,28,29,30,31' -e TZ="America/Halifax" -e HOST_OS="Unraid" -e 'PUID'='99' -e 'PGID'='100' -e 'VERSION'='latest' -e 'NVIDIA_DRIVER_CAPABILITIES'='all' -e 'NVIDIA_VISIBLE_DEVICES'='GPU-386029cb-55e6-6dca-a528-b1eaf7fdc74f' -v '/mnt/user/media/':'/media':'rw' -v '/dev/shm/':'/transcode':'rw' -v '/mnt/user/appdata/plex':'/config':'rw,slave' --runtime=nvidia 'linuxserver/plex' /usr/bin/docker: Error response from daemon: Unknown runtime specified nvidia. See '/usr/bin/docker run --help'. The command failed. When I removed --runtime=nvidia My docker will startup no problem but no nvidia support. This works with my Emby Docker but the Plex Media Server tower-diagnostics-20190210-0059.zip

I was having the same problems and the Asrock Tech asked to send in the motherboard and they investigated and try to replicate the problem. After they witnessed same problem; their solution was to send me a new Motherboard since it was still under warranty. Good news is the new Motherboard isn’t showing any temp spikes or CPU De-assertions. Everything is working normally for now. Fingers crossed Sent from my iPhone using Tapatalk

It would be nice if it was a plug in that you can update.

I started seeing this error in my log Unraid log regarding Plex Docker Jan 26 00:44:48 Tower kernel: Plex DLNA Serve[27299]: segfault at 14cd41f29d89 ip 000014ccfae7242c sp 000014ccf97fd700 error 4 in libjemalloc.so.1[14ccfadd7000+133000] Log is attached tower-diagnostics-20190126-0321.zip

I recently added a WD Elements Shucked drive and have a temp replacement SSD for my cache drive. I noticed my log starting to show this. Jan 11 12:27:23 Tower kernel: ata3.00: exception Emask 0x0 SAct 0xffffffff SErr 0x0 action 0x6 frozen Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/30:00:d8:53:19/05:00:59:00:00/40 tag 0 ncq dma 679936 out Jan 11 12:27:23 Tower kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/48:08:08:59:19/05:00:59:00:00/40 tag 1 ncq dma 692224 out Jan 11 12:27:23 Tower kernel: res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: READ FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 60/00:10:60:b7:fa/01:00:02:00:00/40 tag 2 ncq dma 131072 in Jan 11 12:27:23 Tower kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/40:18:50:5e:19/05:00:59:00:00/40 tag 3 ncq dma 688128 out Jan 11 12:27:23 Tower kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/40:20:90:63:19/05:00:59:00:00/40 tag 4 ncq dma 688128 out Jan 11 12:27:23 Tower kernel: res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/38:28:d0:68:19/00:00:59:00:00/40 tag 5 ncq dma 28672 out Jan 11 12:27:23 Tower kernel: res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/48:30:08:69:19/05:00:59:00:00/40 tag 6 ncq dma 692224 out Jan 11 12:27:23 Tower kernel: res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/40:38:50:6e:19/05:00:59:00:00/40 tag 7 ncq dma 688128 out Jan 11 12:27:23 Tower kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/40:40:90:73:19/05:00:59:00:00/40 tag 8 ncq dma 688128 out Jan 11 12:27:23 Tower kernel: res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/38:48:d0:78:19/00:00:59:00:00/40 tag 9 ncq dma 28672 out Jan 11 12:27:23 Tower kernel: res 40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/68:50:78:7e:19/05:00:59:00:00/40 tag 10 ncq dma 708608 out Jan 11 12:27:23 Tower kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/28:58:e0:83:19/05:00:59:00:00/40 tag 11 ncq dma 675840 out Jan 11 12:27:23 Tower kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/58:60:08:89:19/05:00:59:00:00/40 tag 12 ncq dma 700416 out Jan 11 12:27:23 Tower kernel: res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/c0:68:60:8e:19/06:00:59:00:00/40 tag 13 ncq dma 884736 out Jan 11 12:27:23 Tower kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/e8:70:20:95:19/03:00:59:00:00/40 tag 14 ncq dma 512000 out Jan 11 12:27:23 Tower kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/40:78:08:99:19/05:00:59:00:00/40 tag 15 ncq dma 688128 out Jan 11 12:27:23 Tower kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/60:80:48:9e:19/05:00:59:00:00/40 tag 16 ncq dma 704512 out Jan 11 12:27:23 Tower kernel: res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/58:88:a8:a3:19/05:00:59:00:00/40 tag 17 ncq dma 700416 out Jan 11 12:27:23 Tower kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: READ FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 60/00:90:60:b8:fa/01:00:02:00:00/40 tag 18 ncq dma 131072 in Jan 11 12:27:23 Tower kernel: res 40/00:00:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: READ FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 60/08:98:68:60:5a/00:00:01:00:00/40 tag 19 ncq dma 4096 in Jan 11 12:27:23 Tower kernel: res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/08:a0:70:64:fd/00:00:3b:00:00/40 tag 20 ncq dma 4096 out Jan 11 12:27:23 Tower kernel: res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/40:a8:08:29:19/05:00:59:00:00/40 tag 21 ncq dma 688128 out Jan 11 12:27:23 Tower kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/40:b0:48:2e:19/05:00:59:00:00/40 tag 22 ncq dma 688128 out Jan 11 12:27:23 Tower kernel: res 40/00:b4:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/40:b8:88:33:19/05:00:59:00:00/40 tag 23 ncq dma 688128 out Jan 11 12:27:23 Tower kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/40:c0:c8:38:19/00:00:59:00:00/40 tag 24 ncq dma 32768 out Jan 11 12:27:23 Tower kernel: res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/78:c8:08:39:19/05:00:59:00:00/40 tag 25 ncq dma 716800 out Jan 11 12:27:23 Tower kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/40:d0:80:3e:19/05:00:59:00:00/40 tag 26 ncq dma 688128 out Jan 11 12:27:23 Tower kernel: res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/48:d8:c0:43:19/05:00:59:00:00/40 tag 27 ncq dma 692224 out Jan 11 12:27:23 Tower kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/80:e0:08:49:19/05:00:59:00:00/40 tag 28 ncq dma 720896 out Jan 11 12:27:23 Tower kernel: res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/50:e8:88:4e:19/05:00:59:00:00/40 tag 29 ncq dma 696320 out Jan 11 12:27:23 Tower kernel: res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: READ FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 60/00:f0:88:c1:ad/03:00:1e:00:00/40 tag 30 ncq dma 393216 in Jan 11 12:27:23 Tower kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/70:f8:08:79:19/05:00:59:00:00/40 tag 31 ncq dma 712704 out Jan 11 12:27:23 Tower kernel: res 40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3: hard resetting link Jan 11 12:27:23 Tower kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jan 11 12:27:23 Tower kernel: ata3.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded Jan 11 12:27:23 Tower kernel: ata3.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Jan 11 12:27:23 Tower kernel: ata3.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Jan 11 12:27:23 Tower kernel: ata3.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded Jan 11 12:27:23 Tower kernel: ata3.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Jan 11 12:27:23 Tower kernel: ata3.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Jan 11 12:27:23 Tower kernel: ata3.00: configured for UDMA/133 Jan 11 12:27:23 Tower kernel: ata3.00: device reported invalid CHS sector 0 Jan 11 12:27:23 Tower kernel: ata3.00: device reported invalid CHS sector 0 Jan 11 12:27:23 Tower kernel: ata3.00: device reported invalid CHS sector 0 Jan 11 12:27:23 Tower kernel: ata3.00: device reported invalid CHS sector 0 Jan 11 12:27:23 Tower kernel: ata3.00: device reported invalid CHS sector 0 Jan 11 12:27:23 Tower kernel: ata3.00: device reported invalid CHS sector 0 Jan 11 12:27:23 Tower kernel: ata3.00: device reported invalid CHS sector 0 Jan 11 12:27:23 Tower kernel: ata3.00: device reported invalid CHS sector 0 Jan 11 12:27:23 Tower kernel: ata3: EH complete Diagnostics is attached. Curious what is causing this? And is it serious? tower-diagnostics-20190111-1346.zip

Having trouble with this Plex Docker staying alive. I find myself restarting this every few hours. I see this populating in the log all the time. I attached diagnostics. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. tower-diagnostics-20181221-2041.zip

How do I testdisk?

I reverted to another HBA card to see if I can get my original array. How do I troubleshoot to get it back. tower-diagnostics-20181120-0945.zip

I thought there was a IT Mode but I was wrong. Thanks for the insight. There is an HBA mode but it still didn't pass the drives to the host OS.

Curious if anyone has experience with this card and what do you have for settings. I can't seem to get the drives to passthrough the controller. The controller itself seems to have renamed my drives and it can no longer start. How do I find the proper drive order.