tazire

Thanks for explaining all that. That helps. I have the 2nd server setup with a static ip. So once I got that back online it did rectify the issue and my main shut down gracefully as expected. Is there anyway to mitigate this type of issue in future? I dont want my 2nd server crashing to cause such issues on my main if I can avoid it. I understand it will obviously cause some issues but can I set it up such that when I stop the nfs service it fully stops all persistent requests? Is it a hard vs soft mount difference? Also is the hard vs soft mount something I can configure in UD?

So I had a 2nd unraid server connected through UD as an NFS share. I used this share to backup my appdata using duplicacy. I came home today to find that the connected unraid server had crashed. Duplicacy showed it had been attempting to upload the backup for several hours without progress. So my first port of call was to try stop the duplicacy container... this failed in the normal gui way.. eventually i was able to forcestop it. Grand but I was seeing a persistent "kernel: nfs: server 192.168.1.50 not responding, timed out" in the logs. So I then tried to stop the nfs service... in settings when I changed the setting to No and tried to click apply nothing happened. So again I force stopped the service using "/usr/local/etc/rc.d/rc.nfsd stop" command. I got notified that the service had stopped and the logs also reflected this. Still the nfs timeout warning continued to appear. So i have tried to stop the array and the docker service appears to have stopped successfully however the array will not stop. Also a shutdown doesnt do anything and I continue to get the nfs timeout issue. Not really too sure where to go from here. I havent hard reset the server yet just in case there is something I can do. Any help would be greatly appreciated. Even just to get the server shut down gracefully. server-diagnostics-20260811-1855.zip ***EDIT*** Ok so when I got my 2nd server back up and running... Hard reset its not as vital for me... the server shut down gracefully. But I guess the issue still stands when this instance occurs and I'm not in a position to hard reset the mounted drives what is the best course of action to get to a place to rectify it?

Its insane. I'm not in that league obviously but to even be thinking about it being worth the same price is insane... let alone more. And in your case 10's of times more. Crazy stuff. Not really knowing how much its making for you... I'd nearly be tempted to take half the RAM out (512Gb is still an insane amount) and sell that and the old RAM. You'd be up money and still have an insane server.

I was just thinking about the value of the hardware in my setup... what are the odds that the value is more than we paid over the period of time? Who would have ever thought that would even be a discussion. Lenovo seem to be doing a good deal on rtx 4000 blackwells. got mine for 1450 euro... cant see them anywhere else for less than 2k. if it interests you at all.

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.