can you:
sudo omv-aptclean
sudo omv-mkworkbench all
sudo rm /var/lib/dpkg/lock
sudo folder2ram -syncall
sudo reboot
Then see if you still get it.
Posts by ryecoaaron
-
-
as the direct download is very slow I am getting at most 50-60 KB/s.
Did you try a different mirror? sourceforge has many mirrors. Just click the Problem Downloading? button to select a different mirror. I am downloading at 3MB/s right now.
-
Do you have an apt proxy setup?
-
Especially the OMV Plugins (which folder are they?).
They are in different folders and it depends on the service they configure.
Id like to be able to roll back in case an installation doesnt work out.
What are the relevant folders? Is there a good program for snapshots/rollback?
Even though I can take snapshots of my OMV VMs, I don't remember the last time I reverted to one. That is because apt is typically so easy to fix and/or install a previous version of a package. Rolling back can cause more problems than it helps because you lose logs and possibly other files that might have been created.
If you use the backup plugin, you could just restore a backup. Sure, it takes a while longer but how often do you need to rollback? If your system is important enough that you can't tolerate the downtime, you should be testing updates on another system before installing them on your primary.
And as I mentioned above, OMV and the plugins involve almost all of the folders. Settings are usually /etc, binaries, php, and user interface are /usr, many have files in /var. But some services may put files in /opt, /srv, or even /root. Things like the proxmox kernel will install many things /lib and /boot.
-
You will have to create a saltstack file similar to /srv/salt/omv/deploy/hosts/10default.sls.
-
Is omv-engined complaining about setFanSpeed not existing? I would start omv-engined in debug mode to see.
sudo monit stop omv-engined
sudo omv-engined -df
Also, make sure you have editing: true (link) in your route file for the form page.
-
hat causes the error and what can I do?
Seems like a problem with the new kernel and/or u-boot. I would either ask on the armbian forum or wait a week before upgrading to hopefully a newer kernel.
-
Am i doing sth. wrong? btw: using omv6
You are using the method for OMV 4.x and older. You want:
-
How are you adding them?
-
This has nothing to do with your fstab. You need to change the fsname in the mntent that you copied from /dev/sdc2 to /dev/sde2 (if your new location is /dev/sde).
-
you will need to edit the mntent section in the database for uuid 79684322-3eac-11ea-a974-63a080abab18
-
Nothing other than Debian 11 will work.
-
Can you install Debian 11 on that offering?
-
Is this possible without major problems?
Yep. Linux should not care which port they are plugged into. mdadm looks for the raid signature on the drives to assemble the correct drives.
-
zfs 2.1.4 doesn't compile on the 5.18 kernel. You will have to wait until zfs 2.1.5 is in the repo. We can't control Debian from doing this. So, as raulfg3 says, use the proxmox kernel.
-
Can the omvbackup tool functionality be expanded to be able to restore to a new boot drive?
If you just want to make a clone of your OS drive, use the diskclone plugin.
Since you are the dd person, would you explain how these two options are different?
dd - use dd to clone the OS partition to a compressed image file.
dd full disk - use dd to clone the entire drive to a compressed image file.
Does the description not tell you? dd only clones the OS partition as it says. dd full disk clones the entire disk in one image. If you have four partitions on the OS disk, they will all be in the image. Not sure how to explain that any better.
-
Is there a way to set a quota per share?
No.
Do i need to create another filesystem just for timemachine?
Since timemachine just fills whatever you point it at, yes. You could use LVM to create logical volumes for each share. Then it would be easy to set quotas for each share. If you leave some space in the volume group, you can expand any share that ran out of space.
-
Maybe the plugin could scan all disks and backup the partition with the boot flag and formatted FAT32?
Easier said than done. What if there are two?
-
- ignore the boot partition if boot and system partitions are not on the same drive
The boot partition is very important on arm systems though.
option to disable the EFI/boot partition backup
That would be confusing. People already ask how to use the plugin and the only real setting is backup type. I need to rewrite the plugin to handle these non-standard installs and it complicates using the plugin.
-
because I have an armbian system my boot-partition is on sdcard, the root partition is on an 1TB SSD with gpt. with omv-backup 6.0.5 an dd of EFI is created. It seems to be, that in my case the backup-script trys to make a dd of the whole SSD (1TB). Thereofore it does not come to an end in an adequate time.
The backup plugin probably won't work on your system. It assume the OS stuff is on the same disk and would look for an esp partition on your SSD because it has a gpt partition table. It would be a pain to support this because it is effectively multiple root devices. Not sure if I want to do that.
