tazire

Just to add to this I have followed what you have said and get the same result as rh535.. I didnt need to change the port for my install either. I tried it twice, deleting all files before trying the 2nd time with the same results. Literally identical results to rh535. Essentially from the first pull I just inputted my unraid ip address where it states. bridge mode was set as default as was everything else. Always the same result.

I just figured this out. Kasm was the main culprit. I usually have my zfs datasets hidden. When i opened it up it showed that kasm had over 350Gb of data even though it wasnt being calculated during general operations. I'm guessing hidden files werent being shown. Anyway I dont use it often enough and got rid.

So my appdata cache is currently sitting at 923GB used of 966GB. This pool only has appdata storage (excluding plex which has its own pool) when I calculate the size of the data stored within the appdata folder it shows that there is only 396GB storage in it. This is the only folder on the drive... That I can see. Is there any other reason this pool might be filling up? I've tried restarting docker. server-diagnostics-20251204-2009.zip

@JorgeB Had the same issue on W11 and your command resolved it. Cheers. Let me know if you want diagnostics or anything else.

I've started getting this error recently too. I've been on 7.1.3 for a while but its only started recently. Will try update once a rebuild is finished.

It's ok m8. I got this sorted using the console on the container. Bit of a pain but at least its sorted now!

Do you mind posting a step by step? I have been having a nightmare with this. Cant really figure out how to use adminer to get this sorted either. Thanks

Have to agree with you on that seller. That's who I used for all my gear and it's never missed a beat. Glad everything has worked out.

100% or if like me you cant fit it directly then have a 120mm or 140mm fan directly above it blowing directly at the HBA.

Yea I also went with a newer HBA. 9500.. My logic was that its overkill for the task and maybe it wont get as hot! Probably absolute bull**** and I was just convincing myself to spend the money! Either way I haven't had a problem. It was very much plug and play and hasn't missed a beat.

For me in the end I just replaced the HBA and I havent had any issues since. I would definitely suggest having a fan blowing air on the HBA's if you feel its overheating. They tend to run fairly hot but they also expect server levels of airflow through them.

Ok so between the disk shutdown timeout and immediate shut down request upon power loss this has solved my problem. I'm going to assume the more likely culprit was the shutdown timeout given the other factors I explained earlier. Thanks everyone for the responses.

Is there any ram heatsinks that fit this ram? Also do you think you may have to reconsider the CPU upgrade in future because of this? Glad you were able to find a solution.

Thanks dude I did see that. But as I have said a manual shut down never results in an unclean shut down and I assumed these settings apply then too. So I never even considered that my settings were an issue. I have re adjusted the disk timeout to be 180. But again there is no way to properly test this without pulling the power on the UPS. Which I'd rather avoid given that others have said it can cause degradation of the batteries. Also the fact that other devices are still running post shut down of the server would indicate that there is sufficient time on the batteries to allow for the shut down. Which is why I was confused about my issue specifically.

Weird.... shouldn't this be applied to all shut down requests? Mine is set to 90 seconds. but when a manual shut down is requested it never results in an unclean shut down. It only occurs when a UPS shutdown is requested. I will try to extend it and see what happens. It shouldn't make any difference to my day to day use anyway. Thanks for the suggestion. It does make a lot of sense other than that I never get an unclean shut down when I manually do it.