Hi,
I'm running omv 5 on an old taspberry pi 2B but I think this deosn't matter for my question.
I have a remote mount SMB/CIFS that mount router samba share on my OMV.
I was out when power got lost due maintenance and when it was back OMV started up fine with also all my docker containers.
What was not working was the remout mount: the "local" folder was empty. I executed 'sudo mount -a' and all was back to normal: my local folder contained files present in the router share.
How can I delay OMV remote mount until the remote SMB is available?
Thread
Is there a guide to in place upgrade?
Hi all
Reading bits and pieces in different threads regarding the CLI upgrade path from 5 to 6, but wondered if there's a thread that covers the steps in one place that I'm struggling to find?
My basic understanding is:
1. Backup OS drive
2. Check any used plugins have been ported to OMV6 and if they haven't install via Docker instead
3. Temporarily remove data drives
4. Disable running services
5. Go in via CLI (Putty in my case) and run the couple of update commands (when I find them again!)
6. Wait
…
Reading bits and pieces in different threads regarding the CLI upgrade path from 5 to 6, but wondered if there's a thread that covers the steps in one place that I'm struggling to find?
My basic understanding is:
1. Backup OS drive
2. Check any used plugins have been ported to OMV6 and if they haven't install via Docker instead
3. Temporarily remove data drives
4. Disable running services
5. Go in via CLI (Putty in my case) and run the couple of update commands (when I find them again!)
6. Wait
…