Questions about omv-regen

    I ran omv-regen backup, copied the folder and files, installed OMV on a different system and drive, copied /ORBackup to the new system but running omv-regen regenra seems to get stuck right at the start.


    Is there anyway I can find out what's going on?

    I checked /var/log/omv-regen.log but it doesn't contain anything.


    Should I update my newly installed system? I though the script would do that.


    When I left the script running overnight it made progress. I ended up rerunning it later and for some reason it took about 30min. I suspect there is something strange going on with this system.

    Hi chente, your GitHub help tells:


    Quote

    1) Get a clean installation of openmediavault after a change of openmediavault versions. If, for example, you update OMV6 to OMV7 and the update causes problems, omv-regen can move the configuration to a clean system.

    ...

    2) The openmediavault and plug-in versions must match on the original system and the new system.


    At 1) I read:

    If I have a backup of a OMV6 then I can install OMV7 from scratch and then apply the OMV6 backup to get back my OMV settings.

    But at 2) I read:

    Use only the same versions of OMV and its plug-ins at backup and restore to not get in trouble.


    For me your help text is therefore confusing, not clear.


    My plan was: Make a OMV6 backup, install on a other disk OMV7 from scratch. Use the OMV6 backup at OMV7 to get back my settings.


    Can you give me a clarification?


    Thank you!


    _Michael_


    P.S. It turned out I'm already using OMV7 but a clarification is still appreciated.

    Edited once, last by _Michael_: text extended; "P.S." inserted ().

    • Official Post

    It is not possible to regenerate an OMV7 system with an OMV6 backup. The version must be the same.

    Will this too omv-regen help me to install a new hard drive enclosure? Presently, my server is running on a terramaster 2-bay NAS with its usb ports plugged with three other drives, including the OS ssd with OMV. So recently I just bought another terramaster 5 bay enclosure (not a NAS). I would like to rid myself of all the loose cables coming out of the usb bus and just have the second enclosure plugged in to the NAS. Putting the extra data drives into the new thing doesn't worry me, but I'm just hoping that I can put the OS inside, or else perhaps put it in the "internal" usb where terramaster kept its own infernal server OS before I removed it. Any thoughts?

    • Official Post
    Quote from Perceval

    Will this too omv-regen help me to install a new hard drive enclosure? Presently, my server is running on a terramaster 2-bay NAS with its usb ports plugged with three other drives, including the OS ssd with OMV. So recently I just bought another terramaster 5 bay enclosure (not a NAS). I would like to rid myself of all the loose cables coming out of the usb bus and just have the second enclosure plugged in to the NAS. Putting the extra data drives into the new thing doesn't worry me, but I'm just hoping that I can put the OS inside, or else perhaps put it in the "internal" usb where terramaster kept its own infernal server OS before I removed it. Any thoughts?

    You don't need omv-regen or anything special to change the USB enclosure of your drives. OMV will still recognize the drives by UUID. Simply change the enclosures and start the server, and everything will work as before. You just need to make sure that the new 5-bay enclosure shows the drives to the operating system individually.

    To move the operating system from one of the external drives to the Terramaster's internal drive is where omv-regen could be useful.

    Thanks, chente, that clears up a lot of confusion about the scope of this upgrade project of mine. From what I understand by reading the other posts, then to use omv-regen, I should make a clean iso image of OMV on some other drive that fits inside the NAS, and once I get it to boot, I'll have the old OS plugged in elsewhere and tell omv-regen to make the new boot like the old one. That doesn't seem too difficult.

    Quote from chente

    You don't need omv-regen or anything special to change the USB enclosure of your drives. OMV will still recognize the drives by UUID. Simply change the enclosures and start the server, and everything will work as before. You just need to make sure that the new 5-bay enclosure shows the drives to the operating system individually.

    To move the operating system from one of the external drives to the Terramaster's internal drive is where omv-regen could be useful.

    Well, I've managed to make a mess of it anyway. I decided to upgrade the old system to omv7, and everything went smoothly except for the step to update the linux kernels. So now the old system only boots in recovery mode. I installed omv7 on the internal usb drive and got it running, but now I'm stuck. If I try to follow the steps for omv-regen, it fails to produce the backup because of the auto update followed by kernel not configured.


    My hope was that the omv-regen could work with the old os as is, but alas, no. I do have a backup of the omv6 system prior to the update, using the dd set up for weekly backups, and it is one week old today. If I could restore that, and try all of this again, I wonder if I would still get the error through the omv-regen. Of course I stil, have to figure out how to get the routine backuo resored--I've never tried it.


    Edit: 12 hours later and along with a number of trials and errors, we made some progress. I was able to use the dd backup to get the old os running again. Also, I put iso omv 6.5x installed in a new thumb drive inside the terramaster. Then, as per instructions, we install the omv-regen script and use it to make a backup of the old system, except that the auto-update reported a failure. Feeling impatient, I went ahead and tried to run the regen from those images as isto rebuild upon the fresh install. It complained a few times, but I left it alone,and it seemed to finish somehow.


    I got the workbench running again, but I had to use omv-firstaid to do so. After looking at the workbench, I saw that none of my docker containers were running. Looking further, I see that somehow the mount points for all my data drives got shuffled, and so the compose files point to nonexistent links.


    Now what? Maybe I should just use the dd image to write last week's backup onto the new thumb drive, to see if that will work better?

    • Official Post
    Quote from Perceval

    Well, I've managed to make a mess of it anyway. I decided to upgrade the old system to omv7, and everything went smoothly except for the step to update the linux kernels. So now the old system only boots in recovery mode. I installed omv7 on the internal usb drive and got it running, but now I'm stuck. If I try to follow the steps for omv-regen, it fails to produce the backup because of the auto update followed by kernel not configured.

    I think the first step should be to resolve this issue. omv-regen won't fix this.

    Quote from Perceval

    My hope was that the omv-regen could work with the old os as is, but alas, no. I do have a backup of the omv6 system prior to the update, using the dd set up for weekly backups, and it is one week old today. If I could restore that, and try all of this again, I wonder if I would still get the error through the omv-regen. Of course I stil, have to figure out how to get the routine backuo resored--I've never tried it.

    omv-regen requires the new system to be on the same version as the old system. This is explained in the documentation. You cannot regenerate an OMV6 system on an OMV7 system.

    Quote from Perceval

    we install the omv-regen script and use it to make a backup of the old system, except that the auto-update reported a failure

    The system must be updated to its latest version (in this case, OMV6) before performing the backup. This is also explained in the documentation.


    Quote from Perceval

    Now what? Maybe I should just use the dd image to write last week's backup onto the new thumb drive, to see if that will work better?

    You have several options. If you try to do this with omv-regen, you must follow the procedure. The system (OMV6 or OMV7) must be properly updated before performing the backup, or it won't work. Or you can use dd to restore the system to the internal drive. In either case, you'll have to update OMV6 to OMV7 at some point. I suggest that be your first step and ensure the update is successful.

    I've been trying to restore from a back of a system I've had running for years. It keeps getting stuck at:

    "Failed to install omvextras-unionbackend. Exiting...:"


    A few other older packages that I don't have installed fail as well but those ones ones don't cause it to crash.


    Is there anyway I can tell the restore process to ignore these programs I no longer have installed on the original system? I'm guessing they are still referenced in the old OMV config somewhere and that's why omv-regen is trying to restore them.

    Well, the good news is that now after all this effort, I figured out why my kernel wasn't getting upgraded and thus why the OMV upgrade and rebuild were failing on that step.


    When I first set up the OMV on the Terramaster, I tried plugging in a cheap usb Wi-Fi adapter using an unpopular Realtek driver. I seem to remember noodling with it for a week or so and then giving up on getting it to work. After that, I just forgot about it, but it seems that somewhere down the line the guys who were writing the drivers for that dongle gave up on keeping it current and voila, the newer kernels won't compile unless I remove the driver's package. So now that I have removed them, I got my kernel to advance! Of course, I learned this the hard way, by trying to upgrade to OMV 7, only to findt that the upgrade broke. So I'm back trying to recover with a backup image.

    • Official Post
    Quote from danoldlib

    Is there anyway I can tell the restore process to ignore these programs I no longer have installed on the original system? I'm guessing they are still referenced in the old OMV config somewhere and that's why omv-regen is trying to restore them.

    Yes, you can do it manually. You'll need to open the backup and edit the DpkgOMV file. Delete the line for the add-on you don't want to restore.

    This will prevent the regeneration from attempting to install that add-on.

    However, I can't guarantee the result. If the add-on affects other system settings, the result may be unsuccessful.

    Hi,


    Here it is:


    frederic@omv:~ $ ls /usr/sbin | grep omv

    omv-aptclean

    omv-backup

    omv-backup-fix-cron

    omv-btrfs-dfree

    omv-btrfs-scrub

    omv-changebackports

    omv-compose-backup

    omv-compose-backup-multi

    omv-compose-download-icons

    omv-compose-init-git

    omv-compose-prune

    omv-compose-restore

    omv-compose-restore-multi

    omv-compose-start

    omv-compose-start-multi

    omv-compose-stop

    omv-compose-stop-multi

    omv-compose-update

    omv-compose-update-multi

    omv-confdbadm

    omv-engined

    omv-env

    omv-firstaid

    omv-mkaptidx

    omv-mkraid

    omv-mkrrdgraph

    omv-mkworkbench

    omv-removesftpmount

    omv-resetperms

    omv-rmraid

    omv-rpc

    omv-run

    omv-salt

    omv-scripts-exec-wrapper

    omv-scripts-init-git

    omv-sfsnapadm

    omv-showkey

    omv-showsharedfolder

    omv-sysinfo

    omv-upgrade

    • Official Post

    It should be there.

    Can you post the installation output after running the command?

    wget -O - https://raw.githubusercontent.com/xhente/omv-regen/master/omv-regen.sh | bash

    I know, and yet it isn't there... There's an issue quite similar to mine on your github, but I don't know how it got fixed on the user's side...


    Same thing...


Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login