Hot answers tagged

25

For future reference: after way too many hours researching and debugging this issue, I finally discovered the root cause. The OpenSSH version used by Synology is a highly customized version, that does not behave like the original code. It has lots of hacks and ad-hoc customizations - e.g., additional checking before accepting a login to see if the SSH ...


8

Apart from Favourites list have you checked if the volumes are listed in Volumes and Devices tab in iSCSI initiator properties? And are they set to Auto Configure? This should (in theory) make sure that all volumes are initialized. Source


7

rsync doesn't do SFTP. From the man page: There are two different ways for rsync to contact a remote system: using a remote-shell program as the transport (such as ssh or rsh) or contacting an rsync daemon directly via TCP. SFTP doesn't give you a shell, ergo it doesn't work for rsync. You'll need an SSH connection instead. Once you've ...


6

To circumvent the problem, and since I installed bash via ipkg and I can't be sure /opt will always be available (mounted correctly), I simply put the following in my .profile [ -x /opt/bin/bash ] && exec /opt/bin/bash while /etc/passwd contains /bin/ash as shell.


6

It looks like the system splits up each drive into as many partitions as needed to create a series of RAID5 and/or RAID1 arrays that minimize the amount of unused space on the drives. Those RAID arrays then become physical volumes under LVM, which, in turn, presents all that storage as a single logical volume. Current versions of mdadm do allow you to add ...


5

You can install dstat as a replacement for iostat dstat - 0.7.0-1 - dstat is a versatile replacement for vmstat, iostat, netstat, nfsstat, and ifstat You can install it by using ipkg which allows you to download other tools as well. See the following links: http://forum.synology.com/wiki/index.php/Overview_on_modifying_the_Synology_Server,_bootstrap,...


5

you need to ssh to the synology using root account with your default GUI password. go to directory /var/packages/Tomcat/target/apache-tomcat-6.0.36/conf/ edit the file Tomcat-users.xml stop and restart Tomcat server now can login with your new account


4

You can change the login shell by editing /etc/passwd. Each line is a list of colon-separated values, the last of which is the login shell: user:x:1000:1000:User:/home/user:/usr/bin/zsh If /etc/shells exists, you should add zsh (full path) to it, else some services may not work for your user. Note: I'd suggest against changing the login shell for root (...


4

No there wont be any down time, this really is a standard thing to do now in enterprise, where always up availability is key. LVM does this expansion in the background and it is pretty much instant, it wont have any effect on services, I do this once or twice a week on my estate and haven't had a problem yet


3

Raid 5 is a good compromise between protecting you from data loss and capacity efficiency. However, Raid 1 read performance is better if that matters you. Even when using Raid, you should consider using a good backup solution. Using any Raid level as opposed to backup does not protect you from accidentally/intentionally removed files. I think it is ...


3

True in the past. However, as of Synology DSM 3.1, Synology Hybrid RAID will now have the ability for two redundant drives. This makes the Synology solution much more appealing to me, since I prefer to reuse older, excellent drives over buying four to six new drives every few years. This also allows for expansion by removing the smaller drives and ...


3

You will want to confirm that the model you are interested in can present iSCSI sessions to the number of ESXi boxes that you need to support. Other possibly concerns - single Gigabit interface, slower CPU's\Controllers and thus throughput. The 810+ looks to be capable of supporting about 100Meg/sec sequential write \ 80-100 write IOPs with 4 disks in ...


3

You can change this in your DSM Control Panel. Under Connectivity > Network > DSM Settings you can set the ports. Obviously, make sure that if you have another webserver running on your NAS like Apache, it doesn't listen on those ports.


3

No the existing data will not be erased when you add a disk to the SHR array. The message is simply saying the new drive being added will be formatted. Your data and applications will actually remain available during the expansion process; there is no need at all to even stop using the NAS whilst SHR Vertical Expansion is taking place. That said - before ...


3

First: DON'T ever use a RAID5, especially not with disks that size. The reason is that it's very likely you end up with an error during a rebuild after a failed disk, which will make the array a total failure. To your questions: one hard drive crash I can replace failed disk with a new similar one and embedded software will rebuild the entire system ...


3

EDIT: Ok, so event 113 is KB972107, which is a fairly generic class of problems, but the "...network stack is not fully prepared" caught my attention. Then we see the more interesting event 103. See this experts-exchange post with a similar issue... If I attach them while the server si running, everything appears to function correctly, but if I reboot, ...


2

This was a stupid mistake on my part. Needed to put a / in front of volume1/myshared 192.168.1.*(rw,sync,no_wdelay,no_root_squash,insecure_locks,anonuid=0,anongid=0) so that it becomes /volume1/myshared 192.168.1.*(rw,sync,no_wdelay,no_root_squash,insecure_locks,anonuid=0,anongid=0)


2

As far as where you would find the folder path (/volume1/vms), its at the bottom of the NFS Privledges window in DSM.


2

you can do this by adding the following to your sshd_config DenyUsers username@host for example when you want to ssh acces from the 80.25 ip-range for root: DenyUsers root@80.25.* From the manpages: The allow/deny directives are processed in the following order: DenyUsers, AllowUsers, DenyGroups, and finally AllowGroups.


2

Make sure add to favorites and enable muilti-path is selected when you connect to targets: When you discover portal, click advanced, don’t use defaults click “Microsoft iSCSI Intiator” and you’re NIC IP for Initiator IP.


2

rsync (3.0.9, at least) has a --chmod option, here's what it does: This option tells rsync to apply one or more comma-separated "chmod" modes to the permission of the files in the transfer. The resulting value is treated as though it were the permissions that the sending side supplied for the file,


2

RSync uses something call a 'module name' it's kind of like a 'share name' (for windows). The Synology's default 'module name' for RSync is NetBackup (I assume it's case sensitive). So if you change your command it should work: From: c:\cygwin\bin\rsync -avz /cygdrive/e/Lisa/ Lisa@192.168.1.10:/volume1/homes/Lisa/Backup To: c:\cygwin\bin\rsync -avz /...


2

Your drive overheated at some point in the past. 190 Airflow_Temperature_Cel 0x0022 061 038 045 Old_age Always In_the_past 39 (0 4 43 37 0) Unfortunately it's not possible to be 100% sure of the exact temperature that it reached, only that it was quite a bit beyond the vendor's defined threshold. Though it's most likely that the normalized ...


2

Yes, I have done this. At least, I have removed all the drives, and put them back in, and powered up without data loss. I have not swapped drives in the middle.


2

I figured out a workaround in case anyone else runs into this issue: It looks like the count is based on the number of drives connected and will take the first available number, so what I did was this: Disconnected drive 2 (usbshare2) Connected a spare USB drive I had laying around (format does not matter) Disconnected drive 1 (usbshare1) Connected ...


2

It seems to me that you're happy with rsnapshot but not with tar. If so, the solution is to replace tar with something that preserves the 'only changes' of rsnapshot. Out of my head, I can thing of two easy options: after rsnapshot, find the differences between the last and previous snapshots to store only those to a tar file. It could be simply diff, ...


2

You either have an IP conflict (likely) or a MAC address conflict. There is no other reasonable way for this to occur. If you really can't find the IP conflict, try sending out an arping to the target IP address using the arping utility for linux, or something like that. Watch what comes back. If you want you can even run wireshark and watch the traffic. ...


2

I cannot say specifically, however - if you add a disk to a RAID config, it'll need to be wiped to become part of your RAID. Losing that data is - as you surmised - inevitable. When it comes to the original data though, the answer is a little more complex - RAID, depending on type, will differ in where it writes data in a two drive configuration, as opposed ...


2

In short, yes... you would have a problem with RAID6 and using a smaller drive. RAID6 itself has no way to dynamically re-size the RAID to a smaller disk. You must either: have a RAID controller capable of dynamically resizing the RAID volume copy your data elsewhere, and completely rebuild the RAID and then restore the data back to the volume. I have ...



Only top voted, non community-wiki answers of a minimum length are eligible