February 21, 20233 yr Hi @JorgeB I have just had my server crash and have attached diags, is this related to my other crashes you helped me with last week? the server is on 24/7 and this is the first problem since the possible RAM issue/corruption I had last week. Warning: mkdir(): Input/output error in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 351 unraid1-diagnostics-20230221-1113.zip
February 21, 20233 yr Author Unable to stop the server currently 😞 Feb 21 11:22:18 UNRAID1 emhttpd: shcmd (2491271): umount /mnt/cache Feb 21 11:22:18 UNRAID1 root: umount: /mnt/cache: target is busy. Feb 21 11:22:18 UNRAID1 emhttpd: shcmd (2491271): exit status: 32 Feb 21 11:22:18 UNRAID1 emhttpd: Retry unmounting disk share(s)... Feb 21 11:22:23 UNRAID1 emhttpd: Unmounting disks... Feb 21 11:22:23 UNRAID1 emhttpd: shcmd (2491272): umount /mnt/cache Feb 21 11:22:23 UNRAID1 root: umount: /mnt/cache: target is busy. Feb 21 11:22:23 UNRAID1 emhttpd: shcmd (2491272): exit status: 32 Feb 21 11:22:23 UNRAID1 emhttpd: Retry unmounting disk share(s)... Feb 21 11:22:28 UNRAID1 emhttpd: Unmounting disks... Feb 21 11:22:28 UNRAID1 emhttpd: shcmd (2491273): umount /mnt/cache Feb 21 11:22:28 UNRAID1 root: umount: /mnt/cache: target is busy. Feb 21 11:22:28 UNRAID1 emhttpd: shcmd (2491273): exit status: 32 Feb 21 11:22:28 UNRAID1 emhttpd: Retry unmounting disk share(s)...
February 21, 20233 yr Community Expert Feb 21 11:10:53 UNRAID1 kernel: BTRFS error (device nvme2n1p1): block=160911851520 write time tree block corruption detected This usually means bad RAM or other kernel memory corruption, maybe the RAM issues are not totally solved.
February 21, 20233 yr Author 26 minutes ago, JorgeB said: Feb 21 11:10:53 UNRAID1 kernel: BTRFS error (device nvme2n1p1): block=160911851520 write time tree block corruption detected This usually means bad RAM or other kernel memory corruption, maybe the RAM issues are not totally solved. This is worrying! I replaced all 4 sticks of RAM the other day so they chances of it actually being the RAM are slim to none I would have thought. It is a brand new motherboard and CPU, my old motherboard had 8 slots for RAM and never missed a beat I have now had these errors on both sets of 4 so I am making the assumption that it is not the RAM causing the issue so maybe the motherboard? (Asrock z790 pro rs/d4) I am on the latest BIOS, are there any steps I can take to try and get on top of this issue?
February 21, 20233 yr Run memtest for at least 12 hours. You likely have wrong settings for memory in your bios or are running the memory overclocked without realizing it. Edited February 21, 20233 yr by BRiT
February 21, 20233 yr Author 5 minutes ago, BRiT said: Run memtest for at least 12 hours. You likely have wrong settings for memory in your bios or are running the memory overclocked without realizing it. I ran the 4 sticks I took out in memtest for over 24 hours in another board with no issues and as all 8 sticks have been running without issue in my previous config I am confident there is no physical issue with the RAM (All Corsair Vengeance) I have not overclocked but did choose a power saving option (The reason for changing from a Threadripper) in the BIOS of which I cannot remember but I am going to change that back to standard just to eliminate what the problem could be. I have also enabled power saving in tips and tweaks as this is what brought me under the 150w I was looking for, do you think that could have any influence on this problem?
February 22, 20233 yr 12 hours ago, mbc0 said: I ran the 4 sticks I took out in memtest for over 24 hours in another board with no issues and as all 8 sticks have been running without issue in my previous config I am confident there is no physical issue with the RAM (All Corsair Vengeance) You need to run it on the system you are running unraid on. Otherwise while the sticks may be fine your bios settings could be all jacked up and causing the issues. So all you know is they work on a different system. You don't know if thecurrent system is setup right.
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.