OMV is open source and free of charge—essentially a gift. Yet some people expect this gift to be handed to them on a silver platter. :-((( You probably think everything worked perfectly for me right from the start when I began using it four years ago. It takes a bit of perseverance and patience. The documentation is good, but you do have to learn the basics of networking and Debian yourself; the OMV documentation can't do that part for you. OMV 8 is based on Debian Trixie. If you're using a Raspberry Pi, you should use RaspiOS, which is also based on Debian Trixie. Perhaps you should spend some time getting familiar with RaspiOS/Debian. The fact that your Windows PC doesn't recognize the NAS could also be due to Windows 11 settings or your router configuration. After all, it works very well for a great many people, myself included. Maybe a pre-built NAS would be the best option for you.
I have an unusable OMV, for reasons I don't understand. So just about anything is worth trying, even if from unofficial guides.
If you were able to point me to where I might find information which my help me to get my project functioning, I would appreciate it.
I think it's particularly important not to rely on unofficial sources when you're attempting to troubleshoot a system, as you risk inadvertently making things worse due to bad advice.
With that said, I take it your Windows/Mac computers still don't see any shares from OMV? Or are you having other problems as well?
You've already received a wealth of information and helpful steps in this thread. Help us to help you - by detailing what you've tried so far (step by step) and any errors or unexpected behaviors you see. After all, I don't even know if my and chente's guides to create and share a folder did the trick for you or not.
Another hint if you struggle with W11 SMB shares: Try a simple FTP access.
It's a different protocol and gives you a lighter way to understand shares, user, rights, etc.
PilotPete
Building OMV8 on an R-PI -> Here.
Once the build is complete there's a link in the R-PI build guide that continues to the appropriate location in the -> New User Guide.
If you create your shares in accordance with Creating a Network Share in the New Users Guide, from the server's perspective (OMV), permissions will be open to any user / PC client on the local LAN.
However, the PC Client must be configured to accept local networking connections. That means your windows 11 firewall / network security needs to see the local network as a private network, NOT as a public network. (A Public network enforces higher security.) This can be configured in Control Panel, Network and Sharing Center, Advanced Network Settings.
If you have trouble along these lines, where to go, what to do, settings, etc., might I recommend -> DuckDuckgo's AI. This particular AI is private and does not require a login. Ask it your questions in plain English and it will guide you to the right Client settings.
I admit I have trouble in getting my head around how some terms are supposed to be interpreted in respect of brief instructions, but it doesn't stop me trying to learn as I go along.
Regarding the doc's, I wrote a number of them. In the writing, some PC knowledge had be assumed. (Things like, "connect a power cord, keyboard," etc., were out of the question.) Excessive detail could have easily derailed the overall effort. The intent was to provide what was necessary, and no more, for the broadest cross section of likely OMV users, to get them started. As it was, in the first iteration, the User Guide was some 87 standard pages. Even among absolute beginners, encyclopedic style volumes would not be read. (On the unabridged side of writing, "TLDR" also applies.)
I am no stranger to getting W11 to see their peers. But my Mac OS laptop cant see the NAS either.
In that case, I'll assume you know something about permissions. Again, if shares are configured as laid out in the Guide, permissions should not be a problem. However, OEM versions of Windows can be locked down by the PC OEM. To "help us" a number of OEM's only like to allow web browser connections.
________________
Note that routers, other local network security devices / appliances and local DNS could be an issue.
When it comes to security, SMB uses specific port numbers to establish client server connections.
TCP 445 - SMB over TCP
TCP 139 - SMB over NetBIOS
________________
Some users, with Linux and Mac clients prefer NFS. I've looked at NFS and decided not to cover it. It's another animal altogether that has varying issues among the distro's of Linux and versions of Mac OS. (Adding to that, I don't have a Mac.)
If you start over, using the R-PI build document then proceed to the User Guide, with the link provided in the build document, there's a very good chance that all will work. Try not to stray from the instructions.
First answer in this thread was already a link to omv-extras and many more did so. I don't get why only now it is being considered...
It is not "somewhere else" but this thread and you don't get rubbished but corrected in a very straightforward manner because the statement is absurdly false. What you write is not in the document that people linked for you to work through. You are using the old document for OMV7 and not OMV8. Please just follow the link that people sent you multiple times and for your first install do what is being written. You will get a functioning system! The guides are brilliant and easy to follow.
Quote
Reading further in the installation guide, is there any specific reason to use putty rather than just establishing an SSH session direct from the command prompt?
Setting aside that the process and the screen shots use PuTTY, you can use anything SSH client you want, provided that all install steps are followed.
Debian Trixie is not, currently, supported by OMV7. Use Debian Bookworm, in accordance with the install procedure following.That is for a SBC such as Rpi 4 that I plan on using.
This is true.
OMV7 is permanently married to Debian Bookworm. If you install Raspberry PI OS lite, Bookworm, you'll get OMV7. (I believe this may still be valid. However, note that SBC's are officially supported in the latest version which is, currently, OMV8.) OMV8, the current version, is permanently married to Debian Trixie.
The Raspberry PI OS Lite distro you start with will determine the version of OMV that is installed.
Gday erbenzaeler. I couldn't find any reference in this thread to your name. But if I did read it, I would have moved on, as I don't know what omv-extras are, or why I might need them. So I would have moved on. What are "omv-extras" anyway?
The third party plugin repo that I started that has almost 40 additional plugins including they very popular compose (docker), mergersfs, kvm, and zfs plugins.
The command line is:
wget -O - https://github.com/OpenMediaVault-Plugin-Developers/installScript/raw/master/preinstall | sudo bash
Got a wget: missing URL error. In the previous attempt No1 it must have worked because OMV did install albeit it with some erors.
wget requires a network connection. "Missing" can happen for a number of reasons; net congestion, busy, etc. Try it again.
Just do as the document says. That second command is different from the first.
first: "preinstall"
second: "install"
Don’t have an account yet? Register yourself now and be a part of our community!
