EU Gigabyte Mainboard MC12-LE0 Re1.0 AMD B550 AM4 Ryzen

Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
A

azzurro

New Member
Nov 9, 2023
13
4
3
Hey did anyone experience the issue that the onboard NICs swap places between reboots in TrueNAS Scale?
enp7s0 is configured for management and connected with a cable, I reboot, suddenly enp8s0 is connected instead (but unconfigured).
If I move the cable to the other NIC, I can reach management flawlessly. If I instead reboot once again, NICs swap places again and enp7s0 is connected again and everything works as if nothing ever happened.

I feel like this behavior started, after I had installed an AMD RX560 card via M.2 to PCIe riser adapter (connected to the onboard M.2 slot) and after configuring/enabling IOMMU.
 
A

azzurro

New Member
Nov 9, 2023
13
4
3
Oilyplugs said:
If it's called enp* and not eth* it already uses udev pcie matching. Something is off
Click to expand...
yeah. I managed to create udev rules via midclt, since I didn't know enp* means udev already and what I found out in the process is, that the MAC addresses don't even move! enp7s0 and enp8s0 always keep their MACs but the link moves anyway between the two. wtf o_O

I first disabled the 2nd NIC in BIOS now, which matches to enp7s0. Result: TrueNAS came up without any of the two NICs, no management possible (according to "ip address" neither enp7s0 nor enp8s0 existed).

Now I reenabled the 2nd NIC and disabled the first NIC and now there is one interface, enp8s0, present, available and connected, even across reboots.
What the heck, man.

For reference, the midclt command I used to create the UDEV rule:

Code: 
midclt call tunable.create '{"type": "UDEV", "var": "70-network.rules", "value": "SUBSYSTEM==\"net\", ATTR{address}==\"d8:5e:d3:6f:d6:47\", NAME=\"enp7s0\"\nSUBSYSTEM==\"net\", ATTR{address}==\"d8:5e:d3:6f:d6:48\", NAME=\"enp8s0\""}'
This command queries all existing tunables:
Code: 
midclt call tunable.query
This one deletes a tunable with id <id>
Code: 
midclt call tunable.delete <id>
 
S

SlowmoDK

Active Member
Oct 4, 2023
211
130
43
It's a very known issue on TrueNAS Scale and Proxmox just to name a few .. that when u change out hardware names for NIC's change

boot/reach a console of any sort and fix from there :)
 
  • Like
Reactions: helskor
A

Alloc

New Member
Jan 10, 2025
1
0
1
Hi, I have recently upgraded from a SuperMicro board with BMC to this one. Now I'd like to use SNMP to monitor some basic sensor readings like I did before. Does anybody know where I can get the MIB file for the board? Google brought neither specific results for this board nor generic ones for Gigabyte boards in general on this subject. I would be really happy if anybody had any hints :)
 
O

osvii

New Member
Oct 27, 2024
14
1
3
Hello
So i shut off the PC last nigh, and when i try to turn it on, to access TrueNas it just sits there and restarts after a few seconds.
Even if i try to press F2 or F10 nothing happens, or if it register the command it says please wait and the it restarts again.
What could be the issue?
 

Attachments

S

smakkerlak

New Member
Aug 30, 2019
15
9
3
osvii said:
Hello
So i shut off the PC last nigh, and when i try to turn it on, to access TrueNas it just sits there and restarts after a few seconds.
Even if i try to press F2 or F10 nothing happens, or if it register the command it says please wait and the it restarts again.
What could be the issue?
Click to expand...
If it only boots once or twice after powering on, it could be the battery. Check the P_VBAT_SCALED sensor in ipmi. It should be around 3.2 volts and will have a sensor warning about going low if it is not good anymore.
If it's dead, you need a new CR2032 cell. Make a note of its orientation before you take out the old one, it seems easy to install the wrong way around. Reset bios with a jumper after and redo bios settings.
 
O

osvii

New Member
Oct 27, 2024
14
1
3
smakkerlak said:
If it only boots once or twice after powering on, it could be the battery. Check the P_VBAT_SCALED sensor in ipmi. It should be around 3.2 volts and will have a sensor warning about going low if it is not good anymore.
If it's dead, you need a new CR2032 cell. Make a note of its orientation before you take out the old one, it seems easy to install the wrong way around. Reset bios with a jumper after and redo bios settings.
Click to expand...
It boots indefinitely.
When i go to sensors on IPMI P_VBAT_SCALED is listed on Disabled sensors
 
S

smakkerlak

New Member
Aug 30, 2019
15
9
3
osvii said:
It boots indefinitely.
When i go to sensors on IPMI P_VBAT_SCALED is listed on Disabled sensors
Click to expand...
Check the battery with a multimeter or just replace it, they are cheap. That sensor should as far as i know show the battery voltage, and these boards have been in storage for quite a while. My theory is that your board might be syncing bios settings with ipmi over and over again because there is no battery to remember the data between boots. There might be a message briefly before reboots that says something about syncing settings.

Not ruling out other stuff but this is a quick and easy fix :)
 
T

tiberio87

New Member
Jun 25, 2024
13
1
3
Hi guys, I have a problem with this motheboard. I'm trying to update the BIOS and the BCM, from the IPMI it gives the usual error so I'm following this one: guide My card when I'm in the UEFI shell doesn't recognize the USB pen either in FS0: or in FS1: but from the bios the pen is recognized. The USB pen is formatted in FAT32.
 
R

RolloZ170

Well-Known Member
Apr 24, 2016
6,941
2,142
113
tiberio87 said:
Hi guys, I have a problem with this motheboard. I'm trying to update the BIOS and the BCM, from the IPMI it gives the usual error so I'm following this one: guide My card when I'm in the UEFI shell doesn't recognize the USB pen either in FS0: or in FS1: but from the bios the pen is recognized. The USB pen is formatted in FAT32.
Click to expand...
"Once you are in the UEFI Shell, take a look at the file systems available. "
provide the screen you see please.
maybe a look on it and you see which FSx: your drive is
 
You must log in or register to reply here.
Top Bottom