• Posts

  • Joined

  • Last visited

  • Days Won


Meller last won the day on October 17 2020

Meller had the most liked content!

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Meller's Achievements


Apprentice (3/14)



  1. Why is it trying to use nvenc to encode? I don't have a GPU in my server. If I go to Settings > Video Encoding. I have the Video Codec set to HEVC and the Video Encoder to set to libx265. I've encoded nearly 25,000 tv show episodes so far, and this is the only one that fails over and over, with a huge log file attached to it.
  2. Hey I thought I'd ask again since no one answered before. I have this one file that keeps failing over and over and over. When I tried to view the details, it causes my browser to come to a complete stop. Lags it down really badly. Here's the log from it. No clue what any of this means. Thanks! unmanic_failed_log.txt
  3. Can anyone take a look at these 7 log files I have (I just copied the log from the details for each failed one, and made individual log files in notepad for them)? They keep failing, and I'm not sure why. I'm unsure what to look at specifically to figure out why they're failing. Especially log file #7. It's been failing for the past two weeks, almost instantly and I have no clue why or what to do to fix it. I'd greatly appreciate some help as I'm so confused. logs.rar
  4. Yea, I'm having a lot of super weird occurrences after the most recent update also. The UI/Dashboard for unmanic becomes pretty much unresponsive. set_mempolicy: Operation not permitted in my logs. And I have one fire that just keeps failing. [h264 @ 0x5605116f0680] SEI type 195 size 888 truncated at 48 [h264 @ 0x5605116f0680] SEI type 170 size 2032 truncated at 928 [h264 @ 0x5605116f0680] SEI type 81 size 1920 truncated at 32 [h264 @ 0x5605116f0680] SEI type 195 size 888 truncated at 47 [h264 @ 0x5605116f0680] SEI type 170 size 2032 truncated at 927 [h264 @ 0x5605116f0680] SEI type 81 size 1920 truncated at 31 [h264 @ 0x5605116f0680] A non-intra slice in an IDR NAL unit. [h264 @ 0x5605116f0680] decode_slice_header error [h264 @ 0x5605116f0680] no frame! [h264 @ 0x5605116f0680] SEI type 163 size 248 truncated at 32 [h264 @ 0x5605116f0680] non-existing PPS 2 referenced [h264 @ 0x5605116f0680] SEI type 163 size 248 truncated at 31 [h264 @ 0x5605116f0680] non-existing PPS 2 referenced [h264 @ 0x5605116f0680] decode_slice_header error [h264 @ 0x5605116f0680] no frame! [h264 @ 0x5605116f0680] SEI type 195 size 1448 truncated at 32 [h264 @ 0x5605116f0680] SEI type 195 size 1448 truncated at 30 [h264 @ 0x5605116f0680] top block unavailable for requested intra mode -1 [h264 @ 0x5605116f0680] error while decoding MB 0 0, bytestream 24 [h264 @ 0x5605116f0680] concealing 3600 DC, 3600 AC, 3600 MV errors in I frame [h264 @ 0x5605116f0680] SEI type 33 size 2024 truncated at 16 [h264 @ 0x5605116f0680] non-existing PPS 2 referenced Guessed Channel Layout for Input Stream #0.1 : 5.1 Literally all it says in the log. And it takes a good 10-20 seconds for that to even appear. The most recent unmanic push... is weird.
  5. There's a current "bug" in the most recent build where if you have failed transcodes... and you select more than one to add back to the pending list, it'll only add one and give you the error message to make sure unmanic is still running. Also... I have about 1,000 tv show episodes are are H265 but they are MKV. So it's changing their containers to MKV. Obviously when it does it, it literally only takes a couple of seconds per file. This is spitting out a ton of failed files. Once I readd them to the pending list, they typically go through without issue... but not sure if it's because it's going through so many files so very fast or what. Lastly, I've noticed this happening a lot here recently (past day or so), if I change my works from say 2 to 6. Two workers will select the same file. It'll go all the way to 100% on both workers, then nothing happens. Workers will start selecting the next file in the pending list, complete it almost instantly, never update the completed list as successful or failed, and the file stays in my unmanic transcoding location. I have to set the workers back to like 1 or 2. Completely stop the docker, then start it back... and of course when I do this, it has to completely rescan my entire library, and build the pending list all over again. Just figured I'd let you know.
  6. Ok, well how do I go about getting you these debug logs, because I've tried everything. The only thing I'm not doing that I see others doing is a GPU passthrough. My unraid server has no GPUs. all of my windows VM's just emulate the GPU. Sucks, but it is what it is.
  7. Hey, so first time using this... I followed your youtube video exactly on installing a Big Slur VM. I'm at the part where I just launched the VM for the very first time, opened up VNC, and selected MacOS Base System. It crashes immediately, and I basically just cycle through this one part over and over again. It tells me my "computer" restarted because of a problem. press a key or wait for startup to continue... then it crashes. Any clues on what I can look at that might be the issue?
  8. Strongly disagree. While yes, it took me a couple of weeks to defrag (xfs_fsr) 8x8tb drives all at 89% or higher capacity. I can honestly say... once I finished and had all drives at 1% fragmentation or less... the speed was so much faster. Files and folders open almost immediately, plex media plays almost immediately with the ability to skip/search so SO much faster. I will 100% keep an eye on my disk/file/folder fragmentation for now on as keeping it low has proven first hand how extremely beneficial it is in terms of speed.
  9. Hey, I know you mentioned before that this feature will be coming in a future update. I'm in no way trying to rush you or pester you about... merely curious how far down it is on your priority list. Feature: Adjust the quality, bit depth, CRF, etc of the transcode. Handbrake really gives me a lot of in depth options in regards to video transcode settings. On that note, if I have HDR x264 10 bit movies... will unmanic leave it as HDR and 10 bit, but simply transcode it to my container (in this case it's mkv) and make it x265... leaving the rest as is... IE HDR x264 10 Bit mkv file turns into HDR x265 10 bit mkv file? How does unmanic like Dolby Vision, HDR10, HDR10+ content?
  10. So I have a "small" array (comparatively to some folks). 11 drives, all 8TB (one drive is a parity). I made a post previous about how I was defragging them via xfs_fsr command, one drive at a time. So far I've made it though three drives. 8TB drives with 97% or higher fragmentation on both files and directories takes several days per drive haha. Anyways, I'm kind of curious how bad fragmentation affects xfs arrays. Now all my computers, except my unraid server are 100% purely nvme drives. So fragmentation hasn't been an issues for many years, thanks to SSD's and TRIM. As I'm defragging, I often see things like: extents before:4709 after:1 DONE ino=*numbers* most of the time it's before is less than 100. But I often enough see it say before:26000 after 3 (not done) or the highest so far was before:47569 after:4 (not done). What are extents... and how bad is it that it took up 47,000 and after it only took up 3 - 4?
  11. If you look at the very end, it says bind: address already in use Look at your other dockers and make sure none of them are already using port 5900. For me, krusader was using that port by default. I simply changed TMM's bind to a different port number, and it started up without issue.
  12. Ok, if I disabled parity... how would I go about defragging them in the best method? Is one at a time still the only route?
  13. Ok, if I didn't disable parity... how would I go about defragging them in the best method? Is one at a time still the only route?
  14. So I've read up on people running the following commands xfs_db -r /dev/md# (where # = whichever disk you want to mount to inspect) From there you can run "Frag" to see the fragmentation on the disk. I have 8 drives (7 drives 1 parity). All are roughly 8TB. The lowest one is 6.7TB used and the most full is 7.2TB. When I ran a frag check, I was getting fragmentation at 97.5% on the least fragmented drive, with the highest being over 98%. Most of the articles/reddit/forum posts I see have people talking about anything over say 60% is high enough to make them defrag. Where as a lot of people are at like 40% or well under. With mine being at 97-98%... is there any good way to defrag them all at once, rather than running this method one drive at a time? I understand this can take many days to run, per disk. Just curious what the best approach or method would be.