Polanskiman

Administrators
  • Content Count

    2,512
  • Joined

  • Last visited

  • Days Won

    86

Polanskiman last won the day on January 28

Polanskiman had the most liked content!

Community Reputation

341 Excellent

About Polanskiman

  • Rank
    No one

Recent Profile Visitors

14,923 profile views
  1. I am locking this thread temporarily as the OP is updating/improving the script.
  2. This tutorial is to update to DSM 6.1. The person wants to install DSM 6.1 not DSM 6.2. Loader v1.02b is perfectly suitable for that or did I miss something? This said @than you could still update to DSM 6.2. However you would need loader v1.03b (assuming you are using DS3615xs/DS3617xs) as mentioned by @IG-88. No need for a new NIC if you do not go beyond DSM 6.2 (DSM 6.2.1, DSM 6.2.2) in which case you will need preferably an intel NIC (HP NC360T card for example). Did you disable C1E in the bios? As stated above you do not need a different NIC for DSM 6.2. Only for versions above that (DSM 6.2.1 and higher). Also if you are upgrading from DSM 5.2, you will need after the update to delete the .xpenoboot directory under Root (/) via ssh.
  3. For the community, please note that this critical update does NOT apply to DS3615xs and DS3617xs.
  4. To quote you: Good point.
  5. The question(s) in this topic have been answered and/or the topic author has resolved their issue. This topic is now closed. If you have other questions, please open a new topic.
  6. Good call on the CPU. DS3617xs always had some issues where the GUI stops working at some point due to some shared libraries having some invalid ELF header. I am not sure why this happens but I have not seen this happen on DS3615xs. It's not a drama as it is possible to fix this rather easily. The libraries in question are libsynopkg.so.1 and libsynoshare.so.6. It's just a matter of replacing them with those from the PAT file. For reference:
  7. A word of caution here. DS3617xs has some issues which have been documented over and over again in the forum. Issues might arise randomly in a week, a month or a year. It's easily fixable yet problematic as you have a sword over your head. @IG-88 Can DS3615xs be used with his hardware?
  8. Avez vous désactivé la carte réseau interne de la carte mere?
  9. Deja il faudrait commencez par nous donner le switch que vous utilisez et le le type de Bond que vous essayer de faire.
  10. @bearcat My little finger tells me he wants it as a server but I could be wrong. @norbert A quick Google search gave back the following results: https://github.com/runfalk/synology-wireguard https://www.reddit.com/r/synology/comments/a2erre/guide_intermediate_how_to_install_wireguard_vpn/
  11. The question(s) in this topic have been answered and/or the topic author has resolved their issue. This topic is now closed. If you have other questions, please open a new topic.
  12. Try with the hard disable flag: synoservicecfg --hard-disable pkgctl-Serviio synoservicecfg --hard-disable pkgctl-java8
  13. Try this: synoservicecfg --status pkgctl-java8 if status is 'enable' and is 'start' then: synoservicecfg --disable pkgctl-java8 Do the same for Serviio: synoservicecfg --status pkgctl-Serviio if is status 'enable' and is 'start' then: synoservicecfg --disable pkgctl-Serviio Restart your machine by issuing the following command: reboot Try logging through GUI again.
  14. Try the following command: Htop This will give you the CPU activity in real time and show you if there is anything running heavily. Should point to the right direction.