I don't know if that is feasible for your implementation:
Unfortunately not since you shouldn't have command line structures in the mount file. I am fixing it now.
Posts by ryecoaaron
-
-
This looks like an error to me.
It is. If you don't have a *, it won't work right. What was your wildcard?
-
The official readme is changed and even the script will tell you it needs sudo or root now. https://github.com/OpenMediaVa…ges/blob/master/README.md
-
the correct instruction is:
The old instruction was not incorrect. You just weren't following what I wrote. And please remove the instructions and replace with a link to the official instructions - https://github.com/OpenMediaVa…ges/blob/master/README.md. That way, many places don't need to be updated. There is also no need to activate the extras repo (ever really).
-
Yes but please be so kind and update your first post. Not that other users fall into the same trap I did.
Give me a chance to make changes. These commands are in more than one place as well.
-
now it could be that for a RPI the result was not intentional because the logic is a bit complex
It looks like that because there is a dropdown in the Power Management tab to change what the power button does. Maybe changing that dropdown will fix the RPi power button since it defaults to "nothing".
-
Now that I have run sudo passwd root already , did I thereby activate the root account (which was dormant before, I do not recall actually)? If so is it recommended to disable this again?
You don't have to do anything of that. If you do: sudo su -, you will become root. No need to activate/deactivate or change password.
-
But the goal of OMV is to be a NAS OS which is easy to manage, usually entirely by the Web UI, so if an occasional SSH CLI intervention is necessary, then please make instructions as explicit and unambiguous as possible.
Trust me, it doesn't matter what I post. Someone will still get it wrong. And with OMV 6.x, there is no upload to install omv-extras. So, the script has to be run from the command line.
-
Wonder why OMV install comments this out?
Most servers are setup to not shutdown when the power button is momentarily pressed. I know I don't want just anyone to be able to press the power button and turn my servers (at work and home) off.
-
please improve your initial post to spare the occassional OMV users (like me) some troubles
I try to post instructions that make sense. If the command was run as root, it will work. If the user decides to not run as root and just prepend sudo to the first command, they are not following the instructions. I will try to improve them or maybe the script.
-
Docker has a convenience script for installing docker
Right but most people only run that once (typically never on OMV system since omv-extras is doing it). I was saying that the packages installed don't maintain the .list file. Either way, I will look at avoiding the duplication but it might be tough if people are running the docker script more than once.
-
If you feel that adding OMV to an existing Debian install is a corner case and anyone doing so will be able to troubleshoot and fix the issue themselves, then that's fine.
My recommendation (especially when running my install script) is to start with a fresh install and not have anything configured. So, an existing install with lots of things configured is a corner case.
As I mentioned I did indeed comment out the deb entry in the docker.list file (who knows if Docker will make some change to it in the future so I may as well retain the file itself).
I don't know of any docker package that maintains that sources.list entry. Typically that is added manually by the user or script.
I don't have the knowledge to debate the merits or otherwise of Docker's approach vs Salt's, I just (now) know enough to tell you that if you do both it breaks things.
Neither is wrong. I will see if there is some simpler code that I can add. I won't be adding it to omv-extras 5.x though.
-
I guess the only way to restore this is by running the correct command from a Linux system.
Therefore there is no way to do it from windows. So at least in my case this does not work, I will have to keep doing this manually.
At least now I know why. When a user asks I will know what to answer.
That isn't true. There is no reason you can't do this on Windows. Just give me some time to try some things. I just didn't want to stop working on OMV 6.x things. Sigh...
-
do i need another bridge as described in this link?
You have to change the host to use a bridge. Then you choose the bridge connection for the VM. There are a few posts about this.
-
If I revert back to the old config.xml, then I am back to the error message in the original post. The "shared folder" will not load and comes with this error message:
I don't know where that puts the database. So, don't do that. Just create a new pool. Which part do you not know how to do?
After creating the new pool, just edit the shared folder to point to the new pool.
-
I edited that after sudo omv-showkey mergerfsfolders showed the output from Mergerfs issues after upgrade">#6 post
so now it shows no output
for sudo omv-showkey mergerfsIf you deleted the mntent for c6a9724d-5004-42d2-a791-211aa2697465, that is what is causing the problem. You will have to delete the mergerfs pool and create a new one.
-
openmediavault-kvm plugin in the repo. This is a huge change as well. So, be on the lookout for quirky things.
-
It apparently partitioned the USB drive and burned the image
Nope, it won't partition the drive. It just writes the image after decompressing. Because it is writing the partition table, the partitions come back. If it hung on boot, it is probably a grub issue. If this is an RPi, it is probably something to do with uboot.
-
Also I removed mntent for the old mergerfs from config.xml which allowed mergerfs tab to load on the webU
When? That really changes the exact state I am trying to determine. I need to see:
sudo omv-showkey mergerfs
-
where does that information get stored?
The omv database.
Is there any way to start the queued downloads from the terminal?
Not easily.
I'm looking for a way to setup a job that automatically downloads whatever I've queued up on a schedule.
Maybe something more advanced like jdownloader would work better.
