Jump to content

bonienl

Community Developer
 View Profile  See their activity

  • Posts

    10,233

  • Joined

  • Last visited

  • Days Won

    65

 Content Type 

Report Comments posted by bonienl

    [6.10.0-rc4] NVMe device name changed after upgrading

    in Prereleases

    Posted

    Quote

     

    after resetting the pool and starting the array the device mounts but it continues to show the device as "new"

     

     

    This happens because the internal code of Unraid creates the device ID based on the fields given by udevadm, but this doesn't correspond anymore with the symlink (which has a now double underscore in it), hence it "thinks" it doesn't exist and is new...

     

    [6.10.0-rc4] NVMe device name changed after upgrading

    in Prereleases

    Posted

    The file udev-rules.c has the function "get_key" which retrieves the key. Inside this function leading spaces are/should be stripped.

    Quote

     

    /* skip whitespace */

    while (isspace(linepos[0]) || linepos[0] == ',')

        linepos++;

     

     

    I believe "isspace" comes from a standard library, but no clue which library. Perhaps a problem here?

     

    Quote

    Where does it do that?

    See this PR (it was made 5 years ago)

    https://github.com/eudev-project/eudev/commit/5c39ec9686eb737fc012e4553b820c3ff656d446

    [6.10.0-rc4] NVMe device name changed after upgrading

    in Prereleases

    Posted

    eudev rules concatenate {ID_MODEL}_{ID_SERIAL_SHORT} to create {ID_SERIAL} and the subsequent symlink.

     

    It looks like the leading spaces in the ID_SERIAL_SHORT field are not removed, and replaced by an underscore (eudev by default replaces spaces by an underscore in the symlink).
      

    # /sbin/udevadm info -q property -n /dev/nvme3n1
DEVLINKS=/dev/disk/by-id/nvme-Samsung_SSD_970_EVO_1TB_S5H9NS0NB15476D /dev/disk/by-id/nvme-eui.0025385b01410415
DEVNAME=/dev/nvme3n1
DEVPATH=/devices/pci0000:00/0000:00:03.3/0000:07:00.0/nvme/nvme3/nvme3n1
DEVTYPE=disk
DISKSEQ=20
ID_MODEL=Samsung SSD 970 EVO 1TB
ID_PART_TABLE_TYPE=dos
ID_SERIAL=Samsung SSD 970 EVO 1TB_S5H9NS0NB15476D
ID_SERIAL_SHORT=S5H9NS0NB15476D
ID_WWN=eui.0025385b01410415
MAJOR=259
MINOR=4
SUBSYSTEM=block
USEC_INITIALIZED=32096967

     

    Note the spaces in the ID_SERIAL fields, which are replaced by underscore in the symlink.

     

    I remember my old Micron SSD disks had the same issue with leading spaces in the name, but these were all removed.

    Looks like a later commit to eudev introduces this issue.

     

     

    avahidaemon causing slow DNS Resolution

    in Prereleases

    Posted

    Quote

    What is mDNS doing and why is it causing ping name resolution to fall over?

     

    Avahi is a system which facilitates service discovery on a local network via the mDNS/DNS-SD protocol suite. This enables you to plug your laptop or computer into a network and instantly be able to view other people who you can chat with, find printers to print to or find files being shared. Avahi is primarily targeted at Linux systems.

     

    Avahi interacts with DNS to do name resolution for local devices. In case this is not needed, e.g. no additional linux PCs are hot-plugged in your LAN network, you can disable the service by editing the file share.cfg in the /config folder on your USB device and set 

    shareAvahiEnabled="no"


    After saving the file, reboot the system to make the setting active.

    Note: this is not a true resolution of the problem you observed, but more a workaround which avoids the problem.

     

    Mellanox SFP+ NIC duplicate Mac address

    in Prereleases

    Posted

    Edit the file network-rules.cfg on your USB device in the folder /config and remove the line referring to eth4

     

    # PCI device 0x15b3:0x1003 (mlx4_core)
    SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="e4:1d:2d:08:87:90", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth4"

     

    Save the file and restart your system, please post diagnostics afterwards.

     

    Ps. Dual MAC addresses give conflicts and are not allowed.

     

×
×
  • Create New...