Jump to content
XPEnology Community

elitef

Member
 View Profile  See their activity

  • Posts

    85

  • Joined

  • Last visited

  • Days Won

    1

 Content Type 

Posts posted by elitef

    QNAP with Xpenology VM

    in DSM 6.x

    Posted

    Hi All,

     

    I've been running Xpenology on a QNAP TS-1685. All in all the system runs well, but I'm using Surveillance Station within the VM as my primary source for recording all cams.

    It works well for the most part, but at times, it take a LONG time to connect to Surveillance Station, the camera's have been acting weird where the recordings are supposed to be 30 minutes, but instead, they sometimes are 12 min, or more, or less, so it looses connection for some reason.

     

    I am currently running a DS3617xs Xpenology build. I've allotted 16GB ram if that matters.

     

    Has anyone else experienced the loss of connection with Xpenology, whether on QNAP or not?

    SurveillanceStation-x86_64-8.2.2-5766

    in Програмное обеспечение

    Posted

    3 hours ago, montagnic said:

    Скорее всего косяк в виртуалке на кунапе. Ищите проблему в сетевых настройках. Кунап же не пропадает из сети?

    Da ne, i xpenology tozje net, ono prosto timeout delayet i daeot tot msg. No obe sistemi, kynap i hrenology, oba vidni vsy darogy l, eto prosto kakayato hren s SS pochemyto.

     

    Dazje ne znayu gde nachat iskat risheniya.

    surveillance : use license from a real system on 3615

    in Synology Packages

    Posted

    19 minutes ago, ryerye said:

    I have taken a real SN and MAC from old physical Synology box and set it up on virtual 3615xs Synology.

    Stil not able to activate legally purchased camera license. Still the "Connection failed. Please check your network settings" error.

     

     

    Same here. I've tried the same last week with no luck.

    If you take a 3615xs SN / MAC from a real physical box and put it on the XPEnology 3615xs, then it might work, but if the models dont match up, it wont work apparently.

    DSM 6.2 Loader

    in Loaders

    Posted

    Tried changing the SN / MAC to reflect a real syno that I have 1813 but apparently the system checks somehow that the model 3617 is not correct for the 1815 SN / MAC combo, so cannot log in online, quick connect, or verify surveillance station serial # :(

     

    Does anyone have any ideas/recommendations on getting this to work?

    DSM 6.2 Loader

    in Loaders

    Posted

    35 minutes ago, luchuma said:

     

    in that video time 6:45 dont select IDE

    you need sata 0.0 for loader

     

    IDE worked before with 6.1 loader

    This seems to have worked!

    Thank you VERY much. I have done SATA in VMwW as well as when setting up the initial VM in QNAP, so both are set to SATA and it is now working.

     

    Now to figure out how to get the Surveillance Station to work with a license pack that I have because I end up getting a message that the the connection failed when it tries to reach out to the backend server or something.

    DSM 6.2 Loader

    in Loaders

    Posted

    25 minutes ago, luchuma said:

    use synoboot.vmdk instead usb and then export vm ;]

    Yes, I have done that already which is what I mentioned in my last post. I used the instructions from this youtube Video

    This worked for 6.1.7, but does NOT work for 6.2. I get stuck at the bootloader message to use find.synology.com but it is not discoverable on the network through the website or Synology Assistant.

     

    DSM 6.2 Loader

    in Loaders

    Posted

    5 hours ago, rgarjr said:

     

    I was testing out 6.01 on Qnap VM (using the same method, create vm using vmware workstation, then exporting to .OVF), then after trying to get the 6.2 loader to work.  Got it working now.  Once it was working, I exported the VM to a QVM file so there's no need to go through the process of installing the PAT file.  

     

    https://youtu.be/-uvm_Z0g2fs

     

    Funny enough, I saw your video yesterday.

    Your video shows 6.0.2 version which I've gotten to work just fine, as well as all the way up to 6.1.7. It is the 6.2 that I am having issues with.

    I've created the OVF file in VMwW but I have yet to be able to get it to work on the QNAP because it loads/boots to the screen where it says to use the find.synology.com but my SynoAssistant isnt finding it. When I did the same exact thing using the USB method by BootyTrap on youtube, I was able to create the USB fine, connected it to the QNAP, booted the VM with USB being the primary boot option and it worked just fine. I just do not want to use a USB in order to run it since it is within the QNAP.


    It is as if the 6.2 loader somehow requires something different in VMwW in terms of configuration compared to the older version for 6.1.7.

    DSM 6.2 Loader

    in Loaders

    Posted

    So, I've been testing out the loader for the past few hours and I cannot seem to get it to work the way I need it to.

    I am running XPEnology on a QNAP device. the 6.1.7 DSM installs perfectly fine with the older bootloader but I cannot get past the "find.synology.com" message on the 6.2 loader. It never actually activates for me to go through the installation of the DSM and SynoAssist never finds it.
    I then tried to use the same exact loader by using a USB stick and booting the VM in QNAP to go through the USB stick and it works perfectly fine there and I was able to install it successfully.

     

    Does anyone have ANY clues at all how I can get it to work WITHOUT the USB stick and just using the VM in QNAP with a created file from VMWARE Workstation?

    surveillance : use license from a real system on 3615

    in Synology Packages

    Posted

    13 minutes ago, NoFate said:

    Please search on this forum how to change the sn/Mac ,you need to change some files

     

    But then still,my original question, will the license work on a xpeonology with a real sn/Mac... Seems no one tried it yet

    So I found something where you can change the MAC/SN but it is required to do so before installation. I have already installed. Is there a way to get this changed after it has already been installed or will I need to reinstall because the instructions mentioned the use of a USB stick which I did not use since I am installing this on a QNAP machine. I do have a Syno system as well and would also like to know if I can just use the MAC of that machine (DS1817+), but not sure how to change the SN either way.

    Adding license pack to Surveillance Station fails

    in Synology Packages

    Posted

    I am trying to stick with 6.1.7 since I was not able to install 6.2.

    I am running Surveillance Station but when I attempt to add a license pack number, I get a message "Connection failed. Please check your network settings"

    I am able to download apps from the App Center and they download just fine, so clearly there is an internet connection. 

     

    Does anyone know why this may be happening?

    DSM 6.2 Loader

    in Loaders

    Posted

    On 9/5/2018 at 9:51 AM, elitef said:

    Hi All,

     

    I am attempting to install 6.2 on a QNAP using VM.

    I installed 6.1.7 perfectly fine and running smooth, but when I try to do 6.2, I get the message to use find.synology.com to find the machine, but it never finds it. 

    I then tried to go back to 6.1.7 and use the Update to 6.2 from within the DSM > Control Panel, but that also didn't work.

     

    Are there any specific update instructions since 6.1.7 uses a different loader, how can I update to the 6.2 loader if I am doing the Update from within DSM to 6.2?

    Can anyone please advise on this.

    DSM 6.2 Loader

    in Loaders

    Posted

    Hi All,

     

    I am attempting to install 6.2 on a QNAP using VM.

    I installed 6.1.7 perfectly fine and running smooth, but when I try to do 6.2, I get the message to use find.synology.com to find the machine, but it never finds it. 

    I then tried to go back to 6.1.7 and use the Update to 6.2 from within the DSM > Control Panel, but that also didn't work.

     

    Are there any specific update instructions since 6.1.7 uses a different loader, how can I update to the 6.2 loader if I am doing the Update from within DSM to 6.2?

    Лицензиpoвaние камер как быть

    in Програмное обеспечение

    Posted

    On 1/2/2018 at 1:12 AM, Vir-US said:

    SS 8.1.2-5469.х86_х64 протестирован и работоспособен. Желающие могут постучать(только не громко) в личку.

    На заметку

    - Качаем архив и распаковываем.

    - Устанавливаем  SS 8.1.2-5469!!!(взять можно Тут, но не запускаем(если запустили, останавливаем).

    - Заходим на свой NAS через web.

    - Заходим в Панель управления > терминал и SNMP. Ставим галку "включить службу ssh" и нажимаем применить.

    - Подключаемся к сино с помощью putty или другого ssh клиента под Админом

    - Вводим свой Админский пароль

    - Вводим команду: sudo su -

    - Вводим свой Админский пароль

    - Видим чудо в виде - root@...

    - Вводим команду: synouser --setpw root Ваш_Пароль_Для_Root

    - Далее можно заходить под root используя установленный пароль.

    - Скидываем файлики из архива на сино и при необходимости меняем владельца и права. Сделать это можно разными способами.

    p.s.При использовании WinSCP советую в настройках передачи установить тип файлов "двоичный/binary" для исключения возможных проблем.

    - Запускаем SS из центра пакетов.(если всё сделано правильно, имеем 25 камер)

    - Класть(или если хотите - ложить) сюда>>>
    /var/packages/SurveillanceStation/~target/lib/libssshm.so *chmod=644* *owner=SS* *group=SS*
    /var/packages/SurveillanceStation/~target/lib/libssutils.so *chmod=644* *owner=SS* *group=SS*
    /var/packages/SurveillanceStation/~target/sbin/ssmessaged *chmod=755* *owner=SS* *group=SS*
    /var/packages/SurveillanceStation/~target/webapi/Layout/src/SYNO.SurveillanceStation.Layout.so *chmod=644* *owner=SS* *group=SS*

    Hide

    "- Качаем архив и распаковываем"

    а где архив?

    DS3617xs to QNAP Virtualization Station 3

    in DSM 6.x

    Posted

    Hello All,

    I am really hoping that someone might be able to help me out. I know that the JUN loader is not compatible with QNAP VS3, but I read in a different thread that if you install it on VM Workstation 12 Pro, export it to OVF and then import it into QNAP VS3, that it works, but unfortunately I have not been able to get it working.

     

    The following are the steps that I've taken:

    Install DS3617xs DSM on VM Workstation 12 Pro on my Windows 10 machine using the following video:  

    https://www.youtube.com/watch?v=Si9Y1HNhYrI

    I followed all the steps down packed with the exception of installing 6.1.4 instead of 6.1 (I did try 6.1 too and it did not work either on the QNAP VS3)

    Once installation was completed I then went in to create a BASIC RAID and then a Volume of 5GB (small but just as a test)

    Once all was done, I shut down the DSM and went into File > Export to OVF and saved the file to my desktop.

     

    I then went to the QNAP VS3 > Import > Selected the OVF file. I was then prompted to select the two VMDK files which I've done and selected which folder on the QNAP I wanted it installed/imported under. The import went through successfully, but when I boot up the VM in VS3, Synology Assistant finds the system, but without an installed copy of DSM and it states "No Hard Disk Found on DS3617xs"

     

    Please let me know if anyone knows of a solution for this issue. I'm sure it's a simple setting but I cannot seem to get it to work after multiple attempts all with different types of setting configs.

    Jun's Loader v1.02b with QNAP Virtualization Station 3

    in DSM 6.x

    Posted

    can someone please share how to get this on to a QNAP Virtualization Station 3?

    I am able to get it installed via VMWare on a local computer, then I continue with the set up and get everything set up accordingly. Then I shut down the VMWare DSM, then I export the file into a OVF file, import it into QNAP, but it wants to go through the entire installation process again once I boot it and it does not take the install PAT file for some reason.

×
×
  • Create New...