August 21, 2025Aug 21 I don't know why and first my zfs pool showing one of the drive has too many error, I tried "zpool repair" couple time and it always resulted too many error, today I replaced the drive and resilver took about 10hours, 4 hours later, my machine was unaccessible again. I have to restart the machine again. Now it work again.anybody able to find out what's the problem? Hardware? software? Thanks in advance night-diagnostics-20250820-2012.zip
August 21, 2025Aug 21 Community Expert Take a look here first:https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#findComment-819173
August 21, 2025Aug 21 Author 10 hours ago, JorgeB said:Take a look here first:https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#findComment-819173I have just change the BIOS and updated to latest BIOS Firmware as well. Going to close monitor my machine. Thank you!
August 30, 2025Aug 30 Author On 8/21/2025 at 2:46 AM, JorgeB said:Take a look here first:https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#findComment-819173I'm still crash somehow.From the log I have thisAug 30 13:07:00 Night kernel: br-5362b0a0424e: port 3(vethd82bb6c) entered blocking stateAug 30 13:07:00 Night kernel: br-5362b0a0424e: port 3(vethd82bb6c) entered forwarding stateWhat does this mean?I have attached the syslog. syslog-192.168.3.190.log
August 30, 2025Aug 30 Author What I have done so far.-updated to latest BIOS-change Power Supply Idle Control to "typical current idle"-remove GPU-run 24hrs memtest with 5 pass no error-replaced ethernet cable-start unRAID with safe mode without plugin-docker custom network type from "macvlan" to "ipvlan"-disable docker disable VM-removed all docker reinstall some of the docker.-change ethernet port(my machine has 2 ethernet port)-Replace USB FlashSo far, I haven't pass 30hours mark. It always freeze before 24hrs mark.Next I'm going to -run another memtest for 48hrs to make sure isn't hardware related issue.any other suggestions on what could be the issue?
August 31, 2025Aug 31 Community Expert 14 hours ago, ySkNight said:What does this mean?These are normal when a Docker container starts/restarts; it's only an issue if it keeps happening 24/7. In that case, it generally means there's a container constantly restarting.I don't see anything relevant logged, suggesting more of a hardware issue, one thing you can try is to boot the server in safe mode with all docker containers/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one, including the individual docker containers.
August 31, 2025Aug 31 Author Does memtest same as run as a basic NAS for test hardware issue?I am currently running memtest ongoing 21hours, no crash yet.. Previously I ran it for 25hrs and no crash either.Memtest only use some hardware? like hard drive will not get connect / supply power?
September 1, 2025Sep 1 Community Expert You can use memtest to test the RAM, but keep in mind that memtest is only definitive if it finds errors, if you have multiple sticks try using the server with just one, if the same try with a different one, that will basically rule out bad RAM.
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.