Issues with Mount a WD 4tb My Passport HDD and with install PlugIns.

    • OMV 5.x (beta)
    • Resolved
    • Issues with Mount a HDD and with install PlugIns.

      Hi Team!

      I'm playing with OMV 5.0.5 ona Beelink MiniPC (Nuk type) with 8gb of RAM and booting the system from a USB 3.0 32Gb Stick, also, with an internal 2.5HDD and 2 external thru USB 3.0.
      I have some issues and I had to reinstall all 3 or 4 times. (I will start the 5th early)

      Now, All seems to be fine, I can access to the shared folders and also I installed a Portainer with Transmission without problems.
      But (the fatal "But") when I plug the second HDD via USB, and I tried to mount, the system returned an ERROR:

      Difference-File

      1. Error #0:
      2. OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-salt deploy run fstab 2>&1' with exit code '1': /usr/lib/python3/dist-packages/salt/modules/file.py:32: DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated, and in 3.8 it will stop working
      3. from collections import Iterable, Mapping
      4. /usr/lib/python3/dist-packages/salt/utils/decorators/signature.py:31: DeprecationWarning: `formatargspec` is deprecated since Python 3.5. Use `signature` and the `Signature` object directly
      5. *salt.utils.args.get_function_argspec(original_function)
      6. debian:
      7. ----------
      8. ID: create_filesystem_mountpoint_670e859a-5ff7-46cd-9871-5d12b5bce71a
      9. Function: file.accumulated
      10. Result: True
      11. Comment: Accumulator create_filesystem_mountpoint_670e859a-5ff7-46cd-9871-5d12b5bce71a for file /etc/fstab was charged by text
      12. Started: 15:56:34.324991
      13. Duration: 1.336 ms
      14. Changes:
      15. ----------
      16. ID: create_filesystem_mountpoint_7c989ddd-1fbd-4824-a2ec-2d00f49d8c46
      17. Function: file.accumulated
      18. Result: True
      19. Comment: Accumulator create_filesystem_mountpoint_7c989ddd-1fbd-4824-a2ec-2d00f49d8c46 for file /etc/fstab was charged by text
      20. Started: 15:56:34.326587
      21. Duration: 1.502 ms
      22. Changes:
      23. ----------
      24. ID: create_filesystem_mountpoint_5a3a0a48-0f15-4f99-b3e8-427f33dd0c48
      25. Function: file.accumulated
      26. Result: True
      27. Comment: Accumulator create_filesystem_mountpoint_5a3a0a48-0f15-4f99-b3e8-427f33dd0c48 for file /etc/fstab was charged by text
      28. Started: 15:56:34.328360
      29. Duration: 1.971 ms
      30. Changes:
      31. ----------
      32. ID: create_filesystem_mountpoint_08f256fe-15f4-4ce2-81b7-6f9786aac953
      33. Function: file.accumulated
      34. Result: True
      35. Comment: Accumulator create_filesystem_mountpoint_08f256fe-15f4-4ce2-81b7-6f9786aac953 for file /etc/fstab was charged by text
      36. Started: 15:56:34.330602
      37. Duration: 1.528 ms
      38. Changes:
      39. ----------
      40. ID: create_filesystem_mountpoint_9c9ab426-cc15-42b7-bb01-6d3fda495a7b
      41. Function: file.accumulated
      42. Result: True
      43. Comment: Accumulator create_filesystem_mountpoint_9c9ab426-cc15-42b7-bb01-6d3fda495a7b for file /etc/fstab was charged by text
      44. Started: 15:56:34.332396
      45. Duration: 1.493 ms
      46. Changes:
      47. ----------
      48. ID: append_fstab_entries
      49. Function: file.blockreplace
      50. Name: /etc/fstab
      51. Result: True
      52. Comment: Changes were made
      53. Started: 15:56:34.337040
      54. Duration: 27.312 ms
      55. Changes:
      56. ----------
      57. diff:
      58. ---
      59. +++
      60. @@ -14,4 +14,5 @@
      61. /dev/disk/by-label/Extras /srv/dev-disk-by-label-Extras ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,discard,acl 0 2
      62. /dev/disk/by-label/3Tb /srv/dev-disk-by-label-3Tb ntfs defaults,nofail 0 2
      63. /dev/disk/by-label/Torreznos /srv/dev-disk-by-label-Torreznos ntfs defaults,nofail 0 2
      64. +/dev/disk/by-label/My Passport Blue /srv/dev-disk-by-label-My Passport Blue ntfs defaults,nofail 0 2
      65. # <<< [openmediavault]
      66. ----------
      67. ID: mount_no_bind_mountpoint_670e859a-5ff7-46cd-9871-5d12b5bce71a
      68. Function: mount.mounted
      69. Name: /srv/dev-disk-by-label-750Gb
      70. Result: True
      71. Comment: Target was already mounted
      72. Started: 15:56:34.367593
      73. Duration: 293.391 ms
      74. Changes:
      75. ----------
      76. ID: mount_no_bind_mountpoint_7c989ddd-1fbd-4824-a2ec-2d00f49d8c46
      77. Function: mount.mounted
      78. Name: /srv/dev-disk-by-label-Extras
      79. Result: True
      80. Comment: Target was already mounted
      81. Started: 15:56:34.661349
      82. Duration: 34.608 ms
      83. Changes:
      84. ----------
      85. ID: mount_no_bind_mountpoint_5a3a0a48-0f15-4f99-b3e8-427f33dd0c48
      86. Function: mount.mounted
      87. Name: /srv/dev-disk-by-label-3Tb
      88. Result: True
      89. Comment: Target was already mounted
      90. Started: 15:56:34.696311
      91. Duration: 35.446 ms
      92. Changes:
      93. ----------
      94. ID: mount_no_bind_mountpoint_08f256fe-15f4-4ce2-81b7-6f9786aac953
      95. Function: mount.mounted
      96. Name: /srv/dev-disk-by-label-Torreznos
      97. Result: False
      98. Comment: ntfs-3g: Failed to access volume '/dev/disk/by-label/Torreznos': No such file or directory
      99. ntfs-3g 2017.3.23AR.3 integrated FUSE 28 - Third Generation NTFS Driver
      100. Configuration type 7, XATTRS are on, POSIX ACLS are on
      101. Copyright (C) 2005-2007 Yura Pakhuchiy
      102. Copyright (C) 2006-2009 Szabolcs Szakacsits
      103. Copyright (C) 2007-2017 Jean-Pierre Andre
      104. Copyright (C) 2009 Erik Larsson
      105. Usage: ntfs-3g [-o option[,...]] <device|image_file> <mount_point>
      106. Options: ro (read-only mount), windows_names, uid=, gid=,
      107. umask=, fmask=, dmask=, streams_interface=.
      108. Please see the details in the manual (type: man ntfs-3g).
      109. Example: ntfs-3g /dev/sda1 /mnt/windows
      110. News, support and information: http://tuxera.com
      111. Started: 15:56:34.732150
      112. Duration: 196.532 ms
      113. Changes:
      114. ----------
      115. umount:
      116. Forced unmount because devices don't match. Wanted: /dev/disk/by-label/Torreznos, current: /dev/sdd1, /dev/sdd1
      117. ----------
      118. ID: mount_no_bind_mountpoint_9c9ab426-cc15-42b7-bb01-6d3fda495a7b
      119. Function: mount.mounted
      120. Name: /srv/dev-disk-by-label-My Passport Blue
      121. Result: False
      122. Comment: mount: bad usage
      123. Try 'mount --help' for more information.
      124. Started: 15:56:34.929118
      125. Duration: 85.972 ms
      126. Changes:
      127. Summary for debian
      128. ------------
      129. Succeeded: 9 (changed=2)
      130. Failed: 2
      131. ------------
      132. Total states run: 11
      133. Total run time: 681.091 ms in /usr/share/php/openmediavault/system/process.inc:182
      134. Stack trace:
      135. #0 /usr/share/php/openmediavault/engine/module/serviceabstract.inc(60): OMV\System\Process->execute()
      136. #1 /usr/share/openmediavault/engined/rpc/config.inc(164): OMV\Engine\Module\ServiceAbstract->deploy()
      137. #2 [internal function]: Engined\Rpc\Config->applyChanges(Array, Array)
      138. #3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
      139. #4 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array)
      140. #5 /usr/share/openmediavault/engined/rpc/filesystemmgmt.inc(899): OMV\Rpc\Rpc::call('Config', 'applyChanges', Array, Array)
      141. #6 [internal function]: Engined\Rpc\OMVRpcServiceFileSystemMgmt->mount(Array, Array)
      142. #7 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
      143. #8 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('mount', Array, Array)
      144. #9 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('FileSystemMgmt', 'mount', Array, Array, 1)
      145. #10 {main}
      Display All

      I tried with other external HDD and it works properly, also I checked this HDD in other machine, and all the data is accessible.
      As I can understand, it is like the HDD is already mounted and the system is not able to mount again. ¿?


      As the same time, other issue appears, I'm not able to add plugins, I solved this issue before (in one of the other installations of OMV5) with a new installation.

      [Blocked Image: https://fotos.subefotos.com/c498c013f89312bb37c078ecb3eea06ao.png]



      I think that something was corrupted when I plugged the HDD, and may be it will be easy to restore the stability of the system, but my knowledge is not enough.



      One more point of information: I have in a externar board, Orange Pi Zero, a Pi-Hole system running, and I saw that sometimes I have to disable it to perform some actions, as for example to be able to install the OMV-Extras.



      At the moment, I only publish this post just for share with you and may be some one is able to find an easy solution.



      But don't break your brain at the moment, because I will do a new installation again and any new comment about to type a code line or something will not be done at this point (instead If I will find the same problem again, then, I will update you with all the process).



      Thanks for your time.
    • Can you please post the output of

      Source Code

      1. $ ls -alh /dev/disk/*

      after the USB-HDD has been plugged in?
      Absolutely no support through PM!

      I must not fear.
      Fear is the mind-killer.
      Fear is the little-death that brings total obliteration.
      I will face my fear.
      I will permit it to pass over me and through me.
      And when it has gone past I will turn the inner eye to see its path.
      Where the fear has gone there will be nothing.
      Only I will remain.

      Litany against fear by Bene Gesserit
    • votdev wrote:

      Can you please post the output of

      Source Code

      1. $ ls -alh /dev/disk/*

      after the USB-HDD has been plugged in?
      Hi @votdev,

      I installed again all the system, but the issue is there. May be something wrong with the HDD?? But I can work with him under Windows 10 with no problems.

      Here you have the answer from the system:


      Difference-File

      1. ------> ls -alh /dev/disk/*
      2. /dev/disk/by-id:
      3. total 0
      4. drwxr-xr-x 2 root root 320 Sep 11 18:50 .
      5. drwxr-xr-x 8 root root 160 Sep 11 18:43 ..
      6. lrwxrwxrwx 1 root root 9 Sep 11 18:43 ata-Hitachi_HTS727575A9E364_J3340084JL26TB -> ../../sda
      7. lrwxrwxrwx 1 root root 10 Sep 11 18:43 ata-Hitachi_HTS727575A9E364_J3340084JL26TB-part1 -> ../../sda1
      8. lrwxrwxrwx 1 root root 13 Sep 11 18:43 mmc-SC32G_0x58f718ca -> ../../mmcblk1
      9. lrwxrwxrwx 1 root root 15 Sep 11 18:43 mmc-SC32G_0x58f718ca-part1 -> ../../mmcblk1p1
      10. lrwxrwxrwx 1 root root 9 Sep 11 18:43 usb-SanDisk_Ultra_Fit_4C531001430804122292-0:0 -> ../../sdc
      11. lrwxrwxrwx 1 root root 10 Sep 11 18:43 usb-SanDisk_Ultra_Fit_4C531001430804122292-0:0-part1 -> ../../sdc1
      12. lrwxrwxrwx 1 root root 10 Sep 11 18:43 usb-SanDisk_Ultra_Fit_4C531001430804122292-0:0-part2 -> ../../sdc2
      13. lrwxrwxrwx 1 root root 10 Sep 11 18:43 usb-SanDisk_Ultra_Fit_4C531001430804122292-0:0-part5 -> ../../sdc5
      14. lrwxrwxrwx 1 root root 9 Sep 11 18:43 usb-TOSHIBA_External_USB_3.0_20170525024340F-0:0 -> ../../sdb
      15. lrwxrwxrwx 1 root root 10 Sep 11 18:43 usb-TOSHIBA_External_USB_3.0_20170525024340F-0:0-part1 -> ../../sdb1
      16. lrwxrwxrwx 1 root root 9 Sep 11 18:50 usb-WD_My_Passport_25E2_57583331444337374E415359-0:0 -> ../../sdd
      17. lrwxrwxrwx 1 root root 10 Sep 11 18:50 usb-WD_My_Passport_25E2_57583331444337374E415359-0:0-part1 -> ../../sdd1
      18. lrwxrwxrwx 1 root root 9 Sep 11 18:43 wwn-0x5000cca68ce46604 -> ../../sda
      19. lrwxrwxrwx 1 root root 10 Sep 11 18:43 wwn-0x5000cca68ce46604-part1 -> ../../sda1
      20. /dev/disk/by-label:
      21. total 0
      22. drwxr-xr-x 2 root root 120 Sep 11 18:50 .
      23. drwxr-xr-x 8 root root 160 Sep 11 18:43 ..
      24. lrwxrwxrwx 1 root root 10 Sep 11 18:43 3Tb -> ../../sdb1
      25. lrwxrwxrwx 1 root root 10 Sep 11 18:43 750Gb -> ../../sda1
      26. lrwxrwxrwx 1 root root 15 Sep 11 18:43 Extras -> ../../mmcblk1p1
      27. lrwxrwxrwx 1 root root 10 Sep 11 18:50 'My\x20Passport\x20Blue' -> ../../sdd1
      28. /dev/disk/by-partlabel:
      29. total 0
      30. drwxr-xr-x 2 root root 80 Sep 11 18:50 .
      31. drwxr-xr-x 8 root root 160 Sep 11 18:43 ..
      32. lrwxrwxrwx 1 root root 10 Sep 11 18:43 'Basic\x20data\x20partition' -> ../../sdb1
      33. lrwxrwxrwx 1 root root 10 Sep 11 18:50 'My\x20Passport' -> ../../sdd1
      34. /dev/disk/by-partuuid:
      35. total 0
      36. drwxr-xr-x 2 root root 180 Sep 11 18:50 .
      37. drwxr-xr-x 8 root root 160 Sep 11 18:43 ..
      38. lrwxrwxrwx 1 root root 10 Sep 11 18:43 14839bd2-b743-46c2-b6e5-7ef7a9d9cc69 -> ../../sdb1
      39. lrwxrwxrwx 1 root root 15 Sep 11 18:43 77b7662b-98d8-415f-b7ea-b4893a7f38e9 -> ../../mmcblk1p1
      40. lrwxrwxrwx 1 root root 10 Sep 11 18:43 7a236ad2-01 -> ../../sdc1
      41. lrwxrwxrwx 1 root root 10 Sep 11 18:43 7a236ad2-02 -> ../../sdc2
      42. lrwxrwxrwx 1 root root 10 Sep 11 18:43 7a236ad2-05 -> ../../sdc5
      43. lrwxrwxrwx 1 root root 10 Sep 11 18:43 96419641-01 -> ../../sda1
      44. lrwxrwxrwx 1 root root 10 Sep 11 18:50 eb1e1bfc-b406-4191-8a95-546bb457bbb1 -> ../../sdd1
      45. /dev/disk/by-path:
      46. total 0
      47. drwxr-xr-x 2 root root 280 Sep 11 18:50 .
      48. drwxr-xr-x 8 root root 160 Sep 11 18:43 ..
      49. lrwxrwxrwx 1 root root 9 Sep 11 18:43 pci-0000:00:12.0-ata-2 -> ../../sda
      50. lrwxrwxrwx 1 root root 10 Sep 11 18:43 pci-0000:00:12.0-ata-2-part1 -> ../../sda1
      51. lrwxrwxrwx 1 root root 13 Sep 11 18:43 pci-0000:00:15.0-usb-0:1:1.0-platform-rtsx_usb_sdmmc.0.auto -> ../../mmcblk1
      52. lrwxrwxrwx 1 root root 15 Sep 11 18:43 pci-0000:00:15.0-usb-0:1:1.0-platform-rtsx_usb_sdmmc.0.auto-part1 -> ../../mmcblk1p1
      53. lrwxrwxrwx 1 root root 9 Sep 11 18:43 pci-0000:00:15.0-usb-0:2:1.0-scsi-0:0:0:0 -> ../../sdb
      54. lrwxrwxrwx 1 root root 10 Sep 11 18:43 pci-0000:00:15.0-usb-0:2:1.0-scsi-0:0:0:0-part1 -> ../../sdb1
      55. lrwxrwxrwx 1 root root 9 Sep 11 18:43 pci-0000:00:15.0-usb-0:4:1.0-scsi-0:0:0:0 -> ../../sdc
      56. lrwxrwxrwx 1 root root 10 Sep 11 18:43 pci-0000:00:15.0-usb-0:4:1.0-scsi-0:0:0:0-part1 -> ../../sdc1
      57. lrwxrwxrwx 1 root root 10 Sep 11 18:43 pci-0000:00:15.0-usb-0:4:1.0-scsi-0:0:0:0-part2 -> ../../sdc2
      58. lrwxrwxrwx 1 root root 10 Sep 11 18:43 pci-0000:00:15.0-usb-0:4:1.0-scsi-0:0:0:0-part5 -> ../../sdc5
      59. lrwxrwxrwx 1 root root 9 Sep 11 18:50 pci-0000:00:15.0-usb-0:5:1.0-scsi-0:0:0:0 -> ../../sdd
      60. lrwxrwxrwx 1 root root 10 Sep 11 18:50 pci-0000:00:15.0-usb-0:5:1.0-scsi-0:0:0:0-part1 -> ../../sdd1
      61. /dev/disk/by-uuid:
      62. total 0
      63. drwxr-xr-x 2 root root 160 Sep 11 18:50 .
      64. drwxr-xr-x 8 root root 160 Sep 11 18:43 ..
      65. lrwxrwxrwx 1 root root 10 Sep 11 18:43 00700B67700B62B0 -> ../../sda1
      66. lrwxrwxrwx 1 root root 10 Sep 11 18:50 20E87DF9E87DCE12 -> ../../sdd1
      67. lrwxrwxrwx 1 root root 10 Sep 11 18:43 383C8D5A3C8D13D2 -> ../../sdb1
      68. lrwxrwxrwx 1 root root 10 Sep 11 18:43 5cce6762-3298-4792-842c-722c19690fb5 -> ../../sdc5
      69. lrwxrwxrwx 1 root root 15 Sep 11 18:43 76d48057-9c8d-40dc-a92b-1888bd81793d -> ../../mmcblk1p1
      70. lrwxrwxrwx 1 root root 10 Sep 11 18:43 b4d0e3d6-9b51-4b0d-bc3a-f1be6a6b820e -> ../../sdc1
      Display All
      Thanks for your time
    • What is the output of

      Source Code

      1. $ blkid
      Absolutely no support through PM!

      I must not fear.
      Fear is the mind-killer.
      Fear is the little-death that brings total obliteration.
      I will face my fear.
      I will permit it to pass over me and through me.
      And when it has gone past I will turn the inner eye to see its path.
      Where the fear has gone there will be nothing.
      Only I will remain.

      Litany against fear by Bene Gesserit
    • @votdev, here the info:

      Source Code

      1. /dev/sda1: LABEL="750Gb" UUID="00700B67700B62B0" TYPE="ntfs" PARTUUID="96419641-01"
      2. /dev/mmcblk1p1: LABEL="Extras" UUID="76d48057-9c8d-40dc-a92b-1888bd81793d" TYPE="ext4" PARTUUID="77b7662b-98d8-415f-b7ea-b4893a7f38e9"
      3. /dev/sdb1: LABEL="3Tb" UUID="383C8D5A3C8D13D2" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="14839bd2-b743-46c2-b6e5-7ef7a9d9cc69"
      4. /dev/sdc1: UUID="b4d0e3d6-9b51-4b0d-bc3a-f1be6a6b820e" TYPE="ext4" PARTUUID="7a236ad2-01"
      5. /dev/sdc5: UUID="5cce6762-3298-4792-842c-722c19690fb5" TYPE="swap" PARTUUID="7a236ad2-05"
      6. /dev/sdd1: LABEL="My Passport Blue" UUID="20E87DF9E87DCE12" TYPE="ntfs" PTTYPE="atari" PARTLABEL="My Passport" PARTUUID="eb1e1bfc-b406-4191-8a95-546bb457bbb1"
      7. /dev/mmcblk1: PTUUID="2d55a785-f8ab-45f3-aa9d-ee8c8acd28c3" PTTYPE="gpt"
    • Hi @votdev

      Well, more "bad News" .

      I came back to OMV5.

      I have another WD My Passport 4tb.

      Appears the same error message when I want to mount the HDD. (I will change also the title of this thread)

      Maybe is a incompatibility with this model of HDD?

      Thanks in advance.

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

    • Hi again @votdev,

      Last test that I can do it today:

      I installed OMV5 in another machine, where I has before OMV4 (Old Intel i7 Laptop with overheat issues).

      The issue is the same, something happens with the Western Digital My Passport 4Tb Hard Disk.

      - Who is the "bad guy"?: The Brand, The capacity The HDD Firmware, OMV5?

      This Model of Hard Disk was working properly with OMV4, tomorrow I will came back to OMV4 with the i7 to be sure.

      Error:


      Difference-File

      1. Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-salt deploy run fstab 2>&1' with exit code '1': /usr/lib/python3/dist-packages/salt/modules/file.py:32: DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated, and in 3.8 it will stop working from collections import Iterable, Mapping /usr/lib/python3/dist-packages/salt/utils/decorators/signature.py:31: DeprecationWarning: `formatargspec` is deprecated since Python 3.5. Use `signature` and the `Signature` object directly *salt.utils.args.get_function_argspec(original_function) debian: ---------- ID: create_filesystem_mountpoint_569103a0-b8a2-4d52-a9c2-20ec97a74a25 Function: file.accumulated Result: True Comment: Accumulator create_filesystem_mountpoint_569103a0-b8a2-4d52-a9c2-20ec97a74a25 for file /etc/fstab was charged by text Started: 01:22:38.550194 Duration: 0.579 ms Changes: ---------- ID: append_fstab_entries Function: file.blockreplace Name: /etc/fstab Result: True Comment: Changes were made Started: 01:22:38.551201 Duration: 3.312 ms Changes: ---------- diff: --- +++ @@ -10,3 +10,6 @@ # swap was on /dev/sdb5 during installation UUID=334aca66-d074-476a-a100-a6858974b3cc none swap sw 0 0 /dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0 +# >>> [openmediavault] +/dev/disk/by-label/My Passport Blue /srv/dev-disk-by-label-My Passport Blue ntfs defaults,nofail 0 2 +# <<< [openmediavault] ---------- ID: mount_no_bind_mountpoint_569103a0-b8a2-4d52-a9c2-20ec97a74a25 Function: mount.mounted Name: /srv/dev-disk-by-label-My Passport Blue Result: False Comment: mount: bad usage Try 'mount --help' for more information. Started: 01:22:38.555041 Duration: 362.689 ms Changes: Summary for debian ------------ Succeeded: 2 (changed=1) Failed: 1 ------------ Total states run: 3 Total run time: 366.580 ms

      More Details:


      Difference-File

      1. Error #0:
      2. OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-salt deploy run fstab 2>&1' with exit code '1': /usr/lib/python3/dist-packages/salt/modules/file.py:32: DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated, and in 3.8 it will stop working
      3. from collections import Iterable, Mapping
      4. /usr/lib/python3/dist-packages/salt/utils/decorators/signature.py:31: DeprecationWarning: `formatargspec` is deprecated since Python 3.5. Use `signature` and the `Signature` object directly
      5. *salt.utils.args.get_function_argspec(original_function)
      6. debian:
      7. ----------
      8. ID: create_filesystem_mountpoint_569103a0-b8a2-4d52-a9c2-20ec97a74a25
      9. Function: file.accumulated
      10. Result: True
      11. Comment: Accumulator create_filesystem_mountpoint_569103a0-b8a2-4d52-a9c2-20ec97a74a25 for file /etc/fstab was charged by text
      12. Started: 01:22:38.550194
      13. Duration: 0.579 ms
      14. Changes:
      15. ----------
      16. ID: append_fstab_entries
      17. Function: file.blockreplace
      18. Name: /etc/fstab
      19. Result: True
      20. Comment: Changes were made
      21. Started: 01:22:38.551201
      22. Duration: 3.312 ms
      23. Changes:
      24. ----------
      25. diff:
      26. ---
      27. +++
      28. @@ -10,3 +10,6 @@
      29. # swap was on /dev/sdb5 during installation
      30. UUID=334aca66-d074-476a-a100-a6858974b3cc none swap sw 0 0
      31. /dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0
      32. +# >>> [openmediavault]
      33. +/dev/disk/by-label/My Passport Blue /srv/dev-disk-by-label-My Passport Blue ntfs defaults,nofail 0 2
      34. +# <<< [openmediavault]
      35. ----------
      36. ID: mount_no_bind_mountpoint_569103a0-b8a2-4d52-a9c2-20ec97a74a25
      37. Function: mount.mounted
      38. Name: /srv/dev-disk-by-label-My Passport Blue
      39. Result: False
      40. Comment: mount: bad usage
      41. Try 'mount --help' for more information.
      42. Started: 01:22:38.555041
      43. Duration: 362.689 ms
      44. Changes:
      45. Summary for debian
      46. ------------
      47. Succeeded: 2 (changed=1)
      48. Failed: 1
      49. ------------
      50. Total states run: 3
      51. Total run time: 366.580 ms in /usr/share/php/openmediavault/system/process.inc:182
      52. Stack trace:
      53. #0 /usr/share/php/openmediavault/engine/module/serviceabstract.inc(60): OMV\System\Process->execute()
      54. #1 /usr/share/openmediavault/engined/rpc/config.inc(164): OMV\Engine\Module\ServiceAbstract->deploy()
      55. #2 [internal function]: Engined\Rpc\Config->applyChanges(Array, Array)
      56. #3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
      57. #4 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array)
      58. #5 /usr/share/openmediavault/engined/rpc/filesystemmgmt.inc(899): OMV\Rpc\Rpc::call('Config', 'applyChanges', Array, Array)
      59. #6 [internal function]: Engined\Rpc\OMVRpcServiceFileSystemMgmt->mount(Array, Array)
      60. #7 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
      61. #8 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('mount', Array, Array)
      62. #9 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('FileSystemMgmt', 'mount', Array, Array, 1)
      63. #10 {main}
      Display All
    • New

      You've found a bug. Filesystem labels with blanks were not handled properly. Fixed in openmediavault 5.0.8, see github.com/openmediavault/open…1c38188f45b30dfbbea38dc57 and github.com/openmediavault/open…cf5184f624cce8b67dece6b83.
      Absolutely no support through PM!

      I must not fear.
      Fear is the mind-killer.
      Fear is the little-death that brings total obliteration.
      I will face my fear.
      I will permit it to pass over me and through me.
      And when it has gone past I will turn the inner eye to see its path.
      Where the fear has gone there will be nothing.
      Only I will remain.

      Litany against fear by Bene Gesserit
    • New

      It seems to be that SaltStack can not handle blanks in device names and mount dirs properly. Need to find a workaround and maybe a bug fix for the upstream project.

      I really can’t understand why it is necessary to use blanks in filesystem labels or file names. As SaltStack has it’s problems with it i think blanks in filenames are not widely used in Linux and it seems to me that this absurdity comes from the Windows world.
      Absolutely no support through PM!

      I must not fear.
      Fear is the mind-killer.
      Fear is the little-death that brings total obliteration.
      I will face my fear.
      I will permit it to pass over me and through me.
      And when it has gone past I will turn the inner eye to see its path.
      Where the fear has gone there will be nothing.
      Only I will remain.

      Litany against fear by Bene Gesserit
    • New

      I've opened a bugreport in SaltStack: github.com/saltstack/salt/issues/54508
      Absolutely no support through PM!

      I must not fear.
      Fear is the mind-killer.
      Fear is the little-death that brings total obliteration.
      I will face my fear.
      I will permit it to pass over me and through me.
      And when it has gone past I will turn the inner eye to see its path.
      Where the fear has gone there will be nothing.
      Only I will remain.

      Litany against fear by Bene Gesserit
    • New

      votdev wrote:

      I really can’t understand why it is necessary to use blanks in filesystem labels or file names.
      Probably it is not necessary, but people do it if they are not aware it will cause problems. So maybe an error message when creating the label would help. At least in those cases where the label is added using OMV.
      Odroid HC2 - armbian - OMV4.x | Asrock Q1900DC-ITX - Intenso SSD 120GB - OMV4.x
      :!: Backup - Solutions to common problems - OMV setup videos - OMV4 Documentation - user guide :!:
    • New

      macom wrote:

      votdev wrote:

      I really can’t understand why it is necessary to use blanks in filesystem labels or file names.
      Probably it is not necessary, but people do it if they are not aware it will cause problems. So maybe an error message when creating the label would help. At least in those cases where the label is added using OMV.
      The OMV UI does not allow blanks for labels when creating new filesystem since ages.
      Absolutely no support through PM!

      I must not fear.
      Fear is the mind-killer.
      Fear is the little-death that brings total obliteration.
      I will face my fear.
      I will permit it to pass over me and through me.
      And when it has gone past I will turn the inner eye to see its path.
      Where the fear has gone there will be nothing.
      Only I will remain.

      Litany against fear by Bene Gesserit
    • New

      votdev wrote:

      macom wrote:

      votdev wrote:

      I really can’t understand why it is necessary to use blanks in filesystem labels or file names.
      Probably it is not necessary, but people do it if they are not aware it will cause problems. So maybe an error message when creating the label would help. At least in those cases where the label is added using OMV.
      The OMV UI does not allow blanks in filesystem labels since ages.
      With OMV4, I was able to work with this HDD, also with blanks, for this reason I was worried when with OMV 5 I was not able to mount the HDD, I supposed also that the the HDD was damaged.. .