Upgrade 6 to 7 issues with Helio4

I ran into a few issues upgrading my Helios4 from OMV6 to 7. Some I was able to resolve on my own. I'll post them anyway in case someone runs into the same issues.

The first one was that the network interface changed name from eth0 to end1. So networking was down after reboot. Had to login through the serial console. I then renamed and modified /etc/network/interfaces.d/1-eth0. Then flush (iptables -F) and fix the firewall rules.

Next were a few services that failed to start:

• fancontrol
• helios4-wol
• nut-driver@apcsmt1500

Fancontrol was easy enough to fix: I installed the fancontrol package manually. I still have the openmediavault-helios4 5.0 plugin installed, but it doesn't seem to be available at omv-extras.org...

helios4-wol is set to eth0 and I can't seem to find its config. Is that a remnant of the openmediavault-helios4 plugin?

Finally the nut driver, I'm not so sure what's happening. It's in some sort of boot loop where it just tries to start over and over again with these errors in syslog:

2024-03-18T22:56:29.802295-04:00 localhost nut-driver@apcsmt1500[3528]: Network UPS Tools - Generic HID driver 0.47 (2.8.0)
2024-03-18T22:56:29.802481-04:00 localhost nut-driver@apcsmt1500[3528]: USB communication driver (libusb 1.0) 0.43
2024-03-18T22:56:29.802594-04:00 localhost nut-driver@apcsmt1500[3528]: libusb1: Could not open any HID devices: insufficient permissions on everything
2024-03-18T22:56:29.802694-04:00 localhost nut-driver@apcsmt1500[3528]: No matching HID UPS found
2024-03-18T22:56:29.803053-04:00 localhost nut-driver@apcsmt1500[3527]: Driver failed to start (exit status=1)
2024-03-18T22:56:29.805010-04:00 localhost nut-driver@apcsmt1500[3527]: Network UPS Tools - UPS driver controller 2.8.0
2024-03-18T22:56:29.805249-04:00 localhost systemd[1]: nut-driver@apcsmt1500.service: Control process exited, code=exited, status=1/FAILURE
2024-03-18T22:56:29.805434-04:00 localhost systemd[1]: nut-driver@apcsmt1500.service: Failed with result 'exit-code'.
2024-03-18T22:56:29.805716-04:00 localhost systemd[1]: Failed to start nut-driver@apcsmt1500.service - Network UPS Tools - device driver for NUT device 'apcsmt1500'.
2024-03-18T22:56:43.711336-04:00 localhost systemd[1]: Stopped nut-driver@apcsmt1500.service - Network UPS Tools - device driver for NUT device 'apcsmt1500'.

The thing is, it's not plugged-in via USB. It's managed by another machine and monitored through network.

If someone has an idea, please let me know.

Thanks.

I uninstalled the openmediavault-helios4 package. Seems to have gotten rid of the wol service issue.

Also reinstalling/reconfiguring the nut package resolved the driver start failure. So, all good?

You're right. I got mixed up with something else. The helios4-wol is still looking for eth0