October 31, 20241 yr Recently I rebuilded my NAS after my motherboard failure Now I am having issue that on daily basis my server just completely freezing I am running 7.0.0-beta.4 I have AMD 7900x and X670E Gigabyte Aorus Master with Arc 380 and one HBA card. I am having my logs written to other nas, and last record was on 13:29 during mover doing it's job Can you please advice what can be wrong? fortress-diagnostics-20241031-1540.zip
October 31, 20241 yr Community Expert 1 hour ago, J05u said: I am having my logs written to other nas Post that as well, but if there's nothing relevant logged there, it could be hardware related.
October 31, 20241 yr Community Expert Nothing relevant, 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 docker containers.
November 1, 20241 yr Author Basically tried to play with ram, remove gpu and etc, same story. During parity check or it's either crashing or losing internet What is this story in logs? I have this kind of messages all over the place and I assume this is somehow related. Docker network is ipvlan Nov 1 11:35:05 Fortress kernel: br-a6738b7a6f98: port 24(veth40099c4) entered disabled state Nov 1 11:36:05 Fortress kernel: br-a6738b7a6f98: port 24(veth1c797a4) entered blocking state Nov 1 11:36:05 Fortress kernel: br-a6738b7a6f98: port 24(veth1c797a4) entered disabled state Nov 1 11:36:05 Fortress kernel: veth1c797a4: entered allmulticast mode Nov 1 11:36:05 Fortress kernel: veth1c797a4: entered promiscuous mode Nov 1 11:36:05 Fortress kernel: eth0: renamed from veth4da3b2a Nov 1 11:36:05 Fortress kernel: br-a6738b7a6f98: port 24(veth1c797a4) entered blocking state Nov 1 11:36:05 Fortress kernel: br-a6738b7a6f98: port 24(veth1c797a4) entered forwarding state Nov 1 11:36:06 Fortress kernel: br-a6738b7a6f98: port 24(veth1c797a4) entered disabled state Nov 1 11:36:06 Fortress kernel: veth4da3b2a: renamed from eth0 Nov 1 11:36:06 Fortress kernel: br-a6738b7a6f98: port 24(veth1c797a4) entered disabled state Nov 1 11:36:06 Fortress kernel: veth1c797a4 (unregistering): left allmulticast mode Nov 1 11:36:06 Fortress kernel: veth1c797a4 (unregistering): left promiscuous mode Nov 1 11:36:06 Fortress kernel: br-a6738b7a6f98: port 24(veth1c797a4) entered disabled state Nov 1 11:37:06 Fortress kernel: br-a6738b7a6f98: port 24(veth6c853ce) entered blocking state Nov 1 11:37:06 Fortress kernel: br-a6738b7a6f98: port 24(veth6c853ce) entered disabled state Nov 1 11:37:06 Fortress kernel: veth6c853ce: entered allmulticast mode Nov 1 11:37:06 Fortress kernel: veth6c853ce: entered promiscuous mode Nov 1 11:37:06 Fortress kernel: eth0: renamed from veth5c6f622 Nov 1 11:37:06 Fortress kernel: br-a6738b7a6f98: port 24(veth6c853ce) entered blocking state Nov 1 11:37:06 Fortress kernel: br-a6738b7a6f98: port 24(veth6c853ce) entered forwarding state Nov 1 11:37:07 Fortress kernel: br-a6738b7a6f98: port 24(veth6c853ce) entered disabled state Nov 1 11:37:07 Fortress kernel: veth5c6f622: renamed from eth0 Nov 1 11:37:07 Fortress kernel: br-a6738b7a6f98: port 24(veth6c853ce) entered disabled state Nov 1 11:37:07 Fortress kernel: veth6c853ce (unregistering): left allmulticast mode Nov 1 11:37:07 Fortress kernel: veth6c853ce (unregistering): left promiscuous mode Nov 1 11:37:07 Fortress kernel: br-a6738b7a6f98: port 24(veth6c853ce) entered disabled state Nov 1 11:38:07 Fortress kernel: br-a6738b7a6f98: port 24(veth0afbe5b) entered blocking state Nov 1 11:38:07 Fortress kernel: br-a6738b7a6f98: port 24(veth0afbe5b) entered disabled state Nov 1 11:38:07 Fortress kernel: veth0afbe5b: entered allmulticast mode Nov 1 11:38:07 Fortress kernel: veth0afbe5b: entered promiscuous mode Nov 1 11:38:07 Fortress kernel: eth0: renamed from vethc884152 Nov 1 11:38:07 Fortress kernel: br-a6738b7a6f98: port 24(veth0afbe5b) entered blocking state Nov 1 11:38:07 Fortress kernel: br-a6738b7a6f98: port 24(veth0afbe5b) entered forwarding state Nov 1 11:38:07 Fortress kernel: br-a6738b7a6f98: port 24(veth0afbe5b) entered disabled state Nov 1 11:38:07 Fortress kernel: vethc884152: renamed from eth0 Nov 1 11:38:07 Fortress kernel: br-a6738b7a6f98: port 24(veth0afbe5b) entered disabled state Nov 1 11:38:07 Fortress kernel: veth0afbe5b (unregistering): left allmulticast mode Nov 1 11:38:07 Fortress kernel: veth0afbe5b (unregistering): left promiscuous mode Nov 1 11:38:07 Fortress kernel: br-a6738b7a6f98: port 24(veth0afbe5b) entered disabled state
November 1, 20241 yr Are you sure that your PSU is up to the task? Doing a parity check will strain it the most... Try booting the system without a parity check and see if it's stable. likely your on that knifes edge as to what you need/have
November 1, 20241 yr Author 1 hour ago, mathomas3 said: Are you sure that your PSU is up to the task? Doing a parity check will strain it the most... Try booting the system without a parity check and see if it's stable. likely your on that knifes edge as to what you need/have PSU is more than enough, and it was also without parity checks
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.