omv-regen migration not successful.

I have read instructions regarding migrating OMV to an another drive using "omv-regen". Steps I took as follow:

1. Created Backup in one of the drives (/export/AppData/ORBackup) on the existing OMV 7 system

2. Shutdown and disconnect OMV 7 drive (64GB SSD). Installed new 250GB SSD.

3. Rebooted the system from OMV 7 flash drive and installed on the new 250GB SSD.

4. Run omv-firstaid to set network interface to the same IP Address as the original system.

5. Rebooted to freshly installed OMV 7 and updated and upgraded the system.

6 Mounted file system "/export/AppData" in GUI

7 in OMV CLI copied "/export/AppData?ORBackup/tar.gz file to /ORBackup

8. From /ORBackup i run omv-regen. No errors. Then I was asked to reboot system and run omv-regen again to complete migration.

9. Rebooted system, and I am not able to login (screen blinks and goea back to login prompt) at the OMV console as root nor any other user including admin.

At this point I do not how to get back to the new install (when I switch to the original drive I have OMV running, so that is good) and complete migration.

I need some help to get me through this. Thanks.

Quote from chente

In point 9 after rebooting the system did you run omv-regen again?

Did you receive any error messages? You can check the log.

No errors during boot process. I cannot login at the console level (have monitor and keyboard attached to OMV). When try to login, after typing root password screen flickers a I am taken back to login. So, needless to say I did not/was not able to run omv-regen.

Quote from chente

I'm sorry, but I think the problem lies elsewhere. There's nothing in omv-regen that would cause a failed login to the server.

So, what, in your opinion, would be the issue. I tried twice and got same result. Ended up recreating an entire OMV config from "scratch" that took few hours to finish. I would like to know the right procedure of migrating OMV from 1 disk drive to an another on the same "bare metal". Right now, it looks like, it is not feasible using omv-regen.

@"chente"

Here is output of dpkg -l | grep openme

I do not think there are some special conditions in my computer. It is a MSI B550-A PRO MB with AMD RYZEN 5 5600G CPU, LSI 9207-8i PCIe 3.0, 10GTEC 10GB SFP+ single port with Intel 82599EN controller. Bunch of Seagate 4TB Barracudas. Noting out of ordinary.

Note:

I am running "zsh" shell instead of, default, "bash". Would that have something to do?.

Edit:

I also run MariaDB, Portainer and Sonarr Dockers.

Quote from Teschbert

Just something what came to my mind and I'm asking myself:

When goal is to just replace the system disk, why not simply do a fsarchiver-backup (e.g., or dd, ...) and restore to the new SSD with the help of a 2nd Linux system?

I already did it this way two times - this takes just minutes if the process is clear.

Thanks for the info. I will look into it as an alternative method.

UPDATE --> Successfully migrated system.

I went back to migration directions on GitHub. After carefully reading it I noticed that I did not follow migration direction exactly as instructed.

These are steps I made that resulted in successful migration.

1. On the original system drive I reverted back to bash shell (I am not sure if this is important or not)

2. After reboot I created new backup using omv-regen.

3. Copy dir ORBackup with tar.gz file to my Arch Linux laptop.

4. Shutdown OMV, connect new disk and reboot to installation USB stick.

5. Install OMV on the new drive and rebooted. (did NOT changed and configured anything)

6. installed omv-regen on the new OMV drive

7. From Arch Linux laptop copy ORBAckup dir and tar.gz file to new OMV drive "/" directory

8. run omv-regen (do not touch anything) wait until is finished and rebooted (does it automatically)

9. login as root (yes this time I could login). System is still on DHCP.

10 run omv-regen and weight when is done (it take some time).

11. It rebooted to my static IP as it was on the original drive. Everything migrated just fine. The only thing was I had to restart Dockers manually.

So, all is working when one follows directions to the letter.

@"chente"

No problem. It was just bugging me why it does not work. Migration also did not copy "zsh" shell so, I think, this was an issue as well. I had to re-install "zsh" as well as "vim" (my favorite text editor). CPU temp also needed to be re-installed and reconfigured.

There is one caveat I need to add. omv-regen works great and create complete copy of the original drive, but if you installed "zsh" shell (I did since I use CLI quite a bit) before creating backup revert back to the default "bash" and, to be on safe side, reboot system. The other issue is FTP (I use FTP extensively copying/moving files between HD`s (3.5 in spinners) mounted/located on OMV. With "FXP" switch in FTP setting page, the speed of copy/move is ~120-180 MB/s as opposed to nfs ~ 50MB/s for the same files between same drives). I found out that if you have installed FTP plugin, remove it prior to creating backup. omv-regen, for some reason, does not handle ftp "gently". Once migration is completed and you boot to the new drive, just install FTP plugin and re-create ftp shares. Then all will work as it should.

Thanks "chente" for your assistance in this process.