Posts by pierric

Quote from ryecoaaron

I guess the guide should say (and maybe it does - haven't read it lately) "After installing OMV, don't use the pi user for anything at all especially samba. create new users" When I wrote the install script, I wanted to delete the pi user but too many people complained. People should not use the pi user after omv install though.

Thanks for your reply, I see where you're coming from. It doesn't help that the Raspberry flashing tool offers the option to customise that default user, as part of the standard install, so in my system it's not `pi` but the name of the friend I prepared the install for. Which made it all the more tempting to use as a samba user!

I don't think the current docs have a sentence like the one you wrote there - maybe I missed it, but it doesn't ring a bell. It would be useful to add, somewhere close to the installation steps so it catches everyone's attention.

Hi !

Sorry if I explained incorrectly. I'll try to reply to both.

Quote from ryecoaaron

The guide isn't telling you to create a user before installing OMV. We can't write something for everything a user might do before installing OMV. That is why we tell people to install OMV first.

Indeed, but I did not create a user before installing OMV. When flashing raspberry pi OS using the official raspberry pi flashing tool, a user is created by default, with sudo privileges; root doesn't even get a password set up and cannot log in. So, that user is pretty much the only way to use the Pi, and OMV gets installed by that user, using sudo (the instructions correctly reflect this). Therefore there's no extra step taken. In fact, I'm fairly confident that I literally flashed the OS, logged in via SSH, and immediately updated the system with apt, called the preinstall, rebooted, and called the main install.

That single user that is set up by the raspberry flashing process is then automatically visible in the list of users in OMV, without any action required. BUT it's not obvious to new users like me that for this particular user, I'll need to run smbpasswd manually because that's the user through which I followed the instructions.

Quote from crashtest

1. Flash an SD-card with Rasp. PI OS.
(Then)
2. Install users of your choice, configure WiFI, add additional non-OMV packages, etc., etc.
3. Install OMV.

Where #2 is concerned, it is IMPOSSIBLE to to predict or anticipate what users many do, at any point, before, during, or after:

As per above, step 2 for me was basically nothing. I flashed the os, plugged the device in (incl. ethernet cable, so no wifi setup even), logged in via ssh and moved on with step 3.

Quote from crashtest

It's relatively easy to provide samba access to existing Windows users on the LAN.

Fixing the issue was trivial once it was clear what was happening. However I did struggle in understanding it was happening, from the lack of warning in those raspberry-specific instructions, and the lack of particular warnings in the UI about this user being "somewhat different" because not created through the UI, but by the raspberry install + OMV install together.

Hope that clarifies!

Hi,

I just wanted to bounce on this message, as it gave me the explanation for what I thought was a bug.

I recently installed OMV on a raspberry pi 5 following the instructions at https://wiki.omv-extras.org/do…i_os_updates_and_upgrades .

I struggled for quite a while, not understanding why samba authentication was failing. Until I created a new user and it worked fine. As it happens, this method of installation adds OMV onto an existing raspberry pi OS installation, so the default user is picked up by OMV and can get folders shared without any additional user setup in the UI... BUT technically, it IS created before Samba is running; it's even created before OMV is even installed. So that might explain why I had to run `smbpasswd -a username` for samba to start working for that user.

I would suggest one of 2 improvements:

- make it so that the default user gets a smbpasswd configured automatically during this installation procedure

- if not possible for technical reasons, document this clearly, at least in the page linked above; ideally also inside the UI itself, to let people know "this user was created before OMV was installed; please reset the password if you need this user to have access to SMB shares" - something along those lines.

Hope that makes sense, sorry if not!

P.