I also struggle with the size of OMV-Backup email report, especially when on a mobile mail client and mobile network.
It would be really convenient to have verbosity parameter configurable via GUI or OMV_* variable..
I also struggle with the size of OMV-Backup email report, especially when on a mobile mail client and mobile network.
It would be really convenient to have verbosity parameter configurable via GUI or OMV_* variable..
use one 16GB instead of two 8GB
How much power do you think this saves?
Judging by the measurements at tomshardware.com it looks like the power difference would be in the region of 1W.
I guess it is the matter of opinion (and the intended server usage) if the power savings with a single DDR4 stick worth the sacrifice of dual-channel throughput of two sticks.
Looking at the description of the features, they are enabled by default, and additional configuration is needed only if you want to disable them.
I wonder what Storaxa config and addons people choose to run OMV with a handful of dockers and a couple of VMs?
I am mostly on a fence between AMD and Intel options. Initially I wanted AMD because of ECC support, mostly because my current Microserver uses ECC memory and never let me down. However, ECC may be an overkill for home use and Intel with heterogeneous cores and QS is a better choice.
Also, is SSD caching a thing with OMV? I never fell a need for it, but maybe I missing a lot..
I can also vouch for Samsung FIT Plus 64GB, same as the one pointed by macom - works well as a boot drive for the last half-year. It replaced a rather old 32GB SanDisk which was noticeably slower.
Did you have a chance to read through documentation? It still may be confusing after the first read, but it is rather comprehensive:
Access Rights Management — openmediavault 6.x.y documentation
Do you know what filesystem it was?
I had successfully restored files on fat32 and ext3.
BTW, make sure you do not write to that disk.
KM0201 Yes, indeed - it was a very prompt resolution! (probably just a trivial CSS change, but still impressive response)
I noticed that too - black search text on a dark-grey background, almost impossible to read.
@vcurser will you file a bug report at GitHub please?
I would recommend syncthing - it is easy to install in OMV (docker or apt), takes care of discovery, and worked well for me in similar circumstances.
The only potential issue - syncthing has to be installed on both computers.
Just out of curiosity, what did resolve it?
When you replicate the USB stick are you doing it to another stick or just a backup file somewhere that's easy to restore in case of emergency? The other concern I guess I have is the stick itself taking a dump though from what I understand OMV is not very hard on drives when running as a standalone boot OS and the stick should last as long as I need it to.
I do both
Before going for an update I usually backup System USB image onto HDD with OMV backup plugin. Then I reboot with SystemRescueCD and a "new" USB stick in place of the System USB, and restore the image to that new USB stick.
Basically I alternate between 2 identical USB sticks, and have a couple of recent System images on HDD, just in case.
To prolong the lifespan of USB stick use OMV flash plugin - it moves few most frequently updated directories to RAM disk:
SInce moving to OMV a couple of months ago I tried several options from your list:
I started with Option 2 (both System and Data on the same rather small SSD), but underestimated how much space various docker images occupy...
Then I transferred to Option 3 by moving Data to one of HDDs, but did not like it (speed and spindown aspects).
Now I converged to Option 1 (system on internal USB, data on larger SSD).
The main reason I like this setup is the ease of replicating the whole USB stick, e.g. before system updates, and also the speed of Data SSD.
Glad you figured out a relatively simple solution and your OMV installation is back to normal!
Still would be good to learn what caused the problem in the first place, and how to properly debug and fix it in the future
boxersoft sorry it did not work smoothly for you...
I guess the problem in my setup was different from yours, even though it manifested itself with exact same error message on container.io update.
Worth mentioning -- after container.io update reported an error I tried doing grub-install /dev/my-boot-drive from the command line and it completed with no errors. After that experiment I started to suspect that the update process tried to run grub-install on a wrong drive (I couldn't find the explicit reference to the drive name it in the log though).
Also, in Step 2 I still had container.io queued for update in the web interface -- this seems to be different in your case.
If it helps, I have a snapshot of the system disc from a week ago, so can restore and try to go through the update process again, paying more attention to all the warnings and errors.
Alternatively, we can wait for somebody more knowledgeable to face this problem and propose a robust solution
I faced exact same problem with update of container.io just yesterday. Reading forums did not clarify much. And I did not do anything that could break grub in the last few months...
In the end the following worked for me:
1. uninstall grub-pc package via command line (connected via SSH)
2. proceed with update of container.io via web interface - no error this time
3. reinstated grub-pc via command line
All seems to be good - the system reboots and updates with no issues.
Note I am still not sure what was wrong and if my "solution" is a valid one, so use with caution.
if you aren't using ddfull, there is a chance the grubparts isn't perfect for some systems. I would plan on doing a grub-install if not using ddfull. If it works without it, great.
Thank you for clarifying this!
It would be useful to add such a note to the otherwise nice tutorial by auanasgheps[How-To] Restore OMV system backup made with openmediavault-backup plugin
Running grub-install is the best way to fix this.
Is grub-install a required step in restoration from any backup created by the plugin? Or is it only necessary because something went wrong with backup/restore of grubparts file in my specific case?
Yes, I had a very similar experience just few days ago. I restored grubparts and fsa files to a fresh USB stick (identical to the one I use as OMV 6 system disk). After reboot I got to the same state as in your post.
What "solved" the problem for me was running grub-install for the new USB stick. I thought copying grubparts file with dd would do the same job, but somehow it did not... Could more experienced people of advise on this?