Kralizec - can't create shared folder, no volume?

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • Hello all,

      After all your help, it worked, thanks to subzero and David.

      But then, all of sudden, all the changes to the settings were gone and I'm back to start.

      Devices not listing again. I found out that config.xml was somehow modified and lost the entire mntent section.

      I've rebuild it (according to the instructions above) but nah, not working.

      What the heck??
    • Hello again, subzero!

      Before I saw your post, I had edited the /etc/openmediavault/config.xml and added the following:

      Source Code

      1. <fstab>
      2. <!--
      3. <mntent>
      4. <uuid>b3343e94-52f3-4c18-9060-7ce0c436eb1b</uui$
      5. <fsname>b3343e94-52f3-4c18-9060-7ce0c436eb1b</f$
      6. <dir>/media/b3343e94-52f3-4c18-9060-7ce0c436eb1$
      7. <type>ext4</type>
      8. <opts>defaults,nofail,acl,user_xattr,noexec</op$
      9. <freq>0</freq>
      10. <passno>2</passno>
      11. <hidden>0</hidden>
      12. </mntent>
      13. -->
      14. </fstab>
      Display All


      And it did the trick (I mean, the /dev/sda2 is mounting on boot device). So I cannot tell if your new instructions changed something.

      At this moment, I cannot unmount via webgui -when I try to do that, I get this error:

      Source Code

      1. Error #3003:
      2. exception 'OMVException' with message 'Failed to get configuration (xpath=//system/fstab/mntent[dir='/media/b3343e94-52f3-4c18-9060-7ce0c436eb1b'])' in /usr/share/openmediavault/engined/rpc/filesystemmgmt.inc:958
      3. Stack trace:
      4. #0 [internal function]: OMVRpcServiceFileSystemMgmt->umount(Array, Array)
      5. #1 /usr/share/php/openmediavault/rpcservice.inc(125): call_user_func_array(Array, Array)
      6. #2 /usr/share/php/openmediavault/rpc.inc(79): OMVRpcServiceAbstract->callMethod('umount', Array, Array)
      7. #3 /usr/sbin/omv-engined(500): OMVRpc::exec('FileSystemMgmt', 'umount', Array, Array, 1)
      8. #4 {main}


      My main issue at this moment is, when I try to add a shared folder for instance, I have no device listed. It shows blank.

      David got it working today, but all changes just disappeared some moments later (and later on, config.xml went all blank, luckily I had a backup).

      Then, my questions are:
      a) How can I make the /dev/sda2 show up again on 'devices'?, and
      b) Why the hell is it losing the configuration?

      Thanks again!
    • Hello again!

      Right, here's my actual fstab:

      Source Code

      1. # UNCONFIGURED FSTAB FOR BASE SYSTEM
      2. tmpfs /tmp tmpfs defaults 0 0
      3. UUID=b3343e94-52f3-4c18-9060-7ce0c436eb1b /media/b3343e94-52f3-4c18-9060-7ce0c436eb1b ext4 defaults,nofail,acl,user_xattr,noexec 0 2
      4. #/dev/sda2 /mnt/Data ext4 defaults 0 0
      5. # >>> [openmediavault]
      6. # <<< [openmediavault]


      config.xml (mntent section):

      Source Code

      1. </storage>
      2. <fstab>
      3. <!--
      4. -->
      5. </fstab>
      6. <shares>
      7. <!--
      8. -->
      9. </shares>


      Then I try to unmount /dev/sda2 via webgui and get this:

      Source Code

      1. Error #3003:
      2. exception 'OMVException' with message 'Failed to get configuration (xpath=//system/fstab/mntent[dir='/media/b3343e94-52f3-4c18-9060-7ce0c436eb1b'])' in /usr/share/openmediavault/engined/rpc/filesystemmgmt.inc:958
      3. Stack trace:
      4. #0 [internal function]: OMVRpcServiceFileSystemMgmt->umount(Array, Array)
      5. #1 /usr/share/php/openmediavault/rpcservice.inc(125): call_user_func_array(Array, Array)
      6. #2 /usr/share/php/openmediavault/rpc.inc(79): OMVRpcServiceAbstract->callMethod('umount', Array, Array)
      7. #3 /usr/sbin/omv-engined(500): OMVRpc::exec('FileSystemMgmt', 'umount', Array, Array, 1)
      8. #4 {main}


      dmesg | tail after trying to unmount the partition via webgui: (MAC address hidden)

      Source Code

      1. [ 16.565173] EXT4-fs (sda1): re-mounted. Opts: (null)
      2. [ 23.518545] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: user_xattr
      3. [ 24.998405] IPv6: ADDRCONF(NETDEV_UP): lo: link is not ready
      4. [ 27.581603] eth0: device MAC address xx:xx:xx:xx:xx:xx
      5. [ 29.580277] libphy: stmmac-0:00 - Link is Up - 1000/Full
      6. [ 29.597949] RPC: Registered named UNIX socket transport module.
      7. [ 29.604001] RPC: Registered udp transport module.
      8. [ 29.608696] RPC: Registered tcp transport module.
      9. [ 29.613442] RPC: Registered tcp NFSv4.1 backchannel transport module.
      10. [ 29.808225] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).


      What now? :(
    • If I remember correctly, there also is no support for BTRFS Raid, yet, is it?

      Greetings
      David
      "Well... lately this forum has become support for everything except omv" [...] "And is like someone is banning Google from their browsers"

      Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.


      Upload Logfile via WebGUI/CLI
      #openmediavault on freenode IRC | German & English | GMT+1
      Absolutely no Support via PM!

      I host parts of the omv-extras.org Repository, the OpenMediaVault Live Demo and the pre-built PXE Images. If you want you can take part and help covering the costs by having a look at my profile page.
    • Not in omv to assemble raids in webui. It can be done in cli and on the fly with fs mounted.
      The fstab just needs the first uuid of the raid to mount. Also omv will repeat the fs display as many drives as the raid has. This I guess has to be fixed in the future.
      New wiki
      chat support at #openmediavault@freenode IRC | Spanish & English | GMT+10
      telegram.me/openmediavault broadcast channel
      openmediavault discord server
    • I cannot create shared folder also, when adding shares i cannot select a volume.
      [Blocked Image: http://forums.openmediavault.org/index.php/Attachment/4551-qw2-JPG/]

      [Blocked Image: http://forums.openmediavault.org/index.php/Attachment/4550-qwerttyyuu-JPG/]
      [Blocked Image: http://forums.openmediavault.org/index.php/Attachment/4552-qw3-JPG/]

      I tried to unmount file system as in suggestion but it is inactive.
      Images
      • qwerttyyuu.JPG

        119.09 kB, 1,460×962, viewed 903 times
      • qw2.JPG

        24.4 kB, 931×121, viewed 891 times
      • qw3.JPG

        77.56 kB, 645×400, viewed 916 times

      The post was edited 1 time, last by eXPlosion ().

    • That looks like the OS disk. The os disk cannot be used to create shared folders. You can boot systemrescuecd and run gparted to resize the OS partition to something smaller and use the secondary partition for data.
      Dont complain that's how Omv was designed and it has been always been like that.
      New wiki
      chat support at #openmediavault@freenode IRC | Spanish & English | GMT+10
      telegram.me/openmediavault broadcast channel
      openmediavault discord server
    • subzero79 wrote:

      That looks like the OS disk. The os disk cannot be used to create shared folders. You can boot systemrescuecd and run gparted to resize the OS partition to something smaller and use the secondary partition for data.
      Dont complain that's how Omv was…

      Hi subzero I have the same issue, but mine is not system disk, mine is a 8gb flash disc. I have wd 80gb hdd as system drive and 8gb usb. What can I do to make interface see my usb disc as a volume?
      Thank you :)
    • subzero79 wrote:

      is the 8gb flash already formatted ? If so what format ?

      post here fdisk -l

      wity the disk plugged

      Ye it has already formatted ext4

      Source Code

      1. ​Disk /dev/sda: 80.0 GB, 80026361856 bytes
      2. 255 heads, 63 sectors/track, 9729 cylinders, total 156301488 sectors
      3. Units = sectors of 1 * 512 = 512 bytes
      4. Sector size (logical/physical): 512 bytes / 512 bytes
      5. I/O size (minimum/optimal): 512 bytes / 512 bytes
      6. Disk identifier: 0x000eb416
      7. Device Boot Start End Blocks Id System
      8. /dev/sda1 * 2048 150046719 75022336 83 Linux
      9. /dev/sda2 150048766 156301311 3126273 5 Extended
      10. /dev/sda5 150048768 156301311 3126272 82 Linux swap / Solaris
      11. WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.
      12. Disk /dev/sdb: 7759 MB, 7759462400 bytes
      13. 181 heads, 44 sectors/track, 1902 cylinders, total 15155200 sectors
      14. Units = sectors of 1 * 512 = 512 bytes
      15. Sector size (logical/physical): 512 bytes / 512 bytes
      16. I/O size (minimum/optimal): 512 bytes / 512 bytes
      17. Disk identifier: 0x00000000
      18. Device Boot Start End Blocks Id System
      19. /dev/sdb1 1 15155199 7577599+ ee GPT
      Display All
    • Users Online 1

      1 Guest