jinlife

Community Developer
  • Posts

    173
  • Joined

  • Last visited

Posts posted by jinlife

  1. On 8/13/2021 at 8:08 AM, jinlife said:

    Good to know that. Thanks guys. 

    The script is good for old Unraid versions. I will try the new command. Thanks again.

     

    Just add some comments here, in case someone has same requirement, I want to spindown my NTFS formated USB HDD mounted by UHD plugin.

    1.  Unraid 6.8.x with this script, it works, but it will spinup by Unraid after 20~30 minutes later. No log at all.

    2. Unraid 6.9.2, no need to use this script. Unraid will manage USB HDD automatically, including Array and Unassigned disk. But it will spinup USB HDD after 20~30 minutes with log "emhttpd: read SMART". Looks like tons of complaints in the forum with no solution but revert back to 6.9.1

    3. Unraid 6.9.1, just works like 6.9.2 but it won't spinup USB HDD, it is the perfect solution to me now.

     

    • Like 1
  2. Bad news, it still work like before even disabled the power management.

    Run this script and disk will spin down, but the standy mode will only last for 20~30 minutes, then it will spin up unexpectly, then the script will spin down it again... There is no log in syslog. 

  3. I use the script to spin down the disk and the disk was also unmounted before, so there should be no activity on the disk. But it always spin up unexpectedly, so even I scheduled to run the script every hour, the disk is always awaken.  It is endless loop: up, down, up, down ...

    I will try to disable power management and get back to you about the result. Really appreciate for the help.

  4. On 7/31/2021 at 11:52 PM, 不务正业橘 said:

    之前创建了一些docker,投入了很多精力进行配置,这个可以继承下来吗?

    Docker的配置存在U盘里面。你从U盘的Config目录拷贝出来就行了。 还有appdata也可以备份下来直接用。

    那些占空间的镜像什么的重新下载就行了。

     

    建议可以先做个6.9.2的U盘,然后把config目录替换成6.7.2的看看能不能自动升级,不能那就按二楼的做了。

  5. On 8/2/2021 at 8:06 PM, mgutt said:

    This is really confusing. If you start a VM with the "virtio" network adapter it starts QEMU with the "virtio-net-pci" NIC:

    
    -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:99:b8:93,bus=pci.0,addr=0x3 \

     

    By using "virtio-net" it starts QEMU with the "virtio-net" NIC:

    
    -device virtio-net,netdev=hostnet0,id=net0,mac=52:54:00:99:b8:93,bus=pci.0,addr=0x3 \

     

    But "virtio-net" is not part of the supported NICs?!

    
    qemu -nic model=help
    Supported NIC models:
    e1000
    e1000-82544gc
    e1000-82545em
    e1000e
    i82550
    i82551
    i82557a
    i82557b
    i82557c
    i82558a
    i82558b
    i82559a
    i82559b
    i82559c
    i82559er
    i82562
    i82801
    ne2k_pci
    pcnet
    rtl8139
    tulip
    virtio-net-pci
    virtio-net-pci-non-transitional
    virtio-net-pci-transitional
    vmxnet3

     

    And now the super confusing part:

    
    qemu -device help
    ...
    Network devices:
    name "e1000", bus PCI, alias "e1000-82540em", desc "Intel Gigabit Ethernet"
    name "e1000-82544gc", bus PCI, desc "Intel Gigabit Ethernet"
    name "e1000-82545em", bus PCI, desc "Intel Gigabit Ethernet"
    name "e1000e", bus PCI, desc "Intel 82574L GbE Controller"
    name "i82550", bus PCI, desc "Intel i82550 Ethernet"
    name "i82551", bus PCI, desc "Intel i82551 Ethernet"
    name "i82557a", bus PCI, desc "Intel i82557A Ethernet"
    name "i82557b", bus PCI, desc "Intel i82557B Ethernet"
    name "i82557c", bus PCI, desc "Intel i82557C Ethernet"
    name "i82558a", bus PCI, desc "Intel i82558A Ethernet"
    name "i82558b", bus PCI, desc "Intel i82558B Ethernet"
    name "i82559a", bus PCI, desc "Intel i82559A Ethernet"
    name "i82559b", bus PCI, desc "Intel i82559B Ethernet"
    name "i82559c", bus PCI, desc "Intel i82559C Ethernet"
    name "i82559er", bus PCI, desc "Intel i82559ER Ethernet"
    name "i82562", bus PCI, desc "Intel i82562 Ethernet"
    name "i82801", bus PCI, desc "Intel i82801 Ethernet"
    name "ne2k_isa", bus ISA
    name "ne2k_pci", bus PCI
    name "pcnet", bus PCI
    name "rocker", bus PCI, desc "Rocker Switch"
    name "rtl8139", bus PCI
    name "tulip", bus PCI
    name "usb-net", bus usb-bus
    name "virtio-net-device", bus virtio-bus
    name "virtio-net-pci", bus PCI, alias "virtio-net"
    name "virtio-net-pci-non-transitional", bus PCI
    name "virtio-net-pci-transitional", bus PCI
    name "vmxnet3", bus PCI, desc "VMWare Paravirtualized Ethernet v3"

     

    I highlight it:

    
    name "virtio-net-pci", bus PCI, alias "virtio-net"

     

    Only an alias?! Doesn't make sense at all.

     

    EDIT: Ok, I finally understood the magic behind "virtio-net". It is really only an alias of "virtio-net-pci"! No joke.

     

    The only difference is that "virtio-net" removes the "vhost=on" flag:

     

    virtio-net

    
    -netdev tap,fd=33,id=hostnet0 \
    -device virtio-net,netdev=hostnet0,id=net0,mac=52:54:00:99:b8:93,bus=pci.0,addr=0x3 \

     

    virtio

    
    -netdev tap,fd=33,id=hostnet0,vhost=on,vhostfd=34 \
    -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:99:b8:93,bus=pci.0,addr=0x3 \

     

    And it's absolutelly logic that this causes a bad performance as QEMU then creates an internal "virtio-net device":

    https://www.usenix.org/sites/default/files/conference/protected-files/srecon20americas_slides_krosnov.pdf

    image.png.37d1ad18c9d35c2794ff31b27f2df9c1.png

     

    Instead of sharing the memory with the host:

    image.png.fe341fc7233dacf2e56bf41f2cfe8255.png

     

    A good write-up can be found here:

    https://insujang.github.io/2021-03-15/virtio-and-vhost-architecture-part-2/

     

    And now we understand the help text as well:

     

     

    Not sure about the stability thing, but if the Guest supports it, I would use "virtio", which enables vhost. As I think the names of the adapters are confusing I opened a bug report:

     

    Great research, but I'm also super confused that why virtio-net act like a 1G network, but virtio is 10G network. Just same feeling as in the first post.

    Why is there so big difference for the speed since it is just a alias?  Can we make it work like a 10G network?

  6. 这个 https://raw.githubusercontent.com/Squidly271/community.applications/master/plugins/community.applications.plg 都需要翻墙。

    最好弄个Gitee的链接。

    估摸着Unraid也不好解决这个问题,raw.githubusercontent.com 都被防火墙禁了,很多开源应用都在这上面,这种开源社区代码都访问不了,只能说防火墙太厉害了。

  7. On 5/22/2021 at 11:44 PM, hkcharles said:

    最新版的6.9.2已经集成最新的驱动了。速度还是那样,不管是单硬盘写入还是加装SSD缓存读取都是50+,写入20+

    Unraid驱动有2.5G Intel i225的吗。 另外还有Windows的网卡驱动。先排除Unraid和Windows电脑两边各自驱动的问题。

    换了新硬件,大概率是驱动问题。 

    换个千兆网卡,千兆线看看能跑到100MB不,千兆的驱动问题少点。可以找个千兆USB网卡试试。

  8. Unraid校验盘就是慢,直接访问是只有几十M。这个是Unraid自身特点造成的,无解。 

    如果为了安全,必须要校验盘,那最好弄个固态硬盘做缓存盘,半夜自动Move,让缓存盘和校验数据盘打交道。

    或者去掉校验盘,都是数据盘好了。

  9. 最低开销的做法是可以用开源的bypy脚本,然后在CA User script插件里面定时调用 bypy syncup功能。

    https://github.com/houtianze/bypy

     

    bypy是python脚本,需要先安装NerdPack插件,然后在NerdPack里面安装Python运行时环境。 这种方法无需装虚拟机,不会影响硬盘休眠

     

    如果硬件性能比较强劲,建议用2楼的做法。不过有可能硬盘无法休眠。

     

    • Like 1