After reboot/ upgrade, TrueNAS web interface not accessible any more until hard reset

[Steasenburger]

Hi everyone,
i had a power outage today, so my TrueNAS system was shut down abruptly.
After the power was back again, I restarted the system and noticed that the web interface was not reachable.
Also, I was unable to SSH to the system, but interestingly I was able to SSH to my Linux VM that was apparently running.

In this VM the situation was very weird:
I have a NFS mount of my TrueNAS pools which was only partially accessible, so most of the folders, but not all were missing (maybe some cached stuff?).
Thus, my Docker containers were unable to start.

The only possibility to get my system back running was a hard reset.
After that, everything was fine again.

Then I decided to upgrade from TrueNAS 13.U2 to 13.U3 and when the system was rebooted, I had exactly the same problem.
As a hard reset is not always possible for me, because the machine is located elsewhere, I am asking for your help to find the reason for this behaviour.

As a start, here is the system log from the boot after the upgrade (with SSH/ Web interface not accessible).

 

[Steasenburger]

Here is the full syslog including the multiple successful and unsuccessful boots, if that's more interesting.
The successful can be determined by looking if the DDNS service reports the error "badauth 0.0.0.0" -> so connection was possible (yeah, I have a configuration error there).
The unsuccessful ones report "Failed resolving hostname dyndns.strato.com: Name does not resolve".

 

[WN1X]

Complete hardware spec?

 

[Steasenburger]

Does dmidecode help? Or is there any other FreeBSD equivalent to lshw?

Code:

dmidecode 
# dmidecode 3.3
# SMBIOS entry point at 0xcb803000
Found SMBIOS entry point in EFI, reading table from /dev/mem.
SMBIOS 3.3 present.
54 structures occupying 2258 bytes.
Table at 0x000E6F40.

Handle 0x0000, DMI type 0, 26 bytes
BIOS Information
       Vendor: American Megatrends Inc.
       Version: 6042
       Release Date: 04/28/2022
       Address: 0xF0000
       Runtime Size: 64 kB
       ROM Size: 16 MB
       Characteristics:
               PCI is supported
               APM is supported
               BIOS is upgradeable
               BIOS shadowing is allowed
               Boot from CD is supported
               Selectable boot is supported
               BIOS ROM is socketed
               EDD is supported
               5.25"/1.2 MB floppy services are supported (int 13h)
               3.5"/720 kB floppy services are supported (int 13h)
               3.5"/2.88 MB floppy services are supported (int 13h)
               Print screen service is supported (int 5h)
               8042 keyboard services are supported (int 9h)
               Serial services are supported (int 14h)
               Printer services are supported (int 17h)
               ACPI is supported
               USB legacy is supported
               BIOS boot specification is supported
               Targeted content distribution is supported
               UEFI is supported
       BIOS Revision: 5.17

Handle 0x0001, DMI type 1, 27 bytes
System Information
       Manufacturer: System manufacturer
       Product Name: System Product Name
       Version: System Version
       Serial Number: System Serial Number
       UUID: 24bb05cf-23b2-54f2-3ff5-40b07609074b
       Wake-up Type: Power Switch
       SKU Number: SKU
       Family: To be filled by O.E.M.

Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
       Manufacturer: ASUSTeK COMPUTER INC.
       Product Name: PRIME A320M-K
       Version: Rev X.0x
       Serial Number: 181140690807946
       Asset Tag: Default string
       Features:
               Board is a hosting board
               Board is replaceable
       Location In Chassis: Default string
       Chassis Handle: 0x0003
       Type: Motherboard
       Contained Object Handles: 0

Handle 0x0003, DMI type 3, 22 bytes
Chassis Information
       Manufacturer: Default string
       Type: Desktop
       Lock: Not Present
       Version: Default string
       Serial Number: Default string
       Asset Tag: Default string
       Boot-up State: Safe
       Power Supply State: Safe
       Thermal State: Safe
       Security Status: None
       OEM Information: 0x00000000
       Height: Unspecified
       Number Of Power Cords: 1
       Contained Elements: 0
       SKU Number: Default string

Handle 0x0004, DMI type 8, 9 bytes
Port Connector Information
       Internal Reference Designator: PS/2 Keyboard
       Internal Connector Type: None
       External Reference Designator: PS/2 Keyboard
       External Connector Type: PS/2
       Port Type: Keyboard Port

Handle 0x0005, DMI type 8, 9 bytes
Port Connector Information
       Internal Reference Designator: PS/2 Mouse
       Internal Connector Type: None
       External Reference Designator: PS/2 Mouse
       External Connector Type: PS/2
       Port Type: Mouse Port

Handle 0x0006, DMI type 8, 9 bytes
Port Connector Information
       Internal Reference Designator: VGA
       Internal Connector Type: None
       External Reference Designator: VGA port
       External Connector Type: None
       Port Type: Other

Handle 0x0007, DMI type 8, 9 bytes
Port Connector Information
       Internal Reference Designator: HDMI
       Internal Connector Type: None
       External Reference Designator: HDMI port
       External Connector Type: Other
       Port Type: Other

Handle 0x0008, DMI type 8, 9 bytes
Port Connector Information
       Internal Reference Designator: USB3_56
       Internal Connector Type: None
       External Reference Designator: USB3_56
       External Connector Type: Access Bus (USB)
       Port Type: USB

Handle 0x0009, DMI type 8, 9 bytes
Port Connector Information
       Internal Reference Designator: USB12
       Internal Connector Type: None
       External Reference Designator: USB12
       External Connector Type: Access Bus (USB)
       Port Type: USB

Handle 0x000A, DMI type 8, 9 bytes
Port Connector Information
       Internal Reference Designator: USB3_34
       Internal Connector Type: None
       External Reference Designator: USB3_34
       External Connector Type: Access Bus (USB)
       Port Type: USB

Handle 0x000B, DMI type 8, 9 bytes
Port Connector Information
       Internal Reference Designator: LAN
       Internal Connector Type: None
       External Reference Designator: LAN
       External Connector Type: RJ-45
       Port Type: Network Port

Handle 0x000C, DMI type 8, 9 bytes
Port Connector Information
       Internal Reference Designator: AUDIO
       Internal Connector Type: None
       External Reference Designator: AUDIO
       External Connector Type: Other
       Port Type: Audio Port

Handle 0x000D, DMI type 8, 9 bytes
Port Connector Information
       Internal Reference Designator: SATA6G_1
       Internal Connector Type: SAS/SATA Plug Receptacle
       External Reference Designator: Not Specified
       External Connector Type: None
       Port Type: SATA

Handle 0x000E, DMI type 8, 9 bytes
Port Connector Information
       Internal Reference Designator: SATA6G_2
       Internal Connector Type: SAS/SATA Plug Receptacle
       External Reference Designator: Not Specified
       External Connector Type: None
       Port Type: SATA

Handle 0x000F, DMI type 8, 9 bytes
Port Connector Information
       Internal Reference Designator: SATA6G_3
       Internal Connector Type: SAS/SATA Plug Receptacle
       External Reference Designator: Not Specified
       External Connector Type: None
       Port Type: SATA

Handle 0x0010, DMI type 8, 9 bytes
Port Connector Information
       Internal Reference Designator: SATA6G_4
       Internal Connector Type: SAS/SATA Plug Receptacle
       External Reference Designator: Not Specified
       External Connector Type: None
       Port Type: SATA

Handle 0x0011, DMI type 8, 9 bytes
Port Connector Information
       Internal Reference Designator: M.2
       Internal Connector Type: SAS/SATA Plug Receptacle
       External Reference Designator: Not Specified
       External Connector Type: None
       Port Type: SATA

Handle 0x0012, DMI type 8, 9 bytes
Port Connector Information
       Internal Reference Designator: USB34
       Internal Connector Type: Access Bus (USB)
       External Reference Designator: Not Specified
       External Connector Type: None
       Port Type: USB

Handle 0x0013, DMI type 8, 9 bytes
Port Connector Information
       Internal Reference Designator: USB56
       Internal Connector Type: Access Bus (USB)
       External Reference Designator: Not Specified
       External Connector Type: None
       Port Type: USB

Handle 0x0014, DMI type 8, 9 bytes
Port Connector Information
       Internal Reference Designator: USB3_12
       Internal Connector Type: Access Bus (USB)
       External Reference Designator: Not Specified
       External Connector Type: None
       Port Type: USB

Handle 0x0015, DMI type 8, 9 bytes
Port Connector Information
       Internal Reference Designator: CPU_FAN
       Internal Connector Type: Other
       External Reference Designator: Not Specified
       External Connector Type: None
       Port Type: Other

Handle 0x0016, DMI type 8, 9 bytes
Port Connector Information
       Internal Reference Designator: CHA_FAN1
       Internal Connector Type: Other
       External Reference Designator: Not Specified
       External Connector Type: None
       Port Type: Other

Handle 0x0017, DMI type 8, 9 bytes
Port Connector Information
       Internal Reference Designator: COM
       Internal Connector Type: DB-9 male
       External Reference Designator: Not Specified
       External Connector Type: None
       Port Type: Serial Port 16550A Compatible

Handle 0x0018, DMI type 8, 9 bytes
Port Connector Information
       Internal Reference Designator: AAFP
       Internal Connector Type: Mini Jack (headphones)
       External Reference Designator: Not Specified
       External Connector Type: None
       Port Type: Audio Port

Handle 0x0019, DMI type 8, 9 bytes
Port Connector Information
       Internal Reference Designator: F_PANEL
       Internal Connector Type: Other
       External Reference Designator: Not Specified
       External Connector Type: None
       Port Type: Other

Handle 0x001A, DMI type 8, 9 bytes
Port Connector Information
       Internal Reference Designator: SPEAKER
       Internal Connector Type: Other
       External Reference Designator: Not Specified
       External Connector Type: None
       Port Type: Other

Handle 0x001B, DMI type 8, 9 bytes
Port Connector Information
       Internal Reference Designator: SPDIF_OUT
       Internal Connector Type: Other
       External Reference Designator: Not Specified
       External Connector Type: None
       Port Type: Other

Handle 0x001C, DMI type 10, 6 bytes
On Board Device Information
       Type: Video
       Status: Enabled
       Description:    To Be Filled By O.E.M.

Handle 0x001D, DMI type 11, 5 bytes
OEM Strings
       String 1: Default string
       String 2: Default string
       String 3: MIRINDA
       String 4: Default string
       String 5: Default string
       String 6: Default string
       String 7: Default string
       String 8: Default string

Handle 0x001E, DMI type 12, 5 bytes
System Configuration Options
       Option 1: Default string
       Option 2: Default string
       Option 3: Default string
       Option 4: Default string

Handle 0x001F, DMI type 32, 20 bytes
System Boot Information
       Status: No errors detected

Handle 0x0020, DMI type 34, 11 bytes
Management Device
       Description: ITE IT8655E
       Type: Other
       Address: 0x00000295
       Address Type: I/O Port

Handle 0x0021, DMI type 41, 11 bytes
Onboard Device
       Reference Designation:  Onboard IGD
       Type: Video
       Status: Enabled
       Type Instance: 1
       Bus Address: 0000:00:02.0

Handle 0x0022, DMI type 44, 9 bytes
Unknown Type
       Header and Data:
               2C 09 22 00 FF FF 01 01 00

Handle 0x0023, DMI type 43, 31 bytes
TPM Device
       Vendor ID: AMD
       Specification Version: 2.0
       Firmware Revision: 3.84
       Description: AMD
       Characteristics:
               Family configurable via platform software support
       OEM-specific Information: 0x00000000

Handle 0x0024, DMI type 18, 23 bytes
32-bit Memory Error Information
       Type: OK
       Granularity: Unknown
       Operation: Unknown
       Vendor Syndrome: Unknown
       Memory Array Address: Unknown
       Device Address: Unknown
       Resolution: Unknown

Handle 0x0025, DMI type 16, 23 bytes
Physical Memory Array
       Location: System Board Or Motherboard
       Use: System Memory
       Error Correction Type: Multi-bit ECC
       Maximum Capacity: 128 GB
       Error Information Handle: 0x0024
       Number Of Devices: 2

Handle 0x0026, DMI type 19, 31 bytes
Memory Array Mapped Address
       Starting Address: 0x00000000000
       Ending Address: 0x000CFFFFFFF
       Range Size: 3328 MB
       Physical Array Handle: 0x0025
       Partition Width: 1

Handle 0x0027, DMI type 19, 31 bytes
Memory Array Mapped Address
       Starting Address: 0x00100000000
       Ending Address: 0x0042FFFFFFF
       Range Size: 13056 MB
       Physical Array Handle: 0x0025
       Partition Width: 1

Handle 0x0028, DMI type 7, 27 bytes
Cache Information
       Socket Designation: L1 - Cache
       Configuration: Enabled, Not Socketed, Level 1
       Operational Mode: Write Back
       Location: Internal
       Installed Size: 384 kB
       Maximum Size: 384 kB
       Supported SRAM Types:
               Pipeline Burst
       Installed SRAM Type: Pipeline Burst
       Speed: 1 ns
       Error Correction Type: Multi-bit ECC
       System Type: Unified
       Associativity: 8-way Set-associative

Handle 0x0029, DMI type 7, 27 bytes
Cache Information
       Socket Designation: L2 - Cache
       Configuration: Enabled, Not Socketed, Level 2
       Operational Mode: Write Back
       Location: Internal
       Installed Size: 3 MB
       Maximum Size: 3 MB
       Supported SRAM Types:
               Pipeline Burst
       Installed SRAM Type: Pipeline Burst
       Speed: 1 ns
       Error Correction Type: Multi-bit ECC
       System Type: Unified
       Associativity: 8-way Set-associative

Handle 0x002A, DMI type 7, 27 bytes
Cache Information
       Socket Designation: L3 - Cache
       Configuration: Enabled, Not Socketed, Level 3
       Operational Mode: Write Back
       Location: Internal
       Installed Size: 32 MB
       Maximum Size: 32 MB
       Supported SRAM Types:
               Pipeline Burst
       Installed SRAM Type: Pipeline Burst
       Speed: 1 ns
       Error Correction Type: Multi-bit ECC
       System Type: Unified
       Associativity: 16-way Set-associative

Handle 0x002B, DMI type 4, 48 bytes
Processor Information
       Socket Designation: AM4
       Type: Central Processor
       Family: Zen
       Manufacturer: Advanced Micro Devices, Inc.
       ID: 12 0F A2 00 FF FB 8B 17
       Signature: Family 25, Model 33, Stepping 2
       Flags:
               FPU (Floating-point unit on-chip)
               VME (Virtual mode extension)
               DE (Debugging extension)
               PSE (Page size extension)
               TSC (Time stamp counter)
               MSR (Model specific registers)
               PAE (Physical address extension)
               MCE (Machine check exception)
               CX8 (CMPXCHG8 instruction supported)
               APIC (On-chip APIC hardware supported)
               SEP (Fast system call)
               MTRR (Memory type range registers)
               PGE (Page global enable)
               MCA (Machine check architecture)
               CMOV (Conditional move instruction supported)
               PAT (Page attribute table)
               PSE-36 (36-bit page size extension)
               CLFSH (CLFLUSH instruction supported)
               MMX (MMX technology supported)
               FXSR (FXSAVE and FXSTOR instructions supported)
               SSE (Streaming SIMD extensions)
               SSE2 (Streaming SIMD extensions 2)
               HTT (Multi-threading)
       Version: AMD Ryzen 5 5600 6-Core Processor              
       Voltage: 1.1 V
       External Clock: 100 MHz
       Max Speed: 4450 MHz
       Current Speed: 3500 MHz
       Status: Populated, Enabled
       Upgrade: Socket AM4
       L1 Cache Handle: 0x0028
       L2 Cache Handle: 0x0029
       L3 Cache Handle: 0x002A
       Serial Number: Unknown
       Asset Tag: Unknown
       Part Number: Unknown
       Core Count: 6
       Core Enabled: 6
       Thread Count: 12
       Characteristics:
               64-bit capable
               Multi-Core
               Hardware Thread
               Execute Protection
               Enhanced Virtualization
               Power/Performance Control

Handle 0x002C, DMI type 18, 23 bytes
32-bit Memory Error Information
       Type: OK
       Granularity: Unknown
       Operation: Unknown
       Vendor Syndrome: Unknown
       Memory Array Address: Unknown
       Device Address: Unknown
       Resolution: Unknown

Handle 0x002D, DMI type 17, 92 bytes
Memory Device
       Array Handle: 0x0025
       Error Information Handle: 0x002C
       Total Width: Unknown
       Data Width: Unknown
       Size: No Module Installed
       Form Factor: Unknown
       Set: None
       Locator: DIMM_A1
       Bank Locator: BANK 0
       Type: Unknown
       Type Detail: Unknown
       Speed: Unknown
       Manufacturer: Unknown
       Serial Number: Unknown
       Asset Tag: Not Specified
       Part Number: Unknown
       Rank: Unknown
       Configured Memory Speed: Unknown
       Minimum Voltage: Unknown
       Maximum Voltage: Unknown
       Configured Voltage: Unknown
       Memory Technology: Unknown
       Memory Operating Mode Capability: Unknown
       Firmware Version: Unknown
       Module Manufacturer ID: Unknown
       Module Product ID: Unknown
       Memory Subsystem Controller Manufacturer ID: Unknown
       Memory Subsystem Controller Product ID: Unknown
       Non-Volatile Size: None
       Volatile Size: None
       Cache Size: None
       Logical Size: None

Handle 0x002E, DMI type 18, 23 bytes
32-bit Memory Error Information
       Type: OK
       Granularity: Unknown
       Operation: Unknown
       Vendor Syndrome: Unknown
       Memory Array Address: Unknown
       Device Address: Unknown
       Resolution: Unknown

Handle 0x002F, DMI type 17, 92 bytes
Memory Device
       Array Handle: 0x0025
       Error Information Handle: 0x002E
       Total Width: 72 bits
       Data Width: 64 bits
       Size: 16 GB
       Form Factor: DIMM
       Set: None
       Locator: DIMM_B1
       Bank Locator: BANK 1
       Type: DDR4
       Type Detail: Synchronous Unbuffered (Unregistered)
       Speed: 2666 MT/s
       Manufacturer: Kingston
       Serial Number: 405574E4
       Asset Tag: Not Specified
       Part Number: 9965745-028.A00G    
       Rank: 2
       Configured Memory Speed: 2666 MT/s
       Minimum Voltage: 1.2 V
       Maximum Voltage: 1.2 V
       Configured Voltage: 1.2 V
       Memory Technology: DRAM
       Memory Operating Mode Capability: Volatile memory
       Firmware Version: Unknown
       Module Manufacturer ID: Bank 2, Hex 0x98
       Module Product ID: Unknown
       Memory Subsystem Controller Manufacturer ID: Unknown
       Memory Subsystem Controller Product ID: Unknown
       Non-Volatile Size: None
       Volatile Size: 16 GB
       Cache Size: None
       Logical Size: None

Handle 0x0030, DMI type 20, 35 bytes
Memory Device Mapped Address
       Starting Address: 0x00000000000
       Ending Address: 0x003FFFFFFFF
       Range Size: 16 GB
       Physical Device Handle: 0x002F
       Memory Array Mapped Address Handle: 0x0027
       Partition Row Position: Unknown
       Interleave Position: Unknown
       Interleaved Data Depth: Unknown

Handle 0x0031, DMI type 13, 22 bytes
BIOS Language Information
       Language Description Format: Long
       Installable Languages: 9
               en|US|iso8859-1
               fr|FR|iso8859-1
               zh|TW|unicode
               zh|CN|unicode
               ja|JP|unicode
               de|DE|iso8859-1
               es|ES|iso8859-1
               ru|RU|iso8859-5
               ko|KR|unicode
       Currently Installed Language: en|US|iso8859-1

Handle 0x0032, DMI type 9, 17 bytes
System Slot Information
       Designation: PCIEX16_1
       Type: x16 PCI Express
       Current Usage: Available
       Length: Long
       ID: 0
       Characteristics:
               3.3 V is provided
               Opening is shared
               PME signal is supported
       Bus Address: 0000:00:1f.7

Handle 0x0033, DMI type 9, 17 bytes
System Slot Information
       Designation: PCIEX1_1
       Type: x1 PCI Express
       Current Usage: In Use
       Length: Short
       ID: 1
       Characteristics:
               3.3 V is provided
               Opening is shared
               PME signal is supported
       Bus Address: 0000:03:04.0

Handle 0x0034, DMI type 9, 17 bytes
System Slot Information
       Designation: PCIEX1_2
       Type: x1 PCI Express
       Current Usage: In Use
       Length: Short
       ID: 2
       Characteristics:
               3.3 V is provided
               Opening is shared
               PME signal is supported
       Bus Address: 0000:03:07.0

Handle 0x0035, DMI type 127, 4 bytes
End Of Table

 

[jgreco]

Does dmidecode help? Or is there any other FreeBSD equivalent to lshw?

No, dmidecode doesn't help that much, too much noise, and lshw sucks in that uniquely Linux style too.

What we'd like is something like

Chassis Supermicro SC826-BE16 with redundant 920SQ PSU's
Mainboard X9DRi-LN4F
HBA Dell H310 crossflashed to LSI IT P20 20.00.07.00 with BIOS
One SFF8087 connected to backplane expander port A
2x Intel E5-2643 v2 CPU
256GB ECC RAM (8 x 32GB)
1x Intel X520-DA2 (dual card) with SFP+ connected to (your switch type)
2x 64GB Supermicro SATADOM for boot
etc.

The point is that almost no one here is an iXsystems employee, and rather than having a bunch of random community members try to back-engineer what you've got from an insipid tool's output, it is much better to summarize your setup especially with a focus on the bits that are likely to be interesting to those of us here in the forums. You may note that I've left out a lot of fluff details -- we probably don't care what speed your memory is, for example, but putting that in is fine too. At the end of the day, trying for a concise description is very useful.

With the "web interface not accessible", you are advised to indicate what has popped up on the console after the DCUI menu, where it should provide a URL at which the NAS can be reached for management. The usual problem is that networking is broken. And, just to get right to it, that usually happens because of poor hardware choices for the ethernet hardware (Realtek, Atheros, etc). So focus a bit on this for the fastest help possible.

What I did notice was that there's mention of PRIME A320M-K in there, which if I recall right, a bunch of people have come into the forums with complaining about them. My recollection is that the LAN port is based on the tragic and awful Realtek 8111 chipset, which is nearly the worst ethernet chipset ever produced. Guessing it is failing to negotiate for you; perhaps ASUS sourced a bunch of them from a Shenzhen back alley black market (this actually can and does happen).

The usual fix is to find yourself a genuine (not from Amazon or eBay) Intel Desktop CT ethernet adapter.

 

[Steasenburger]

I'm sorry, I just hadn't much time the last days, that's why I was only looking for a convenient command to export all the necessary information.
I will try to stick to your format:

Classic Desktop PC Chassis with one BeQuiet power supply (like 300W or so)
Asus PRIME A320M-K
AMD Ryzen 5 5600
32 GB ECC RAM (2x16GB Kingston)
2x 64GB Supermicro SATADOM for boot
4x 2TB HDDs
1x 250 GB NVMe SSD
2x SanDisk Ultra Fit USB Sticks for Boot (32GB)
1x Intel I210 1Gbit Network Card

I know that my mainboard has a poor Realtek network chip (I posted a thread about this here ).
That's why i've recently bought an Intel-based PCIe network card, to hopefully improve the situation, because these are said to make the least problems.
It's this one in particular: https://www.amazon.de/gp/product/B09H5XRD4N/
I know it's not a high-end one but the chip should be fine (...?).

And the connectivity problems that I had this time were different from before.
Before I was completely unable to connect to anything that was running on my system. Not TrueNAS nor any VM.
This time the VM was reachable and working more or less (apart from mounted stuff from TrueNAS), but TrueNAS was offline.

I can't tell you what the boot-log said would be the URL to reach the web interface, because I had no physical access to the machine.

 

[Steasenburger]

I just tried rebooting the system again and indeed the problem occurred again.
TrueNAS was not reachable via SSH or web interface, but the VM was.
This time i had a display attached, so I could see what was happening, but interestingly TrueNAS said that i can access the web interface via my IP address 192.168.0.97 (which was not possible).
I then reconfigured the re1 interface (the Realtek one) to use DHCP, because I was worried, that my fixed IP and those two interfaces could somehow collide (not sure if this can happen at all).

A few restarts later the system was reachable again, but I am not sure what (temporarily) "fixed" the problem.

 

[jgreco]

I know that my mainboard has a poor Realtek network chip

Yup

because these are said to make the least problems.
It's this one in particular: https://www.amazon.de/gp/product/B09H5XRD4N/
I know it's not a high-end one but the chip should be fine (...?).

Yup. In general, the Intel chips are well designed and high performance. There's a bunch of people at Intel tasked with this, plus they write their own driver too.

However, when I pulled up the URL you provided, Amazon barfed up a lungful of redirects and cookie warnings, before settling on a webpage displaying a Chinese knock-off card, identifiable by the reddish orange heatsink and lack of any Intel markings. That's not promising, especially in light of ...

And the connectivity problems that I had this time were different from before.

... it still not working.

Looking through your messages.txt, it looks like the system wasn't getting any DHCP and was trying to soldier on ahead with 0.0.0.0. So I think there's still a good chance that the network card (, cable, etc) is broken. If you can hop onboard the console, you can try manually setting an IP address to something that should work, and then ping your default gateway for a quick test.

 

[Steasenburger]

Yup



Yup. In general, the Intel chips are well designed and high performance. There's a bunch of people at Intel tasked with this, plus they write their own driver too.

However, when I pulled up the URL you provided, Amazon barfed up a lungful of redirects and cookie warnings, before settling on a webpage displaying a Chinese knock-off card, identifiable by the reddish orange heatsink and lack of any Intel markings. That's not promising, especially in light of ...



... it still not working.

Looking through your messages.txt, it looks like the system wasn't getting any DHCP and was trying to soldier on ahead with 0.0.0.0. So I think there's still a good chance that the network card (, cable, etc) is broken. If you can hop onboard the console, you can try manually setting an IP address to something that should work, and then ping your default gateway for a quick test.

Hmm that's disappointing.
I've especially bought this card to fix network problems that I've only ever had with TrueNAS/ FreeBSD.
I am using Linux and Windows for everything else, and i've never even thought about buying a separate network card, because the on-board ones were always working without any problems.
And those weren't any high-end main boards, i think they all have some kind of Realtek chip integrated.

Could a switch from TrueNAS to TrueNAS Scale help with that? Maybe the driver quality on Linux is just a bit better?

Anyway, ...
Until now, DHCP was not active on any of the two network interfaces, but a static IP address instead.
Is it important that those two interfaces have different IP addresses assigned to them, even if just one has a cable attached?

And by the way, after i've rebooted the system a few times, the network connection was there and is stable since then.
So I can easily check the GUI/ console to check anything.

 

[Steasenburger]

Here is what i get form pciconf.
I know these values could be faked, but it's at least something:

Code:

        For more information, documentation, help or support, go here:
        http://truenas.com
Welcome to FreeNAS
truenas# pciconf -lv | grep -A1 -B3 network
igb0@pci0:4:0:0:        class=0x020000 rev=0x03 hdr=0x00 vendor=0x8086 device=0x1533 subvendor=0xffff subdevice=0x0000
    vendor     = 'Intel Corporation'
    device     = 'I210 Gigabit Network Connection'
    class      = network
    subclass   = ethernet
re0@pci0:6:0:0: class=0x020000 rev=0x15 hdr=0x00 vendor=0x10ec device=0x8168 subvendor=0x1043 subdevice=0x8677
    vendor     = 'Realtek Semiconductor Co., Ltd.'
    device     = 'RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller'
    class      = network
    subclass   = ethernet

Are there any more log files/ commands apart from "var/log/messages" that i could check for errors?

 

[jgreco]

And those weren't any high-end main boards, i think they all have some kind of Realtek chip integrated.

Right. Because the stress level for a Realtek chip is that it has to work with Windows doing occasional network accesses mostly out to the Internet, so if there are problems, people write it off as their ISP sucking. Realtek ethernet chips are terrible quality. Many of them are not even made by Realtek, but rather by some anonymous knockoff black market manufacturer in Shenzhen and sold in bulk at a cheap price to discount mainboard manufacturers who are looking to shave another dollar off their parts cost. And people wonder why their $50 mainboard sucks. It's the same difference between a Ford Pinto and a Toyota Highlander. It's the details that count, not the four wheels.

You don't need a "high-end main board". What you want is a server mainboard. Because stuff like a high performance ethernet chipset will almost always be included, and only adds a few bucks to the cost of the system, which is probably a better deal than burning a PCIe slot and adding an aftermarket $35 Intel Desktop CT card.

Could a switch from TrueNAS to TrueNAS Scale help with that? Maybe the driver quality on Linux is just a bit better?

The drivers might be different. In general, Realtek provides relatively little (and in many cases no) documentation on their chipsets that would be useful to driver authors, which leaves authors in the position of trying to reverse engineer what should be done. This is not optimal. By way of comparison, your Intel, Chelsio, Solarflare, etc., cards are written by driver teams at those manufacturers who have access to the designs and can talk to the designers of the silicon. This tends to make those drivers much more effective and robust. By way of comparison, the Linux and BSD driver authors often have to snoop around the source code of other open source drivers to benefit from what their peers have discovered. None of the open source Realtek driver authors have access to the entire set of chipsets that their drivers may try to support, so driver quality tends to suffer when compared to Intel where there is an entire R&D division with a lab full of all the Intel parts.

Bill Paul's commentary in the FreeBSD rl driver says a lot:

Code:

/*
 * RealTek 8129/8139 PCI NIC driver
 *
 * Supports several extremely cheap PCI 10/100 adapters based on
 * the RealTek chipset. Datasheets can be obtained from
 * www.realtek.com.tw.
 *
 * Written by Bill Paul <wpaul@ctr.columbia.edu>
 * Electrical Engineering Department
 * Columbia University, New York City
 */
/*
 * The RealTek 8139 PCI NIC redefines the meaning of 'low end.' This is
 * probably the worst PCI ethernet controller ever made, with the possible
 * exception of the FEAST chip made by SMC. The 8139 supports bus-master
 * DMA, but it has a terrible interface that nullifies any performance
 * gains that bus-master DMA usually offers.

Here is what i get form pciconf.
I know these values could be faked, but it's at least something:

What you probably want to do is actually try configuring the interface and see what happens. If we're talking about a knockoff card, there's no reason to believe it will work well (or even at all). Try configuring the interface and seeing if it links, stays linked, and can talk to neighbors on the network. iperf3 and ping are great tools for this.

 

[Steasenburger]

I'm sure that a server mainboard would have been a better choice back then, but now i simply can't afford switching the whole platform for some occasional network issues.
And yes i know that I can't compare my daily usage to a in-depth test of the network chipset, but i've never intended to do so in the first place.
I've just never experienced that there is simply no connection at all to the LAN possible unless you restart the system a few times.
I'm feeling confident enough in my IT/ network skills to differentiate an ISP problem from a problem of my PC/ network card.

But okay, I understand that driver development for Realtek chips is particularly hard (even though the chip that Paul mentioned seems to be another model than my, but it's most likely a general Realtek problem).

Could you maybe elaborate a bit more what you mean by "configuring the interface"?
If it's only setting an IP address, I already have done this when i first booted up the system with the new network card.

I've also tried to do a few tests that you recommended.
I'm not an expert with iperf3 (I just took the first Google result that i found), so if you had any other commands in mind, please feel free to tell me.

Code:

truenas# ping 192.168.0.39
PING 192.168.0.39 (192.168.0.39): 56 data bytes
64 bytes from 192.168.0.39: icmp_seq=0 ttl=64 time=0.126 ms
64 bytes from 192.168.0.39: icmp_seq=1 ttl=64 time=0.147 ms
64 bytes from 192.168.0.39: icmp_seq=2 ttl=64 time=0.132 ms
64 bytes from 192.168.0.39: icmp_seq=3 ttl=64 time=0.141 ms
64 bytes from 192.168.0.39: icmp_seq=4 ttl=64 time=0.123 ms
64 bytes from 192.168.0.39: icmp_seq=5 ttl=64 time=0.127 ms
64 bytes from 192.168.0.39: icmp_seq=6 ttl=64 time=0.128 ms
^C
--- 192.168.0.39 ping statistics ---
7 packets transmitted, 7 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.123/0.132/0.147/0.008 ms
truenas#  iperf3 -c 192.168.0.39 -P 6
Connecting to host 192.168.0.39, port 5201
[  5] local 192.168.0.97 port 52375 connected to 192.168.0.39 port 5201
[  7] local 192.168.0.97 port 57856 connected to 192.168.0.39 port 5201
[  9] local 192.168.0.97 port 58932 connected to 192.168.0.39 port 5201
[ 11] local 192.168.0.97 port 57444 connected to 192.168.0.39 port 5201
[ 13] local 192.168.0.97 port 12363 connected to 192.168.0.39 port 5201
[ 15] local 192.168.0.97 port 55256 connected to 192.168.0.39 port 5201
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  14.3 MBytes   120 Mbits/sec  198    776 KBytes      
[  7]   0.00-1.00   sec  17.6 MBytes   147 Mbits/sec    3   1.51 MBytes      
[  9]   0.00-1.00   sec  39.2 MBytes   329 Mbits/sec    0   3.00 MBytes      
[ 11]   0.00-1.00   sec  23.3 MBytes   195 Mbits/sec    3   1.51 MBytes      
[ 13]   0.00-1.00   sec  11.5 MBytes  96.2 Mbits/sec  509    771 KBytes      
[ 15]   0.00-1.00   sec  16.0 MBytes   135 Mbits/sec  450   1.10 MBytes      
[SUM]   0.00-1.00   sec   122 MBytes  1.02 Gbits/sec  1163            
- - - - - - - - - - - - - - - - - - - - - - - - -
[  5]   1.00-2.00   sec  10.8 MBytes  90.3 Mbits/sec    0    796 KBytes      
[  7]   1.00-2.00   sec  18.1 MBytes   152 Mbits/sec    0   1.52 MBytes      
[  9]   1.00-2.00   sec  37.5 MBytes   315 Mbits/sec    0   3.00 MBytes      
[ 11]   1.00-2.00   sec  19.3 MBytes   161 Mbits/sec    0   1.53 MBytes      
[ 13]   1.00-2.00   sec  10.7 MBytes  90.0 Mbits/sec    0    791 KBytes      
[ 15]   1.00-2.00   sec  15.9 MBytes   133 Mbits/sec    0   1.12 MBytes      
[SUM]   1.00-2.00   sec   112 MBytes   941 Mbits/sec    0            
- - - - - - - - - - - - - - - - - - - - - - - - -
[  5]   2.00-3.00   sec  11.2 MBytes  93.5 Mbits/sec    0    816 KBytes      
[  7]   2.00-3.00   sec  19.2 MBytes   161 Mbits/sec    0   1.54 MBytes      
[  9]   2.00-3.00   sec  37.4 MBytes   314 Mbits/sec    0   3.00 MBytes      
[ 11]   2.00-3.00   sec  18.5 MBytes   155 Mbits/sec    0   1.55 MBytes      
[ 13]   2.00-3.00   sec  10.9 MBytes  91.6 Mbits/sec    0    811 KBytes      
[ 15]   2.00-3.00   sec  15.7 MBytes   132 Mbits/sec    0   1.14 MBytes      
[SUM]   2.00-3.00   sec   113 MBytes   947 Mbits/sec    0            
- - - - - - - - - - - - - - - - - - - - - - - - -
[  5]   3.00-4.00   sec  10.7 MBytes  89.7 Mbits/sec    0    834 KBytes      
[  7]   3.00-4.00   sec  18.7 MBytes   157 Mbits/sec    0   1.56 MBytes      
[  9]   3.00-4.00   sec  37.4 MBytes   314 Mbits/sec    0   3.00 MBytes      
[ 11]   3.00-4.00   sec  18.7 MBytes   156 Mbits/sec    0   1.57 MBytes      
[ 13]   3.00-4.00   sec  11.0 MBytes  92.1 Mbits/sec    0    829 KBytes      
[ 15]   3.00-4.00   sec  15.7 MBytes   131 Mbits/sec    0   1.16 MBytes      
[SUM]   3.00-4.00   sec   112 MBytes   940 Mbits/sec    0            
- - - - - - - - - - - - - - - - - - - - - - - - -
[  5]   4.00-5.00   sec  11.1 MBytes  92.7 Mbits/sec    0    854 KBytes      
[  7]   4.00-5.00   sec  18.7 MBytes   157 Mbits/sec    0   1.57 MBytes      
[  9]   4.00-5.00   sec  37.4 MBytes   314 Mbits/sec    0   3.00 MBytes      
[ 11]   4.00-5.00   sec  18.7 MBytes   157 Mbits/sec    0   1.58 MBytes      
[ 13]   4.00-5.00   sec  10.9 MBytes  91.5 Mbits/sec    0    849 KBytes      
[ 15]   4.00-5.00   sec  15.4 MBytes   129 Mbits/sec    0   1.17 MBytes      
[SUM]   4.00-5.00   sec   112 MBytes   941 Mbits/sec    0            
- - - - - - - - - - - - - - - - - - - - - - - - -
[  5]   5.00-6.00   sec  11.2 MBytes  93.6 Mbits/sec    0    873 KBytes      
[  7]   5.00-6.00   sec  18.6 MBytes   156 Mbits/sec    0   1.59 MBytes      
[  9]   5.00-6.00   sec  37.5 MBytes   314 Mbits/sec    0   3.00 MBytes      
[ 11]   5.00-6.00   sec  18.8 MBytes   158 Mbits/sec    0   1.60 MBytes      
[ 13]   5.00-6.00   sec  10.8 MBytes  90.4 Mbits/sec    0    868 KBytes      
[ 15]   5.00-6.00   sec  15.6 MBytes   131 Mbits/sec    0   1.19 MBytes      
[SUM]   5.00-6.00   sec   112 MBytes   943 Mbits/sec    0            
- - - - - - - - - - - - - - - - - - - - - - - - -
[  5]   6.00-7.00   sec  11.1 MBytes  93.0 Mbits/sec    0    890 KBytes      
[  7]   6.00-7.00   sec  18.5 MBytes   156 Mbits/sec    0   1.61 MBytes      
[  9]   6.00-7.00   sec  37.4 MBytes   313 Mbits/sec    0   3.00 MBytes      
[ 11]   6.00-7.00   sec  18.6 MBytes   156 Mbits/sec    0   1.61 MBytes      
[ 13]   6.00-7.00   sec  11.1 MBytes  93.4 Mbits/sec    0    886 KBytes      
[ 15]   6.00-7.00   sec  15.1 MBytes   127 Mbits/sec    0   1.21 MBytes      
[SUM]   6.00-7.00   sec   112 MBytes   938 Mbits/sec    0            
- - - - - - - - - - - - - - - - - - - - - - - - -
[  5]   7.00-8.00   sec  10.5 MBytes  88.4 Mbits/sec    0    907 KBytes      
[  7]   7.00-8.00   sec  19.1 MBytes   160 Mbits/sec    0   1.62 MBytes      
[  9]   7.00-8.00   sec  37.5 MBytes   314 Mbits/sec    0   3.00 MBytes      
[ 11]   7.00-8.00   sec  18.6 MBytes   156 Mbits/sec    0   1.63 MBytes      
[ 13]   7.00-8.00   sec  11.0 MBytes  92.6 Mbits/sec    0    903 KBytes      
[ 15]   7.00-8.00   sec  15.7 MBytes   132 Mbits/sec    0   1.23 MBytes      
[SUM]   7.00-8.00   sec   112 MBytes   943 Mbits/sec    0            
- - - - - - - - - - - - - - - - - - - - - - - - -
[  5]   8.00-9.00   sec  11.7 MBytes  97.8 Mbits/sec    0    925 KBytes      
[  7]   8.00-9.00   sec  18.0 MBytes   151 Mbits/sec    0   1.64 MBytes      
[  9]   8.00-9.00   sec  37.4 MBytes   314 Mbits/sec    0   3.00 MBytes      
[ 11]   8.00-9.00   sec  19.2 MBytes   161 Mbits/sec    0   1.65 MBytes      
[ 13]   8.00-9.00   sec  10.9 MBytes  91.8 Mbits/sec    0    922 KBytes      
[ 15]   8.00-9.00   sec  15.0 MBytes   126 Mbits/sec    0   1.25 MBytes      
[SUM]   8.00-9.00   sec   112 MBytes   941 Mbits/sec    0            
- - - - - - - - - - - - - - - - - - - - - - - - -
[  5]   9.00-10.00  sec  10.9 MBytes  91.3 Mbits/sec    0    943 KBytes      
[  7]   9.00-10.00  sec  18.9 MBytes   159 Mbits/sec    0   1.66 MBytes      
[  9]   9.00-10.00  sec  37.3 MBytes   313 Mbits/sec    0   3.00 MBytes      
[ 11]   9.00-10.00  sec  18.4 MBytes   155 Mbits/sec    0   1.66 MBytes      
[ 13]   9.00-10.00  sec  10.9 MBytes  91.2 Mbits/sec    0    939 KBytes      
[ 15]   9.00-10.00  sec  15.5 MBytes   130 Mbits/sec    0   1.26 MBytes      
[SUM]   9.00-10.00  sec   112 MBytes   939 Mbits/sec    0            
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.00  sec   113 MBytes  95.0 Mbits/sec  198             sender
[  5]   0.00-10.04  sec   112 MBytes  93.3 Mbits/sec                  receiver
[  7]   0.00-10.00  sec   186 MBytes   156 Mbits/sec    3             sender
[  7]   0.00-10.04  sec   184 MBytes   154 Mbits/sec                  receiver
[  9]   0.00-10.00  sec   376 MBytes   315 Mbits/sec    0             sender
[  9]   0.00-10.04  sec   374 MBytes   313 Mbits/sec                  receiver
[ 11]   0.00-10.00  sec   192 MBytes   161 Mbits/sec    3             sender
[ 11]   0.00-10.04  sec   190 MBytes   159 Mbits/sec                  receiver
[ 13]   0.00-10.00  sec   110 MBytes  92.1 Mbits/sec  509             sender
[ 13]   0.00-10.04  sec   108 MBytes  90.4 Mbits/sec                  receiver
[ 15]   0.00-10.00  sec   156 MBytes   131 Mbits/sec  450             sender
[ 15]   0.00-10.04  sec   154 MBytes   129 Mbits/sec                  receiver
[SUM]   0.00-10.00  sec  1.11 GBytes   950 Mbits/sec  1163             sender
[SUM]   0.00-10.04  sec  1.10 GBytes   938 Mbits/sec                  receiver

iperf Done.
truenas#  iperf3 -c 192.168.0.39
Connecting to host 192.168.0.39, port 5201
[  5] local 192.168.0.97 port 34762 connected to 192.168.0.39 port 5201
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   114 MBytes   956 Mbits/sec    0    970 KBytes      
[  5]   1.00-2.00   sec   112 MBytes   942 Mbits/sec    0   1.10 MBytes      
[  5]   2.00-3.00   sec   112 MBytes   941 Mbits/sec    0   1.23 MBytes      
[  5]   3.00-4.00   sec   112 MBytes   942 Mbits/sec    0   1.35 MBytes      
[  5]   4.00-5.00   sec   112 MBytes   941 Mbits/sec    0   1.47 MBytes      
[  5]   5.00-6.00   sec   112 MBytes   942 Mbits/sec    0   1.57 MBytes      
[  5]   6.00-7.00   sec   112 MBytes   941 Mbits/sec    0   1.66 MBytes      
[  5]   7.00-8.00   sec   112 MBytes   942 Mbits/sec    0   1.76 MBytes      
[  5]   8.00-9.00   sec   112 MBytes   942 Mbits/sec    0   1.84 MBytes      
[  5]   9.00-10.00  sec   112 MBytes   941 Mbits/sec    0   1.93 MBytes      
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.00  sec  1.10 GBytes   943 Mbits/sec    0             sender
[  5]   0.00-10.04  sec  1.10 GBytes   938 Mbits/sec                  receiver

iperf Done.
truenas#

As far as I can tell, there seems to be no problem with the connection.
This corresponds with my experiences: When the connection is up and the interface is working at some point, there are no issues anymore.

By the way, thank you very much for your help and your background information.
I'm really looking for a solution or at least a reasoning for my problem.

 

[jgreco]

I'm sure that a server mainboard would have been a better choice back then, but now i simply can't afford switching the whole platform for some occasional network issues.

Yes, a common problem. I see you've already bought an "Intel" card, and I'm not looking to re-read the entire thread here, but I kind of get the impression it's a knock-off of some sort? Is there any chance you'd be able to find and try a legitimate Intel Desktop CT ethernet card? These are the usual recommendations for problematic mainboards with Realtek.

I've just never experienced that there is simply no connection at all to the LAN possible unless you restart the system a few times.

That's definitely a driver thing that has been discovered by other people. The easier fix is to go onto the console and do "ifconfig re0 down; sleep 5; ifconfig re0 up" which fixes it for a large percentage of users.

I'm feeling confident enough in my IT/ network skills to differentiate an ISP problem from a problem of my PC/ network card.

So when you get this up and running, please do run iperf3 and do some bandwidth testing on your local network. If you've got Realtek on just one end, guessing you see about 750-850Mbps max.

But okay, I understand that driver development for Realtek chips is particularly hard (even though the chip that Paul mentioned seems to be another model than my, but it's most likely a general Realtek problem).

Yes, that was a 10/100 chipset from years ago. I believe Bill Paul was at Columbia when it was written, which might have been a factor in his feeling free to speak his mind. More recently, Bill Paul has moved to Wind River Systems, which does this stuff as a business, and such comments in code might be frowned upon. Nothing I've seen in the years since has convinced me that Realtek has improved, and specific chips like the RTL8111 keep popping up here as tragic problems for TrueNAS users.

Could you maybe elaborate a bit more what you mean by "configuring the interface"?
If it's only setting an IP address, I already have done this when i first booted up the system with the new network card.

I may have lost track of the state of this discussion. Were we discussing the Realtek (re0) or Intel (igb0) card? That screenshot shows the Intel as configured. Unfortunately I don't like the GUI for debugging network issues. The shell prompt usually seems better.

You can set up and verify an interface's config at the shell prompt, like this:

Code:

# ifconfig em0
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=9b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM>
        ether 00:50:56:ab:2c:7d
        hwaddr 00:50:56:ab:2c:7d
        inet 10.64.68.237 netmask 0xfffffe00 broadcast 10.64.69.255
        nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
        media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active

This is an Intel em0 virtual interface (you can tell from the MAC that it's VMware). First, be aware that anything you do here will NOT be saved by TrueNAS and may interfere with operation. But it's useful for testing.

Notice in particular the media and status. You are going to want to inspect and experiment with this for your re0 and igb0 interfaces, referred to hereinafter as xx0.

You can "ifconfig xx0 up" or "ifconfig xx0 down" to put the interface into an administratively up or down state. If there is a physical layer link, doing an "ifconfig xx0 up" and then checking in a few seconds with "ifconfig xx0" should show that the media has autoselected 1000baseT <full-duplex> and that it is active. Once so, you should be able to ping or iperf3 with other hosts on that network. It may also be convenient to add or delete IP configuration. This is "ifconfig xx0 inet 10.64.68.237/23" in the example above or "ifconfig xx0 delete 10.64.68.237" to remove.

It is not a good idea to try to put both interfaces on the same IPv4 network though. This will just be confusing.

iperf3 works on a client and server model, and is available for Windows if need be. Basically you run "iperf3 -s" on the server side (doesn't mean the machine has to be a server) and then "iperf3 -c xx.xx.xx.xx" where xx.xx.xx.xx is the IP of the server side.

By the way, thank you very much for your help and your background information.
I'm really looking for a solution or at least a reasoning for my problem.

Happy to help where I can.

 

[Steasenburger]

iperf3 works on a client and server model, and is available for Windows if need be. Basically you run "iperf3 -s" on the server side (doesn't mean the machine has to be a server) and then "iperf3 -c xx.xx.xx.xx" where xx.xx.xx.xx is the IP of the server side.

All right, that's exactly what I tried in my experiment from above.
The results were even better than you predicted (close to 1000mbit/s).

I may have lost track of the state of this discussion. Were we discussing the Realtek (re0) or Intel (igb0) card? That screenshot shows the Intel as configured. Unfortunately I don't like the GUI for debugging network issues. The shell prompt usually seems better.

You are right, since i already got this (fake?) Intel card, I only use it for the internet connection and not the integrated Realtek one any more.
Here you see the configuration for the igb interface:

Code:

truenas# ifconfig igb0
igb0: flags=8963<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        description: intel
        options=4a520b9<RXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,WOL_MAGIC,VLAN_HWFILTER,VLAN_HWTSO,RXCSUM_IPV6,NOMAP>
        ether 00:1b:22:81:32:e0
        inet 192.168.0.97 netmask 0xffffff00 broadcast 192.168.0.255
        media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active
        nd6 options=9<PERFORMNUD,IFDISABLED>

To me, it seems all fine.

I will try to manually switch the interface from UP to DOWN state using your ifconfig commands the next time when I'm physically at my server's location.
Otherwise, i fear that i will kick out myself from SSH access to the system.
And I will also see what happens when i execute `ifconfig xx0 up` after a reboot when no network connection is possible.