if it is not in use why is it listed in omv-firstaid which implies an AID to rescue something??
no access to web gui no more
-
- OMV 5.x
- Hans Schmitt
-
-
-
macom: Thanks for clarifying that. Hence the config shouldn't be changesd UNTIL the Apply config knob is pressed and everything is finished. So again why is that point listed? It is not clear for me...
I read through the linked chapter and it seems to be real complicated to do a restore. Why is that so? Why can we not do a SAVE of the config (files) and simply restore the config (files) if the system breaks somehow? Like in PFSense e.g.?
-
-
If I remember well it is due to constant changes of services, plugins and omv itself. Those change lead to changes in config.xml. So it should be possible if you have exactly the same versions of those installed, but that seems unpractical.
Instead of using the backup plugin you can just make a clone/image of the OS drive.
-
The main problem is the UUIDs of disks in the config and the passwords for users and some secrets, which are not in the config.xml.
It is possible to backup and recover by copying the config.xml only in some cases. If it was a supported feature it would have to work in more cases.
-
Instead of using the backup plugin you can just make a clone/image of the OS drive.
Yes, you are right. But this seems to be unpractical for me. Because it needs a lot of time, the correct (paid) Software, the correct Harddrivesize as well as access to the hardware. As every actual backup method of OMV this seems not an easy way for me. So I will wait until next breakdown and setup system again. This will take approximately the same time as recover a backup or reiinstall an Image or hardrive, Thank you for all who help in this case.
As I mentioned above: for me its very interesting (important) WHY the config.xml changed to non ASCII.
Regards and have a nice weekend
-
But this seems to be unpractical for me. Because it needs a lot of time, the correct (paid) Software, the correct Harddrivesize as well as access to the hardware
Not every one of us runs the same hardware/OS drives so, there's no "one-size-fits-all" solution.
The pushing for a cloned OS drive is the solution for all if people follow the advice of 1 small drive (USB/SD/SSD, etc) with 16-32Gb.
In some situations where you have physical access to the NAS, it's a 3 step method:
1 - Shutdown Server
2 - Clone the OS drive on a different PC
3 - Boot the Server with the new cloned drive
For those that don't have physical access, use the backup plugin to make a "dd full" clone of the OS drive and save it to an external shared folder so you have access to the file outside the NAS. This will imply the same similar steps as above:
1 - Clone the "dd full" copy to a drive on another PC
2 - Shutdown Server
3 - Boot the Server with the new cloned drive
Of course, you will have to try, AT LEAST 1 TIME, if the "dd full" cloned drive really works. You don't won't to find that it doesn't, when you'll REALLY need it.
And you better try it while everything is running than waiting for the Server to fail.
Only catch here is that if you have your Server in a bad/remote/unaccessable place, you will always have to access it sometime.
-
Because it needs a lot of time, the correct (paid) Software, the correct Harddrivesize as well
You can do an image with Clonezilla (free) and it will compress the image.
-
As I mentioned above: for me its very interesting (important) WHY the config.xml changed to non ASCII.
Regards and have a nice weekend
So what is the content of config.xml now? Try file /etc/openmediavault/config.xml and then strings /etc/openmediavault/config.xml or take a look inside using a hex editor . This my give a hint what happened.
Have you done a fs check?
-
In my experience, sometimes text files become binary when something is corrupted in the file system (eg: after an unclean shutdown or a power surge).
Sometimes a fsck solves everything, but it depends on the cases.
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!