Posts by penguin

Good to see another fellow beginner! I am also new to a lot of this but have recently accomplished what you state are your goals (i.e. "to store all my data (office, accounting, insurance stuff etc., music, pictures/photos). In addition, I want to have access to this data at any time, be it in the LAN or from outside.")

In my use case, I did not need to access my files remotely very often. So here are the steps I did:

1) Install Debian 10 via netinstall

2) Install OMV using the script: https://github.com/OpenMediaVa…-Developers/installScript

3) Install OpenVPN following this guide: https://www.digitalocean.com/c…envpn-server-on-debian-10

Note - I did not install it in a Docker container because Docker is 'not compatible' with UFW (universal firewall) rules. I wanted OpenVPN to be subject to my UFW rules so I installed it directly onto Debian OS, not via Docker.

4) I used something similar Duck DNS to have my dynamic IP mapped to a URL from my router

5) Installed Nextcloud via Docker following the guide on this forum for how to do this on OMV5.

With this I now have a situation where my photos are accessible in Nextcloud so I can see them across all my devices.

If I am not at home / can't access my local network with my VPN I connect and it gives me access to my local network as if I was at home. I can access nextcloud, OMV admin etc. when connected via VPN.

The downside is that I have to connect via VPN each time I want to add / view my photos in Nextcloud remotely. But this is not frequent in my case so I don't mind. I hope this helps you

I have not tested if I can access SMB files. But I should be able to once connected to VPN.

Also for your port forwarding you can check here: https://www.portchecktool.com/ - to see if your router is doing it correctly.

So I ended up doing this and it seems to be working well. My nextcloud install and data is now stored on my SSD and the interface seems faster than when it was a separate HDD.

If anyone else is in the same position, here are the relevant lines from my docker-compose file

#fornextcloud
volumes:
      - /home/dockeruser/appdata/nextcloud/config:/config
      - /home/dockeruser/appdata/nextcloud/data:/data  

#for mariadb (nextclouddb container)
 volumes:
      - /home/dockeruser/appdata/nextclouddb:/config    #/srv/dev-disk-by-label-disk1 needs to$

Quote from gderf

Just change the name of the partition's disk label from home to something else, more typical of a hard drive, say disk-1

OMV has a /home folder in its rootfs. At least the typical install using the iso image does. Not sure what you have there but Debian must have created a /home. Maybe OMV is using it also.

2GB of RAM is a bit thin. I would still see if you can get by without swap, but if not then a 4GB swap partition would be typical (2x RAM). Not sure I would want to run a heavily hit swap on an SSD, but that's me.

OMV installed via iso will take over the entire disk it is installed to, and as you know, you have no control over the partitioning........during the install. Once installed you could shrink the OS partition down to something reasonable, say 16GB, shrink or grow swap to say 4GB and have what's left over as a one or more data partition(s) that you would mount into OMV like any other hard drive. Food for thought if you wind up reinstalling.

Display More

Sorry for the confusion - the partition itself isnt called home. But it houses the home directories for users. So there are folders like /home/user1, /home/user2 etc.

In other words, the mount point for that partition is /home.

If you see this image - I chose the 2nd option when installing Debian (ignore the highlight on option 3): https://www.linuxtechi.com/wp-…Debian10-Installation.jpg

Thanks for the tip. I don't completely follow - what do you mean by "replace the /home partition with something generic?"

If I understand correctly you're saying rename the /home/user1 directory created for our new user (user1) to something generic and somehow mount it to /srv/dev-disk-by-label-genericname - is that right?

The machine only has 2GB DDR RAM so I thought swap might be used quite a lot.

And the reason for installing Debian first is that the first time I attempted to install OMV it threw up errors (it is possible the OMV iso file was corrupt - lesson learnt to verify the checksums before burning to disc!). Also installing Debian first lets you partition it during set up.

Ok, the context/problem is that I installed Debian and OMV on a 1TB SSD. I partitioned when installing Debian but accidentally partitioned it so that the OS is installed on one partition and the other 900GB partition contains the /home folder (there is also a 3rd swap partition).

The other option is I can use gparted to create a new partition so I have the following partitions:

1) OS

2) /home

3) swap

4) data

What do you suggest is the best way to do this?

sdfsdfsd

I have reinstalled OMV on a new drive - fresh Debian install with OMV installed on top. The data drives are untouched - including the HDD I am using for Timemachine backups.

I have the Debian machine a different name to before when I installed Debian 10 on this new drive.

I have set up a user with the same username and password as before, set up a shared folder on the Timemachien HDD, adjusted permissions and set it up under SMB drives with TimeMachine support enabled.

TimeMachine sees the drive but starts making a whole new back up.

How can I get TimeMachine to update the existing backup that already exists on this HDD rather than start from scratch?

I am using OMV 5.0 with Portainer to host Nextcloud containers. I will add more docker containers in the future for things like VPN, PiHole etc.

My system is very old and modest by today's standards (or even mid 2010s standards!) - 2GB DDR RAM, AMD Athlon 64 X2 processor, 250GB HDD running OMV and Debian.

When Nextcloud is syncing with multiple clients, the web UI goes very laggy and I can see using htop that both my CPU cores are at 100% utilisation. RAM used is less than 1.5GB and swap space seems under full capacity too.

Ideally I do not want to upgrade my processor/motherboard. Would I see much benefit from a SSD to run Debian, OMV and Docker/Nextcloud?

Thanks!

I'm new to a lot of this and have managed to get OMV set up in a way I am happy with by repurposing hardware that is over 10 years old. Please let me know if I am doing anything silly or if there are best practices that I am not following. This is my set up:

1x newer 1TB SATA disk used by various Apple machines for TimeMachine backups (set and forget type of thing). The plan is for each Apple device to back up to an OMV NAS drive on the fly and manual backups to be made on each machine by plugging in a USB HDD manually into the Apple machines every now and then. I would like to upgrade this to a 2TB SSD at some point.

1x old 250GB SATA disk has the OMV & Debian install. I've also set this as the target for a Nextcloud install via Docker. I am going to install NextCloud iOS and OSX clients locally on all our machines so we can add photos into this NextCloud from all our different devices and they will be stored on the OMV disk as well as the iMac's disk when they sync with the iMac via the NextCloud app. For photos taken with a DSLR, this will be hooked up to the iMac and photos stored locally. That local folder will sync to NextCloud so the camera photos will exist on the iMac's local drive as well as the OMV/Debian/Nextcloud SATA drive and can be browsed on mobile devices with the NextCloud app. For now my media is only 100GB in size but when it gets bigger, I will upgrade this 250GB SATA disk to a 1 or 2TB SSD.

1x old 120GB SATA disk for raw video dumps (I don't mind if this fails, the data isn't that important but just storing it because I have the space so why not!). Transfers will be done over SMB.

Small capacity USB stick for acting as a dropbox/DLNA server. Whenever we want to play photos or a video file we will just move it to this stick and this can be read by the TV. The USB stick is connected via USB to the main machine running Debian/OMV. It's not a big deal if data on it is lost as a copy of the same files will exist elsewhere.

External (USB) 1TB USB HDD to take regular (manual) backups of the OMV/Debian disk via the feature in the OMV admin panel.

[Soon I will add another 1TB HDD over SATA and create private folders for individuals to have a drag and drop of their most important files to back up manually whenever they wish.]

So the main things are:

* OS X machines are backed up in 2 different locations via TimeMachine.

* Personal Photos and Media are stored on the iMac 1TB internal HDD, synced to a OMV NAS drive and also will be part of the iMac timemachine backups on the OMV NAS. Photos can be added via iOS devices with the NextCloud app and will be synced to the iMac and OMV NAS drive.

The main Debian/OMV machine is very old. It's running an AMD Athlon64 X2 Processor, 2GB DDR ECC RAM and has the original 250GB SATA HDD it came with running the OS and OMV and Nextcloud.

My questions are:

1) Am I taking any risks (in terms of network security and storage reliability) by having Nextcloud on the main OS drive?

2) What's the better upgrade - a) 1-2TB SSD for the Debian/OMV/NextCloud drive (cost £100-200); b) 3x 250GB to 2TB SSDs for the NAS drives (cost £300-400) or c) new RAM for the Debian machine (cost £100for 4GB ECC DDR RAM - it is so old it's hardly sold by anyone!) So far performance has been fine, although the NextCloud web interface is a bit slow but not bothering me too much.

3) Should I bother with setting up RAID or is it not worth the cost (of new, larger disks) and hassle given my backup strategy above?

4) I'd like to test more docker containers (there are a lot of good open source/self-hosted apps for all sorts of things these days). Is it safe to have these Docker containers in the main OS drive with my personal data there too? Or else I'd like to install node.js and PHP/mysql so I can experiment with some web development, again this would have to be on the OS disk I think but if it's not recommended I will just get a RaspberryPi for this or an AWS account!

Thanks all for your help. This has been a great, active community from my experience And I'm amazed at how much better OMV on a 10 year old machine is - I'm moving from a Buffalo NAS which gave me a lot of headaches and just didn't work with the most basic things!

This worked a treat, thank you!

Quote from macom

point(1): yes

point(2): if you search within Nexcloud in the App section in any category for "external" you will find the external storage app at the bottom of the page as app from other category; I have not found out in which category it is

I have installed the plugin now but am having some trouble configuring NextCloud to access a share.

I set up the share with the Mini DLNA plugin following this guide: (https://www.htpcguides.com/ins…na-plugin-openmediavault/). It is working well, my DLNA clients can see and play the server files.

I've also set it up as a SMB share.

a) Is there anything else I need to do in OMV Admin or Portainer before I configure it in Nextcloud Admin?

b) And what are the configuration settings I should use when setting it up in NextCloud so it mounts and can be used?

Quote from MrC

You can add as many "Containers path's" as you want.

Here's what I did for the container :

and for the "external storage" settings :

Where are you configuring the settings in picture 1? I can't find it in the OMV admin, but maybe that is because I am on version 5. Or is it from a different admin interface?

That's great thank you. I encountered a few issues but found a solution - you can consider adding them as replies to your tutorial in case others run into them:

1) I couldn't access NextCloud admin set up at first but searched that it should be http*s*://192.168.X.X:450.

2) I got a failed to connect error - Access denied for user when trying to set up NextCloud via web interface. Apparently this is due to mariadb version. The advice in this thread resolved it! RE: Nextcloud with Letsencrypt using OMV and docker-compose - Q&A

Thank you Macom (for your answer and for authoring the tutorial I am following!).

Just to confirm point (1), does that mean that in the docker-compose.yml file i create I can replace "/srv/dev-disk-by-label-disk1" with "/" for it to install on the OS drive?

And in response to point (2), all of the apps titled "external storage" on NextCloud are created for use with a particular cloud backup system like oneDrive, Dropbox etc. https://apps.nextcloud.com/?search=external+storage Any ideas which specific app I need?

I am following this guide to install Nextcloud: [How-To] Nextcloud with Letsencrypt using OMV and docker-compose

And I only want to access it locally so I am making the modifications suggested in post #6 here: Need help to install Nextcloud with Docker and Portainer

I want to install NextCloud on the same drive as my Debian OS & OMV install. It's a 250GB HDD. So I would replace "/srv/dev-disk-by-label-disk1" with "/"

1) is this possible?

2) From what I understand my NextCloud install will be able to access files in all shared folders across all volumes - including shared folders on different volumes. Is that correct? Or does Nextcloud need a separate drive to be installed into and all Nextcloud files must only be kept in that single drive that Nextcloud is also installed on?

if (2) what is the minimum size of drive required? I currently have a 2GB drive connected to test with. It's acting as a dlna server for now but can be ereased to test with NextCloud. But is the capacity enough or do I need to attach a bigger drive?

The main use cases for Nextcloud are (for now) to serve as a cloud drive (on our own home network) and to start syncing my contacts and calendar locally rather than with Google.

At some point I would like to put it on the world wide web and use NextCloud Talk (VoIP video calls)

Thanks