shackwove

okay! thanks

Tested and working perfect with this update! I'm on Update 2. Do i have to follow the same procedure as the first post to update from Update 2 to Update 7? Or can i just do it the normal way?

Yeah this is unfortunate -_- i don't feel to good about adding all these other random sources to be honest

Yes everything is working here : fileshanker> pwd /root fileshanker> ls -la drwxr-xr-x 5 root root 4096 May 7 23:59 . drwxr-xr-x 24 root root 4096 May 3 13:47 .. -rw------- 1 root root 16 May 7 23:59 .esd_auth drwx------ 2 root root 4096 May 2 19:42 .gnupg -rw-r--r-- 1 root root 366 Feb 14 12:08 .profile drwx------ 2 root root 4096 May 8 00:43 .pulse -rw------- 1 root root 256 May 7 23:59 .pulse-cookie drwxr-xr-x 2 root root 4096 May 2 19:15 pci -rw-r--r-- 1 root root 249507 Feb 22 11:45 syno-i686-bootstrap_1.2-7_i686.xsh fileshanker> openssl version WARNING: can't open config file: /usr/syno/ssl/openssl.cnf OpenSSL 1.0.1g-fips 7 Apr 2014 The dpkg_upgrade.log : 2014/05/02 16:40:28 ===========[-x /volume1//@smallupd@te_deb/smallupdate_4.3-3827-s2_all.deb /smallUpd@teTempFolder]===== 2014/05/02 16:42:16 ===========[-i /smallupd@te/iptables-1.4.2-bromolow-bin_1.4.2-3827-s1_all.deb ]=========== Authenticating /smallupd@te/iptables-1.4.2-bromolow-bin_1.4.2-3827-s1_all.deb ... passed Selecting previously unselected package iptables-1.4.2-bromolow-bin. (Reading database ... 0 files and directories currently installed.) Unpacking iptables-1.4.2-bromolow-bin (from .../iptables-1.4.2-bromolow-bin_1.4.2-3827-s1_all.deb) ... Setting up iptables-1.4.2-bromolow-bin (1.4.2-3827-s1) ... 2014/05/02 16:42:17 ===========[-i /smallupd@te/libsynosdk-bromolow-bin_4.3-3827-s1_all.deb ]=========== Authenticating /smallupd@te/libsynosdk-bromolow-bin_4.3-3827-s1_all.deb ... passed etc etc A quick google search leads me to believe that this is a permissions issue. Maybe try to run the update as admin? Also did you run the commands as root? Also, these are strange to me : gpg: keyblock resource `/var/services/homes/root/.gnupg/secring.gpg': No such file or directory because i don't have these directories either. I don't have User Homes enabled though, maybe you do and it's causing issues? Control Panel > Users > User Home p.s tu peux aussi ouvrir un thread dans la section FR du forum, même si ton anglais n'est pas mauvais à mon avis.

For an added layer you can forward a port in your router to your SSH port on DSM. Your router's config would look like this : External port : 35775 Internal port : 22 now you only have to connect to it using ssh -p 35775 user@ip You can also disable the ability to ssh as root, this is common practice to any ssh box, you can then login as say "admin" and then switch to root if you have to. DSM is particular tho and we have to change something first or we won't be able to switch user afterwards. 1. Login as ssh root@dsm 2. Change permissions on /bin/su with chmod a+s /bin/su 3. Try it, login with ssh admin@dsm 4. Type su 5. Enter password and type whoami < this should return "root" 6. Disable root login in /etc/ssh/sshd_config as root user do vi /etc/ssh/sshd_config locate the line that says #PermitRootLogin yes Press insert and edit it so it looks like "PermitRootLogin no" Press escape and type ":wq" and press enter 7. In the web GUI, Control Panel > Terminal > Disable SSH and apply > Enable SSH and apply 8. Try to connect as root, it shouldn't let you anymore, so connect as admin That's it, nobody can longer connect to your DSM as root but you still have root capabilities! Place your cursor over this line

DSM dit "Raid" même si mets un seul disque pour te donner la possibilité d'éventuellement convertir ton volume en ajoutant un disques. En bref, tu n'a qu'a choisir raid et tu vas pouvoir créer un volume avec un seul disque. Répète à nouveau pour le second.

Well with the USB method you definitely can and should remove it after the system has booted, should be the same with the CD?

Panneau de configuration > Dossier Partagé Tu devrais voir tout tes dossiers, il suffit de redonner les droits à ton compte

Kind of solved. I installed Trantor's 4.3 beta7 + update 2 on volume1. Did a clean installation over 5.0 4458. With 4.3 running great i then plugged in the 2 4TB drives (now that's where it would boot to the DSM installation that was present on the 4tb volume when i tried gnoboot) but with Trantor's it booted onto my recently installed 4.3! Upon booting, DSM immediately recognized volume2 and mounted the share i had created on it. Clicked on repair and i was done. This is exactly how i wanted it to behave so i'm pretty happy about that Too bad i won't be using 5.0 but that's fine.

I got the button but my download fails? its accepted, any ideas? I remember it didn't work everytime so you might want to try again. First try, asking me to install python : After installing python all is working! :

If you are unable to get your former DSM installation working again you can always mount the hard drives in your main computer or from a live CD such as Ubuntu. Synology has a good write up about it http://www.synology.com/en-us/support/faq/579 i was able to access my Raid 1 that i created in DSM using this method.

Ça ne marche pas directement, suis les instructions ici : viewtopic.php?f=2&t=2999

Je trouve que c'est le plus gros désavantage d'utiliser DSM, j'aimerais avoir plus de contrôle sur la gestion de l'installation Par exemple ça serait bien de pouvoir simplement ajouter des disques qui contiennent déjà du data sans devoir formater. Ou de simplement ajouter des disques et les formater en ext4 ou ntfs pour pouvoir les déplacer facilement d'une machine à une autre.

Même en choisissant "Les mise à jours importantes seulement" comme dans ce screen? J'ai aussi passé de 5.0 à 4.3 il n'y a pas 3 heures et j'ai pu updater à Update 2 As-tu fais clean installation ou as tu migré?

Easy as 1-2-3, thanks for putting this up there!