NAS Odyssey: Up and running

After lots of attempts (see here, here and here), I have finally resolved my disk space problems and the RAID-5 NAS server is up and running since about two weeks now. I have stayed with Fedora 6, successfully installed Samba, configured the shares and copied all family JPEG’s, videos, MP3’s etc onto the huge 907 GB large RAID5 share. The old NSLU2 is still dead – I did not have any time to try to re-flash it, but all content of it’s disk was without any issues readable by the new server (the NSLU2 was using ext3 filesystem) so I did not even have to try to use backups.

Most of things in Fedora can be configured graphically. The only case I had to go to shell were final configuration changes in Samba. As it turned out, the default umask allowed search on directories (rwxr-xr-x), but none on files (rwx——). This lead to strange behaviour when the images were visible from Windows client – user could see the file names in the directory but no viewer could display them. Fix was trivial:

find . -name “*.jpg” -exec chmod +r ‘{}’ \;

It’s kind of funny how old skills reapper when you need them. Unix is like riding a bike: you get uncomfortable and out of form but you never loose it completely. I even remembered quite a few vi and emacs key combinations (but happily switched to use gedit or JEdit).

One thing that did not work out of the box was VNC server (I am getting ready to disconnect monitor and keyboard, move the box under the desk and forget about it for next year or so :-)). When attempting to start the VNC server using the GUI interface – it does not report any error, but does not start either. When trying from command line (using /sbin/service), the error explained the problem with Xstartup. I found this useful info, will try it out.

So far I am very happy with performance of the system (I have copied about 150 GB of content on the NAS).

Lessons learned:
– the “NAS” like distributions (FreeNAS, NASLite+) have variety of limitations (like lack of readonly/readwrite access support, user access rights) and are basically all-or-nothing solutions
– OpenFiler is not good solution for home network either. It goes to the other extreme – unless you have domain controller, you are out of luck, as it does not support local users
– from full distributions, Fedora provides everything you need to have NAS as well as well user friendly environment for administration. To be fair, I did not try OpenSUSE or Mandriva. Ubuntu – despite being known as the “most user friendly” distro did not work for me: the desktop edition (which indeed was great user experience) does not contain server components and the server edition requires really experienced Linux admin as it has no GUI at all.

All summed up: lots of fun. Worth every penny.

Explore posts in the same categories: linux

One Comment on “NAS Odyssey: Up and running”

  1. Peter M. Says:

    Hi Miro,

    link you’ve found – – is a very nice explanation of how I am using VNC for over 2 years. I would add two things:
    1. servers configured in /etc/sysconfig/vncservers are started automatically upon system start (quite convenient, but they eat resources even if not used).
    2. ~/.vnc/xstartup: add following line near the top (before ‘exec’):
    vncconfig -nowin &
    This will enable clipboard transfer between host system and VNC server.

    I am using vino (Gnome remote desktop) as well, on my new Fedora/Gnome desktop machine. Vino needs you to start the X session locally (monitor/keyboard attached), then you can use both local and remote access (sleeping with notebook :-),

    Take care

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: