Syncthing is ideal for this - set it up in docker on each machine and choose what folders to sync.
Thanks I hadn't come across that in what I've read so far.
I happens with every reboot.Code
A few days ago I started to get error emails on restart as follows :
Followed by a second:
Is this anything to worry about?
Have a look at my system specs below pretty much matches what you are looking for but it has a low cost Pentium Gold CPU not an integrated one.
Thanks changed the policy to mfs, rebooted and the new drive is being added to. Still errors with mergerfs.balance but less need to use it now.
Using the exclude option deals with the aquota* error but now some new errors to investigate today.
Thanks for your input.
I created two directories that exist on the pool on the /srv/dev-disk-by-uuid-a017c3b4-20f1-4ab5-a0de-e39565cfbf07 drive (the new 3TB USB drive) and again ran :
Same error message.Code
Changed policy to most free space - same error message.
Something isn't right with Disk 3 but can't work out what it is.
I have four disk mergerfs setup :
The array is /srv/144ab994-0e0f-4a42-a06b-f37e84454803
I add 3TB external USB drive:
Shows as added in file system pages.
Policy is existing path, most free space.
The new drive is not being added to with new files so I run mergerfs.balance with output as below - so something wrong with disk 3 - how can I fix?
Any help appreciated.Code
I have several drives in the system and they are listed in /srv/ as:
803befbe-2c10-4331-9b07-1691582f4de1 (Remote NFS mount)
dev-disk-by-label-NVME (OS drive)
dev-disk-by-label-Disk1 (WD 4TB drive)
dev-disk-by-label-Disk2 (WD 4TB drive)
dev-disk-by-label-Disk3 (WD 4TB drive)
dev-disk-by-label-Disk4 (WD 4TB drive)
dev-disk-by-label-Parity (5TB USB SnapRAID parity drive)
I added a new USB 3TB drive today, added it to the MergerFS pool and SnapRAID.
It has appeared as follows:
All drives have been added under OMV 5 i.e. no upgrading from OMV 4.
Why is the new drive mounted by UUID when the older ones are mounted by label?
All working just curious to know.
SnapRAID is what you need. Buy an external USB drive bigger than the biggest of your 2.5 drives and install the plugin. Plenty of info in this forum on setting it up.
Jellyfin - Emby fork - free and very good. Install in Docker:
Install the Kodi sync queue and at the Kodi end use the Jellyfin / Kodi add on
- /srv/dev-disk-by-label-Datas/plexmediaserver/Library/Application Support/Plex Media Server/:/trasncode
Is "trasncode" a mistype and the drive filling with transcode files?
You can create some extra useable space on the parity drive as follows- quoting from SnapRAID manual:
In Linux, to get more space for the parity, it's recommended to format the parity file-system with the -m 0 -T largefile4 options. Like:
On a 8 TB disk you can save about 400 GB. This is also expected to be as fast as the default, if not faster.
When I has this problem it was with copying large files to an NFS share on a second device.
Didn't know that, I have two Windows 10 desktops with fixed IPs and PiHole works with them. Only device in the house I have changed is my wife's ipad as she likes ads
Surely the beauty of PiHole is you change the DNS on the router so no need to do so all your devices?
It makes a good webserver if this is any consolation - I had it running a few low volume Worpress sites ran for months without intervention. Just the big file transfers didn't work.
My board has an M.2 slot so may as well use it for the OS they are too expensive and low capacity to load up with movies etc.