Error Mounting USB drive.

    • OMV 5.x (beta)
    • Error Mounting USB drive.

      Hi guys, Im pretty new to this so please bare with me.

      Set up my Open Media Vault tonight,
      Have 3 internal HDDs in the PC
      No OS other than OMV.

      Everything seems to be working great other than mounting my final drive. It's an external USB drive (5TB).

      I have tried multiple ports,
      Changing the name of the drive to have no spaces.
      But to no avail.

      any help would be great.

      Error:

      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/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_36dd0dc1-9761-40a9-a531-133e273e6736 Function: file.accumulated Result: True Comment: Accumulator create_filesystem_mountpoint_36dd0dc1-9761-40a9-a531-133e273e6736 for file /etc/fstab was charged by text Started: 23:15:46.082591 Duration: 1.263 ms Changes: ---------- ID: mount_filesystem_mountpoint_36dd0dc1-9761-40a9-a531-133e273e6736 Function: mount.mounted Name: /srv/dev-disk-by-id-ata-WDC_WD5000AACS-00ZUB0_WD-WCASU2417855-part2 Result: False Comment: ntfs-3g: Failed to access volume '/dev/disk/by-id/ata-WDC_WD5000AACS-00ZUB0_WD-WCASU2417855-part2': No such file or directory ntfs-3g 2017.3.23AR.3 integrated FUSE 28 - Third Generation NTFS Driver Configuration type 7, XATTRS are on, POSIX ACLS are on Copyright (C) 2005-2007 Yura Pakhuchiy Copyright (C) 2006-2009 Szabolcs Szakacsits Copyright (C) 2007-2017 Jean-Pierre Andre Copyright (C) 2009 Erik Larsson Usage: ntfs-3g [-o option[,...]] <device|image_file> <mount_point> Options: ro (read-only mount), windows_names, uid=, gid=, umask=, fmask=, dmask=, streams_interface=. Please see the details in the manual (type: man ntfs-3g). Example: ntfs-3g /dev/sda1 /mnt/windows News, support and information: tuxera.com Started: 23:15:46.085098 Duration: 588.314 ms Changes: ---------- ID: create_filesystem_mountpoint_7c49138c-96d5-47db-ab4f-37b30a6f4b80 Function: file.accumulated Result: True Comment: Accumulator create_filesystem_mountpoint_7c49138c-96d5-47db-ab4f-37b30a6f4b80 for file /etc/fstab was charged by text Started: 23:15:46.674125 Duration: 4.421 ms Changes: ---------- ID: mount_filesystem_mountpoint_7c49138c-96d5-47db-ab4f-37b30a6f4b80 Function: mount.mounted Name: /srv/dev-disk-by-label-Media Result: True Comment: Target was already mounted Started: 23:15:46.678985 Duration: 200.681 ms Changes: ---------- umount: Forced remount because options (acl) changed ---------- ID: create_filesystem_mountpoint_e759856f-d84c-4dae-931e-8463019dde9b Function: file.accumulated Result: True Comment: Accumulator create_filesystem_mountpoint_e759856f-d84c-4dae-931e-8463019dde9b for file /etc/fstab was charged by text Started: 23:15:46.880177 Duration: 2.442 ms Changes: ---------- ID: mount_filesystem_mountpoint_e759856f-d84c-4dae-931e-8463019dde9b Function: mount.mounted Name: /srv/dev-disk-by-label-5TBDrive Result: True Comment: Target was successfully mounted Started: 23:15:46.882926 Duration: 9005.37 ms Changes: ---------- mount: True ---------- ID: append_fstab_entries Function: file.blockreplace Name: /etc/fstab Result: True Comment: Changes were made Started: 23:15:55.892839 Duration: 224.503 ms Changes: ---------- diff: --- +++ @@ -12,5 +12,5 @@ # >>> [openmediavault] /dev/disk/by-id/ata-WDC_WD5000AACS-00ZUB0_WD-WCASU2417855-part2 /srv/dev-disk-by-id-ata-WDC_WD5000AACS-00ZUB0_WD-WCASU2417855-part2 ntfs defaults,nofail 0 2 /dev/disk/by-label/Media /srv/dev-disk-by-label-Media ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2 -/dev/disk/by-label/USB\x20Media\x20Drive /srv/dev-disk-by-label-USB\040Media\040Drive ntfs defaults,nofail 0 2 +/dev/disk/by-label/5TBDrive /srv/dev-disk-by-label-5TBDrive ntfs defaults,nofail 0 2 # <<< [openmediavault] Summary for debian ------------ Succeeded: 6 (changed=3) Failed: 1 ------------ Total states run: 7 Total run time: 10.027 s


      Error #0: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/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_36dd0dc1-9761-40a9-a531-133e273e6736 Function: file.accumulated Result: True Comment: Accumulator create_filesystem_mountpoint_36dd0dc1-9761-40a9-a531-133e273e6736 for file /etc/fstab was charged by text Started: 23:15:46.082591 Duration: 1.263 ms Changes:---------- ID: mount_filesystem_mountpoint_36dd0dc1-9761-40a9-a531-133e273e6736 Function: mount.mounted Name: /srv/dev-disk-by-id-ata-WDC_WD5000AACS-00ZUB0_WD-WCASU2417855-part2 Result: False Comment: ntfs-3g: Failed to access volume '/dev/disk/by-id/ata-WDC_WD5000AACS-00ZUB0_WD-WCASU2417855-part2': No such file or directory ntfs-3g 2017.3.23AR.3 integrated FUSE 28 - Third Generation NTFS Driver Configuration type 7, XATTRS are on, POSIX ACLS are on Copyright (C) 2005-2007 Yura Pakhuchiy Copyright (C) 2006-2009 Szabolcs Szakacsits Copyright (C) 2007-2017 Jean-Pierre Andre Copyright (C) 2009 Erik Larsson Usage: ntfs-3g [-o option[,...]] <device|image_file> <mount_point> Options: ro (read-only mount), windows_names, uid=, gid=, umask=, fmask=, dmask=, streams_interface=. Please see the details in the manual (type: man ntfs-3g). Example: ntfs-3g /dev/sda1 /mnt/windows News, support and information: tuxera.com Started: 23:15:46.085098 Duration: 588.314 ms Changes:---------- ID: create_filesystem_mountpoint_7c49138c-96d5-47db-ab4f-37b30a6f4b80 Function: file.accumulated Result: True Comment: Accumulator create_filesystem_mountpoint_7c49138c-96d5-47db-ab4f-37b30a6f4b80 for file /etc/fstab was charged by text Started: 23:15:46.674125 Duration: 4.421 ms Changes:---------- ID: mount_filesystem_mountpoint_7c49138c-96d5-47db-ab4f-37b30a6f4b80 Function: mount.mounted Name: /srv/dev-disk-by-label-Media Result: True Comment: Target was already mounted Started: 23:15:46.678985 Duration: 200.681 ms Changes: ---------- umount: Forced remount because options (acl) changed---------- ID: create_filesystem_mountpoint_e759856f-d84c-4dae-931e-8463019dde9b Function: file.accumulated Result: True Comment: Accumulator create_filesystem_mountpoint_e759856f-d84c-4dae-931e-8463019dde9b for file /etc/fstab was charged by text Started: 23:15:46.880177 Duration: 2.442 ms Changes:---------- ID: mount_filesystem_mountpoint_e759856f-d84c-4dae-931e-8463019dde9b Function: mount.mounted Name: /srv/dev-disk-by-label-5TBDrive Result: True Comment: Target was successfully mounted Started: 23:15:46.882926 Duration: 9005.37 ms Changes: ---------- mount: True---------- ID: append_fstab_entries Function: file.blockreplace Name: /etc/fstab Result: True Comment: Changes were made Started: 23:15:55.892839 Duration: 224.503 ms Changes: ---------- diff: --- +++ @@ -12,5 +12,5 @@ # >>> [openmediavault] /dev/disk/by-id/ata-WDC_WD5000AACS-00ZUB0_WD-WCASU2417855-part2 /srv/dev-disk-by-id-ata-WDC_WD5000AACS-00ZUB0_WD-WCASU2417855-part2 ntfs defaults,nofail 0 2 /dev/disk/by-label/Media /srv/dev-disk-by-label-Media ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2 -/dev/disk/by-label/USB\x20Media\x20Drive /srv/dev-disk-by-label-USB\040Media\040Drive ntfs defaults,nofail 0 2 +/dev/disk/by-label/5TBDrive /srv/dev-disk-by-label-5TBDrive ntfs defaults,nofail 0 2 # <<< [openmediavault]Summary for debian------------Succeeded: 6 (changed=3)Failed: 1------------Total states run: 7Total run time: 10.027 s in /usr/share/php/openmediavault/system/process.inc:182Stack trace:#0 /usr/share/php/openmediavault/engine/module/serviceabstract.inc(60): OMV\System\Process->execute()#1 /usr/share/openmediavault/engined/rpc/config.inc(167): OMV\Engine\Module\ServiceAbstract->deploy()#2 [internal function]: Engined\Rpc\Config->applyChanges(Array, Array)#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)#4 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array)#5 /usr/share/openmediavault/engined/rpc/filesystemmgmt.inc(899): OMV\Rpc\Rpc::call('Config', 'applyChanges', Array, Array)#6 [internal function]: Engined\Rpc\OMVRpcServiceFileSystemMgmt->mount(Array, Array)#7 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)#8 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('mount', Array, Array)#9 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('FileSystemMgmt', 'mount', Array, Array, 1)#10 {main}
    • If you didn't mount the drive in the OMV web interface, you can't use it in the web interface. Problem #2 - forum.openmediavault.org/index…tions-to-common-problems/
      omv 5.2.3 usul | 64 bit | 5.3 proxmox kernel | omvextrasorg 5.2.0
      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!
    • ryecoaaron wrote:

      If you didn't mount the drive in the OMV web interface, you can't use it in the web interface. Problem #2 - forum.openmediavault.org/index…tions-to-common-problems/
      thanks ryecoaaron. it is the hard drive that i installed OMV on. I did not mount anywhere, it just appeared under file systems as 'mounted' but I can not unmount and then mount it through the OMV web interface because those buttons are greyed out. The hard drive is 1 TB so did I need to create partitions etc?
    • tannaroo wrote:

      thanks ryecoaaron. it is the hard drive that i installed OMV on. I did not mount anywhere, it just appeared under file systems as 'mounted' but I can not unmount and then mount it through the OMV web interface because those buttons are greyed out. The hard drive is 1 TB so did I need to create partitions etc?
      The OS filesystem is listed just to show free space. You cannot use it for shared folders. So, if you install OMV on a 1 TB hard drive, you will need to partition it to use it for data. The concept of OMV is not put data on the OS drive so that you don't lose data when/if it fails.
      omv 5.2.3 usul | 64 bit | 5.3 proxmox kernel | omvextrasorg 5.2.0
      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!
    • ryecoaaron wrote:

      tannaroo wrote:

      thanks ryecoaaron. it is the hard drive that i installed OMV on. I did not mount anywhere, it just appeared under file systems as 'mounted' but I can not unmount and then mount it through the OMV web interface because those buttons are greyed out. The hard drive is 1 TB so did I need to create partitions etc?
      The OS filesystem is listed just to show free space. You cannot use it for shared folders. So, if you install OMV on a 1 TB hard drive, you will need to partition it to use it for data. The concept of OMV is not put data on the OS drive so that you don't lose data when/if it fails.
      I have used gparted live bootable to create 2 partitions on my HDD - one is 20gb (/dev/sda1) for the OS and the second is the rest of space (/dev/sda2) - all formatted to ready to go.

      I then reinstalled OMV but when I get to screen where it wants the install OMV OS - it only finds SCS1 (sda) which is the combination of /sda1 and /sda2 so it looks as though it going to install and reformat the OS back onto the full drive?
    • tannaroo wrote:

      I have used gparted live bootable to create 2 partitions on my HDD - one is 20gb (/dev/sda1) for the OS and the second is the rest of space (/dev/sda2) - all formatted to ready to go.

      I then reinstalled OMV but when I get to screen where it wants the install OMV OS - it only finds SCS1 (sda) which is the combination of /sda1 and /sda2 so it looks as though it going to install and reformat the OS back onto the full drive?
      Yes, the OMV installer will always re-partition your drive. You have to re-partition after installing OMV -or- using the Debian iso then install OMV.
      omv 5.2.3 usul | 64 bit | 5.3 proxmox kernel | omvextrasorg 5.2.0
      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!
    • tannaroo wrote:

      is there a way to rename the Label, so that I know its the OMV 0S Hard drive?
      e2label will change it and depending on how your re-partitioned it, most things like gparted allow you to edit the label name too. Although I don't think it is necessary. The OMV web interface won't let you incorrectly use the OS partition.
      omv 5.2.3 usul | 64 bit | 5.3 proxmox kernel | omvextrasorg 5.2.0
      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!
    • tannaroo wrote:

      i presume this is required and part of the omv operating system?
      Depending on the amount of ram your system has, it may be required. It is created by default though and is part of Linux.
      omv 5.2.3 usul | 64 bit | 5.3 proxmox kernel | omvextrasorg 5.2.0
      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!
    • Users Online 1

      1 Guest