OMV 3 wird nicht mehr unterstützt. Die sources.list zeigt auf nicht mehr vorhandene Quellen.
Edit: entschuldigt den Nekrobump, wurde mir bei neuen Beiträgen angezeigt und ich habe nicht aufs Datum geachtet.
Beiträge von getName()
-
-
-
When it tells you to look for details, its a good way to start. Propably you missconfigured it.
-
Or the following scenario: your fs fails, you recover but loose some inodes. Just before you recover your rsync starts working and deletes your backup. You should really be using more than just a plain copy.
-
Maybe you should consider to keep at least a few older versions. Something like full backup each month, than only diffs and remove everything older than current and last month.
Dataloss due to mistakes do and will happen at some point. -
I am not all too familiar with the omv specific commands, but maybe omv-firstaid can reconfigure the network correctly.
I personally would go with the sed mentioned above, than grep for enp1s0 and remove all doubling entries.
@tkaiser I agree that NetworkManager has a more robust behaviour in this situation. -
What do you mean by "crashes"? Is it still reachable by ssh?
-
Are you swapping?
Those are two seperate commands. -
Just a friendly reminder, forcing ( -f) apt may break a lot, if you dont know the dependencies I would not do that.
-
Looks good to me.
-
Ok, did you put in or remove pcie devices?
The nic it tries to configure is located in another (as it is an onboard device virtual) pcie slot than the one existing. This happens sometimes with consumer hardware. This may be caused by adding or removing devices as well as changing bios settings.
This can be fixed quite easily. Just reconfigure the network settings and set the old settings for enp1s0 instead of enp2s0.
Edit: just read you did in fact remove pcie cards. Some consumer hsrdware unfortunally creates virtual pcie slots for onboard hardware behind the last slot used. This is hardware specific behaviour which can lead to the problems encountered. -
Just fyi, you dont need to restart ssh, it uses pam anyways.
In my opinion permitRootLogin is only a good idea, if there server is only reachable from intranet, and there is no iot crap in it. Or you got some port knocking protection. -
This works pretty well with a mounted filesystem with both ext4 and btrfs with recent 4.x/5.x kernels: https://github.com/armbian/bui…size-filesystem#L129-L139
Oh, I see! Thank your for the link and info.
-
Did you use ext4? This can be resized quite well, but of course you should not use it during resize. Mount a livestick or similar.
The main question to me is, why do you use more than 8gb. Standard installations should not be that big, afaik. -
Please provide ip link show.
Are there multiple ethernet ports? Did you set one to be forced up which is not connected anymore?
/sbin/ifup -a --read-environment [b](code=exited, status=1/FAILURE)[/b]
I think we should solve this one. Are there any additional logs? What happens if you restart that service after boot completed? -
After adding the new drive, please provide output of - -detail again.
-
-
It looks like the manager crashes.
systemctl - -state=failed will show failed modules. -
As it tells you, look inside sources.list. It seems to be broken. The address inside is wrong.
-
Not enough infos to debug now. Propably just a wrong grub.cfg
Also, why would you do this without backup?? Changing partition tables on a system drive for no reason without backup makes me kind of think that a forced reinstallation has great educational value to learn to not to do something like this.