Problems with filesystems and disks after moving from RAID to MHDDFS/AUS

    • OMV 1.0
    • Problems with filesystems and disks after moving from RAID to MHDDFS/AUS

      Hey guys, so been a long time OMV user and trying to get my OMV GUI back up and working correctly but having some problems and hoping someone could help me out.

      I originally was using a RAID5 setup for my drives, until after having a few RAID issues I decided to move to using mhddfs instead as i'm not that worried about the data, and wanted the additional space available when using an mhddfs setup.

      So I switched over to mhddfs about a year or so ago (was before OMV supported mhddfs/aus), got everything setup and working correctly without any issues. I had my own mhddfs entry added in the /etc/fstab file, everything works just fine.

      Problem is when I try to go into my OMV admin gui to setup the mhddfs (after unmounting) there aren't any available pools to add to a new mhddfs/aus setup. My drives show up just fine in the Physical Drives section, as well as under filesytems, but I can't for the life of me figure out how or what I need to do to be able to setup my mhddfs configuration in OMV.

      I uploaded diagnostic information, the ID is DhciuvRE (OMV 1.19)

      I am unable to setup any new shared folders, mhddfs/aus, or really anything in regards to drives or filesystems. The "Volume", "Drive", and "Pool" dropdowns in the configurations are empty and i'm hoping someone can help me figure this out so I can go back to using the OMV interface for managing everything.

      Thanks guys!!
    • Thanks for the reply, the fstab I believe should be in that report but i'll post it here as well. Tried to send again, here's the error I get when trying to send it:

      your log ID is: 9GiWDdeU, please refer to this log ID in your posts.

      Source Code

      1. Creating sysinfo file...
      2. Creating config.xml file with passwords and SSL certs removed...
      3. Received message too long 1416128883


      I'll send you the file in a private message just in case it didn't upload

      Here's

      Source Code

      1. ​omv-showkey mntent


      Source Code

      1. <mntent>
      2. <uuid>xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx</uuid>
      3. <fsname>xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx|xxxx-xxxx|/dev/xxx</fsname>
      4. <dir>/xxx/yyy/zzz</dir>
      5. <type>ext2|ext3|ext4|xfs|jfs|iso9660|udf</type>
      6. <opts></opts>
      7. <freq>0</freq>
      8. <passno>0|1|2</passno>
      9. </mntent>


      Here's /etc/fstab, there are a few commented out as that was an old drive, and just so I know where each disk is in the actual server:

      Source Code

      1. # /etc/fstab: static file system information.
      2. #
      3. # Use 'blkid' to print the universally unique identifier for a
      4. # device; this may be used with UUID= as a more robust way to name devices
      5. # that works even if disks are added and removed. See fstab(5).
      6. #
      7. # <file system> <mount point> <type> <options> <dump> <pass>
      8. proc /proc proc defaults 0 0
      9. #
      10. # / was on /dev/sda1 during installation
      11. #UUID=218c8697-ae7a-4836-872f-1ad10d940367 / ext4 noatime,discard,errors=remount-ro 0 1
      12. #
      13. #/dev/disk/by-id/scsi-SATA_SanDisk_SDSSDP0131696402407-part1 / ext4 noatime,discard,errors=remount-ro 0 1
      14. /dev/disk/by-id/ata-TS128GSSD370_C207810183-part1 / ext4 noatime,discard,errors=remount-ro 0 1
      15. #
      16. # swap was on /dev/sda5 during installation
      17. #UUID=388e4454-8949-450e-bea9-46811d08c4b6 none swap sw 0 0
      18. #
      19. #/dev/disk/by-id/scsi-SATA_SanDisk_SDSSDP0131696402407-part5 none swap sw 0 0
      20. /dev/disk/by-id/scsi-SATA_TS128GSSD370_C207810183-part5 none swap sw 0 0
      21. #
      22. #/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0
      23. tmpfs /tmp tmpfs defaults 0 0
      24. #
      25. ######################
      26. # ROW 1
      27. ######################
      28. # START DOWNLOAD DRIVE -- This drive below is used for downloads and is set for ext4 filesystem, not to be used with MHDDFS
      29. /dev/disk/by-id/scsi-SATA_WDC_WD25EZRS-11_WD-WCAWZ0636047-part1 /disks/r1/d1 ext4 defaults 0 2
      30. # END DOWNLOAD DRIVE
      31. /dev/disk/by-id/scsi-SATA_WDC_WD25EZRS-11_WD-WMAWZ0164944 /disks/r1/d2 xfs defaults 0 2
      32. /dev/disk/by-id/scsi-SATA_WDC_WD20EARX-00_WD-WCAZAD530422 /disks/r1/d3 xfs defaults 0 2
      33. /dev/disk/by-id/scsi-SATA_SAMSUNG_HD204UIS2H7J9EZC12920 /disks/r1/d4 xfs defaults 0 2
      34. /dev/disk/by-id/scsi-SATA_SAMSUNG_HD204UIS2H7J9EZC12921 /disks/r1/d5 xfs defaults 0 2
      35. ######################
      36. # ROW 2
      37. ######################
      38. /dev/disk/by-id/scsi-SATA_ST4000DM000-1F2_Z300CG63 /disks/r2/d1 xfs defaults 0 2
      39. /dev/disk/by-id/scsi-SATA_ST4000DM000-1F2_Z302AFRL /disks/r2/d2 xfs defaults 0 2
      40. #/dev/disk/by-id/ /disks/r2/d3 xfs defaults 0 2
      41. /dev/disk/by-id/scsi-SATA_ST3000DM001-1ER_Z5007BME /disks/r2/d4 xfs defaults 0 2
      42. /dev/disk/by-id/scsi-SATA_ST3000DM001-1ER_Z500777H /disks/r2/d5 xfs defaults 0 2
      43. ######################
      44. # ROW 3
      45. ######################
      46. # Furthest from PS
      47. ######################
      48. #/dev/disk/by-id/W1E7TGG1 /disks/r3/d1 xfs defaults 0 2
      49. #/dev/disk/by-id/S2H7J9EC300240 /disks/r3/d2 xfs defaults 0 2
      50. #/dev/disk/by-id/W1E0EY7F /disks/r3/d3 xfs defaults 0 2
      51. #/dev/disk/by-id/Z1E28L83 /disks/r3/d4 xfs defaults 0 2
      52. #/dev/disk/by-id/Z1E3QRR8 /disks/r3/d5 xfs defaults 0 2
      53. #######################
      54. mhddfs#/disks/r1/d2,/disks/r1/d3,/disks/r1/d4,/disks/r1/d5,/disks/r2/d1,/disks/r2/d2,/disks/r2/d4,/disks/r2/d5 /nfm fuse defaults,allow_other,nonempty,mlimit=100G,logfile=/var/log/mhddfs.log 0 0
      Display All


      Thanks!!
    • The send report is not working properly.

      You have an extended custom fstab, omv only works with fstab entries created by omv and registered in config.xml. You have nothing there created by omv

      You should delete all fs or comment the entries there that you want to make mhdfs, or if you want delete all entries except for rootfs and swap. Then reboot and start mounting filesystems with the webui, once there you should be able to configure a pool.

      fstab entries created by omv are enclosed in a <openmediavault> tab, you'll see later when you start mounting with omv
      New wiki
      chat support at #openmediavault@freenode IRC | Spanish & English | GMT+10
      telegram.me/openmediavault broadcast channel
      openmediavault discord server