File System not mounted on export

1st Official Post

    After reboot the file system seems to be mounted on a different folder.

    I just setup OpenMediaVault on a RaspberryPi and connected 2 drives via USB.
    I was able to set it all up and get it to work properly. Mounted the NFS share from my laptop and added a bunch of files to the folder. So far so good.


    After a (or more) reboot of the Pi, I still was able to mount the NFS share but now the folder is empty.
    When I check on the Pi itself how the disk is mounted, I see it's set to /srv/dev-disk-by-uuid-[id]/

    The files I added earlier are indeed in this location, and no longer in /export/


    I'm sure I'm overlooking something simple, but can't seem to fix this. What's going on here and what should I do to get this to work again properly?

  • macom

    Approved the thread.
    • Official Post

    Not sure what you did. Here is what I would do

    1. Make sure the two disks have their own power supply and are not powered by the RPi
    2. mount the file systems on the drive from the GUI of OMV (they will be mounted in /srv/dev-disk-by-uuid-....)
    3. in OMV create shared folders pointing at folders on these filesystem
    4. add these folders to the NFS service in OMV and enable NFS service
    5. mount the shared folders from your laptop (I do this using autofs) or use a file manager like Dolphin to access the folders
    Quote from macom

    And please note that OMV5 is end of life. Why don't you use OMV6? Seems to be a fresh install anyway.

    I'm still using OMV5 due to my Raspberry is only PI 3B+ and I read with OMV6 is more of a system hog to be used on RPI3 than the new Pi 4.

    Quote from macom

    Where did you read that?

    As below Sir:

    Under :Recommended Hardware and Considerations for a good use experience

    Raspberry PI's

    (Hereafter referred to as “R-PI's”.) Given the current market for SBC's, the majority of SBC users will likely be owners of R-PI's.

    Openmediavault runs well on the R-PI 4. While openmediavault will run on an R-PI model 2B and the various models of the R-PI 3, it is not recommended. Performance is poor. What exactly does “poor performance” mean? In this context, if the R-PI's CPU is running at 100%, openmediavault my not show up on the local network and / or network shares may not open. This may give the false impression that there's a software or permissions problem. In other instances, the WEB GUI login page may not respond.

    These issues may appear to be software related, but that's not always the case. Older R-PI's are very easily over stressed and, during periods where the CPU is running at 100%, they may not respond to external input. With this performance limitation in mind, earlier versions of the R-PI (2B and 3X models) should be used only as a basic file server for 1 or 2 user home environments, where multitasking is less likely. If running automated tasks, it's best to schedule them to run in the early morning hours when user access would not be affected.

    Quote from macom

    Ok, but this does not mention that OMV6 runs worse than OMV5 on an RPi. I have an HC2 (also SBC) and did not notice any difference between OMV5 and OMV6.

    I would run OMV6 on the RPi.

    The part where it says below got me worried to upgrade. I am currently using 5.6.21-1 V5. What is the best way to upgrade my situation? Also, what version is your RPI?


    if the R-PI's CPU is running at 100%, openmediavault my not show up on the local network and / or network shares may not open

    • Official Post
    Quote from Jefok

    What is the best way to upgrade my situation?

    If you have not done a lot of configuration, I would do a fresh install.


    I do not have an RPi. I have an Odroid HC2 and an amd64.

    Quote from macom

    If you have not done a lot of configuration, I would do a fresh install.


    I do not have an RPi. I have an Odroid HC2 and an amd64.

    Im just running basic SMB file share over the network for all my devices. I don't run Docker or any other stuff right now as I'm still a newbie.


    would sudo omv-upgrade take me to 6+ versions if I run under root in my RPI?

    Also, would I have to reformat the hard drive to suit 6v? or will my current formatted hard drive that's Omv's 5v format (NTFS), be plug and play on the 6v from 5v?

    • Official Post
    Quote from Jefok

    would sudo omv-upgrade take me to 6+ versions if I run under root in my RPI?

    These are the suggested steps for an upgrade. But it is a lot of stress for the SD card


    Post
    RE: Is there a guide to in place upgrade?
    Contributions wanted:
    1. Backup the OS drive (this is allways a good idea, not only for upgrades)
    2. Make sure, you have enough free space on your os drive
    3. Check any installed plugins if they have been ported to OMV6
      If you are using plugins which have not been / will not be ported, get rid of the plugins except unionfs / mergefolderfs. These two will automatically be be converted to the newer mergerfs plugin
      (Many plugins can be replaced by docker containers. Do this before upgrading)
    4. If you installed
    …
    Zoki



    Quote from Jefok

    Also, would I have to reformat the hard drive to suit 6v? or will my current formatted hard drive that's Omv's 5v format (NTFS), be plug and play on the 6v from 5v?

    No. However it is strongly suggested to use a native linux file system like ext4 for permanent storage. NTFS is only meant for import/export of data.

    Quote from macom

    These are the suggested steps for an upgrade. But it is a lot of stress for the SD card


    Post
    RE: Is there a guide to in place upgrade?
    Contributions wanted:
    1. Backup the OS drive (this is allways a good idea, not only for upgrades)
    2. Make sure, you have enough free space on your os drive
    3. Check any installed plugins if they have been ported to OMV6
      If you are using plugins which have not been / will not be ported, get rid of the plugins except unionfs / mergefolderfs. These two will automatically be be converted to the newer mergerfs plugin
      (Many plugins can be replaced by docker containers. Do this before upgrading)
    4. If you installed
    …
    Zoki



    No. However it is strongly suggested to use a native linux file system like ext4 for permanent storage. NTFS is only meant for import/export of data.

    Ok Thank You, I will use that guide before installation.

    I can create a new USB image of 6V and run that off the Pi and just store the USB with 5V as a backup if things go wrong.

    My concern is would my SSD with the current file system that has all my data be plug-and-play or will I need to reconfigure to read the drives again? (eg, Shares folder permissions etc)

    • Official Post

    If you do a fresh installation, then you have to redo the configuration. Mount the filesystem, create shared folders pointing at the existing folders on the drive, add the folders to smb service, create user, give user permissions on the shared folders etc.


    If you do an omv-release-upgrade and everything goes well, the configuration will be there.

    • Official Post
    Quote from Jefok

    My concern is would my SSD with the current file system that has all my data be plug-and-play or will I need to reconfigure to read the drives again? (eg, Shares folder permissions etc)

    In any case, I would consider reformatting that disk to a format compatible with Linux.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login