Mistershiverz

@Jarskyappreciate the feedback. Yes amongst the troubleshooting and after running the memtest i did update the boards bios in hope that it would resolve some of the errors. No this is worth a look but when in this board's bios i could not see any mention of the RAM using an XMP Profile. Hmm ok i may have to start looking at hardware replacements as all the feedback looks to be failing hardware.

@Lavoslav cool appreciate the feedback. Similar story here the Server was rock solid for 12 Months now struggling to get a 48 hours of uptime.

@PSYCHOPATHiO thanks for that i have also replaced the Boot USB during this troubleshooting process as i also had read another thread where a user with similar errors reported that resolved it for them. Unfortunately in my case has made no change.

@JorgeB @Lavoslav Thanks for the feedback. I'm beginning to share the same suspicion, but I want to understand these errors thoroughly before investing in new hardware. Is it safe to conclude that segfault errors are typically indicative of failing hardware? I've noticed that when I decrease the number of dockers running, the crashes happen less frequently. However, could this simply be because there's less strain on the hardware?

Hey everyone, I'm dealing with frequent server crashes and having a tough time figuring out what's causing them. When the server crashes, I'm left with no choice but to hard reboot it. Sometimes, the unRaid GUI remains responsive, but basic functions like stopping dockers or rebooting the server don't work or get stuck. I've been going through the server's syslogs and noticed some common errors, mainly segfault errors, whenever the crashes happen. After looking around this forum, I found that many people suggest running a memtest on the server's RAM when encountering these errors. I've already done this, and it didn't report any issues. I even tried replacing the RAM with new ones, but the problem persists. So far, I've tried: 1. Running a memtest on the previous RAM, which showed no errors. 2. Buying new RAM, but it didn't solve the issue. 3. Removing all unRaid plugins except the essential ones (like CA Plugins). 4. Disabling all Docker containers except for essential ones like Plex. Despite these steps, I'm still struggling to identify the root cause of the problem. I'm not sure if it's related to a specific docker/plugin, an unraid function, or failing hardware. Any advice or insight into this issue would be greatly appreciated. I've attached the server's diagnostics and a couple of recent syslogs showing the common errors I'm encountering. Thanks in advance for any help with this issue. tower-diagnostics-20240421-0738.zip syslog.txt syslog2.txt syslog-previous.txt

This can be marked as Solved. Thanks again.

That was it thank you. Removing the "Pools" File resolved the issue. Again thank you all for your help resolved in under 24hours and much appreciated.

Navigating the the /boot/config/ i can see a file tabled pools but no folder is this the issue?

Unfortunately the same issue i cannot create a pool with the newly created USB Drive. I have attached the diagnostics again just to be sure. Can i manually create the Pool directory on the USB Drive? ironmike-diagnostics-20220806-2159.zip

Ok i will try that and keep you posted thank you for the help.

@JorgeB ok what would you recommend in this situation can i manually create this directory? Or do i need to look into replacing repairing USB Drive? Permissions?

Yes i have tried that it is mounted in the screenshot as i thought that it may help with creating the pool.

Done thank you let me know if there is any other info you need.

Hey Team I am unable to create a cache pool after updating to 6.10.3 coming from 6.8.3. I have selected the "Add Pool" and once i have created the pool i get no option on the UI to add my previous cache drive. I can see my SSD as a unassigned drive but without being able to create a pool i cannot assign this to a cache pool. Im getting no error or output on why i cannot create a pool so any help would be appreciated. ironmike-diagnostics-20220806-0816.zip

Yes sorry i have rebooted after the update. If i experience this issue again i will be sure to update this thread with the command line results. Again thank you for your help today.

Sorry i may have jumped the gun and currently rebuilding docker.img and also updating to latest release of Unraid. Will it still be of a help to provide the info from that command even if i have rebuilt the .img or does it need to be provided from the time of the errors.

@trurl The docker image at the time of the errors was at about 18% usage and all container size looked normal the only issue i had was the log file showing 100% usage due to the errors.

Hi @trurl I cannot recall why the docker.img has been set to 40G as this server has been running well for a good couple of years now but i will get that changed when i rebuild the .img I rebuilt the .img about 5 days ago and everything has been fine until today is there are partucular docker etc that i can look at that would be causing this issue or should i rebuild the .img and go from there? Again thanks for the help much appreciated.

Hi @XDD128 sorry to jump in on your thread but i have been getting the exact same issues myself for the last week it seems. Has this also recently started happening for you also?

Hi Team Currently experiencing issues related to the errors below where i will login to my server and notice a couple docker containers have stopped and a few are hung. When trying to restart the Dockers i then receive the Execution 403 error on Start. I have had a look through the forums regarding this issue with it looking to be related to the Docker.img or a failing cache drive. I have gone ahead and deleted the Docker.img and rebuilt this a few days ago all was fine and the errors are present again. Can anybody help me with how to proceed or what is causing this issue is it the Docker.img or a failing drive that will need to be reformatted/replaced? Below is a list of errors i am receiving is the Logs and Diagnostics posted below: kernel: loop: Write error at byte offset 7824109568, length 4096. kernel: print_req_error: I/O error, dev loop2, sector 15281464 kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 1, rd 0, flush 0, corrupt 0, gen 0 kernel: BTRFS error (device loop2): parent transid verify failed on 9361899520 wanted 9195 found 9104 Thanks in advance for any help it much appreciated. tower-diagnostics-20200903-1916.zip

Thank you very much for your help i removed all plugins and can now access WebGUI so we are all go thanks again and appreciate your help.

Just to confirm can plugins be stopping me from accessing the WebGUI even when i have the array set to not AutoStart?

Hi Itimpi Ok thanks for that. How would i go about working out/deleting plugins to sort this issue? I have attached the Diagnostic Zip below. Thanks again for your help. ironmike-diagnostics-20180914-1838.zip

Hi Team I am currently running Unraid 6.5.3 and unable to access WebGUI. After performing a shutdown I connected a monitor to the server and can see this: /usr/local/sbin/emhttp: line 54: 9394 Segmentation Fault /usr/local/sbin/emhttpd After this I performed another shutdown and could access my server in Safe Mode with no plugins. I have set unread to not Auto-Start the array but still get no response from WebGUI when not in SafeMode Any help would be much appreciated please let me know if I can attach any logs to help with this issue. Thanks in advance.

Hi Team Can somebody tell me or point me in the right direction on what could be causing this error? Mar 5 09:44:11 IronMike nginx: 2018/03/05 09:44:11 [error] 5132#5132: *6481 user "root": password mismatch, client: 192.168.1.6, server: , request: "GET /Main HTTP/1.1", host: "192.168.1.7" I have tried stopping all dockers to see if it is docker related and still getting the error. I also rebooted the server and was still getting this error in the logs when the array was stopped. Thanks in advance