April 4, 20251 yr Hi, I recently had a server freeze, which forced me to reset the server by force. After that reboot, I saw that the last disk of the array had most of it's files missing (3.8 TB left instead of 17TB), so I used the maintenance mode to fix the errors present on all the drives in hope of having my files back on that drive. Without success, so I removed the drive from the server to have the emulated version. Same problem, only 3Tb present. So I copied the emulated files I could on a new drive (some where indeed not working and crashed the copy which turn without end), and decided to clean up the 2 Parity drives and the defective drive by formatting them and start over. But I am now unable to sync the parity again. It’s starting correctly (at around 90MB/s) but at one point it will appear to continue but in fact stop completely and render the server unresponsive over time, blocking me to even stop the array or the docker containers if I wait too long. I can generate the error by starting some dockers containers, but I am not sure it’s really related to them directly. A fix permissions does the same thing and I reinstalled all the containers just in case, but without improvement. I think that it’s when some container starts to read some part of the array that the problem occur and that I have to reset the server by force. By doing so, I have to fix the drives again (in maintenance mode) but I don’t lose any files anymore. I even removed the parity drives and only did a read check of the disk of the array, but I have the same issue. I also noticed several CPU errors in the syslog, but I was able to do a successful Memtest, so it does not seem to be related to the memory either. Could you take a look at the diagnostic files and help me find the cause of the issue? For the moment I think it could be a CPU problem or an error present on one of the drives, but an error that the disk check cannot find. The problem start in the syslog file attached with the following line : Apr 4 16:01:15 unraid kernel: ------------[ cut here ]------------ Thanks in advance for your help. Ed unraid-diagnostics-20250404-1603.zip
April 4, 20251 yr Unraid driver is crashing, this is almost always a hardware issue, most often bad RAM, but since you have a 14900K, it can also be the Intel 13/14 gen issue.
April 4, 20251 yr Author The Memtest is not showing any problem and XMP is disable. But you are right, I had big issues with the 14900K before. My server was crashing every other day, but I updated the BIOS to the last version in December 2024 (which should be ok now dixit Intel) and was able to replace my CPU at the same time by a new one. And I didn't have any freeze since then expect the one of last week. So could it still be the same issue not freezing the server anymore but preventing the parity sync only? I also started a "xfs_repair -nv /dev/sdh" trough ssh on one of the drive, and it started like this : root@unraid:~# xfs_repair -nv /dev/sdh Phase 1 - find and verify superblock... bad primary superblock - bad magic number !!! attempting to find secondary superblock... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .............................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................. .......................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................... Is that normal? Edited April 4, 20251 yr by Edgard666 Added informations
April 4, 20251 yr Solution 33 minutes ago, Edgard666 said: So could it still be the same issue not freezing the server anymore but preventing the parity sync only? Yep, since it's under more load. 33 minutes ago, Edgard666 said: xfs_repair -nv /dev/sdh This is not the correct device, for array devices use mdXp1, where X is the disk number, you can also use /dev/sdh1, but it won't update parity, though if it's not synced, doesn't really matter.
April 4, 20251 yr Author Incredible! I changed the 14900k CPU with a 12700K that I had in stock, and it seams to be OK now.... Rebuild in progress and the docker containers doesn't create any issue for now. I will wait to see of the issue come back during the rebuild, but I have hope since it never last that long before. I didn't think this CPU would come to mess with me again. :-( What a piece of crap. Thanks again.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.