An OMV server running OMV 3 (Erasmus) may experience a loss of wifi (wlan0) due to drivers being removed from the backports package.

Run the code below to download the broadcom wifi controller drivers and re-enable wifi (wlan0) (from OMV forums)

wget https://github.com/RPi-Distro/firmware-nonfree/raw/master/brcm80211/brcm/brcmfmac43430-sdio.bin
wget https://github.com/RPi-Distro/firmware-nonfree/raw/master/brcm80211/brcm/brcmfmac43430-sdio.txt
sudo mv brcmfmac43430-sdio* /lib/firmware/brcm/
sudo reboot

 

Consequently, this is also a good time to learn about wireless network troubleshooting tools:

ifconfig -a
iwconfig
sudo iwlist wlan0 scan
sudo ifdown wlan0 && sudo ifup -v wlan0

If any of these show an error or do not show the wlan0 interface, you may have a driver issue, such as the one with OMV and the RPi3 backport repository.

References: 1, 2, 3, 4

 

I previously created a RPi3 OMV server to share some pictures and movies across the network. But I configured the underlying Debian  to check for updates outside of OMV, which means it probably upgraded to Debian 8 Jessie instead of staying with Debian 7 Wheezy. Since OMV was based on version 2 (Stoneburner), it crashed everything.

So I started again. This time, I wanted to be sure I didn’t crash everything, so I installed OMV 3 (Erasmus) on Raspbian Lite (Jessie). What a headache! OMV reconfigures a bunch of things I didn’t want it to, especially sshd configs and wifi configs.

The first issue was that I couldn’t login through ssh. To fix that, add your user to the root or ssh group in the OMV web interface. You also want to check the sshd config to make sure that root can’t login and make other security changes.

Then, I rebooted the Pi and it was gone from my network. I couldn’t understand why, as I was working remotely, but when I got home, I saw it was still running and could bring up a locally connected display. It just wasn’t connecting to the internet. Trying ifconfig -a will give you an idea if it is connected or not.

To fix that, I had to go into the /etc/network/interface file and add back a bunch of wifi lines:

allow-hotplug wlan0
auto wlan0
iface wlan0 inet dhcp
    wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

Now it’s working…again…I hope.

Servers@GeorgeLiu.me

Did you ever get this code while using FreeFileSync: “Windows Error Code 1314: A required privilege is not held by the client.“?

I did. Many times. I thought it was a Linux file permission error on my Raspberry Pi 3 OMV setup, and I chmodded and chowned an unbelievable amount of times, to no effect. And then, while setting up a new temporary NAS on a Raspberry Pi 3, I found a new page: “Windows Error Code 1314: A required privilege is not held by the client.

If you don't really need to copy file system permissions, 
turn them off in global settings.

I solved the problem!