mount usb hdd raspberry pi NAS

    • OMV 3.x
    • Resolved
    • mount usb hdd raspberry pi NAS

      I have installed OMV version 3.0.59 on a raspberry pi 3.


      My intent is to replace my existing NAS with the pi and 2 external usb hdd. I have 2 usb hdd (called drive 1 & drive 2) attached via a powered usb hub . All works fine in that I can view the drives create NFS shares & access from local network.

      I have noticed when I reboot sometimes Drive 1 is /dev/sda and other times it is /dev/sdb.

      Would it be better to mount the drives in fstab using their UID ?

      cheers
    • Thats a anoying problem and using the uid in fstab would indeed solve the problem. But it bypassed the omv configuration. If I'm not mistaken omv stores your drives also in some kind of a xml file to be aware of them. This might give trouble later on.

      I've only recently migrated from debian to omv so not sure how to fix this. You could search for "openmediavault mount usb drive UID". This probably would give a similar exeriences and poblems. Kinda interested myself since my remote backup is using a pi 3 to that soon needs a second drive.
    • cork22 wrote:

      Would it be better to mount the drives in fstab using their UID ?
      OMV always uses the UUID in fstab. Can you post your fstab?
      omv 4.1.13 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • Ok here's my fstab and I see they are listed here

      Source Code

      1. GNU nano 2.2.6 File: /etc/fstab
      2. proc /proc proc defaults 0 0
      3. /dev/mmcblk0p1 /boot vfat defaults 0 2
      4. /dev/mmcblk0p2 / ext4 defaults,noatime,nodiratime 0 1
      5. # >>> [openmediavault]
      6. UUID=fa36508a-b3c4-4499-b30a-711dd5994225 /media/fa36508a-b3c4-4499-b30a-711dd5994225 ext4 defaults,nofail,acl,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfm$
      7. UUID=56fd45ed-fb50-4afa-8642-341e0c7990b8 /media/56fd45ed-fb50-4afa-8642-341e0c7990b8 ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vf$
      8. UUID=d84e7169-ccc5-4898-82d6-a67822503b5e /media/d84e7169-ccc5-4898-82d6-a67822503b5e ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vf$
      9. /media/d84e7169-ccc5-4898-82d6-a67822503b5e/backup /export/backup none bind,nofail 0 0
      10. # <<< [openmediavault]
      11. # a swapfile is not a swap partition, no line here
      12. # use dphys-swapfile swap[on|off] for that
      Display All
      I can see both disks being mounted here the UID ending "b5e" is my WD Passport USB which is currently on /dev/sda this is where I want it to stay.
      The other usb drive on /dev/sdb UID ends "0b8"
      Is it jusst a question of moving the position in fstab to ensure they keep the same dev ?
    • cork22 wrote:

      Is it jusst a question of moving the position in fstab to ensure they keep the same dev ?
      No. Position doesn't mean anything. Everything looks fine and drive letters changing shouldn't affect your fstab.
      omv 4.1.13 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • Shouldn't cause a problem. Your fstab (and all OMV) use UUIDs. Those don't change unless your re-format the drive.
      omv 4.1.13 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • I have the same issue.

      latest image just downloaded and installed and on my zeroW and pi3 is gives an error after start and goes back to CLI login.

      Oh and just checked root: I can login but not GUI.

      I did see some faults during initial startup but I could not see what was not loading correctly.