Showing posts with label NAS. Show all posts
Showing posts with label NAS. Show all posts

Saturday, November 16, 2013

installing Oracle "Java SE for Embedded" on a Synology NAS


I think, I will use his description for setting up Java on my Synology NAS (resp. NASs), so that I can run the Hibiscus Server (implemented in Java) on them. My NAS at home has plenty of Internet bandwith available, so that I can get my bank account transactions updated over the Internet quite often each day.

Oracle's description on "Oracle Java SE Embedded Downloads":

For the DS112+ I chose the "ARMv5 Linux" entry "successfully". The ARMv6/7 and ARMv7 entries did not run at all. 

For the DS213+ I chose the "Power Architecture Linux - … - e500v2" entry "successfully".

Wednesday, November 6, 2013

Synology® Releases Its Latest 2-Bay High Performance NAS for Small Business – The DS214+

Tuesday, November 5, 2013

"Synology unleashes its most affordable 2-bay NAS ever, the DS214se for $160" says 9to5toys


You may want to compare the specs of the DS213+ and the DS214se. I still quite like to own the DS213+.

Monday, October 21, 2013

VirtualBox vs iSCSI

iSCSI supposes Gigabit LAN, so that's a good reason to replace my last non-Gigabit FRITZ!Box by a Gigabit one.
Somebody will get my last FRITZ!Box 7270 (non-Gigabit), and I will get me a new FRITZ!Box 7490.

Friday, October 11, 2013

DVB-C (and DVB-T2/-T) for my Synolgy NAS "diskstations"

It needs the following software:

    These two mentioned diskstations are compatible with these two DVB-C USB connectable devices:

    This DVB-T2 /-T/-C USB connectable device would be my favourite, if it were supported by dvblogic for the NAS-s mentioned above and also for the Raspberry Pi:

    Sunday, September 15, 2013

    my new UPS: APC BE700G-GR


    • Now my Synology DS213+ (NAS) gets its power from the UPS, and the UPS also controls USB-wise, when the NAS goes to "Safe Mode". For the USB-connected NAS, this is "local UPS support". This Synology device is now the "Synology UPS server", that controls, the remaining Synology DiskStations powered by the UPS.
    • My Synology DS112+ (NAS) uses the DS213+ as "Synology UPS server".
    It feels well, to have your NAS-s powered by your UPS.

    Thursday, August 29, 2013

    my new "mobile NAS": Synology DS112+

    DS112+ Products - Synology Inc. Network Attached Storage


    Installation procedure from CD-ROM:
    • you are starting with a DiskStation with a bare disk, i.e. no DSM (the DS Management system)
    • mount the supplied CD-ROM
    • mount DSAssistant-SYNOLOGY_….dmg from the CD-ROM
    • run the assistant App from there
    • the assistant App helps you installing the DSM, either from a  DSM_DS112+_….pat file (around 40 MB large) on the CD-ROM (it comes with DSM-4.1) or from a file you download from the Synology website (bleeding edge: DSM-4.3)
    • that includes formatting the hard disk
    Installation procedure following following the quick set up leaflet:
    • surf to find.synology.com
    • it is meant to discover all reachable Synology DiskStations
    • in this situation it does not find the DiskStation in question (running a DSM)
    • it points you to DSAssistant-SYNOLOGY_….dmg, to be downloaded from the Synology website
    • mount the downloaded DSAssistant-SYNOLOGY_….dmg
    • run the assistant App from there
    Because I had temporary trouble accessing the supplied CD-ROM, I had to download the DSAssistant…, but I used the DSM-4.1 on the CD-ROM. That decision was unreasonable and done a little too fast, as I seriously intended to operate using DSM-4.3. So in the meantime I downloaded DSM-4.3, and after having set up DSM-4.1 entirely and properly, I set up DSM-4.3.

    Further steps:
    • setting up a personal user account
    • allowing SSH access
    • SSH log-in in using the root account
    • modifying /etc/passwd to allow shell login for the user accounts in question (the resp. record has a "nologin" instead of a proper shell path)
    Further steps:
    • I followed the instructions listed in my own "my new NAS (…): Synology DS213+" (taken from somewhere else and my own experience)
    • install the ipkg installation system
    • install a proper rsync through ipkg; I will have to call this rsync as /opt/bin/rsync from now on
    • "standard standard" installation is broken for the DS112+, but the wiki page describes the actual standard procedure including a fix in some bootstrap.sh
    • commenting out the standard PATH setting in ~root/.profile and ~MY_ACCOUNT/.profile
    • my first personal rsync-s to the DiskStation

    Sunday, July 7, 2013

    NFS mount behind NAT (virtualbox)

    NFS mount behind NAT (virtualbox) | The GNULinux Community Portal

    The situation and trouble described there is rather similar to my set-up (VirtualBox + NAT + Linux guest), just that my NFS server is a Synology DiskStation.

    I added "insecure" to the options of this share, switched off "Enable NFS" on the DiskStation, made sure the option is still there, enabled NFS on the DiskStation again, finally mounted the share again, and it was there – what a surprise!!!

    I still have a UID mapping problem with this set-up.

    Wednesday, June 19, 2013

    disk back-ups sorted, new scanning computer sorted – happily looking forward

    Integrated my "new" Synology NAS into my back-up concept in practice; I can of course back up at home on the LAN, but I can also back up over WAN (which is the more crucial variant) – rsync-wise "of course", i.e. sort of "differentially". And for the time being rsync-ing to my NAS seems to work as well again. I can talk to the NAS Mac-wise ("AFS"), and through SSH / RSYNC / SMB, but I have not accessed it successfully through NFS yet – which would be nice for accessing it from (openSUSE) Linux.

    I also manage again backing up to USB disks from my VirtualBox openSUSE guest OS.
    But occasionally I install openSUSE updates, and they enforce OS restarts, which I usually delay for far too long, so in the meantime no back ups and no access at all to my "Encrypted Big Disk" outside my computer, where I keep all sorts of long-term data.

    I got me a Mac Mini, that stays of course in the office room, and it talks to the printers and the scanner, and of course it talks to the NAS. So I can take, whatever comes in from wherever (I am referring to the letters in my mailbox, that I am supposed to take out on Fridays on my arrivals at home), and take that stuff to my "scanning facility" and get them scanned, move the files to the NAS, so I can pick them up from there from wherever. Even from outside over the WAN. If there's enough time, I can even name the files properly.

    All this doesn't really do the work to be done itself, but it facilitates achieving things. It makes me look forward a little happier and more optimistic. I do know now, how to achieve certain things within my rather limited time.

    How to access files on Synology NAS NFS-wise ...

    How to access files on Synology NAS ... - Synology Inc. Network Attached Storage - NEW NAS Experience

    Maybe I will have to play a little with the "Root squashing" next time, I have LAN access to the NAS. Remember: NFS goes over LAN, not WAN (AFAIRC).

    Saturday, March 9, 2013

    my 1st concurrent backups from my Mac and my openSUSE Linux VM to the Synology DS213+

    With the "alternative rsync" (see my older article on rsync and Synology!) things started looking a little more successful.

    Apparently a lot of files by the name "@eaDir" get created "automagically" in various subdirectories. And as I usually start rsync with "--delete-after", they all get removed in the end. I am not sure, whether the DiskStation OS ("DSM") likes that, so for the time being I will do w/o that command line option. I will investigate the "@eaDir" issue "in the near future" (TBD).

    Another issue: lots of messages like "cannot chgrp …". Apparently that's because the group identifier on the source system does not exist on the target system. I definitely don't want to see that message, so something must be done in that area (TBD).

    It really is a relief to have a regular backup procedure in place again.

    "rsync over ssh" to a Synology NAS – IPKG, opkg

    Nota Bene / before:
    • This is the text, that helps me personally re-installing rsync, whenever it magically disappears, maybe caused by an DSM update.
    • True, I should bring a little structure into this article.
    • I never ever care about rsyncd, as I am doing "rsync over ssh";  any activity suggested regarding rsyncd does not concern me. (But then sometimes I am misled, and I erroneously do invest time in false paths, and I do get into problems that are actually rsyncd-related.)
    • I have my own ways of backing up data.
    • I have my own ideas of keeping data long term outside my computer's built-in disks.

    The Synology system provided rsync is not for me. It's somehow modified and spoilt.

    backup - Rsync over ssh: "ERROR: module is read only" suddenly appeared - Server Fault

    Well, it's not only me experiencing weird effects with the "built-in" rsync. And I think, quite a few of the answers to that forum article do not quite fit at all.

    The details of the case:
    • "rsync over ssh" does not use the remote rsync daemon at all, i.e. no rsyncd.conf applies
    • it's not unlikely, that these rsync problems have to do with a Synology special version of rsync
    • after this: "DiskStation> /usr/syno/etc.defaults/rc.d/S84rsyncd.sh stop", the error message does not change, so it's really not an "rsync daemon" issue, as that one is no longer running
    I fixed this problem by installing an rsync package provided on an Unslung Project repository for the CPU used within my Synology NAS. This brings dependencies on the Unslung Project, their IPKG installer, their Optware, their specific Synology repository. This kills me a little, to be honest.

    I mainly followed the "German Synology wiki" on IPKG. (Anxiously as I am, I do keep a backup of that article at …/com/synology-wiki.de/ . Yes, I do have an idea, that this step alone is rather in vain.)
    So, well 1st I had to install IPKG itself.
    My CPU on the DS213+ is an e500 (actually: e500v2), so I went the e500 way in their description.
    My CPU on the DS112+ is a "Feroceon 88FR131 rev 1 (v5l)", there is a note on how to deal with the DS112+, pls follow that one.

    Then I installed the rsync package provided by IPKG.

    An entry for /etc/rc.optware got created in /etc/rc.local, and they suggest to remove it, and I did that.
    I am not sure, it concerns me at all, as I mention "my" rsync on the NAS by full path on my command lines outside the NAS.

    Now my only minor problem with the "alternative rsync" is, that I have to specify the remote rsync on my local rsync command lines like this: "--rsync-path=/opt/bin/rsync". That's a PITA, but that's not too hard.

    Update 2013-08-31: en.wikipedia.org/wiki/Ipkg says IPKG was discontinued. en.wikipedia.org/wiki/Opkg is the follower, code.google.com/p/opkg/, but it hasn't really taken off.

    the wikis for the Synology DiskStation

    Saturday, March 2, 2013

    my new NAS (and so much more): Synology DS213+

    DS213+ Products - Synology Inc. Network Attached Storage

    The box makes itself known as diskstation.local resp. DiskStation on my LAN. (Reliability …)

    Of course it deserves a "1 Gbit/s" on my FRITZ!Box.

    The box's OS is BusyBox; here are a few more details:


    DiskStation> uname -a
    Linux DiskStation 2.6.32.12 #2668 SMP Tue Dec 11 13:01:16 CST 2012 ppc GNU/Linux synology_qoriq_213+


    I enabled SSH access for my personal user account rather soon, but the SSH login was not instantly successful. I tried "ssh -v", and from there the login seriously looked, as if it was almost successful. My web research wasn't successful either. Rather desperately I enabled "telnet access"; I tried to log in, and this was the result:
    login: can't run /sbin/nologin: No such file or directory
    It was clear then, that the default shell in the /etc/passwd entry for my user account was in my way /sbin/nologin so far. I made /bin/ash the default shell and everything was fine. Of course, I disabled telnet access again thereafter. And of course, once I added "nologin" to my web query, I found a few articles describing the issue.

    SCP works; "rsync over ssh" (with my personal user account) does not work yet:

    $ rsync -va --rsh='ssh -l root' /etc/motd diskstation:tmp/ # works$ rsync -va /etc/motd diskstation:tmp/ # fails
    sending incremental file list
    ERROR: module is read only
    rsync error: syntax or usage error (code 1) at main.c(1034) [Receiver=3.0.8]
    rsync: connection unexpectedly closed (9 bytes received so far) [sender]
    rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.8]
    Fiddling with /etc/ssh/sshd_config – I really don't know, what to change in order to overcome this obstacle.


    Perl is not part of its standard equipment, but Python apparently is,

    Through their Download Center I found this FTP server link. You can find various software for their boxes on their. There are also Perl installation packages, but the ones I tried are not for the current firmware release of "my" box, and in a way I am not up for an upgrade to beta software for my NAS.

    (For now I summarised here everything I have tried so far, so I will be able to procede from here.)

    A few more links:
    There are suggestions on the wiki(s) to install ipkg (yet another packaging system, not officially supported by Synology), and to install another rsync through ipkg. I may consider this, but I am not yet sure. I am quite able to use rsync (over ssh) as user root, but I am not with my personal account. I have no clue, what rights it needs, to allow my personal account to work as smoothly as user root. (To Be Solved!)

    To be continued …