lolvince

Members
  • Content Count

    100
  • Joined

  • Last visited

Community Reputation

0 Neutral

About lolvince

  • Rank
    Advanced Member

Recent Profile Visitors

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

  1. lolvince

    DSM 6.2 Loader

    I was in 6.1.7, I should have done the migration in case N ° 2.
  2. lolvince

    DSM 6.2 Loader

    sorry i don't understand your question. I have an N40L which works in DSM 6.2.2-24922 Update 4 with the native network only, with the loader 1.03B and the drivers V0.5 for ds3615
  3. lolvince

    DSM 6.2 Loader

    see here : https://xpenology.com/forum/topic/21663-driver-extension-jun-103b104b-for-dsm622-for-3615xs-3617xs-918/
  4. lolvince

    DSM 6.2 Loader

    no need to add an additional LAN card with Driver extension jun ... my N40L works perfectly
  5. Yes it works well on my side too, but the fact of not declaring the MACs does not affect the functioning of the syno? suddenly, why declare the MAC in the GRUB file? does it serve to use official syno MACs like serial instead of the original MACs of our xpenology?
  6. Hello, for the USB Network Card should we add the MACs to the grub file also?
  7. lolvince

    DSM 6.2 Loader

    this loop is launched every 30 seconds, in any case it identifies an emulated synology ...
  8. lolvince

    DSM 6.2 Loader

    yes yes I imagine, but I went around the little application installed, but the notifications are based on this indicated in the control panel, and the one well push disabled ...
  9. lolvince

    DSM 6.2 Loader

    thank you for your reply. but I did not activate push notification: / I'm looking for what is causing this ...
  10. lolvince

    DSM 6.2 Loader

    I regularly get this error message: 2020-02-03T18: 38: 40 + 01: 00 N40L synocloudserviceauth: cloudservice_get_api_key.cpp: 21 Cannot get key 2020-02-03T18: 38: 40 + 01: 00 N40L synocloudserviceauth: cloudservice_register_api_key.cpp: 246 Validate api key failed: Serial number invalid 2020-02-03T18: 38: 40 + 01: 00 N40L ssnotifyd: pushservice_update_ds_token.c: 52 fgets failed 2020-02-03T18: 38: 40 + 01: 00 N40L ssnotifyd: pushservice_update_ds_token.c: 147 Can't set api key 2020-02-03T18: 38: 40 + 01: 00 N40L ssnotifyd: pushservice_utils.c: 325 SYNOPushserviceUpdateDsToken failed. 2020-02-03T18: 38: 40 + 01: 00 N40L ssnotifyd: pushservice_utils.c: 387 GenerateDsToken Failed is this normal? System info: DSM version: DSM 6.2.2 24922 UPDATE 4 Loader version and model: JUN'S LOADER v1.03b - DS3615xs Using custom extra.lzma: 1.03b_mod ds3615 DSM 6.2.2 v0.5_test Installation type: BAREMETAL - N40L
  11. Thanks for the work;) Patch successfully applied! System info: DSM version: DSM 6.2.2 24922 UPDATE 4 Loader version and model: JUN'S LOADER v1.03b - DS3615xs Using custom extra.lzma: 1.03b_mod ds3615 DSM 6.2.2 v0.5_test Installation type: BAREMETAL - N40L
  12. lolvince

    DSM 6.2 Loader

    Hi ! well I confirm, everything is back to normal;)
  13. lolvince

    DSM 6.2 Loader

    thanks for your reply, i just did this, and i was going to indicate it. it seems to work perfectly. I just go back down my configuration and my packages from my backup while keeping my data present on the existing volume.
  14. lolvince

    DSM 6.2 Loader

    The clean installation on my N40L with the same USB dongle is OK, which means that if Synology detects a suspicious installation, it "breaks" it, and it will require reinstallation to find something clean ... reinstalling DSM on a "corrupt" volume also does not work. you have to start from 0 and go back down a backup ...
  15. lolvince

    DSM 6.2 Loader

    Hello, my backups made via Hyper Backup on C2 from my N40L are ok on a RS820 + NAS. so I saved all of my N40L on another NAS as a backup. I reinstall my N40L on another HDD in order to validate the loader and my config. if it is OK, I go back down my backup of my N40L after having reset it!