Surprisingly Smooth Upgrade 7 -> 8

My upgrade went very well, just having one issue:

/etc/cron.daily/openmediavault-mdadm:
mdadm: Value "omv2:0" cannot be set as devname. Reason: Not POSIX compatible. Value ignored.

This is my md output:

/dev/md0:
           Version : 1.2
     Creation Time : Mon Aug  7 19:27:47 2023
        Raid Level : raid0
        Array Size : 23441316864 (21.83 TiB 24.00 TB)
      Raid Devices : 6
     Total Devices : 6
       Persistence : Superblock is persistent

       Update Time : Mon Aug  7 19:27:47 2023
             State : clean
    Active Devices : 6
   Working Devices : 6
    Failed Devices : 0
     Spare Devices : 0

            Layout : -unknown-
        Chunk Size : 512K

Consistency Policy : none

              Name : omv2:0
              UUID : b36f5276:7a5eb43e:cfad32f3:51279d74
            Events : 0

    Number   Major   Minor   RaidDevice State
       0       8        0        0      active sync   /dev/sda
       1       8       16        1      active sync   /dev/sdb
       2       8       32        2      active sync   /dev/sdc
       3       8       80        3      active sync   /dev/sdf
       4       8       64        4      active sync   /dev/sde
       5       8       48        5      active sync   /dev/sdd

I am not sure why it is named omv2:0 and who named it that way, but clearly the name is violating POSIX standards.

It was typically /dev/md/md127 or something alike and now it is /dev/md/omv2:0

I now changed /etc/mdadm/mdadm.conf to this:
# definitions of existing MD arrays
ARRAY /dev/md/omv1 metadata=1.2 UUID=b36f5276:7a5eb43e:cfad32f3:51279d74

and also rebuild the initframfs:
myuser@openmediavault:~$ sudo update-initramfs -u

Now the command executred by anacron daily is executing without an error message.

Wow and just as I see it, Raid 0 was not intended. Not sure what I have setup there ...

Okay time to rebuild the raid copy all data over ...

I successfully completed the upgrade from 7 to 8.04-1 this morning. I experienced only one issue which I was able to resolver fairly quickly.

All was going well after executing "omv-release-upgrade", it stopped, reporting the following error:

updating workbench configuration files ... 
restarting engine daemon ... 
errors were encountered while processing: grub-pc

Google search suggested: Latest update/s fail grub-pc

Followed the simple step:

"ssh into omv as root and run the command dpkg --configure -a"

I was never presented a to selectr the correct boot device. Nothing appeard to happen at all.

I rebooted the server.

I then ran: sudo wget -O - https://github.com/OpenMediaVault-Plugin-Developers/installScript/raw/master/fix7to8upgrade | sudo bash which took a few seconds to complete and my install completed.

• All disks, file systems and shared folders were back.
• All network shares present.
• All plugins previously installed were present and correct.
• All Docker stacks and containers were running as before.
• Plex services running perfectly.
• All user accounts intact.

When I saw the grub error I feared the worst, especially as I run a headless server. (PITA sometimes), but my fears were unfounded!

Thank you everyone whop worked on this. I am seriously impressed.

Worked without issues for me too. Thanks!

Upgrade to 8.0.5-2 with mergerfs and snapraid worked without issues for me too

Well I have to say, that was almost too simple.

Upgrading from OMV 7 to 8 simply ran without any problems, but now I'm searching through it trying to find what went wrong that I didn't catch. Not found anything yet.

It was indeed surprising to me as from 6 to 7 was something of a nightmare, so this was a very pleasant surprise.

I know it's so annoying when you're having terrible problems and others are smugly saying "all works great for me" and I'm normally in the former group, but very happy to be in the latter group this time. Well done to those who put together this upgrade.

Upgraded on of my OMVs earlier today....went through relatively OK.

Did notice a number of dpkg warnings however suspect these are expected.

At the end, got the following:

Updating workbench configuration files ...
Restarting engine daemon ...
Errors were encountered while processing:
 grub-pc
E: Sub-process /usr/bin/dpkg returned an error code (1)

Did reboot then soon after tried logging in to the GUI....got the "Bad Gateway" message however, as gderf mentioned, run the fix7to8upgrade script and it was all good.

I was then able to successfully login to the GUI yet it wanted to save the configuration changes and there was a message about a required restart.

After the restart, could login to the GUI....no issues with anything. That being said, this OMV doesn't have much going on.

I'll be backing up my others before I do them .... KVM, Docker, etc.

1 command and everything is working after the upgrade without manual intervention....Where are the bugs?
Great work!. this was a very smooth upgrade on a DIY i3 NAS.

Snapraid, Mergerfs, Docker etc, seems to work fine.

Most of times updates on OMV are smooth. I recently moved from 7 to 8 and I had only a minor hiccup about array that system was convinced disappeared and reappeared...

I just upgraded to OMV8. No problems.

Me, too. No issues.

The first upgrade somehow broke my OS. Luckily, I had a full backup to restore the OS drive. Now I’m on my second try. Hopefully, this works out. Unfortunately, I couldn’t figure out why the first upgrade attempt broke the OS on my Orange Pi 5 Plus.

Quote from ryecoaaron

If you are using the orange pi provided debian image, it does some odd things that I can see breaking during an upgrade. Did you keep the output or the log file from the upgrade?

Unfortunately, I did not.

It worked fine right after the upgrade finished, but after a few minutes, more and more components started failing. Eventually, SSH stopped working, and even the HDMI ports became unusable. I’m not a Linux expert, so it’s hard for me to describe the details or know what exactly to look for.

The second upgrade, however, was successful so far, and I haven’t encountered any problems since.

The only thing I’ve noticed is that the Orange Pi now takes significantly longer to boot — around two minutes instead of just a few seconds as before.

I was using this distribution:

Armbian_25.11.1_Orangepi5-plus_bookworm_vendor_6.1.115-omv_minimal.img.xz (possibly not the exact same version). Downloaded from armbian directly.

Quote from Gestation0916

The only thing I’ve noticed is that the Orange Pi now takes significantly longer to boot — around two minutes instead of just a few seconds as before.

My machine is a bog standard PC and I have the same thing happening. The OS is on an SSD and now the time it takes to boot is more like when it was on stock HDD. It's not a deal-breaker to wait a bit longer but it would be nice to know what changed and if it can be improved upon.

Quote from ryecoaaron

This should tell you what is taking so long: sudo systemd-analyze blame | head -n20

2min 85ms systemd-networkd-wait-online.service
   7.821s openmediavault-issue.service
   2.622s systemd-journal-flush.service
   2.027s smartmontools.service
   1.859s tor@default.service
   1.669s smartctl-hdparm.service
   1.631s smbd.service
   1.488s phpsessionclean.service
   1.482s dev-sdd1.device
   1.211s omv-writecache-setup.service
    986ms dpkg-db-backup.service
    894ms proftpd.service
    882ms php8.4-fpm.service
    784ms chrony.service
    736ms systemd-fsck@dev-disk-by\x2duuid-21fbff2f\x2dc82b\x2d43cc\x2d8b30\x2d5dd7021400ec.service
    724ms lvm2-monitor.service
    720ms quotaon@srv-dev\x2ddisk\x2dby\x2duuid\x2d999994cb\x2d4194\x2d4b8c\x2d9b69\x2ded48c733e35b.service
    698ms openmediavault-engined.service
    694ms podman-auto-update.service
    609ms srv-remotemount-Fritznas.mount

This is what mine says.

I have openmediavault 7 running on raspberry pi 4b 8GB system for more than a year and is working fine.

Version - 7.7.24-7 (Sandworm)
Processor - Raspberry Pi 4 Model B Rev 1.5
Kernel - Linux 6.12.47+rpt-rpi-v8

From what I understand reading through is, I just have to run below command to upgrade to 8?

sudo omv-release-upgrade

Can some one please advice?

Quote from chente

Yes, that's all you need. Run omv-release-upgrade.

As a precaution, I would first make an image of the SD card where the operating system is installed.

I assume you have the omv-flashmemory plugin installed. This plugin is deprecated; you should replace it with omv-writecache.

Yes, I see I have "openmediavault-flashmemory 7.0.1" installed and I am running omv from a SDCARD.

Should I just uninstall "openmediavault-flashmemory 7.0.1" first and then install "openmediavault-writecache 7.0.0-13" before performing the OMV 8 upgrade?