Unplug all data disks except the one that is dedicated as OS drive while installation. Note, OMV will use the whole root disk for the OS. After the installation re-connect all other disks. MD software raids will be auto-detected. You only need to mount the filesystem of this RAID.
Ok. Really appreciate your time. Thanks 
Yeah. In OMV7 the mdadm GUI was moved to that plugin. Just install it.
Many thanks! Really appreciate your help
Yeah. You will only have to mount the existing file system.
You will need to install the openmediavault-md plugin.
Ok... Install the plugin once I have V7 installed to recognise the existing array...?
You would have to upgrade OMV5 to OMV6, and then upgrade OMV6 to OMV7. But I recommend that you do a fresh installation of OMV7, you will probably finish sooner and without problems.
You can take screenshots of the current settings for reference. You can also install OMV7 on a pendrive and keep your OMV5 installation as a backup by disconnecting the system disk until everything is working.
Ok... will the new install recognise the existing RAID setup...?
No. This is how Debian works related to upgrades. OMV, which is using Debian as its base OS, can't change anything here.
So, install from scratch? What will happen to my existing RAID array?
Did you try clearing the browser cache or trying to access it from another browser?
By the way, you should update to OMV7.
Yes, I did try another browser. Still didn't work. (Is there a painless way for a Nervous Newb to move to V7...?)
Check what plugins you're using. Many got ported, some got changed (new names, functionality) others got dropped.
The UI has changed, get familiar with it.
Also, if you're using advanced stuff like custom configurations or environment variables, there are new commands to set them.
It's a very vanilla install fortunately so I think I'm only using the flash drive plugin, which I perhaps don't even need for an SSD drive...? A second NAS drive is running V6 so I can find my way around...
Please consider installing your system using OMV7 from scratch because otherwise you need to do full distro upgrades from Debian 10 -> 11 -> 12 with all the pitfalls that my occur.
That sounds a bit hairy for a newb... Is there a relatively painless method...? Will my existing RAID array stay in place and be recognised or will I have to back it up and tear it all down again?
Hi, Up until recently my OMV5 system has been running so well that I was happy to leave it alone. As it's been giving me hassle lately, I thought I might as well upgrade to V6...
As I understand it I should just run run omv-upgrade and then omv-release-upgrade to move to V6 but I see some systems getting borked in the process.
Is there anything I can do to minimise potential issues...?
S
Hi, I managed somehow to get back into my server and I'm able to run omv-firstaid.
My issue now is that I can't get a static ip address for my server. If I set the ip address using omv-firstaid I get someting like "The web control panel is reachable at url: 192.168.0.211:80". In fact it's probably unreachable or is only reachable at another ip address.
Only if I use DHCP can I reach the WebGui. I have reset things using both the WebGui and omv-firstaid to try to get a static address but it never sticks.
What can I do?
S
cat /etc/mdadm/mdadm.conf
# This file is auto-generated by openmediavault (https://www.openmediavault.org)
# WARNING: Do not edit this file, your changes will get lost.
# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#
# by default, scan all partitions (/proc/partitions) for MD superblocks.
# alternatively, specify devices to scan, using wildcards if desired.
# Note, if no DEVICE line is present, then "DEVICE partitions" is assumed.
# To avoid the auto-assembly of RAID devices a pattern that CAN'T match is
# used if no RAID devices are configured.
DEVICE partitions
# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes
# automatically tag new arrays as belonging to the local system
HOMEHOST <system>
# instruct the monitoring daemon where to send mail alerts
MAILADDR omvnotifications@spampit.co.uk
MAILFROM root
# definitions of existing MD arrays
ARRAY /dev/md0 metadata=1.2 spares=1 name=openmediavault.local:zulu UUID=e722afd9:58035460:ce00e630:17883000mdadm --detail --scan --verbose
ARRAY /dev/md0 level=raid5 num-devices=4 metadata=1.2 name=openmediavault.local:zulu UUID=e722afd9:58035460:ce00e630:17883000
devices=/dev/sda,/dev/sdb,/dev/sdc,/dev/sddyep
Well... I couldn't get that to work but by some miracle my original root password was recognised once I rebooted back into OMV...
If you boot from the Debian netinstall iso, you can choose the repair option and change the root password.
Just so I'm clear... I can create a bootable USB stick and go from there...? https://www.debian.org/CD/netinst/
When you say "cli", do you mean ssh or local console?
At the moment I'm connected directly to the server with screen and keyboard but nothing works over the network either...
Hi,
As a result of a power outage (I guess) my OMV 5 file server won't mount on my Mac. It has been running perfectly up until now.
When I try to log in over the CLI, no password is recognised. I know the root password is correct as I have used the CLI before, to replace a RAID disk. Now it's not recognised.
I'm connected directly to the server now and I see the OMV prompt. I was hoping to be able to run omv-firstaid but I need to be logged in for that...
I found this: https://www.softzone.es/linux/…ar-contrasena-root-linux/ but I don't ever see a GRUB menu.
At the OMV login prompt, when I try to enter my password where the username should be, I notice that when I try to type a £ sign (Mac keyboard), which is part of my password, it's not recognised. A "3" appears. Could this be why my password isn't recognised? It contains both £ and $. In Unicode you're supposed to be able to type "Option-shift-U-003" to get a £ sign but I can't get this to work either...
What can I do please?
bast aproach is: use a monitor & keyboard atached to your NAS and login on it, and use omv-firstaid to change root password.
Thanks. As soon as I find a VGA cable around here I'll try that. Won't I need any sort of a password to run omv-firstaid though...?
S
This gets worse...Chatgtp got me past the encryption errors but now my root password isn't recognised.
Is there anything I can do?
I Googled the ssh error above and ended up going round in circles...
Mac-Pro:~ s$ ssh root@192.168.0.211
Unable to negotiate with 192.168.0.211 port 22: no matching key exchange method found. Their offer: diffie-hellman-group1-sha1
Mac-Pro:~ s$ ssh -oKexAlgorithms=+diffie-hellman-group1-sha1 root@192.168.0.211
Unable to negotiate with 192.168.0.211 port 22: no matching host key type found. Their offer: ssh-dss
Mac-Pro:~ s$ ssh -oHostKeyAlgorithms=+ssh-dss root@192.168.0.211
Unable to negotiate with 192.168.0.211 port 22: no matching key exchange method found. Their offer: diffie-hellman-group1-sha1I just got an email from the system looking for the Backup disk, which I had disconnected:
The system monitoring needs your attention.
Host: openmediavault
Date: Tue, 17 Sep 2024 16:47:55
Service: mountpoint_srv_dev-disk-by-label-Backup
Event: Status failed
Description: status failed (1) -- /srv/dev-disk-by-label-Backup is not a mountpoint
This triggered the monitoring system to: alertSomething is obviously running, I just can't reach it...
S
Hi, I know this is an old setup but it's been running like a train so I've left it alone...
I have a RAID 5 setup using OMV5 serving my files accessed by SMB.
Usually this is trouble free but suddenly my Mac can't mount the OMV SMB share.
The web gui can't be reached.
The server will respond to a Ping:
PING 192.168.0.211 (192.168.0.211): 56 data bytes
64 bytes from 192.168.0.211: icmp_seq=0 ttl=64 time=2.744 ms
64 bytes from 192.168.0.211: icmp_seq=1 ttl=64 time=0.926 ms
64 bytes from 192.168.0.211: icmp_seq=2 ttl=64 time=7.488 ms
64 bytes from 192.168.0.211: icmp_seq=3 ttl=64 time=1.197 ms
64 bytes from 192.168.0.211: icmp_seq=4 ttl=64 time=1.057 ms
64 bytes from 192.168.0.211: icmp_seq=5 ttl=64 time=3.013 ms
64 bytes from 192.168.0.211: icmp_seq=6 ttl=64 time=0.991 ms
64 bytes from 192.168.0.211: icmp_seq=7 ttl=64 time=1.105 ms
64 bytes from 192.168.0.211: icmp_seq=8 ttl=64 time=2.837 ms
64 bytes from 192.168.0.211: icmp_seq=9 ttl=64 time=1.312 ms
--- 192.168.0.211 ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet lossI'm 99% sure that ssh access is enabled as I've used it before but this is what I get in my Mac Terminal:
ssh root@192.168.0.211
Unable to negotiate with 192.168.0.211 port 22: no matching key exchange method found. Their offer: diffie-hellman-group1-sha1Can anyone help me past this?
S
Thanks
Do I need it when the boot drive is an SSD, not a USB stick...?
I'm thinking I don't need it suddenly...
No, seems it's not required for SSD drives...