Intel 10G NIC disconnected on fresh TrueNAS 12.0
Description
Problem/Justification
Impact
SmartDraw Connector
Katalon Manual Tests (BETA)
Activity
Alexander Motin January 21, 2021 at 8:51 PM
I think you should not try to disable the DHCP for ue0, but should only explicitly configure ix0, that will disable all other unconfigured interfaces.
Kevin Deldycke October 26, 2020 at 4:55 PM(edited)
The thing is: having all interfaces with DHCP enabled by default makes it impossible to set it up for only one of them. See the issue here, from a fresh install:
https://www.youtube.com/watch?v=vDMooVj-flM
If this is expected, should we add a disclaimer to first time users (pop-up on web UI welcome screen? Warning on the ISO download page?) to tell them not to install TrueNAS on a machine that is connected with 2 interfaces?
Alexander Motin October 23, 2020 at 4:49 PM
On fresh install all interfaces work like have DHCP enabled on them. But that is a request for troubles if more then one is connected. That is why I've recommended to configure one interface (ix0) explicitly, in which case TrueNAS will disable all other (unconfigured) interfaces.
Kevin Deldycke October 23, 2020 at 4:24 PM
I can't disable or enable DHCP on interfaces. As all came with the option set by default, I get the following error as soon as I try to change them:
Error: Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/middlewared/main.py", line 137, in call_method
result = await self.middleware._call(message['method'], serviceobj, methodobj, params, app=self,
File "/usr/local/lib/python3.8/site-packages/middlewared/main.py", line 1191, in _call
return await methodobj(*prepared_call.args)
File "/usr/local/lib/python3.8/site-packages/middlewared/schema.py", line 973, in nf
return await f(*args, **kwargs)
File "/usr/local/lib/python3.8/site-packages/middlewared/plugins/network.py", line 742, in commit
await self.__check_dhcp_or_aliases()
File "/usr/local/lib/python3.8/site-packages/middlewared/plugins/network.py", line 670, in __check_dhcp_or_aliases
raise CallError(
middlewared.service_exception.CallError: [EFAULT] At least one interface configured with either IPv4 DHCP, IPv6 auto or a static IP is required.So here is the important question: should all network interfaces set DHCP as active as default (i.e. on a fresh install)?
Kevin Deldycke October 23, 2020 at 4:03 PM
OK, forget my last commend, the KVM is working as intended. Just had to re-login into the BMC. I was able to select the 11th menu entry, TrueNAS was properly shutdown.
Details
Details
Assignee
Reporter
Labels
Impact
Fix versions
Affects versions
Priority
LowMore fields
Time tracking
More fields
Time trackingKatalon Platform
Linked Test Cases, Katalon Defect Results, Katalon Studio Test Results
Katalon Platform
Right after a fresh install of TrueNAS 12.0 on my machine, the web UI gets accessible for a couple of minutes before getting this error message:
Connecting toTrueNAS ... Make sure the TrueNAS system is powered on and connected to the network.
It seems the NIC lost its connection to the network. Using the remote management interface got me this error message:
My hardware:
Motherboard: ASRock RackE3C246D2I
CPU: Intel Core i3-9300T Coffee Lake-R, 4 cores, 3.2GHz, 8MiB L3 cache
RAM: 2 * 8GB KingstonKSM26ES8 /8ME 2666MHz DDR4 ECC CL19
NIC: 10Gtek X520-10G-1S-X8, PCIe x8 single SFP + port
More details on my hardwre is available on my blog at: https://kevin.deldycke.com/2020/05/nas-hardware/#final-configuration