[[6.12.3] VM Getting Multiple MAC Addresses]

Just now, Tucubanito07 said:

So, this is normal and there is no way to tell Unraid to treat it as one nic for the VM so the switch does not think is multiple devices on the same port?

As mention, I haven't those NIC, so no much help can provide.

[[6.12.3] VM Getting Multiple MAC Addresses]

7 minutes ago, Tucubanito07 said:

I will leave it like this for a while to see if it falls off. However, how can we make this work with the pcie two port nic card? That port I have a different used for it. 

I haven't those multiple port / controller NIC, it have some different behavior if compare to general NIC, but this also work with Unraid.

Mutliple MAC on a switch port not a problem.

 

If you have 10G NIC ( because sufficient BW ), you don't need separate different thing to different NIC, but this need VLAN to isolate those stuff. 

[[6.12.3] VM Getting Multiple MAC Addresses]

AQC107 70:85:c2:bf:38:08 have connect to port 6 before, after aging time it will remove from the switch. If no more duplicate mac on VM port ( #7 ), then it should solve your org. question.

 

If AQC107 70:85:c2:bf:38:08 show on port 7, it still normal.

[[6.12.3] VM Getting Multiple MAC Addresses]

 

But why 00:07:43 Chelsio Communications instead AQC107 ?

 

[[6.12.3] VM Getting Multiple MAC Addresses]

On 9/3/2023 at 9:49 PM, Tucubanito07 said:

Also, on this screenshot you can see that it says three machines, but only two got IP addresses, however, the connection switch port #7 is correct but no IP address.

 

 

Pls note I never touch your router / switch part, because according previous post, the VM ( br2 ) was connect to port #7. Pls understand the test are use same setting, just only change the eth2 ( br2 ) to use AQC107 NIC.

[[6.12.3] VM Getting Multiple MAC Addresses]

15 minutes ago, Tucubanito07 said:

Now the VM is not getting an IP address. See below.

Does eth2 connect to port #7, btw no problem on network setting.

[[6.12.3] VM Getting Multiple MAC Addresses]

Just now, Tucubanito07 said:

Do you mean set this Interface eht2: to Atlantic on the Interface rules? @Vr2Io

 

 

Yes

[[6.12.3] VM Getting Multiple MAC Addresses]

Already set AQ107 be eth2 ? What those MAC are ?

[[6.12.3] VM Getting Multiple MAC Addresses]

3 minutes ago, Tucubanito07 said:

So you want me to place it back to BR2 and see if the multiple MAC address happens and multiple IPs?

Yes, if you insist one MAC and IP ( VM )  in standalone switch port i.e. #7, set eth2 ( br2 ) to use AQC107, VM use br2.

[[6.12.3] VM Getting Multiple MAC Addresses]

Pls found I have edit the post.

[[6.12.3] VM Getting Multiple MAC Addresses]

For ping issue, Windows firewall default were disable , pls check does this is the case.

 

For still found two different MAC, it show 70:85:C2 is Asrock physical NIC ( eth0 ), so you have add it to VM actually. Pls check VM XML.

Due to it is Unraid eth0, so it is normal. ( And I think two MAC problem already gone )

 

If you want further prove this, you need use Aquantia Corp. AQC107 be eth2 ( br2 ) to test again.

 

[[6.12.3] VM Getting Multiple MAC Addresses]

6 hours ago, Tucubanito07 said:

One of them is the Unraid IP address and Docker containers. I want that VM on a different subnet so I can controlled the traffic on that VM.

Understand that, the test is to identify the problem source. Virtual NIC won't change MAC address self, but I notice you have some call trace relate GPU, this may cause problem too.

[[6.12.3] VM Getting Multiple MAC Addresses]

# PCI device 0x1d6a:0x07b1 (atlantic)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="70:85:c2:bf:38:08", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

 

# PCI device 0x1425:0x4409 (cxgb4)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:07:43:17:13:d0", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"

 

Try swap eth1 & eth2, so, Aquantia Corp. AQC107 be eth2 ( br2 ), of course, you need connect it to switch port #7 too.

 

Or more simple, change VM NIC using br0 ( then IP will be 10.10.1.43/24 ) and check back same problem happen or not.

 

Why try not use Chelsio NIC, because it have multiple ethernet controller.

 

0f:00.0 Ethernet controller [0200]: Chelsio Communications Inc T420-BT Unified Wire Ethernet Controller [1425:4009]
    Subsystem: Chelsio Communications Inc T420-BT Unified Wire Ethernet Controller [1425:0000]
    Kernel driver in use: cxgb4
    Kernel modules: cxgb4
0f:00.1 Ethernet controller [0200]: Chelsio Communications Inc T420-BT Unified Wire Ethernet Controller [1425:4009]
    Subsystem: Chelsio Communications Inc T420-BT Unified Wire Ethernet Controller [1425:0000]
    Kernel driver in use: cxgb4
    Kernel modules: cxgb4
0f:00.2 Ethernet controller [0200]: Chelsio Communications Inc T420-BT Unified Wire Ethernet Controller [1425:4009]
    Subsystem: Chelsio Communications Inc T420-BT Unified Wire Ethernet Controller [1425:0000]
    Kernel driver in use: cxgb4
    Kernel modules: cxgb4
0f:00.3 Ethernet controller [0200]: Chelsio Communications Inc T420-BT Unified Wire Ethernet Controller [1425:4009]
    Subsystem: Chelsio Communications Inc T420-BT Unified Wire Ethernet Controller [1425:0000]
    Kernel driver in use: cxgb4
    Kernel modules: cxgb4
0f:00.4 Ethernet controller [0200]: Chelsio Communications Inc T420-BT Unified Wire Ethernet Controller [1425:4409]
    Subsystem: Chelsio Communications Inc T420-BT Unified Wire Ethernet Controller [1425:0000]
    Kernel driver in use: cxgb4
    Kernel modules: cxgb4
0f:00.5 SCSI storage controller [0100]: Chelsio Communications Inc T420-BT Unified Wire Storage Controller [1425:4509]
    Subsystem: Chelsio Communications Inc T420-BT Unified Wire Storage Controller [1425:0000]
0f:00.6 Fibre Channel [0c04]: Chelsio Communications Inc T420-BT Unified Wire Storage Controller [1425:4609]
    Subsystem: Chelsio Communications Inc T420-BT Unified Wire Storage Controller [1425:0000]
0f:00.7 Ethernet controller [0200]: Chelsio Communications Inc Device [1425:0000]
    Subsystem: Chelsio Communications Inc Device [1425:0000]

[[6.12.2] Formatted Cache drive to zfs now SMART report showing errors]

Did this occur due to the formatting of the drives or the new zfs format?

> No.

 

Only sdp got error, as not "Uncorrectable", pls perform read verify and check any file have corrupt.

 

ID# ATTRIBUTE_NAME          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
  5 Reallocated_Sector_Ct   PO--CK   099   001   010    Past 4
  9 Power_On_Hours          -O--CK   088   088   000    -    57775
 12 Power_Cycle_Count       -O--CK   095   095   000    -    4705
177 Wear_Leveling_Count     PO--C-   001   001   000    -    3996
179 Used_Rsvd_Blk_Cnt_Tot   PO--C-   099   001   010    Past 4
181 Program_Fail_Cnt_Total  -O--CK   100   100   010    -    0
182 Erase_Fail_Count_Total  -O--CK   100   100   010    -    0
183 Runtime_Bad_Block       PO--C-   099   001   010    Past 4
187 Uncorrectable_Error_Cnt -O--CK   100   100   000    -    0
190 Airflow_Temperature_Cel -O--CK   073   045   000    -    27
195 ECC_Error_Rate          -O-RC-   200   200   000    -    0
199 CRC_Error_Count         -OSRCK   100   100   000    -    0
235 POR_Recovery_Count      -O--C-   099   099   000    -    1823
241 Total_LBAs_Written      -O--CK   099   099   000    -    419824524767

[[6.12] Networking not working correctly after upgrading to 6.12 and changing docker to ipvlan]

 

You can resolve bbc.co.uk, pls try ping the router 192.168.1.254.

 

If ping bbc.co.uk still fail, try reboot router.

Or try disable docker "host access", because there may be "shim" network + your router + 6.12 have issue.

[ZFS write speed issue (array disk, no parity) on 6.12.0-rc6]

Sound interesting, performance drop half, I use Btrfs no such issue.

[[6.11.5 - 6.12.0] Docker is Maxing out CPU and Memory, Triggering `oom-killer`]

Right, you run docker in storage not RAM, so something ( may be individual docker ) cause OOM. 

[[6.11.5 - 6.12.0] Docker is Maxing out CPU and Memory, Triggering `oom-killer`]

22 hours ago, Ryonez said:

The system when running steady uses 60% of 25GB of ram.

 

22 hours ago, Ryonez said:

And this wasn't an issue with the set of containers I was using until the start of this month. 

 

Diskover ( indexing ) may use up all memory suddenly. Once OOM happen, system crash also expected. I run all docker in /tmp ( RAM ), even CCTV's recording, as memory usage really steady so haven't trouble.

 

Try below method to identify which folder will use up memory and best map out to a SSD.

 

 

[Disks Spinning Up (For no reason).]

I haven't problem on SAS3008 chips or microsemi hba. ( 6.11.5 )

 

May be try disable storage OptROM or interrupt 19 capture at BIOS. At least I always disable those and haven't random spinup issue.

 

To eliminate OS/plugin relate, I recommend use another USB to install fresh Unraid, just keep array stop and click spin down then check any disk will spinup self.

[[6.11.2] Complete Unraid Server Freeze-up]

Good sign 👍

[[6.11.2] Complete Unraid Server Freeze-up]

9 hours ago, Kendel said:

It does seem odd that the server seems to keep churning along while the parity check is in progress (which takes about 1-1/2 days) and than it fails several hours later while the system is idle.  Something going to sleep??

 

Almost same symptom have found in 1st gen Ryzen due to CPU enter idle ( low power state ), but this can fix by disable C6 power management in BIOS. You may try similar setting in BIOS.

 

I have Intel 3rd gen, may be I can make some test on it.

 

Edit : No problem in idle for 9hr uptime ( 6.11.5 , 3570K no VT-d )

 

[[6.11.2] Complete Unraid Server Freeze-up]

May be try disable SMT then VT-x / Vt-d

[Disk wont stay spun down - i am 99.9 % sure its SMART - not a plugin, docker or vm]

On 9/12/2022 at 4:58 PM, Michael H said:

so as i said, its not my raid controller (although i completely agree they can be bothersome)

Like others mentions, raid controller may be the issue and I also agree that. Seems you only have 3 data disk, could you try connect disks to onboard SATA to bypass the RAID controller for troubleshoot ?

 

I use Unarid several yrs ( up to 6.10 didn't try 6.11 ), spindown usually work well with onboard SATA or LSI HBA. Below is one of 7x24 Unraid, basically it only spinup once per day. ( Other spinup just because I access it )

 

[[unRAID 6.10.0-rc1] - emhttpd: read SMART events keep spinning up array disks]

7 hours ago, moguiyu said:

so i wonder if it is disk controller compatability issue?

Depends on the controller model and type, i.e. HBA or RAID controller, does Toshiba 1T oemed and other disks connect to same controller ?

You should provide diagnostic.

[[unRAID 6.10.0-rc1] - emhttpd: read SMART events keep spinning up array disks]

15 hours ago, moguiyu said:

This solution unfortunately did not help us which i tried twice before: turn off both the docker and VM then triggered the mover, but the disks are still read smart.

i also used all these 3 apps to track, there is no sign of disk use or file read.

Or any plugin continue reading array disk ? What disk controller use ? Any disk in USB ?

If array in maintenance mode, does wakeup in same ?