Clean Install of OMV7 Hangs - Multiple attempts

Quote from Soma

Can you check if the IP changed either on the router or with a IP scanner tool?

Or just ping the IP to see if it's still the same.

On a side note, I had an issue on pi5 with the network.

All it took was to disable the predictable network names on raspi-config.

Thread

OMV7 on RaspberryPi 5 - INFO - DO NOT INSTALL UNLESS FOR TESTING

[EDIT]
DISCLAIMER: This is just a proof-of-concept and shouldn't be used in a production environment.
The idea for this is for experienced people to test and brush off any possible issues.
If you don't know how to, DO NOT TRY IT UNTIL IT'S READY AND RELEASED!!!
[/EDIT]

Following the instructions from @votdev
Install OMV7 on Debian 12 (Bookworm) - Guides - openmediavault

This is what has been going on, on the Pi5:

Flashed SDcard with RaspiOS 64 Lite (Bookworm) with pre-sets for:
Hostname
Locale (PT)
SSH…

Soma

Nov 11th 2023

There's already several threads with successfull updates/installs of OMV7 on Pi4.

Curious if it's some issue with the ONE itself.

Is your case the v2 (no bottom addons)or the M2 (m.2 addon bottom board)?

Display More

narrowed down. Hostname. On me for not trying IP but i haven't had to with OMV6 and ultimately - i need the hostname to work for my timemachine backups.

Quote from lucid3ye

narrowed down. Hostname. On me for not trying IP but i haven't had to with OMV6 and ultimately - i need the hostname to work for my timemachine backups.

it's an assigned by MAC IP address (reserved). It's now been plugged in at two different points on network - claims correct ip.

update to this thread - downloaded the hosts plugin - added host "mystorage" and rebooted. host still does not respond to pings, ssh, HTTP, or SMB as "mystorage.local"

removed hosts plugin, went into network settings - reset host name to "mystorage" applied configuration..

well - that bricked it, lol. I can't see it by IP or anything. So I'll do another reload knowing it's just the hostname dropping and see what i can do from there.

thanks for the help, i think it's safe to close this thread unless you want to open another on the hostname dropping for some reason..

Quote from macom

You can change the host name in the GUI of OMV

so here's the rub - and i think it's pointing to where the issue may lie. hostname works fine until you turn on SMB/CIFS - then you can't log in to host at hostname and use IP . Here's where it gets better. I just did a clean install, configured all of my usual plugins, drives, shares, etc - everything was working as long as I was willing to go by IP.

then i did as you just suggested above and changed the hostname via the GUI - just deleted the last letter of storage "e" and put it back so I could hit save. They system prompted me to apply changes - i did so. it stopped responding everywhere - could not SSH, could not ping, could not hTTP. waited 10 minutes. powered down and rebooted. Same result. No IP response. Its as if there is an issue somewhere in network stack on PI platform.

I'm doing another clean install working just within IP addresses and will not attempt to change hostname and will see how long it lasts... for now i think there are two variables here - hostname and PI. the hostname drops off when you enable SMB - if you try and change it you're gone.

Clean install - everything is working all plugins I use:

Compose
SMB/CIFS
UPS NUT
CPU Temp

system does not respond to hostname at all. works via IP address. About to put up my Homebridge and see if it works.

The hostname and SMB/CIFS configuration seem to be linked. As soon as you enable SMB, hostname disappears. if you try to change it via the GUI the system becomes unresponsive.

to update this thread - i continued to configure using IP address. Once I had my Homebridge up - it seemed to push out the hostname for whatever reason, and magically hostname started working everywhere.

currently I'm backing up via Timemachine to shared folder - and homebridge is up and running with a plugin acting up that I don't blame on OMV7.

Thanks for the help. I hope that the information I provided was helpful to someone.

Quote from jata1

lucid3ye - I know you know what you are doing but have you checked the name assigned to your ethernet in the GUI (network > Interfaces) vs looking at the diagnotic report (diagnostics > report).

I have found that there is a difference in the name (eth0 vs. end0) and this will cause issues when setting up services that rely on the network.

The fix is easy if this is the case and you need to do this before configuring anything else. Just delete incorrect interface from GUI. Don't apply changes. Add correct interface name. Save. Apply.

pleased to report that with time everything just seemed to start working as i stuck with it and configured. I'm not sure if there is some issue on my network - but i don't think that was the issue as the host would simply stop responding - all that being said. It seems like when you initially enable SMB/CIFS something happens that makes the hostname temporarily unresponsive. If you continue using the IP address - eventually the system resolves to the hostname again via all protocols.

Quote from lucid3ye

pleased to report that with time everything just seemed to start working as i stuck with it and configured. I'm not sure if there is some issue on my network - but i don't think that was the issue as the host would simply stop responding - all that being said. It seems like when you initially enable SMB/CIFS something happens that makes the hostname temporarily unresponsive. If you continue using the IP address - eventually the system resolves to the hostname again via all protocols.

also - while I'm an expert at networking and hardware - linux - i am no expert. I'm learning. So all of the help in the forum was appreciated. It forced me to try some different things i wasn't thinking through. For instance, when hostname stopped responding reverting to IP. That's a no-brainer I should have done, lol.

Quote from jata1

lucid3ye - I know you know what you are doing but have you checked the name assigned to your ethernet in the GUI (network > Interfaces) vs looking at the diagnotic report (diagnostics > report).

I have found that there is a difference in the name (eth0 vs. end0) and this will cause issues when setting up services that rely on the network.

The fix is easy if this is the case and you need to do this before configuring anything else. Just delete incorrect interface from GUI. Don't apply changes. Add correct interface name. Save. Apply.

This sir is the problem. Many Thanks - going to attempt your fix. I noticed on dashboard end0 is grabbing and IP while when i look under network settings its using eth0 which doesn't exist. Couldn't get this to change - your process above i will try!

Quote from crashtest

A couple things:

First, with the following comment:

I was not addressing you, lucid3ye.

You have a different set of circumstances, that does not include "raspi-config", so I don't know why or where the snark is coming from. But I will say this; it's not helpful when forum users inject themselves into the middle of a direct conversation with a specific user, with quotes and comments that don't apply and snark added as garnish. Problems are not dealt with by "piling on". They're solved one-at-a-time.

In any case, I did the test run and found what appears to be a systemd network issue.

Having cut my computing teeth on a Commodore 64 and DOS 1.X, 2.X, etc., I seriously doubt that you were building systems when I was in diapers. In my diaper days, "a computer" might have been crossing over from tubes to some of the very first, experimental, TTL circuity. Building a system at that time would have taken the equivalent of a tractor trailer van full of equipment, DARPA PhD's (ARPA at that time), a ton of money and resources.

Further, having been retired for a bit over 13 years now, it's possible that I may be older than you are.

You followed an install guide for OMV 6.0, to install OMV7 RC1. Had you followed the install for OMV 6.0, as it was written, OMV6 would have installed flawlessly. (Absent hardware problems and user induced mystery issues.) OMV7? Obviously, there are no guarantees. At the moment, I'm working on the OMV7 install guide for AMD64 ISO - one thing at a time.

With the above noted, if you think you can write a guide for installing OMV7 on R-PI's that's succinct, not confusing for beginners, that will support broadest cross section of users (beginners and enthusiasts alike), and you're willing to support it, please feel free. I'll even publish it on the Wiki for you, so you won't have to go through the Markdown and HTLM learning curves.

You see, the support angle comes with trying to figure out hardware issues, build problems, and how users go off the beaten path. The latter, not following instructions or deviating without admitting it, is easily where +60% of installation issues come from and it's where a LOT of forum time is wasted. (As forum contributors look into the "crystal ball" of their expertise, experience and intuition trying to figure issues out, remotely.)

___________________________________________________________________________

Reading through your posts, it appeared that you might have a DNS issue which might indicate a problem with your local router, the router's configuration or your DCHP server, if it's separate from the router. (This is what I was talking about when saying you have a different set of circumstances.)

Local hostname lookups have very little to do with your R-PI (assuming it's not being used as a DNS or DHCP server). If you have local DNS, you could misname the R-PI's hostname and it's domain suffix, in OMV, and it wouldn't matter.

You can setup a crude form of local DNS by:

1. Setting up static DHCP leases for the IP address(es) of your server(s) which should include their hostname(s).
2. In my setup, I statically address my OMV servers with the same IP address used for their static DHCP leases.
(While optional, static server addressing eliminates a server's reliance on network connections and an external, DHCP, process.)

When clients do a hostname lookup, the local Router/DCHP Server acts as a local DNS and returns an IP address. This has worked well for me. It might work for you.

Display More

it actually sounds like we cut our teeth on the same equipment and same OSes, lol. Again sorry for being snarky.

Problem is resolved.. turned out to be the eth0 / end0 named in another comment. Everything is running swimmingly now.

Quote from jata1

lucid3ye - I know you know what you are doing but have you checked the name assigned to your ethernet in the GUI (network > Interfaces) vs looking at the diagnotic report (diagnostics > report).

I have found that there is a difference in the name (eth0 vs. end0) and this will cause issues when setting up services that rely on the network.

The fix is easy if this is the case and you need to do this before configuring anything else. Just delete incorrect interface from GUI. Don't apply changes. Add correct interface name. Save. Apply.

winner winner - chicken dinner. Issues resolved and thank you.

Quote from votdev

What is the output of ip addr? Is it possible that the system was previously configured via eth0? OMV added support for DSA network interfaces (e.g. this end0) some times ago.

no it appears that the default PIOS starts with end0 and somewhere along the way OMV uses eth0. Maybe PI is being weird because i have never seen end0