• Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About passuff

  • Rank

Recent Profile Visitors

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

  1. Plane ein ähnliches Setup. Hast du es mittlerweile geschafft die Icy Box in Synology einzubinden?
  2. I tried to set Synology MTU manually to 1500. After network restart MTU was on automatic again.Is it a bug? I then set it to 2000 and it persists. Speed is ok now. Issue is solved. Even when I turn it to automatic again. I guess there is something buggy....
  3. I did the same tests with a original DS216 and DS416 and both had no troubles with IPv6. It seems it is connected to XPEnology. Someone knows where I can report bugs/errors?
  4. I'm using my DS for a while now with IPv4 without any issues. Unfortunately I had to change my ISP for one that is using IPv6 only. This means I need to access my DS now with IPv6 only. In LAN I can for sure access it with IPv4. THe problem currently is ,a that access from external or internal with IPv6 results in a lot of connection aborts and a very slow speed. I tried to setup another XPEnology on VirtualBox. The same slow behaviour on this machine unfortunately. I have a raspberry Pi that is working just normal with IPv6, so the issue is definetly not the router or anything else but the DiskStation. I'm wondering if it is something based on my wrong DS settings or on XPEnology? Anyone?
  5. Anybody moved to a more recent version as DSM 5.1-5022 without having the bug? Maybe someone updated to DSM 6 and can confirm this bug is not present anymore?
  6. hey trantor. what do you mean in detail? There is already a release which has that permission bug fixed? Gesendet von meinem SM-G920F mit Tapatalk
  7. I stayed with DSM 5.1-5022 because in newer versions either HDD spin down or encryption stopped working... As far as I know no one cared about it so far so I expect it to be a Xpenology bug and not Synology. I asked synology support team for that issue but they didn't reply.
  8. Did you solve the problem? I'm still on latest 5.1 because I'm afraid of the same issue happening again..
  9. I backed up files and completely restored file system with a fresh 5.2. I didn't restore the setting and did all manually again but still cant change permissions for encrypted folders. I finally solved it by just downgrading to 5.1. I'm afraid it's a bug of 5.2 and I will never be able to upgrade again..
  10. Folder access rights changed on some of my encrypted shared folders after updating to DSM 5.2. I identified it very fast and tried to change them back to the right way. Unfortunately I recieved the following error message: "The volume where the share is located does not support ACL. PLease refer to Help for more information." Refernig to help I found out that only ext4 volumes can handle ACL...But my single Raid volume is ext4 and was all the time... I tried to create a new folder and change access right. Everything went fine. THen I created a new encrypted folder and tried to change access rights and tadam, same error message again. So I think something went wrong when I moved from DSM 5.1 to 5.2.. Anybody has a clue how I can solve this?
  11. Thats how I finally solved it. Downgrade to initial 4493 and 5hen direct update to version 7. I need several reboot until server finally started properly. Now everything is working like it should. I even not lost any system property. ..
  12. Not working for me. After finally clicked on proceed button installation failed at 43%. Error message " file corrupted" (translated from german).. I'm even not able to install complete new version (185mb).. Ithink something is corrupted now.. Is there anyway to start from scratch again?