jinlife

Community Developer
  • Posts

    173
  • Joined

  • Last visited

Posts posted by jinlife

  1. 14 hours ago, hoeman said:

     

    Hi, I know I'm an idiot 对不起我傻逼, but I'm trying to follow these instructions but I'm assuming the mac address details and the pci address details are to be filled in by the end-user according to his / her device config, right? So let's say my eth0 mac address is 70:88:6B:8A:17:69 then I should fill the following in:

      

        <interface type='direct'>
          <mac address='70:88:6B:8A:17:69'/>
          <source dev='eth0' mode='vepa'/>
          <model type='virtio'/>
          <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
        </interface>
        <interface type='bridge'>
          <mac address='ANYRANDOMMAC?'/>
          <source bridge='virbr0'/>
          <model type='virtio'/>
          <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/>
        </interface>

     

    Correct? So the direct one points to the actual mac address since source dev='eth0' while the bridge virbr0 I can just fill in any random mac address. Am I right so far? Sorry for being a total noob.

     

    After doing that, what about the pci address entries? I don't know how to fill that out. I left it at the code you gave but it says slot has to be >=1.

     

    Also, does this part "b. the second interface uses the default NAT based virbr0 to connect the Unraid host with an independent subnet. For advanced customizations, you can refer to the libvirt docs[1] and this example guide[3]. Note that the configs are located in /etc/libvirt/qemu/networks but you must use the virsh command to edit them in the command line." mean that VMs are on a different subnet?

    I'm not expert so here is just my experiences, maybe wrong. Most of your expectations are correct.

    1. The MAC for direct interface is the current VM's mac to the outer world. Your router will allocate local network IP to this MAC, such as 192.168.1.105. But please aware Unraid or other VMs cannot access this IP if they share the interface eth0.

    2. Unless you pass through a physical interface eth1 to another VM, then this VM can access 192.168.1.105 directly. Other independent devices can access this IP as well, even from the DDNS.

    3. The MAC for bridge interface is the VM's mac to inner world, this network is only exist in virbr0 which is used between the Unraid and all other VM who is sharing eth0, the IP could be 192.168.122.5. So if you created a Synology VM, and want to add its share in Unraid, you need to use IP 192.168.122.5 or Synology network name.  The MAC can be any one since it only exist in virbr0, it is a super small local subnet. You can use virsh to control it.

    4. PCI is just virtual configuration to VM, if the slot is occupied, then you can just use any other available number.

    So the Synology VM will have two network interfaces, one is direct and another is bridge, it has two IPs, 192.168.1.105 and 192.168.122.5. They have different scope and purpose.

    Hope it answers your question.

     

  2. On 1/9/2023 at 10:48 AM, woodust said:


    image.thumb.png.5d38572cee3b3426d0a2d515e9331d2b.png

     

    有个奇怪的问题。

    机器上有一个板载2.5G网卡,还有一个USB2.5G网卡。

    不装楼主补丁时,USB网卡可直通给群辉,但是不到1天就断网。unraid的setting网络里,看不到usb网卡,所以不能把usb网卡留给unraid做管理口。

    装了楼主补丁后,unraid的setting网络里可以看到usb网卡,改成eth0后,可以作为unraid管理口,但是也是不到1天就断网。如果像截图一样,直通给群辉,群晖里识别不出这个usb网卡。

     

    有没有哪位知道这是什么情况。谢谢。

    USB在Unraid里面使用,是用的Unraid带的驱动。直通到群晖里面用,是用的群晖带的驱动,两边的驱动都得靠谱才行。另外你这个断网,估计有好几个方面的原因:

    1. 群晖里面的驱动不够新,群晖内USB R8156这网卡的bb-qq的套件,也不是蛮灵,经常要重新启动几次套件才行。最好是编译群晖的loader的时候就把R8156的驱动编译进去。不会编译的话,那建议用巴西人的arpl这个loader。

    2. 网卡硬件有问题,有些USB网卡过热就会断网,散热还不好。除了换个品牌的网卡,没什么办法。加风扇都不一定有用,质量问题。

    3. 不要热插拔USB网卡,插好就别动了,重启Unraid和群晖才能正常使用。Unraid对热插拔USB网卡的支持不咋地。

  3. 2 hours ago, GeorgeJetson20 said:

    Does this patch break VM's??   I can't create a VM on my machine that works.  I am able to run VM's that were already created without any problem..   This is a post I made in a different group.   I'm frustrated and not sure what to do next because I never had a problem. 

     

     

    Having the strangest problem trying to add a new VM on a machine I was always able to add VM's until upgrading to 6.9.15.   When I try to start the newly created VM, it just shows the VNC unable to connect screen.  Not sure what I am doing wrong. I tried scrubbing the libvert and rebooted but just not working.  If someone can point me in the correct direction.  The VM's that already existed on here work fine but i have tried on several different SSD's and even leaving it on auto but no luck.   Here is my diagnostics, but you need any other information, i will post that.

    Thanks so much.

     

    Some other helpful info is when I start - I get "NO VNC" and this is the line that browser goes to for VNC...

    http://192.168.0.201/plugins/dynamix.vm.manager/vnc.html?v=1640104829&autoconnect=true&host=192.168.0.201&port=&path=/wsproxy/5701/

     

    phantekone-diagnostics-20221215-1753.zip 121.83 kB · 0 downloads

    This is just a network card patch, it cannot impact VM.

    I think you issue was caused by upgradation to Unraid 6.11.5. (6.9.15?) The web content might be changed for VNC, you need to clear the cached session or data of browser, especially for the google chrome browser.

  4. On 12/9/2022 at 3:52 PM, always67 said:

    大佬,我看到你编译了6.10的内核,能不能编译个6.11.5的呢?我来测试显卡的SR-IOV功能。我看到有人在PVE的5.19内核使用DKMS的方式加载了i915的驱动,直通给Windows 虚拟机成功了。

    Unraid的内核比较难搞的,我拿着那个适配PVE的源代码没编译通过,之前的6.10也有问题。估计要改代码才能编译通过, 一时半会搞不定了。

    想追新还是用PVE吧,Unraid不开源,比较封闭,不好改。等哪天inte库l的代码内核更新上来了可能好改点。

  5. 20 minutes ago, itimpi said:

    If you click on the drive on the Main tab then you can set the spindown delay for that specific drive from the resulting dialog.   This will then precedence over your global setting for spindown on that drive.

    Thanks for reminding, I cannot find this setting, it looks like the setting does not exist for unassigned disk or passed through disk.

     

    This is a normal cache setting:

    image.png.1d6d4d94cf0889c78cae9e6119388006.png

     

    This is unassigned disk Dev 1, all settings are missing.

    image.png.fe857be98650962061315c0479fb5d18.png

  6. Unexpected spin down in Unraid 6.11.5

     

    Scenario:

    1. Insert one Sata SSD and pass through this disk to a Synology VM.

    2. Mark the SSD as passed through in UD settings.

    image.thumb.png.c569cceb71b71e39e99a6c37c80c1b28.png

     

    But Unraid alway spin down this SSD disk intervally and VM will spin it up right away. This is very anony.

    It seems there is no disk activity from Unraid OS, so unraid will spin it down every 15 min (which is my disk setting)

    Is it possible to ignore the spin down of this passed through disk? I have no need to spin it down and just want to keep it running.  Thanks.

    @dlandon

    image.png.3b2f161f8e0d4fe8367b73ecd6d66cbc.png
     

     

  7. 18 hours ago, Jojo1965 said:

    THX, but how do i write to the flash drive?

    Two ways:

    1. Insert Unraid flash drive to Windows PC, then copy the files, just like any other USB disk.

    2. Change flash shared permission to public in Unraid Web, then you can navigate to the shared folder: \\unraid_IP\flash, copy the files.

    But hey, please make sure you need this patch. There is known issue 2 in the first post. You can translate it by google. Thanks.

    • Like 1
  8. 7 hours ago, Jojo1965 said:

    I am a total Noob with Unraid, can someone please explain how to patch the system step by step? 

    THANK YOU!!!

    Just download the patch, extract and overwrite the files in the Unraid USB flash disk, reboot Unraid.

    If you don't like the patch, then overwriting these files again with official ones will recover it, after another reboot.

    • Like 1
  9. 7 hours ago, GeorgeJetson20 said:

     

    UPDATE: End up ordering an Intel 225 card which seems like it will work

     

    (Now that I translated the Chinese to English I understand how to do this now) at first it didn't register

     

    Is there a network card that can be purchased on Amazon that is 2.5gb (or better but supports 2.5gb and will work)  that will work with Unraid?   I would get that if someone can recommend one that will because it's so hard finding something that will work.  My Pluggable USB 2.5gb (Realtek) worked until I upgraded to 6.11.5 (from 6.9.2) and now I am using my motherboard ethernet but it's only 1g and I read thru the outdated hardware list for unraid but it doesn't really help anymore to select a working one.  I read thru here on this thread but i don't think i am good enough on the linux side to understand how to make this work.   

    Intel 225 is a good choice for PCI card although the driver is not stable enough too.

    If you want to use the USB 2.5GB(Realtek) which could be R8156 chip, then it should only work with the patch in this first post. Just download the patch, extract and overwrite the files in the Unraid USB flash disk, reboot Unraid. It seems Unraid has dropped support for the R8156 for the new version although 6.9.2 already support it.

  10. 这个问题挺严重,专门查了下。恢复数据最好不能有格式化硬盘,rebuild就行了。不知道是不是格式化硬盘的原因,可以按如下步骤再试试。

     

      https://wiki.unraid.net/Replacing_a_Data_Drive

    1. Stop the array
    2. Unassign the old drive if still assigned (to unassign, set it to No Device)
    3. Power down
    4. [ Optional ] Pull the old drive (you may want to leave it installed for Preclearing or testing)
    5. Install the new drive
    6. Power on
    7. Assign the new drive in the slot of the old drive
    8. Go to the Main -> Array Operation section
    9. Put a check in the Yes, I'm sure checkbox (next to the information indicating the drive will be rebuilt), and click the Start button
    10. The rebuild will begin, with hefty disk activity on all drives, lots of writes on the new drive and lots of reads on all other drives
    All of the contents of the old drive will be copied onto the new drive, making it an exact replacement, except possibly with more capacity than the old drive.
    
    1.停止阵列
    2.如果仍然分配旧盘,则取消分配(取消分配,将其设置为无设备)
    3. 断电
    4. [ 可选 ] 拉出旧盘(您可能希望保留它安装以进行预清除或测试)
    5.安装新盘
    6.开机
    7.在旧盘的插槽中分配新盘
    8. 转到 Main -> Array Operation 部分
    9. 勾选 Yes, I'm sure 复选框(在指示将重建驱动器的信息旁边),然后单击 Start 按钮
    10. 重建将开始,所有驱动器上的大量磁盘活动,新驱动器上的大量写入和所有其他驱动器上的大量读取
    旧驱动器的所有内容都将复制到新驱动器上,使其成为完全替代品,但容量可能比旧驱动器大。

     

  11. 17 hours ago, ukiyoec said:

    🥲不好意思说错了。。是x4……也就是第二根全长pcie的位置,和m.2_2共用的x4好像,应该都是被分在PCH里同一个分组。。

    估计悬,这两硬件上就是共享的,如果补丁分不开那就是不支持了。迫击炮这个共享带宽的设计挺坑,建议用华擎或华硕的主板组NAS。

    迫击炮可以插第一个插槽,用VM的DownStream模式,也可以网卡分组。

  12. On 10/7/2022 at 6:53 PM, yulu_2000 said:

    6.11.1版r8125和r8152网卡驱动补丁貌似有问题,我覆盖原文件后重启unRaid阵列无法启动了,原文件重新覆盖回去后一切正常!之前几个版本的补丁我一直都用的很好,就最新的这个不行,麻烦楼主检查一下吧。

    额,官方貌似加了什么限制,不好随便换文件了。这个得花时间调查了。。。等有空吧。要么继续用老的,新的也没啥新功能。

    还有个妥协的办法就是先在原始文件里面将阵列启动好,生成阵列配置文件之后,再替换补丁重启看看,貌似补丁不支持新阵列配置的创建,官方有某些检查md版本的限制?

    可以试试。一般硬盘阵列配置也不会常换的。

     

  13. 原生的Unraid对R8125和R8156支持都不好,否则我也不用出这个补丁了。 官方好像也没意愿改进,说是等下个可以支持自定义驱动的Unraid版本,不知道啥时候出来。现在市面上好多主流主板都自带R8125网口了,都在玩2.5G网速,关键时刻缺驱动。

     

    补丁版本不要混用。要是能混用,我干嘛还分别出6.10和6.9的补丁。这些版本的Linux内核版本都不一样的,用可能碰巧能用,但是很可能会有bug。最好用对应版本的补丁才会稳定。

    6.11.0补丁正在制作中。