Posts by drap

Hi,
Bit of a strange problem, but if a file name has a character outside of English alphabet eg. é, then Minidlna refuses to index it and Greyhole fails to move it from the Landing Zone, until I rename the file without the é.
Is there some sort of character encoding etc that I need to change?
Thanks,

Update: Solved the problem. Make sure the locale in /usr/bin/greyhole is the same as the locale when typing

locale

in the terminal.
Eg.
/usr/bin/greyhole:

//setlocale(LC_COLLATE, "en_US.UTF-8");
//setlocale(LC_CTYPE, "en_US.UTF-8");
setlocale(LC_COLLATE, "en_GB.UTF-8");
setlocale(LC_CTYPE, "en_GB.UTF-8");

locale:

LANG=en_GB.UTF-8
LANGUAGE=en_GB:en
LC_CTYPE="en_GB.UTF-8"
LC_NUMERIC="en_GB.UTF-8"
LC_TIME="en_GB.UTF-8"
LC_COLLATE="en_GB.UTF-8"
LC_MONETARY="en_GB.UTF-8"
LC_MESSAGES="en_GB.UTF-8"
LC_PAPER="en_GB.UTF-8"
LC_NAME="en_GB.UTF-8"
LC_ADDRESS="en_GB.UTF-8"
LC_TELEPHONE="en_GB.UTF-8"
LC_MEASUREMENT="en_GB.UTF-8"
LC_IDENTIFICATION="en_GB.UTF-8"
LC_ALL=

It has been suggested elsewhere to also increase the notify interval in the minidlna.conf file

notify_interval=90000

I tried this on my setup and my connection between server and TV (UE40ES6800) has been fairly stable, I have still had the occasional disconnect though.

I actually agree with you in that it's difficult to diagnose since I cloned a USB. At some point I will reinstall, I don't have much really, but I setup Greyhole manually - that's probably the most tricky to successfully reinstall.
I think this thread is moving away too much from the OPs problem. I'll update my own thread if I continue to have the same issue once (when) I reinstall.
Thanks for the help.

I take your point about ECC ram, although I hope not to need to change it.
I am not blaming OMV, sorry if it came across that way, in fact I am extremely grateful that such a piece of software exists.
I haven't used jmiller's script (is that the write minimisation one?) can you point me to it?
Thanks,

No. Why?
Are you asking because I mentioned transmission? I use torrents to share simulation data between home and university.

I didn't see the OP mention a confirmed "lockup" only that he couldn't log in via ssh or web interface - I had the same problem. In my case the server would respond to pings and further after rebooting and logging in the log clearly shows that the server was still up and running but, for example, transmission couldn't connect to any trackers. Hence my opinion that it was a network issue (either hardware or software) rather than an issue related to memory or installation media.

MnM, when this happens next, can you see if OMV responds to pings and if the syslog has been updating during the period in which the server was unaccessible.

It seems many users have a similar problem, myself included (http://forums.openmediavault.org/viewtopic.php?f=15&t=1581), with no resolution.
Often users are installing on a USB drive, but in both of our cases we're installing on an SSD.
Hopefully OMV 0.5 will address this problem.

I've rebooted my router a couple of times, but still wouldn't put it past being a router problem. My router is the horrible one that Sky (UK) provide, unfortunately you can't change them (I don't think).
My SSD is a SanDisk Ultra 120gb.
I've re-partitioned now to have a 2gb swap partition,

/dev/sda1             7.5G  1.2G  5.9G  17% /
tmpfs                 1.9G     0  1.9G   0% /lib/init/rw
udev                  1.9G  132K  1.9G   1% /dev
tmpfs                 1.9G     0  1.9G   0% /dev/shm
tmpfs                 1.9G  832K  1.9G   1% /tmp
/dev/sdb1             230G   88G  130G  41% /media/6ff58b33-a3a8-467c-8fb7-6a2208c1f013
/dev/sdc1             2.7T 1008G  1.6T  39% /media/bb18550c-8af1-44f9-968a-b04ad899fd2d
/dev/sda3             101G  188M   96G   1% /media/d0cbc95d-753b-463e-9b03-a716a67bb04d

My NIC is the standard one on the motherboard of the HP N40L Microserver that many are using.
I'm increasing the swap now, after that I'll see how it goes.
I have my IP address assigned statically, I wonder if my router has some sort of timeout which is not routing connections - no idea though.

I have 4gb of DD3 ECC ram.
I will increase the swap size, but do you have any ideas why I am loosing connection to the server? I noticed that other users seemed to have similar problems, but all seemed to be using a USB drive. I was previously using a USB drive before cloning it over to an SSD, not sure if that has caused any problems.

Hi, Yes I repartitioned the SSD, 8gb to OMV, 450mb for swap and the rest as user accessible space.
I'll keep an eye on the space, but used space hasn't changed since the my last post, around an hour ago.

Hi,
I haven't tried logging in locally when it becomes unresponsive, I'll try that when it next happens.
What should I check for when (if) I log in?

The current output of df -h is,

root@openmediavault:~# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/sdc1             7.5G  1.2G  5.9G  17% /
tmpfs                 1.9G     0  1.9G   0% /lib/init/rw
udev                  1.9G  132K  1.9G   1% /dev
tmpfs                 1.9G     0  1.9G   0% /dev/shm
tmpfs                 1.9G  832K  1.9G   1% /tmp
/dev/sda1             230G   88G  130G  41% /media/6ff58b33-a3a8-467c-8fb7-6a2208c1f013
/dev/sdb1             2.7T 1008G  1.6T  39% /media/bb18550c-8af1-44f9-968a-b04ad899fd2d
/dev/sdc3             103G  188M   97G   1% /media/d0cbc95d-753b-463e-9b03-a716a67bb04d

Hi,
SSD is brand new, so I hope it's not that.
Services that are running are mainly transmission, miniDLNA and greyhole.
The drive is not full, but is there a limit somewhere for the amount of space log files can take? How can I check the combined size of the logs?
However if it was log file size then I wouldn't have thought a reboot would solve the problem - which it does.
Thanks!

I have almost exactly the same problem, however my OMV is installed on a SSD drive. :s

Hi,
I seem to have a recurring problem that OMV is no longer accessible on the network after sometime.
The machine will respond to pings but will not allow ssh (connection refused error) nor will it be accessible through the web interface. Further, when this happens, I can not browse DLNA shares via my TV.
The only way I found to recover from this is to physically power off the machine and back on again.
OMV is installed on a 120GB ssd.
I've looked through the syslog and can't see anything that might suggest why it is no longer accessible.
Can anyone please help.
Thank you very much.

Update:I left OMV running overnight and the same thing happened again. I don't know at what time it stopped being responsive, but looking at the syslog I can see that it didn't crash since transmission is still looking for peers for torrents I had running; of course it didn't find any.
Any ideas?

Hi,
I finally have got myself an SSD for OMV on my N40L.
I used clonezilla to clone my USB stick, that I previously had OMV installed to, on to my SSD.
I then increased the swap to 500MB and the OMV partition from ~4GB to ~8GB. The remaining space on the SSD I have formatted to ext4 and will probably use to store my VirtualBox virtual machine disks.
My question is, is there anything I should be aware of or should change when using OMV on a SSD? Things I think could be relevant (but don't know for sure) are:

Block Size
TRIM support
Write minimization

Thank you for any advice.

Having said all of the above, I have noticed a slight problem. I believe during updates the /etc/samba/smb.conf file gets over written and manual changes I made for Greyhole settings get lost. For example, the smb.conf file should have lines such as

[global]
unix extensions = no
wide links = yes
[Videos]
dfree command = /usr/bin/greyhole-dfree
vfs objects = greyhole

However I those chances have been lost, I assume this happened during some update.
Can anyone help as to how to makes these changes persistent through updates?
Thank you.

I too was disappointed not to see a greyhole plugin for 0.4. However after some prompting from other forum members, I took the plunge and installed greyhole and mange/configured via CLI. This wasn't as difficult as I thought it would be, once setup there isn't much (or any) CLI work you really need to do. I found that the simplest way of installing and configuring greyhole was to install a OMV 0.3 installation in a virtual machine, setup greyhole in that using the plugin, and then essentially copying the information in the config files to my 0.4 installation (of course making the required basic changes).
Admittedly even with this process it took me half a day to setup, but I am glad I did it and would certainly recommend it.

My only one concern is, if a plugin is eventually written will it successfully read all my config files and allow me to continue managing Greyhole through the new plugin or, if once you go down the CLI route are you forced to stick with that even when a plugin appears.

Good luck and give it a go!

It would be great if we could obtain some clarification as to whether the greyhole plugin will be ported to 0.4 or even if it will ever be maintained/supported, especially since 0.3 is now officially end of life.

Quote from "ribbles"

Eh, I'm moving away from greyhole. In 2 days I had 3 files "fail to copy" to the storage pool and just completely disappear. Don't trust this thing at all.

Hi ribbles, would you be able to suggest some alternatives to greyhole? Thanks!