DirtyDan

Jorge, did you need to do anything special? Tried RC1 a few days ago and could not get it working. Was this specifically for getting firmware to let you us SR-IOV?

Did anyone have troubles with the Tailscale Plugin? I tried RC1 and it flat out would not work. I didnt see any others talk about that. Also, couldnt get my intel B50 working on RC1, not sure if I was missing anything, but I thought from research that the newer kernel would enable Plex to use it.

Thanks for doing this.

Looking into the appdata share, I’ve been storing my app data backups there. I’ll probably move it to the array and/or reduce to 1(maybe 2) backups kept.

New Diagnostics here: I am now realizing 500gb is barely enough for my app storage. How can I go about increasing the size? Would I just follow the instructions in the thread below? Or follow instructions here? garciaunraid-diagnostics-20250417-0648.zip

@trurl I would like to have my data stored in the safest, but fastest possible spot. Which I would feel like would be the the cacheapps pool, since it has 2 drives in that array for redundancy plus those are NVME drives. Is that best use case? I will work on getting Minimum Free Set for pools and shares.

@trurl i saw a couple containers showing that they werent started, then tried to start which gave the same error as before. Didnt notice I had selected two different containers from different repo's, they were using the same port allocation and that was causing the error. Seems things are working normally. you mentioned on recommendations to make sure this doesn't happen again. What do I need to be looking at?

All done. Everything seems to be back in order. Edit: I may have spoke to soon, seems I am still having the same error as before. Here are the new diagnostics garciaunraid-diagnostics-20250409-1712.zip

Awesome, will do. Should have some time to work on this later today. I appreciate the help.

So this only occurred last night, after I executed the mover function. For future reference, should I not do that while the array is live? Also, I run the CA Backup plugin/app, am I able to recreate/restore from that? Edit: Also, my cache drive is no longer full since I had executed the mover function.

@trurl see attached. garciaunraid-diagnostics-20250409-0907.zip

Hi Unraid users Last night I decided to download a few large ISO's, filling my cache drive up and I noticed my Overseerr container became unresponsive and was not letting me log in. When I checked around the server dashboard, thats when I noticed the cache was full and I decided to execute the mover function. What I probably should have done is stop the array docker itself and then execute move... But bad on me, I didnt.... So now, I am unable to start any docker that was stopped during that time. Fix common problems is showing it as "docker image is either full or corrupted". I have not restarted the server, or stopped the docker image. I do have CA app data running and backing up, most recent was on 4/7. Before I go any further and cause more mayhem on my Unraid box, should I restore from backup, or is there other steps I should take. Below is the main error I see: Logs attached. docker.log syslog.txt

Hey, So I think from the research I did after my post, it really is an AlderLake iGPU and you dont really need it to read raptor lake on the 14500, beacuse it isn't the actually the updated iGPU that came on the higher end chips, IE 14600 and above.

I am in the same boat here with a 14500, currently struggling to get HDR transcoding working, but everything else does. I feel like unraid is not recognizing the CPU correctly because it keeps listing it as Alder Lake in the system devices and that also what shows up in Plex.

Thanks for responding. I have been having a hard time finding any hard evidence of it still reporting Alderlake for the 14500.