IST QIAN

Transition Members
  • Content Count

    10
  • Joined

  • Last visited

  • Days Won

    1

IST QIAN last won the day on August 9

IST QIAN had the most liked content!

Community Reputation

2 Neutral

About IST QIAN

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Since FreeBSD's bhyve hypervisor didn't provide SMART for RDM, There a patch for this. You can specify SMART Info of Host's disk to virtual AHCI disk. that will make DSM recognize it. You can get the patch here: https://reviews.freebsd.org/D25975 Without patch and specify passthrough SMART device, DSM cannot tell SMART. After Patch and sepecify a SATA SSD as the passthrough device. here is the SMART result. Since my M2 SSD is not in SMART database, the attribute are not showing correctly.
  2. IST QIAN

    NVMe cache support

    Hi guys. I make two nvme emu disk for ds918+, and it works. Thank you very much.
  3. 通过你的描述,无法准确判断问题所在。 你这个问题需要进行排查。方法大致如下: 1. 首先需要判断系统是否支持你的网卡。这个可以登陆控制台(开启SSH),然后通过dmesg这个命令来看看网卡是否正常加载驱动。 万兆网卡有很多型号,芯片各不相同。原装的DSM并没有包含很多驱动。论坛中有extra驱动,可以看看是否支持你的网卡。 2. 如果第一步中,已经发现驱动加载上了,那么第二步通过ifconfig来看看网络界面是否已经UP,IP地址是否分配。 不要太依赖DSM的网页管理,那里的东西只是对于正常状态的设备能正常显示。异常时就不灵了。 如果你能进一步提供一下排查时的信息,获取可以再提供一下排查思路。
  4. 问题在于esxi的缺省虚拟switch设定中,禁止网卡的mac更改。 而jun loader的grub.cfg中设定了将虚拟网卡的mac地址改成群晖的MAC地址,所以esxi对改过mac之后的通讯进行丢弃。 导致外部网络找不到黑裙。 解决办法有两个 1. 将虚拟的虚拟网卡mac设置成黑裙的mac地址。这个地址在grub.cfg中有定义。 2. 修改esxi的虚拟交换机安全设置,允许虚拟机进行mac地址更改。
  5. 你只是将硬盘map过去,并不是直通sata控制器。从虚拟机上看,你的ssd还是一个虚拟的hdd。 如果你想使用SSD加速,有两个办法: 1. 直接将接ssd的sata控制器直通给DSM. 这个操做需要你有额外的sata控制器,并且硬件支持VT-d直通。由于不知道你的硬件情况,无法进一步提供指导。 2. 虚拟一个nvme硬盘给虚拟机。由于DS918支持nvme硬盘加速,所以你可以通过虚拟机添加nvme硬盘来让DSM觉得你有nvme ssd硬盘。 当然,虚拟的磁盘文件要放在SSD这个datastore才行,要不然没效果。 另外,DSM会检查nvme的信息,所以你需要打补丁。具体补丁你可以找一下本论坛。
  6. As of a FreeBSD user, I use ZFS to store my data, but DSM provide some feature/app very nice, I would show how to run XPenology DSM 6.2 on FreeBSD 12.1R. Hardware configuration will be a little special. here is my Build: Xeon E5 2687v2 * 2 SuperMicro X9DRH-iF 256GB RAM other staff. Because bhyve only support e1000/virtio-net emu adapter, for performance and stability consideration a physical ethernet interface will be provide better performance. The key is MB/CPU should support VT-d, otherwize you have to choose a newer CPU platform(XEON E5 v3 or above) to run DS918+. which is support e1000. I will not cover how to install FreeBSD/vm-bhyve and config VT-D here. by using vm-bhyve, the vm config file will be as follow: loader="uefi-csm" cpu=8 cpu_sockets=1 cpu_cores=4 cpu_threads=2 memory=4G ahci_device_limit="1" disk0_type="ahci-hd" disk0_name="ds3617-1.03b.img" disk1_type="ahci-hd" disk1_name="disk0.img" disk1_opts="sectorsize=4096/4096" debug="yes" passthru0="3/0/0" since I am running ds3617+ with 1.03b loader, I use 8 vcpu and 4G ram. and, two disks. one is 50M jun loader, and one data disk. which is disk0.img. there is a ahci_device_limit=1 here. that is tell vm-bhyve will use one SATA controller for one disk. ther reason I will explain later. since our HDDs are organize by FreeBSD's zfs, only one data disk here is enough. we can make it larger. such as 100TB, so we won't have space issue on DSM later. So the VM folder will have 3 files. root@nas253:/zones/vm/jnas # ls -lh total 21798 -rw------- 1 root wheel 100T Mar 1 08:27 disk0.img -rw-r--r-- 1 root wheel 50M Aug 1 2018 ds3617-1.03b.img -rwxr-xr-x 1 root wheel 255B Mar 1 08:26 jnas.conf before you start the VM, make sure you have a DHCP server running in your local network. vm start jnas after the, you can attach to console by using following command vm console jnas and you will see the serial output. Running /usr/syno/etc/rc.d/J99avahi.sh... Starting Avahi mDNS/DNS-SD Daemon cname_load_conf failed:/var/tmp/nginx/avahi-aliases.conf :: Loading module hid ... [ OK ] :: Loading module usbhid ... [ OK ] ============ Date ============ Sun Mar 1 08:30:59 UTC 2020 ============================== starting pid 5957, tty '': '/sbin/getty 115200 console' Sun Mar 1 08:31:00 2020 DiskStation login: after you saw this, you can query which IP is assigned by your DHCP server. and access that IP by web browser and contine setting. the steps are common. As the loader disk is shown inside DSM, you can modify grub.cfg and replace following setting. set sata_args='DiskIdxMap=1F00' and make sure loader entry use this parameter. (grub boot select ESXi entry, or by modify enty setting) that is all. thanks. Here is an instance I have already run for half year Thank you for people who provide loader!!!
  7. your rc.modules in extra.lzma only contain virtio virtio_ring virtio_scsi, no virtio_net. so the network interface will not bring up.
  8. I am using bhyve hypervisor. FreeBSD's bhyve only support virito_net and e1000. (not e1000e) unfortunately, e1000 is not so stable, and virito-net is not automatic loading with extra.lzma. Currently I passthough a dual port e1000e to vm. and DSM 6.2.2 works flawlessly. (with jun's 1.03b, 3617xs) I have a Chelsio T520-CR on FreeBSD host. and SR-IOV works. I'd like to passthough a VF of T520-CR to DSM. Here is the pci info after I pass the VF (command output from DSM 6.2.2) 0000:00:08.0 Class 0200: Device 1425:5801 Subsystem: Device 1425:0000 Flags: bus master, fast devsel, latency 0 Memory at c0204000 (32-bit, non-prefetchable) [disabled] [size=4K] Memory at c0208000 (32-bit, non-prefetchable) [disabled] [size=32K] Memory at c0210000 (32-bit, non-prefetchable) [disabled] [size=8K] Capabilities: [70] Express Endpoint, MSI 00 Capabilities: [b0] MSI-X: Enable- Count=8 Masked- Capabilities: [50] MSI: Enable- Count=1/32 Maskable+ 64bit+ cxgb4.ko and cxgb4vf.ko already exists in exra. But I can't find cxgb5vf source from linux kernel. Any way to build the kernel module from driver that come from chelsio website?
  9. Thanks!!! Yes, this is the correct way hiding the bootdisk. Here is the detail on how to hide the bootdisk on bhyve. 1. first, you have to make bhyve use two sata contoller instead of one. I dont know how to do that in FreeNAS, I am using vm-bhyve manager. and the vm config as follow: loader="uefi-csm" cpu=8 cpu_sockets=1 cpu_cores=4 cpu_threads=2 memory=4G ahci_device_limit="1" disk0_type="ahci-hd" disk0_name="ds3617-1.03b.img" disk1_type="ahci-hd" disk1_name="disk0.img" disk1_opts="sectorsize=4096/4096" passthru0="2/0/0" passthru1="2/0/1" ahci_device_limit will limit one controller one disk. I have two disks, so the actual bhyve commandline will be like below: -s 0,hostbridge -s 31,lpc -s 4:0,ahci-hd,/tank/vm/synas/ds3617-1.03b.img -s 5:0,ahci-hd,/tank/vm/synas/disk0.img,sectorsize=4096/4096 -s 6:0,passthru,2/0/0 -s 6:1,passthru,2/0/1 that shows pcie slot 4 and slot 5 are sata controllers. from view of vm, vm have 2 sata controllers, bootdisk attach to controller 1(pcie slot 4), data disk attach to controller 2(pcie slot 5). 2. second, modify the grub.cfg As you may know, there are 3 boot entries in grub.cfg menuentry "DS3617xs 6.2 Baremetal $VERSION" --class os { set img= savedefault loadlinux 3617 usb loadinitrd showtips } menuentry "DS3617xs 6.2 Baremetal $VERSION Reinstall" --class os { set img= loadlinux 3617 usb mfg loadinitrd showtips } #menuentry "DS3617xs 6.2 Baremetal AMD $VERSION" --class os { # set img= # set zImage=bzImage # savedefault # loadlinux 3617 usb # loadinitrd # showtips #} menuentry "DS3617xs 6.2 VMWare/ESXI $VERSION" --class os { set img= savedefault loadlinux 3617 sata loadinitrd showtips } default entry is for beremental, It will NOT USING the sata_args defined in the config!!! set sata_args='sata_uid=1 sata_pcislot=5 synoboot_satadom=1 DiskIdxMap=1C SataPortMap=1 SasIdxMap=0' so you can comment out first two menu or modify first menu entry use sata_args. something like below (replace usb with sata) menuentry "DS3617xs 6.2 Baremetal $VERSION" --class os { set img= savedefault loadlinux 3617 sata loadinitrd showtips } also modify sata_args as below (bhyve only use sata controller) #set sata_args='sata_uid=1 sata_pcislot=5 synoboot_satadom=1 DiskIdxMap=1C SataPortMap=1 SasIdxMap=0' set sata_args='DiskIdxMap=1F00' as define DiskIdxMap=1F00, the first sata controller disk number is from 32, second sata controller disk number is from 0. that will make bootdisk invisible. if you check the sata device name from command line root@QNAS:/# ls /dev/sda* /dev/sda /dev/sda1 /dev/sda2 /dev/sda3 /dev/sdaf3 sda is the name of data disk, and sdaf is the bootdisk's name. Finally, the 50M bootdisk will not shown in web interface. Cheers.