I would hide some details or you will be getting the spam bots forever
Which details?
I would hide some details or you will be getting the spam bots forever
Which details?
I don't know if that makes any difference but for me Gmail works well with the following settings:
SMTP port: 465
Encryption mode: SSL/TLS
In username I put in the username without the "@gmail.com". The rest of the settings are the same as yours.
By the way, I have a suggestion for the German localization of the individual menu entries of the compose plugin.
I believe help is always welcome.
A few comments though:
Display MoreSettings -> Einstellungen That's already used.
Files -> Dateien good idea
Services -> Dienste That's already used.
Stats -> Statistiken good idea
Images -> Abbilder Maybe. Is it necessary/helpful though?
Networks -> Netzwerke That's already used.
Volumes -> Datenspeicher I disagree. Datenspeicher means data storage. A docker volume is something else. In German texts about Docker this term is usually not translated (same for docker images).
Containers -> Kontainer Okay. But why the k? (Container is the German word. And writing it with c is far more common than with k. In fact I just learned now that writing it with k is correct spelling as well since it's so rare.) Edit: I just noticed "Container" (without "s" in the end) is already used. That's the best option imho.
Dockerfiles -> Dockerdateien I don't know. A dockerfile is also a specific type of file and the term is usually not translated.
Schedule -> Zeitplan or Terminplan Zeitplan is already used.
Restore -> Wiederherstellen That's already used.
Encrypting a hard disk only protects you from theft. During operation, the hard disk is open and exposed and anyone with the appropriate rights can see everything.
True. I believe encrypting your drives gives you peace of mind in a few more cases though: If your drive fails and you want to send it back to the manufacturer or just throw it away, it might not be possible to wipe your data properly with the tools you have at home, and skilled people can still access your data. If your drives are encrypted, that's not the case.
Encrypting drives has become so easy, I just take the "Better safe than sorry" approach and have them all encrypted. This doesn't replace online security measurements of course.
thanks.
is nextcloud do the synchro also ?
There is a mobile app that can upload your fotos to your Nectcloud. Similar to Dropbox or iCloud or Google Photos.
You are probably looking for something like Nextcloud.
If you only want to synchronize your photos there are other options, e.g. Immich which is similar to Google Photos (but I wouldn't expose that to the internet), or just file sync tools that sync to your nas. The full cloud experience including drive, photos, calendar, etc. is available with Nextcloud.
Display MoreWell. I think I found the problem. I used to have the OMV dashboard open in a browser tab and it seems that this keeps the disks running.
Once I closed the tab and checked after a certain period everything was ok. When I leave the dashboard open in the browser tab it remains open - perhaps I have too much infos on the dashboard.
I checked several times closing and reopeing the tab and this seems to be the source why the disk don't spin down.
Is this a known behaviour?
Depends on your widgets I guess. The S.M.A.R.T. and filesystem widgets spin the disks up when you open the dashboard. I can imagine they keep them spinning in order to collect the information they display. I removed everything drive related from the dashboard and my drives only spin up when accessing the drive related sites of the Web UI.
OMV 5 has reached end of life and is not supported anymore. You won't receive updates or security fixes. That's a security risk.
OMV 6 will only be supported for another month or so. My suggestion: Bring both servers to OMV 7.
Alright thanks I'll give that a go, can I somehow still transfer my current NC setup with files, accounts config and everything to the AIO version?
That version is long outdated and to still run it is a huge security risk. Maybe Nextcloud AIO is more suitable for you:
If you access the data on a drive, it will wake up. Using a Samba share is accessing the data. The drives will even wake up if you access the drive- or S.M.A.R.T.-sections in the web GUI or if you access the dashboard and use the filesystem-, drive temperature- or S.M.A.R.T.-widget.
A further question, in open media vault are nvme disks managed?
Thanks in advance for the reply.
You mean, if it's possible to use NVME drives? Yes. No problem. I use a NVME SSD as my system drive and another one as data drive.
Is this a DNS problem? Have you tried setting a DNS server in the network settings?
Please change things to not use relative paths. I really dislike them and relative paths that drop a directory (or more) will never be supported in the backup. This was the whole point of adding CHANGE_TO_COMPOSE_DATA_PATH.
Is this still the case? I just discovered this thread while searching for something else. Since relative paths were mentioned in the wiki I have been using them in nearly all my compose files and also used things like ../ in some of them. Will this cause trouble when I have to restore a backup?
Thanks in advance!
Eventuell auch mit Symlinks lösbar? Also die bestehenden Dateien in die neue Struktur verlinken. Müsste man halt für jede Datei einzeln machen bzw. per Skript.
Now, throw BTRFS RAID5 problems and BTRFS filesystem recoveries (difficult to nearly impossible) into the mix, along with users that have no backup. Yeah, from a forum support perspective, that would be a freaking disaster. It's already bad enough, as it is, with home users insisting on using mdadm RAID without backup and SBC users setting up RAID over USB connections. If even 1 in 100 to 250 users had a problem with BTRFS, the forum would be overrun. The last thing this forum needs, from a support perspective, is the wide adoption of unstable filesystem being used on data drives.
Fair enough. I can understand that!
It's already been said that BTRFS profiles other than RAID56 are and have been stable for some time. But SUSE, and more recently Fedora, are not primarily advocating BRTFS for bulk data use. They picked BRTFS as the default for the "root partition" of installs with snapshots managed by "snapper". The same thing has been adopted by smaller distros like "Spiral Linux". With pre & post snapshots taken after each apt upgrade a BTRFS aware version of GRUB allows booting into the various OS snapshots.
The OP raised the question of BTRFS RAID5 or ZFS RAIDZ1/2 for bulk data, which has mostly been the focus of this thread.
By all means use BTRFS RAID1 with multiple drives , but there are caveats users ought to be aware of. There's even one thing that BTRFS offers which ZFS currently does not, namely "server side copy" both within and between subvolumes.
Thanks for your answer and sorry for hijacking this thread. I was just curious. I have no plans on setting up a RAID on my server but I have been playing with the thought of using btrfs on my laptop..
Some years ago, there was a forum moderator that was pushing BTRFS on Linux newbies largely because it was integrated into the kernel. I never understood his reasoning or the "unfounded trust". Since most newb's don't have backup, I saw recommending BTRFS as a potential disaster from a forum support perspective. Thankfully, it wasn't widely adopted.
Is it that catastrophic? It's not recommended to be used in RAID5, but it's the default filesystem for both Fedora and Suse (openSUSE and SLES) and has been for years. I'm not aware of reports that large parts of Fedora and Suse users are losing their data.
I can't speak from my own experience though, I have only ever used ext filesystems.
just do what soma has said on post 6 than you don't need to mess about.
That's the safer way.
If you have no experience in those things I'd recommend to go that way as well.
what partition do I need to create to store files there after reducing the system size?
Ext4
Another option - if you feel comfortable using partition tools and live disks - would be to boot into a Linux live environment (e.g. GParted Live. But an Ubuntu live disk or most other live disks would work as well) and shrink the system partition using GParted (16 GiB should be more than enough for most use cases) and then create a second partition on the disk that you can use for data. You need a pendrive for that to use as live disk though (if your server has a cd or dvd reader you could also burn a GParted Live CD).
If you have never done anything like that before, Chente's suggestion is probably the better option though.