February 8, 20242 yr I have had unraid for years and 8 years ago purchased a Dual intel xeon E5v2 processor and boared. Worked great for last 8 years or so. I had been thinking of upgrading and last month for some reason the IOMMU stopped working and started having random crashes with my server. SO I thought its time to upgrade anyways and so purchased: AMD Ryzen 9 7900x Asus ROG Strix B650E-F MB G-skill Trident Z5 Neo 64 GB DDR5 RAM Samsung 990PRO 4tb NVME I cont to have my old LSI 9210-8 Card NVIDIA P2000 GPU card Once I installed everything, I am getting multiple errors. Lots of XFS Metadata corruption Errors CPU: 5 PID: 7867 Comm: kworker/u48:6 Tainted: P W O 6.1.36-Unraid #1 BTRFS Error NVME temp errors the system freezes when I start my old VM's when the system freezes I cannot reach it at all, not through SSH, web UI etc it does not log anything new on the Syslogs its extremely frustrating especially since this server is a headless server and I am unable to login using monitor and keyboard due to location without pulling it out. I have a pikvm but unable to get the video out into it. I have attached the syslog files, and am hoping one of you guys can help with fixing it. I do have a parity check running currently that should hopefully be done in next 12 hours as I'm concerned about the data on the drives. thank you in advance for your help! tower-diagnostics-20240208-0815.zip
February 8, 20242 yr Community Expert There are macvlan call traces, those will usually end up crashing the server, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)), then reboot. Next check filesystem on disk9, and post new diags if issues persist.
February 16, 20242 yr Author On 2/8/2024 at 8:46 AM, JorgeB said: There are macvlan call traces, those will usually end up crashing the server, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)), then reboot. Next check filesystem on disk9, and post new diags if issues persist. So this fixed the issue. I am able to log on and everything has been stable except I started receiving errors for my Drives. I ran smart test on drive 14 and it is stuck at 10%. It has been running for over 3-4 days. Attached my diagnostic files. appreciate your help! tower-diagnostics-20240216-1308.zip
February 16, 20242 yr Community Expert Issus with disk14 look more like a power/connection problem, recommend checking/replacing the cables and retest.
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.