Thanks for the replies.
Here’s a bit of history and series of events to this system
it was previously on Ubuntu 19.10 (desktop) on a completely different PC
i move the boot drive to this a new the M93p without reinstalling. it booted fine, everything works.
upgraded to 20.04 LTS (desktop), upgraded successfully. Plex works, full-featured.
as Plex update released, I updated via CLI… then Plex transcode stopped working. The rest of the system worked fine. (UniFi Controller and UniFi Video)
As recommended by a few Ubuntu savvy friends, it was unfavorable to update from a non-LTS to an LTS, I was then told to do a fresh install and stick with LTS from now on.
since I wasn’t using the “desktop” very much, I opted to install the “server”.
installed UnFi stuff, then Plex. Plex works. HW transcoding works.
[ 0.787709] Console: switching to colour dummy device 80x25
[ 0.787744] i915 0000:00:02.0: vgaarb: deactivate vga console
[ 0.792227] usb 1-1: new high-speed USB device number 2 using ehci-pci
[ 0.796241] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 0.796244] [drm] Driver supports precise vblank timestamp query.
[ 0.800279] i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
[ 0.811454] [drm] Initialized i915 1.6.0 20190822 for 0000:00:02.0 on minor 0
[ 0.813503] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no)
[ 0.813725] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input2
I’m still unsure what went wrong. I can only say that either Plex update has borked things, or the latest kernal update borked things…or both.
Well I might be mistaken, but I learned you always need to reinstall OS if you switch fundamental hardware like the motherboard and/or processor because the system needs to properly recognise it and install the appropriate drivers etc.
That is true for windows.
for my minor knowledge of linux (or the lack of), Linux isn’t too much of an issue with major hardware changes. hard drive locations is device ID based. not port based. you can unplug cable and put it in another port, Linux will find it no problem and boot as that physical change never happened.
Same with the dangerous RAID-0 arrays, swapping cables back and forth didn’t seem to break it either…
BSD on the other hand (pfsense), failed to boot.
All these hardware changes for me is a roulette. the M93p is the newest of 2 boxes. the oldest/slowest became pfsense. This cycle will repeat if i find some i7 USFF tiny form factor.
Then this M93P will become the new pfsense box
yes, I shouldn’t have just throw the old boot drive to the new box…but it booted as if i didn’t swap hardware. Mounted/mapped all the drives, UniFi controller worked, UniFi Video found all my cameras and started recording. Plex found all the media libraries (mounted remotely on an NAS)
Next, is when plex was upgraded, HW encoding was nowhere to be seen. I didn’t notice this until i had 4 HEVC streams going and it started to buffer. This was a rare sight to see as my NAS (Terra-Master F2-421) can do better than that…
Transcoding temp files remotely seems to work, i see files get created, in segments, then gets deleted soon after its been played. I do this as there’ a single SSD in the box. everything is beings transmitted to the NAS. Less wear n’ tear on the SSD.
The setup: M93p has 2 NIC bonded together. The NAS has 4xNIC bonded together. Transmission of data between these 2 units has a least a 2gb pipe.
I have two Plex servers. One on the NAS, One on the M93p. both point to the same library located on the NAS drives. I have about 30 families/close friends on various devices watching media on my servers. Since i personally know all their devices they will be using, I manually load-balance them on my end… 1/2 the users on Plex-1, the other half on Plex-2 (usualliy the lower end devices that most likely would require transcoding)
My plans for the M93p was so that I can have a testbed NVR to handle more than upcoming 20 cameras install. Plex is “for CPU idle-cycles” perk… for fun.
I am no Linux expert either, but still in my opinion you still have proof that re-using your boot drive may work, but not necessarily. Most of your system seem to work with now issues, but the hardware recognition didn’t. Lesson learned, it can go well, but you might run into problems.
That is why it is good practice to reinstall the OS with every major hardware change.
What was the old pc (cpu & motherboard)? If you went from a newer processor to an older (haswell) then the bios will certainly be a factor.
Having re-read all the thread.
I have a Haswell system and loaded Ubuntu 20.04 LTS server with no desktop. The HW transcoding didn’t work. I didn’t dig too deeply, the /dev/dri, group and the drivers were there. Rather than waste time, I just reloaded with Debian 10.
I have a similar problem. I am using an RPi4 with ext4 booted SSD with an NTFS drive linked to /var/lib/plexmediaserver/Library -> /mnt/EXP/Library and /var/lib/plexmediaserver/Media -> /mnt/EXP/Media.
Some codecs files would not work so I made the /mnt/EXP/Library filesystem type ext4. I do not know how to get plex to install the codecs again into /var/lib/plexmediaserver/Library/Application\ Support/Plex\ Media\ Server/Codecs/.
I get these warnings: Preformatted textJun 14, 2020 23:44:47.860 [0xb6f04c80] WARN - [FFMPEG] - Error loading external lib: /var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Codecs/99c90e0-3095-linux-armv7hf_neon/libac3_decoder.so: failed to map segment from shared object
Jun 14, 2020 23:44:47.869 [0xb6f04c80] WARN - [FFMPEG] - Error loading external lib: /var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Codecs/99c90e0-3095-linux-armv7hf_neon/libhevc_decoder.so: failed to map segment from shared object
Jun 14, 2020 23:44:47.876 [0xb6f04c80] WARN - [FFMPEG] - Error loading external lib: /var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Codecs/99c90e0-3095-linux-armv7hf_neon/liblibx264_encoder.so: failed to map segment from shared object
Jun 14, 2020 23:44:47.877 [0xb6f04c80] WARN - [FFMPEG] - Error loading external lib: /var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Codecs/99c90e0-3095-linux-armv7hf_neon/libaac_encoder.so: failed to map segment from shared object
Jun 14, 2020 23:44:47.885 [0xb6f04c80] WARN - [FFMPEG] - Error loading external lib: /var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Codecs/99c90e0-3095-linux-armv7hf_neon/libh264_decoder.so: failed to map segment from shared object
Jun 14, 2020 23:44:47.893 [0xb6f04c80] WARN - [FFMPEG] - Error loading external lib: /var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Codecs/99c90e0-3095-linux-armv7hf_neon/libaac_lc_decoder.so: failed to map segment from shared object Preformatted text
if unable to load .so files, make 100% certain the partition / drive is mounted with the exec option.
Seeing “WARN” implies DEBUG logging (default) has been turned off (which doesn’t save any space as log sizes are fixed).
Logs of the entire sequence are helpful here. It’s very difficult to properly diagnose in isolation. DEBUG logs ZIP, not VERBOSE.
Be advised: There is no hardware transcoding support on ARMv8 processors at this time.
