Could not resolve httpredir.debian.org

Make sure you are connected to the Internet.

Try:

ping google.com

... and see if you get a response from google.com.

Zitat von tkaiser

/---/ We should really drop RPi support /---/

I wholeheartedly agree and have said the same thing, for the reasons outlined in this post.

Of course, in dropping support for the R-PI, a few inconvenient facts would have to be, shall we say, "overlooked".

For example the R-PI, by itself, is roughly 3 times more popular than all other supported SBC's combined (approximately 18 separate models). And it should be noted that R-PI users may be very close to being 1/3 of the entire OMV user base.

Regardless and despite the numbers, if you're involved, it's obvious that R-PI users are not going to be treated with a modicum of decency or respect. You've even went so far as to put a message about R-PI's "being slow", and an external link, in the OMV4 / R-PI image motd. (This guarantee's that your opinion of the R-PI will be known to R-PI users, EVERY TIME they log in with SSH. )

So why talk about it anymore? - stating the same old thing over, and over, and over, and over, for years without end.

Do away with R-PI support and be done with it.

Keep the RPI image and users but create a special RPi-FAQ for them. Politely refer to that FAQ when they ask RPi questions on the forum. In the FAQ the problems with RPI in regards to use as a NAS can be described in detail. And generic alternatives suggested. (An SBC with SATA(/USB3?) and GbE?) Expand the FAQ as needed.

As I understand it a connection to Internet is necessary during the install. But if there is no connection an unattended or headless install is still finished, perhaps with a borked OMV install. And there is very little to indicate that there is a problem unless you read the logs and understand them.

Perhaps the install should fail so that the GUI just displays "Install failed, please only install while attached to a network with a working DHCP server and a working gateway to the internet." And a similar login message if you SSH in.

Preferrably leaving the SD-card in a state that can be used to reinstall successfully if tried again with a working connection to the internet.

An alternative is that the install finish with a fully working install but with nags in the GUI and shell about an update is needed using a working connection to the internet.

Zitat von Adoby

Keep the RPI image and users but create a special RPi-FAQ for them. Politely refer to that FAQ when they ask RPi questions on the forum.

That's a good idea, especially your reference to "polite", but you'd have to have been part of the forum for years to see just a sample of the heinous interactions with R-PI users and others. (While much of the nonsense is focused on the R-PI, it's certainly not limited to it.) I could, quite literally, fill 3 forum pages with references to interactions that are way "over the top" and "sophmoric" in nature.

And I'll give you a prime example direct from this thread: Why say "RTFM" when it's easy enough to just say RTM?

Just because a user has an R-PI and doesn't know Linux, in general, is not a reason to throw decorum out the window. If advice is given and ignored, that's not a trigger to act out. It's simple enough to stop responding.
_____________________________________________________

What is obvious, at least from my point of view, is that support for the R-PI will likely end at OMV4 with the current image. Given the base that's required, I'll acknowledge there are real issues with creating and maintaining an R-PI image. It's a serious challenge. But after listening to same broken record for years, it's equally obvious that there's just no interest. (That is also, right here, for all to see.)

So, rather than endlessly belabor the issue, let's be done with it.