Jump to content
XPEnology Community

raultaboraz

Member
  • Posts

    23
  • Joined

  • Last visited

Posts posted by raultaboraz

  1. On 12/7/2018 at 9:28 AM, hoppler said:

     

    • Login (replace URL, PORT, USER, PASS)
      • https://URL:PORT/webapi/auth.cgi?api=SYNO.API.Auth&method=Login&version=1&account=USER&passwd=PASS

     

    for ActiveBackup its the following urls

    • Get Activationstatus
      • https://URL:PORT/webapi/entry.cgi?api=SYNO.ActiveBackup.Activation&method=get&version=1
    • Set ActivationStatus (use your SERIALNUMBER)
      • https://URL:PORT/webapi/entry.cgi?api=SYNO.ActiveBackup.Activation&method=set&version=1&activated=true&serial_number="SERIALNUMBER" 

     

    for Office365 its the following urls

    • Get Activationstatus
      • https://URL:PORT/webapi/entry.cgi?api=SYNO.ActiveBackupOffice365&method=get_activation&version=1
    • Set ActivationStatus (use your SERIALNUMBER)
      • https://URL:PORT/webapi/entry.cgi?api=SYNO.ActiveBackupOffice365&method=set_activation&version=1&serial_number="SERIALNUMBER"

     

    for GSuite its the following urls

    • Get Activationstatus
      • https://URL:PORT/webapi/entry.cgi?api=SYNO.ActiveBackupGSuite&method=get_activation&version=1
    • Set ActivationStatus (use your SERIALNUMBER)
      • https://URL:PORT/webapi/entry.cgi?api=SYNO.ActiveBackupGSuite&method=set_activation&version=1&serial_number="SERIALNUMBER"

     

    Maybe the API has changed? I am using v2.0.5-0534 of Active Backup G Suite and (DSM DSM 6.2.2-24922 Update 4) it doesn't work.

     

    1st step for Login is OK, it works, but 2nd and 3rd step are not working "{"error":{"code":102},"success":false}"

     

    You did mention 102 code is because app is not started, I have opened it and tried to activate, uninstalled, re-installed, disabled 2FA, always the same. I have tried HTTPS or HTTP and also creating a new admin user with silly password like 123456789 in order to test it, so... I have tried also 3 backups apps, ActiveBackup Business, G suite, Office 360... none of them work.

     

    I really think that this is because the API has changed and it is not working anymore.

     

    Could you please help me? Can you all please confirm which version of ActiveBackup and DSM are you using? Thanks a lot

  2. 56 minutes ago, IG-88 said:

    its a disaster if it breaks your raid (can easily happen when just cutting power or having psu problems) - did happen to me last weekend but data recovery is kind of a hobby horse ... (and i have a backup too)

     

     

    as jun created the loader there was just dsm 6.2.0 and later on (a update version of 6.2.1?) synology introduced a change in the way the kernel is compiled, breaking the compatibility with most "old" drivers - not synology's concern, they deliver drivers for the hardware they sell inside dsm but a problem for xpenology users as in most cases that meant fallback to drivers that are not affected (very few) or drivers that where delivered by dsm (native drivers)

    for legal reasons i only provide drivers that are made from open source, not a loader that contains files (IP) from synology (like the kernel from DSM *,pat file zImage, rd.gz)

    anyone can stick out his/her neck, combine loader, new extra.lzma and new zImage/rd.gz and offer it as complete loader for download, i have no copyright on this stuff and as long as its labeled with the version of the extra.lzma it contains i would not complain (i don't need my name attached to this) - beside this i guess jun would like to see it marked when its a loader that has been changed in any way, he should not be held responsible for my mistakes or assumptions (same as i dont feel responsible for that 1019+ image/loader containing my 918+ driver pack, not tested not my doing)

    thank you very much for explanations. If can I make a suggestion, I would say that a warning would be nice for avoiding disasters like mine ;-) I think there is any information about "missing" drivers. Thanks

  3. 30 minutes ago, IG-88 said:

    no, you can read about it here

    https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/

    on 918+ its a little different as it needs a intel 4th gen haswell cpu, 3615/17 is still the same as before

     

    i tested the 3615/17 with a q6600 as it was one of the test systems i had at hand

    whatever is causing problems, its not the cpu,the only reliable method is a serial console as dsm switches to this right when it starts booting

     

    i guess because of the driver changes, in that version, after going above 6.2.0 you had the driver conflict i mentioned above and the only way to solve this is the new driver pack, as its compiled for this version

    but it should work when you use the new driver with then 6.2.2 zImage and rd.gz, you boot from usb and the synology assistant should find your system in network (if 6.2.1 is installed on disk and 6.2.2 on the loader it will not boot up, it will wait as when installing a new system to be provided with the 6.2.2 *.pat file for installing)

     

     

    Thank you for your explanations. It really was double mistake 1st) Drivers were not updated like you said. 2nd) The GFX card I tried was broken, I didn't see anything so I thought my PC was broken. In the middle time the Power Supply stopped working as well, so I needed to change it again... So my 6.2.2 has been a total disaster :-)

     

    Anyway I have a question, why v1.0.3b is not including new drivers? It doesn't have sense to me adding them manually

     

    Thank you all

  4. 3 hours ago, smilenkovski said:

    Thanks for the info. I thought that limitations for update come from cpu gen. (q6600)

    just for your info:

     

    my NEW NAS (recycled computer) is a Gigabyte GA-EP35-DS3 + CPU Q9400 + 8GB 800 Mhz. is working perfectly with 6.2.2 latest

    my latest NAS (broken computer) is a Gigabyte GA-EP35-DS4 + CPU Q6600 + 8GB 800 Mhz. was working perfectly with 6.1.7 latest but I didn't have a chance to test it with 6.2.2 because it stops working while migration...

     

    Good luck!

  5. 50 minutes ago, smilenkovski said:

     

    Hi @smilenkovski I confirm that another very similar motherboard to ours GA-EP35-DS3 http://es.gigabyte.com/products/page/mb/ga-ep35-ds3_21#kf works perfectly with 6.2.2 latest. I have used Juns loader 1.0.3b + extra.lzma + zImage.lzma + rd.gz mods commented on post above

     

    I just take off my HDDs + pendrive from my hardware broken NAS and I have putted into new PC (hackintosh) just for testing... So, it works, maybe I will recycle this one for NAS purposes.

     

    Thanks

  6.  
    if you want to test risk free you would create a new usb with 1.03b (preferably with latest drivers, see below)
    disconnect all disks and connect only one empty disk for a test installation, install the latest version 6.2.2, if that works you can put that stick aside (single test hdd is not need anymore), get your old usb up with all the disks, update with the gui to 6.2.2 - it will prepare the installation and reboot and it will fail on reboot as the usb loader does not match (anymore), now use your prepared 1.03b loader and the system should be continue with updating to 6.2.2
     
    also read about the new drivers for 6.2.2, i'd suggest to prepare the 1.03b usb with the new driver pack (2nd half about 3615/17)
    https://xpenology.com/forum/topic/21663-driver-extension-jun-103b104b-for-dsm622-for-3615xs-3617xs-918/
     
     
    Hello, thanks for update... I have bricked it.
    I updated to 6.2 perfectly and everything was ok. I tried to update to 6.2.1 and everything went bad. I have lost access it does not boot anymore.
    Maybe I will update pendrive with those drivers like you said...

    I have installed a graphic card like I did some years ago, but I can't see anything. My PC/NAS it's like dead, no beeps, no screen, no boot. I can't recover it. Everything is running, lights, hard disks, but I can't see anything on screen.

    I guess power supply dies while we was updating. I will try to try another one. I have reset CMOS but my PC/NAS seems to be death at all. It's very strange that just after rebooting to 6.2.1 everything went wrong.

    I know that this is not hardware forum, but maybe you have any ideas about what happened here?

    Thanks!
  7. Hello,

    I am currently in 6.1.7 with 1.0.2b working ok.

     

    I would like to update to 6.2 and I have done 1.0.3b pendrive as usual.

     

    Can I test 1.0.3b on 6.1.7 first? I am not sure about it... I have seen on compatibility charts that 1.0.3b is for 6.2.x but will it work with 6.1.7 for testing?

     

    I am asking because my NAS is hidden without graphic card, monitor and it's very big to move. So I would like to be as cautious as possible...

     

    Thanks

  8. Saludos, 
     
    sino recuerdo mal, en las últimas versiones de DSM, si el synology no está registrado a través de QuickConnect no funcionaba la transcodificación a través de la aplicación de Synology (DS Video). Yo he utilizado desde siempre Plex, prueba al menos con ella a ver si te ocurre lo mismo. 
    Por otra parte,  si el portátil es muy muy antiguo, y está haciendo transcodificación porque no tienes suficiente ancho de banda de subida en tu conexión a Internet o de descarga en el dispositivo en el cuñal estás intentando ver el video, es probable que la CPU llegue al 100% de uso y no sea capaz de gestionar el formato de archivos de video que tengas almacenados.  Así pues:
    1. Prueba con videos en distintos formatos y tamaños.
    2. Busca tu cpu en www.passmark.com y dinos que puntuación tiene.
    3. Comprueba el ancho de banda que necesitan tus videos para verse fluidos sin transcodificación. 
    4. Prueba con Plex
     
    Espero te sirva...
    Plex is referís a ver el video de la cámara por Plex? O probar a reproducir una peli normal?
  9. you could try connecting with winscp (enable ssh etc), that has a nice folder browser that shows the various folder permissions/owner. then you could try chmod etc commands to alter the permissions on the required folders.
    Thank you a lot. I already have access by winscp (you can't do it as root), the only folder I can see are homes of users... But I would like to navigate to volumes, configs, etc...

    Or maybe you can tell me what is the chmod command?
    Thanks
  10. 1 hour ago, Polanskiman said:

    Would uninstalling and then re-installing the package solve your permission issue?

    no :(

    I would like to maintain folders of old DSM installation (corrupted) because it maintains config files. I have docker with a lot of containers, surveillance with a lot of cameras, etc...

     

    While it seems to keep config, it doesn't work well, for example Surveillance finds cameras config but can't access to recording folders (I guess because permissions).

     

    How could I get those?

     

    Thanks!

  11. Hi all,

     

    I have installed 6.1 and most of the packages detect old configuration folders, For example Surveillance Station, but it can't write on folders, I guess because permissions...

     

    Could you help me how to know what kind of permission should I make? 644 755 ???

     

    Thanks!

  12. 10 hours ago, IG-88 said:

    whats the hardware?

    if you had, 6.0 an now you try loader 1.02b (for 6.1) there might be drivers missing, 6.1 has a much smaller driver stock

    after booting with the 1.02b try to find the system with the synology assistant in your lan

     

     

    some of the two? more like one of the two? beside this, the system (dsm) is on every disk (raid1 over all disks automatically created when disk is "initialised"), that the way dsm works

     

     

     

    yes, there is a giude if you want to do it

     

     

    if you are sure you had 6.0 you can try it with a 6.0 bootloader and  look what the synology ass intent finds, as long as you dont install anything nothing will be changed, the bootloader should show up in network and should find the local dsm system and shoe you information like migrateable (when using a 6.1 loader with a 6.0 installed system)

     

     

    thanks for your help!

     

    The hardware is standard old PC GA-EP35-DS4 which was working pretty well...

     

    but How can we sure that is the boot USB which is corrupted? I would like to know what happened here...

     

    Thanks a lot

  13. Hi,

     

    My NAS was working very well for 1 year (6.01) and recently from 3 weeks ago (last reset). I did lost connection so I forced a hard reset. When I see what happens on a Monitor I can see that the systems stops on "booting kernel..." and nothing happens more about this screen.

     

    I tried to alternate and plug or disconnect some of the 2 HDDS I have (one of them with xpenology), nothing... I thought it was corrupt boot pendrive, so I tried to make a newer one (now with 1.0b2) and nothing.

     

    I also have booted with Ubuntu live and it can see HDDs, but obviously I need to use more tools for accesing that.

     

    I can't boot :-(

    Can you help me to know what is hapenning here?

     

    Thanks!

  14. Hello all,

     

    I am sorry if this is a repeated question. I have read Controversious information. There is a guide which says it is required... But some people on forums say that latests boots are not required anymore...

    Could you please tell me the true or where can I can find it?

     

    I would like to also ask about Sleeping... I have read on Synology official help that USB drivers will prevent to sleep... Is that correct? Because then with XPNOLOGY we can NEVER sleep our servers. Is that true?

     

    My main worries is about energy, for that reason I wanted to change MAC, for sleep and wake up lan etc...

     

    Thanks to all in advance

  15. Hi all!

     

    I just have discovered this community and I would like to thank you all for sharing your knowledge :smile:

     

    I am making my own tests and everything runs ok with custom PC with GIGABYTE GA-EP35-DS3. I have not changed serial or mac address yet, but I have full Wake on lan by mac hardware address.

    And I can poweroff via SSH root@ commands. It is ok!

     

    The problem that sometimes it is instant, sometimes it takes 20 minutes to poweroff!

    It seems that there aren't any users connected etc.

     

    Could you please help me why this may happen?

    Thanks in advance!

×
×
  • Create New...