November 28, 20223 yr I think the ethernet port became unresponsive, need to confirm from the diagnostics. Anyone ever see this before or what I should do about it (other than replace the onboard NIC)? tower-diagnostics-20221128-0032.zip
November 28, 20223 yr Community Expert There are some IOMMU related call traces, update to latest Unraid and post new diags.
January 25, 20233 yr Author Updated to 6.11.5 over the holidays, today it went down twice. tower-diagnostics-20230125-1419.zip
January 26, 20233 yr Community Expert Nothing much to see but diags are just after a reboot, you can enable the syslog server and post that after a crash to see if it catches something.
January 26, 20233 yr Author Thought the diagnostics would include the syslog... but since it might not have been retained, it wouldn't be able to bundle it in. I've attached the most recent syslog since the crash - possibly different from the initial problem. SMBD errors. syslog (2).zip Edited January 26, 20233 yr by hanmaan
January 26, 20233 yr Community Expert Try switching to ipvlan (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)).
January 26, 20233 yr Author I've enabled ipvlan, still seeing a lot of sky2 rx errors, is that concerning? tower-syslog-20230126-1440.zip
January 26, 20233 yr Community Expert It's not great, you can try removing it if the issues continue to see if it helps.
January 26, 20233 yr Author Went down again - I guess maybe I'll try replacing the NIC. syslog (3).zip
January 27, 20233 yr Author Solution I put in a USB dongle and disabled the onboard NIC. Looks like the onboard NIC is flaky (Marvell 88E8056) and shouldn't be relied on because the rx errors no longer appear on startup.
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.