Got your point, I would also prefer having it in a docker container.
However I believe it is not trivial to have it running as docker container on ARM, caused by the dependencies Seafile has. That is the reason why the specific build for ARM based boards is (still) there and not yet replaced 
RoiBurgonde In case you still want to give Seafile a try:
https://github.com/haiwen/seafile-rpi/releases
This is a specific build for ARM machines, which I use since a few years already.
Works perfectly fine as an self-hosted Dropbox-like solution.
There is also a - bit outdated - guide on how to Seafile here in the forum: How to install Seafile with MySQL and SSL
Now it is actually simpler to setup than this guide, once you have a mysql or mariaDB instance running - e.g. as docker container.
I prefer it over Syncthing, as I had a hard time getting Syncthing to run as I wanted to.
First you have to mount it via OMV UI, then you'll find the directory by this command
lsblk
But in case you still have an old OMV installation with a 3.4 kernel simply forget about and start from scratch with latest official OMV image
Yes, I want to move from OMV 2 to 3, so I will start from scratch anyway. Then I think I'll stick to getting a new sd-card, from your link I guess you recommend Samsung evo sd-cards. I guess there is no difference if it's a micro-sd with adapter compared to a normal sized sd-card?
sourceforge.net/projects/openm…s/Other%20armhf%20images/ --> write the image with Etcher --> boot it --> activate SSH access in the UI --> partition the SATA device manually as you want (OMV doesn't need that much space unless you want to also run Plex without modifications) --> nand-sata-install --> /dev/sda1 --> done (tested by me when working on nand-sata-install +10 times)
Thanks for the rapid answer!
I did it exactly like you said, but:
After moving it to SSD with nand-sata-install script, I couldn't reach the webUI. Ping was possible, but nothing else. Somehow the server didn't come up correctly.
But when you say it should work, I'll try it again...
Otherwise I already thought about getting a new sdcard, as the one I have is old & crappy.
--> Is it possible to copy the whole OS from an old to a new sdcard, without setting up everything from scratch again?
Hat denn jemand es bisher geschafft OMV 3 auf einem Banana PI laufen zu lassen
UND von der einer HDD/SSD zu booten, ohne, dass diese nur als read-only gemountet wird?
Oder habt ihr das OS einfach auf der sd-card belassen?
Grüße
one partition of the sdcard is obviously damaged.
I am not accessing the sd card anymore except for the boot-partition which seems to work well...
There are many tutorials on the internet on how to do that.
I moved everything on my SSD, without reinstalling everything with a BananaPI.
The tutorial is especially for ARM devices like raspberry or banana pi, as these need some parts on the sdcard to boot.
Hi all,
my OMV2 is running since over 300 days non stop on a banana PI without any issues.
Everything is moved onto a SSD via SATA.
So there is only the required boot-stuff on the sdcard.
Since last night I get high CPU percentage because of high wait-io.
The iostat command tells me 100% utilization of the sdcard:
avg-cpu: %user %nice %system %iowait %steal %idle
12.12 0.00 3.79 84.09 0.00 0.00
Device: rrqm/s wrqm/s r/s w/s rkB/s wkB/s avgrq-sz avgqu-sz await r_await w_await svctm %util
sda 0.00 3.00 0.00 10.50 0.00 54.00 10.29 0.01 0.95 0.00 0.95 0.95 1.00
mmcblk0 0.00 0.00 0.00 0.00 0.00 0.00 0.00 106.00 0.00 0.00 0.00 0.00 100.00Is the sdcard damaged or where does the high wait IO come from?
I do not want to try to reboot, as this would probably fail, if the sdcard is damaged.
Thanks a lot.
That's all fine and dandy on a locally-hosted OC installation, but completely impossible on a shared hosting people may use for availability reason.
The first or second command line for an upgrade, according to OC's manual, is:
sudo -u www-data php occ maintenance:mode --on
There's no such thing as sudo on a shared hosting, or the provider has more serious problems than supporting an outdated version of OC.
My post was about Seafile not OC..
I'd say that Seafile is possible to be installed only with user-rights - no sudo or similar needed.
Does it include easier updates than OC?
For regular updates and if you're used to it, it doesn't take more time then 1-2 minutes.
It's like: Stop server, download and extract new version, run upgrade script, start server
FYI: Seafile 6.0.4 was recently released for Raspberry PI and other ARM devices.
I already upgraded without any issues.
https://github.com/haiwen/seafile-rpi/releases/tag/v6.0.4
Direct download link:
https://github.com/haiwen/seaf…er_6.0.4_stable_pi.tar.gz
Keep in mind to stop seafile,
extract the downloaded file with the specific user,
use the upgrade script from the /upgrade directory from the previously extracted folder (e.g. upgrade_5.1_6.0.sh to upgrade from 5.1.3 to 6.0.3)
check all file permissions
start seafile.
and your done.
More information helps by the way.. OMV version? plugin version? What do you want to do with the plugin?
If you don't want any Supervision on sockets or IPs, put a "-" into the IP-Range field. Maybe that helps...
Hi,
I just wanted to suggest to include the 'whois' package to be installed with the fail2ban-plugin.
When the mail-setting is set to 'action_mwl' The whois information cannot be retrieved & shown inside the email.
Correct me if I'm wrong. I just encountered this issue personally.
Thanks!
mail: /tmp/mail.RsXXXXEuq1v8: No space left on device
Sieht danach aus, als wäre das Laufwerk auf welches du kopieren möchtest voll.
Die Fehlermeldungen im angehängten Bild haben damit erstmal nichts zu tun.
Yes, but this will be the system drive ...
Yes, sure. Depending on your OMV configuration, whether you use a SD card or HDD/SSD it might be useful to change the mysql data directory. 
updating seafile-server-latest symbolic link to /opt/seafile/seafile-server-5.1.3 ...
You obviously didn't run the right script. This script does not automatically download and update to the newest version.
You have to download and extract the new version, as @Zoki already said.
For the upgrade, you have to run the seafile script of the new version, inside the new directory.
In this case:
../seafile-server-5.1.4/upgrade/
Alles anzeigenThe avatar folder is part of seafile ever since.
If you do not have it, the application would show a strange behaviour.
One thing which might cause these kind of errors is if you run the seafile scripts with different users (which changes file permissions on the go)
So to all:
Do only run seafile scripts as the seafile user.
Do not use sudo unless you did installed as root.
If things go wrong, check file permissions and ownership first.
Thanks Zoki, I totally agree!!
AND: Stop the seafile server before upgrading!
I already upgraded it, too, to 5.1.4, but didn't encounter that error.
Did it work after creating the folder?
