Jump to content
XPEnology Community

viktortrass

Member
  • Posts

    36
  • Joined

  • Last visited

Posts posted by viktortrass

  1. 19 hours ago, viktortrass said:

     

    Hello, It is possible to use CMS on xpenology VM for DVA3221(by default 8 licenses) to give surveillance station licenses to a xpenology baremetal installation DS3622XS like in this video ?

     

    I can confirm it is working good and now I have 10 licenses for use with face recognition.

     

    Thankss

  2. On 7/22/2022 at 12:28 PM, Orphée said:

    With DVA3221 loader, you have 8 camera available instead of 2.

    unless you need more than 8 camera, no need to buy licences.

     

    DVA3221 loader works without real NVIDIA GPU, you will not have AI feature without the GTX1650 NVIDIA GPU, but you will still have the 8 camera working normal like on a standard NAS.

     

    If your host is powerfull enough to run Proxmox or VMWare ESXi, you can even run more than one loader VM instance and use CMS feature to have 8 x n instances running

     

    Hello, It is possible to use CMS on xpenology VM for DVA3221(by default 8 licenses) to give surveillance station licenses to a xpenology baremetal installation DS3622XS like in this video ?

     

  3. Hello I would like to ask what is actually the best model or version to choose for a HP Microserver Gen8 Xeon E3-1265LV2?

    I think it is DS3622XS, is correct?

     

    I actually have DSM 6.2.3 with juns loader on DS3615XS model but I want to update it with ARPL.

     

    I want to build the bootloader based on DS3622XS but my question is... will I have any problem updating to DSM 7 If I change model version to DS3622XS or I must update with the same model as before (DS3615XS)? Maybe If I select different model Synology Wizard will ask me to reinstall DSM.

     

    Can I just make new usb with ARPL, build the bootloader and update DSM without loosing data or something? any advice?

     

    Thanks in advance

  4. This post is from 4 years ago but I have to say that even it is a violation of Synology Terms, each one can do whatever he want.

     

    We do not provide any tutorial or info.

     

    Im not going to post the way but I have to say that is totally possible to use a real SN and a real MAC with xpenology on DSM 6 or 7.

     

    Thanks

    • Confused 1
  5. 38 minutes ago, KeepItSave said:

    @viktortrass your howto is brilliant, but my system stucks in this window: grafik.thumb.png.0582e6287863f4ceb53b1589966c436e.png

     

    My current setup of the VM looks like this:

    <?xml version='1.0' encoding='UTF-8'?>
    <domain type='kvm' id='4'>
      <name>DSM-ds918p-7.1.1-42962</name>
      <uuid>9295d191-59ea-7f66-9090-ef2fbd3b85fa</uuid>
      <metadata>
        <vmtemplate xmlns="unraid" name="CentOS" icon="centos.png" os="centos"/>
      </metadata>
      <memory unit='KiB'>4194304</memory>
      <currentMemory unit='KiB'>4194304</currentMemory>
      <memoryBacking>
        <nosharepages/>
      </memoryBacking>
      <vcpu placement='static'>2</vcpu>
      <cputune>
        <vcpupin vcpu='0' cpuset='0'/>
        <vcpupin vcpu='1' cpuset='1'/>
      </cputune>
      <resource>
        <partition>/machine</partition>
      </resource>
      <os>
        <type arch='x86_64' machine='pc-q35-6.1'>hvm</type>
        <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader>
        <nvram>/etc/libvirt/qemu/nvram/9295d191-59ea-7f66-9090-ef2fbd3b85fa_VARS-pure-efi.fd</nvram>
      </os>
      <features>
        <acpi/>
        <apic/>
      </features>
      <cpu mode='host-passthrough' check='none' migratable='on'>
        <topology sockets='1' dies='1' cores='2' threads='1'/>
        <cache mode='passthrough'/>
      </cpu>
      <clock offset='utc'>
        <timer name='rtc' tickpolicy='catchup'/>
        <timer name='pit' tickpolicy='delay'/>
        <timer name='hpet' present='no'/>
      </clock>
      <on_poweroff>destroy</on_poweroff>
      <on_reboot>restart</on_reboot>
      <on_crash>restart</on_crash>
      <devices>
        <emulator>/usr/local/sbin/qemu</emulator>
        <disk type='file' device='disk'>
          <driver name='qemu' type='raw' cache='writeback'/>
          <source file='/mnt/user/appdata/DSM - CCTV/tinycore-redpill.v0.9.2.9.img' index='2'/>
          <backingStore/>
          <target dev='hdc' bus='usb'/>
          <boot order='1'/>
          <alias name='usb-disk2'/>
          <address type='usb' bus='0' port='1'/>
        </disk>
        <disk type='file' device='disk'>
          <driver name='qemu' type='raw' cache='writeback'/>
          <source file='/mnt/user/domains/DSM-ds918p-7.1.1-42962/vdisk2.img' index='1'/>
          <backingStore/>
          <target dev='hdd' bus='sata'/>
          <alias name='sata1-0-3'/>
          <address type='drive' controller='1' bus='0' target='0' unit='3'/>
        </disk>
        <controller type='usb' index='0' model='qemu-xhci' ports='15'>
          <alias name='usb'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/>
        </controller>
        <controller type='sata' index='0'>
          <alias name='ide'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/>
        </controller>
        <controller type='sata' index='1'>
          <alias name='sata1'/>
          <address type='pci' domain='0x0000' bus='0x06' slot='0x01' function='0x0'/>
        </controller>
        <controller type='pci' index='0' model='pcie-root'>
          <alias name='pcie.0'/>
        </controller>
        <controller type='pci' index='1' model='pcie-root-port'>
          <model name='pcie-root-port'/>
          <target chassis='1' port='0x10'/>
          <alias name='pci.1'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/>
        </controller>
        <controller type='pci' index='2' model='pcie-root-port'>
          <model name='pcie-root-port'/>
          <target chassis='2' port='0x11'/>
          <alias name='pci.2'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/>
        </controller>
        <controller type='pci' index='3' model='pcie-root-port'>
          <model name='pcie-root-port'/>
          <target chassis='3' port='0x12'/>
          <alias name='pci.3'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/>
        </controller>
        <controller type='pci' index='4' model='pcie-root-port'>
          <model name='pcie-root-port'/>
          <target chassis='4' port='0x13'/>
          <alias name='pci.4'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/>
        </controller>
        <controller type='pci' index='5' model='pcie-root-port'>
          <model name='pcie-root-port'/>
          <target chassis='5' port='0x14'/>
          <alias name='pci.5'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/>
        </controller>
        <controller type='pci' index='6' model='pcie-to-pci-bridge'>
          <model name='pcie-pci-bridge'/>
          <alias name='pci.6'/>
          <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/>
        </controller>
        <controller type='virtio-serial' index='0'>
          <alias name='virtio-serial0'/>
          <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/>
        </controller>
        <interface type='bridge'>
          <mac address='00:11:32:7f:f5:d3'/>
          <source bridge='br0'/>
          <target dev='vnet3'/>
          <model type='virtio-net'/>
          <alias name='net0'/>
          <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
        </interface>
        <serial type='pty'>
          <source path='/dev/pts/1906'/>
          <target type='isa-serial' port='0'>
            <model name='isa-serial'/>
          </target>
          <alias name='serial0'/>
        </serial>
        <console type='pty' tty='/dev/pts/1906'>
          <source path='/dev/pts/1906'/>
          <target type='serial' port='0'/>
          <alias name='serial0'/>
        </console>
        <channel type='unix'>
          <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-4-DSM-ds918p-7.1.1-429/org.qemu.guest_agent.0'/>
          <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/>
          <alias name='channel0'/>
          <address type='virtio-serial' controller='0' bus='0' port='1'/>
        </channel>
        <input type='tablet' bus='usb'>
          <alias name='input0'/>
          <address type='usb' bus='0' port='2'/>
        </input>
        <input type='mouse' bus='ps2'>
          <alias name='input1'/>
        </input>
        <input type='keyboard' bus='ps2'>
          <alias name='input2'/>
        </input>
        <graphics type='vnc' port='5900' autoport='yes' websocket='5700' listen='0.0.0.0' keymap='de'>
          <listen type='address' address='0.0.0.0'/>
        </graphics>
        <audio id='1' type='none'/>
        <video>
          <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/>
          <alias name='video0'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/>
        </video>
        <memballoon model='virtio'>
          <alias name='balloon0'/>
          <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/>
        </memballoon>
      </devices>
      <seclabel type='dynamic' model='dac' relabel='yes'>
        <label>+0:+100</label>
        <imagelabel>+0:+100</imagelabel>
      </seclabel>
    </domain>

     

    I have a Unraid running on a "HP ProLiant MicroServer Gen8"

     

    Does someone has an idea what the root cause could be ?

     

     

    Have you tried to find the server with synology assistant desktop app or find.synology.com?

    This is normal. Have you booted from usb or sata?

     

    Try to select usb boot elsd try sata boot let it load for about 3-5min, then try to find ip assigned by DHCP with Synology Assistant.

  6. This tutorial is a supplement to the ESXi TCRP installation tutorial located here:

     

    https://xpenology.com/forum/topic/62547-tutorial-install-dsm-7x-with-tinycore-redpill-tcrp-loader-on-esxi/

     

    Installing DSM 7.1.0.-42661 on UNRAID 6.10.3

     

    I have been trying to install DSM 7.1 on my unraid server for the last night. After some problems and testing I have created this guide to install DSM 7.1 on UNRAID working perfectly.

     

    This is my vm config:

     

    983366734_dsmonunraid1.thumb.jpg.d41bb2d47124a5ac1e449297251e3895.jpg

     

     


    STEP 1-Virtual machine creation: 
        

    •     Download tiny core from https://github.com/pocopico/tinycore-redpill
    •     Select CentOS VM Template and apply correct options from the attached image.
    •     Select Q35-6.2
    •     Select 3.0 (qemu XHCI)
    •     Load tiny red core as vdisk1 USB by selecting manually (you can create previously the name of the folder for the VM inside /domains and upload the tinycore img )
    •     Create secondary disk 50G or whatever you want (this is your data storage for synology) as vdisk2 SATA
    •     Select Network model: e1000
    •     Save.
    •     Uncheck "Start VM after creation"

    •     Edit again vdisk2 in the advanced xml template (top right corner) to controller='1' (if we don't do this tiny red core will not detect the disk properly when doing the satamap and will not install DSM correctly and will ask you to reinstall the *.pat infinitely)

     

    STEP 2-Start VM and connect via SSH

     

    •     Start VM and load tiny red core
    •     Once the OS is loaded, open the terminal and enter ifconfig to find out the ip of the machine
    •     Connect via ssh (with Putty) to the obtained IP address.

            user: tc
            password: P@ssw0rd

     

     

    STEP 3-Run the following commands:

     

    •     To update tiny red core with the latest data 

     

    ./rploader.sh update now
    ./rploader.sh fullupgrade now

     

    •     To generate random mac and serial numbers (copy mac address generated to set on unraid vm template later)

     

    ./rploader.sh serialgen DS918+ (or whatever version you want, you can see all versions available with command info ./rploader.sh)

     

    •     To map the connected disks

     

    ./rploader.sh satamap now

     

    •     To record the vid/pid from usb

     

    ./rploader.sh identifyusb now

     

     

    •     To install NIC drivers (sometimes it loads the e1000e module instead of the e1000 and it doesn't work, adding this command will make sure that the e1000 module for the NIC is loaded correctly)

     

    For e1000 Network Card run:

     

    ./rploader.sh ext apollolake-7.1.0-42661 add https://raw.githubusercontent.com/pocopico/rp-ext/master/e1000/rpext-index.json

    NOTE: change version according your selection for CPU and DSM version

     

    For virtio-net Network Card run:

     

    ./rploader.sh ext apollolake-7.1.0-42661 add https://raw.githubusercontent.com/pocopico/rp-ext/master/v9fs/rpext-index.json

    NOTE: change version according your selection for CPU and DSM version

     

    •     To build the image

     

    ./rploader.sh build apollolake-7.1.0-42661

     

    STEP 4-Download your .pat for your correct cpu architecture from official repo or mega download for this version apollolake , we will need it to install DSM later.

     

    https://global.download.synology.com/download/DSM/release/7.1/42661-1/DSM_DS918%2B_42661.pat - Offical repo

     

    STEP 5-Edit VM settings on advanced xml mode and install *.pat

     

    • After doing all the above we shut down the machine.
    • Edit the virtual machine on xml advanced mode (if we change mac address in normal editing mode you will lose controller="1" option set for vdisk2 we did previously so you will have to set it again everytime you change and/or save a setting from normal mode, try to edit always in xml advanced mode), look for MAC address and set the MAC generated by tiny red core.
    • Save
    • Start VM
    • Select the first option USB and leave it a few minutes until we find it with synology assistant

    redpill.thumb.jpg.4a610f985dbd3195930dee44ade90041.jpg

    • Open WebGui and install *.pat

     

    We now have DSM 7.1 working on unraid.

    There is other method with SATA boot but I have to test it better.

     

    Hope this guide help someone.

     

    Regards.

     

    • Like 1
    • Thanks 1
  7. On 6/21/2022 at 6:32 PM, borzoy said:

    at the moment, the dsm is installed immediately on the hardware and during installation indicated "SataPortMap": "62", "DiskIdxMap": "0006"

    Edit VM and choose XML view

    Look for your vdisk2 or sata hdd drive and change controller='0' to controller='1'

    Save and restart the VM. Installation should continue.

    If you edit something on normal view edit, changes on xml view will be gone and you will have to do it again.

  8. 1 hour ago, IG-88 said:

    https://archive.synology.com/download/Package/spk/

    look for "node..."

     

    you could use a search engine with "NODE JS synology package"

     

    you can also open the spk file with 7zip and have a look at the file INFO

    there should be a listed depedency like this

    install_dep_packages="xxx:yyy:zzz"

     

    Eynio seems to be from 4/2017 (DSM 5.x)  and not maintained anymore, so you might want to test a older package from the link above dating back to that time

    you could also dig deeper in the spk file like opening "package.tgz" or the install scripts to see what node.js version might be used initially

    v4 or v6 seemed to be used at this time, maybe eve v0.10

     

    when downloading a spk manually you need to look for the platform of you installed dsm version (in the file name of the spk)

    x86_64 is for all three

    bromolow is 3615

    braswell is 3617

    apollolake is 918+

     

    Thank you for your help, I have just extracted it with 7zip and looked info file, it show node js so I found the package node js and install the last version, now is working perfectly, why this versions of node js are not showing on package center??

     

    Thanks.

  9. Hello, I have problems with download and upload speed over internet, I use ddns and a hp microserver gen8 baremetal with DSM 6.2!!In my lan speed are over 980mbits! is a gigabit connection but over internet I download at 15MB/sec and upload at 1MB/sec, I have fiber 600/600 in the nas side and 1gpbs/400mb in the other side so this is not the problem!!anyone with the same problem? thanks

  10. On 11/5/2019 at 6:02 AM, FOXBI said:

     

    do use 7zip

     

    1. extract DSMxxx.pat check of hda1.tgz file

     

    2. extract hda1.tgz check of hda1 follder 

     

    3. extract hda1 check  of hda1~ folder

     

    eg.) c:\DSM_DS3615xs_24922\hda1\hda1~\usr\syno\synoman\webman\modules\AdminCenter

     

    4. you can find original admin_center.js & admin_center.hs.gz

     

    5 do use sftp, upload and overwite two files.

     

    After checking back your DSM information

     

    and then you do run again.

    thank you very much I will do that tomorrow!

  11. hello, first of all thanks for the great effort.

    I have a problem, I executed the script on my previous cpu and worked well but now I have changed it to Intel Xeon E3-1265LV2, I choose the redo option but nothing happens, tried to delete \root\xpenology and do first run but still nothing, it shows the same as before. what can I do friend?

  12.  

    On 10/15/2019 at 8:59 AM, bearcat said:

    @viktortrass I was referring to the 2. option: " Resume DSM to my ..."

    If that is chosen, any "open object" at log-out, will reopen on log-in.

     

    I have updates available for my system, but as in your case, they are not valid for my G7, 

    but I do NOT have the automagicly open controlpanel, update and restore.

    I have this checked but still do the same, open it when I log in

×
×
  • Create New...