After latest update: Mounting / unmounting USB Harddrive causes error message

    • OMV 1.0

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

    • After latest update: Mounting / unmounting USB Harddrive causes error message

      I did install the lastest updates via the GUI this morning.

      When I tried to to mount a usb harddisk for the weekly external backup, I received this error message when trying to "apply changes" (yellow bar):

      Source Code

      1. Error
      2. Failed to execute command 'export LANG=C; monit restart collectd 2>&1': /etc/monit/conf.d/openmediavault-filesystem.conf:28: Error: service name conflict, fs_media_0294023894022EAB already defined '/media/0294023894022EAB'
      3. Error #4000:
      4. exception 'OMVException' with message 'Failed to execute command 'export LANG=C; monit restart collectd 2>&1': /etc/monit/conf.d/openmediavault-filesystem.conf:28: Error: service name conflict, fs_media_0294023894022EAB already defined '/media/0294023894022EAB'' in /usr/share/php/openmediavault/monit.inc:113
      5. Stack trace:
      6. #0 /usr/share/php/openmediavault/monit.inc(70): OMVMonit->action('restart', 'collectd', false)
      7. #1 /usr/share/openmediavault/engined/module/collectd.inc(53): OMVMonit->restart('collectd')
      8. #2 /usr/share/openmediavault/engined/rpc/config.inc(206): OMVModuleCollectd->startService()
      9. #3 [internal function]: OMVRpcServiceConfig->applyChanges(Array, Array)
      10. #4 /usr/share/php/openmediavault/rpcservice.inc(125): call_user_func_array(Array, Array)
      11. #5 /usr/share/php/openmediavault/rpcservice.inc(158): OMVRpcServiceAbstract->callMethod('applyChanges', Array, Array)
      12. #6 /usr/share/openmediavault/engined/rpc/config.inc(224): OMVRpcServiceAbstract->callMethodBg('applyChanges', Array, Array)
      13. #7 [internal function]: OMVRpcServiceConfig->applyChangesBg(Array, Array)
      14. #8 /usr/share/php/openmediavault/rpcservice.inc(125): call_user_func_array(Array, Array)
      15. #9 /usr/share/php/openmediavault/rpc.inc(79): OMVRpcServiceAbstract->callMethod('applyChangesBg', Array, Array)
      16. #10 /usr/sbin/omv-engined(500): OMVRpc::exec('Config', 'applyChangesBg', Array, Array, 1)
      17. #11 {main}
      Display All


      Somehow the HDD was mounted anyway, without being able to "apply changes" and I could do my backup run.

      Then, when I tried to unmount the disk, again an error message:

      Source Code

      1. Failed to get configuration (xpath=//system/fstab/mntent[uuid=''])
      2. Error #3003:
      3. exception 'OMVException' with message 'Failed to get configuration (xpath=//system/fstab/mntent[uuid=''])' in /usr/share/php/openmediavault/rpcservice.inc:551
      4. Stack trace:
      5. #0 /usr/share/openmediavault/engined/rpc/fstab.inc(216): OMVRpcServiceAbstract->deleteConfigObjectByPath('//system/fstab/...', 'org.openmediava...')
      6. #1 [internal function]: OMVRpcServiceFsTab->delete(Array, Array)
      7. #2 /usr/share/php/openmediavault/rpcservice.inc(125): call_user_func_array(Array, Array)
      8. #3 /usr/share/php/openmediavault/rpc.inc(79): OMVRpcServiceAbstract->callMethod('delete', Array, Array)
      9. #4 /usr/share/openmediavault/engined/rpc/filesystemmgmt.inc(959): OMVRpc::exec('FsTab', 'delete', Array, Array)
      10. #5 [internal function]: OMVRpcServiceFileSystemMgmt->umount(Array, Array)
      11. #6 /usr/share/php/openmediavault/rpcservice.inc(125): call_user_func_array(Array, Array)
      12. #7 /usr/share/php/openmediavault/rpc.inc(79): OMVRpcServiceAbstract->callMethod('umount', Array, Array)
      13. #8 /usr/sbin/omv-engined(500): OMVRpc::exec('FileSystemMgmt', 'umount', Array, Array, 1)
      14. #9 {main}
      Display All


      [edit] Forgot to say, that I basically can't unmount the USB disk anymore...[/edit]

      I am assuming it has something to do with the latest updates, because last week everything was working like a charm.

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

    • I shutdown the server, disconnected the USB drive and then restarted the server.

      When trying to mount the USB HD I get the following error now:

      Source Code

      1. Failed to mount '/dev/disk/by-uuid/0294023894022EAB': [mntent]: line 1 in /etc/fstab is bad [mntent]: line 21 in /etc/fstab is bad Failed to write lock '/dev/sde1': Resource temporarily unavailable Error opening '/dev/sde1': Resource temporarily unavailable Failed to mount '/dev/sde1': Resource temporarily unavailable
    • Ok. omv writes to fstab if the drive is mounted, and deletes the entry if the drive is unmounted. With that NTFS drive unplugged from the system edit the file in CLI with:
      nano /etc/fstab, look for the entries for NTFS drives and delete them. NTFS drives look like this in fstab, they have a shorter UUID, different from the ones native in linux

      /dev/disk/by-uuid/550EB77E650BEE9E /media/550EB77E650BEE9E ntfs defaults,nofail 0 2, once edited, reboot the system, and once running plug your drive.

      Make sure youre running OMV 1.1. There were some patches added to OMV lately to improve ntfs drive handling
      New wiki
      chat support at #openmediavault@freenode IRC | Spanish & English | GMT+10
      telegram.me/openmediavault broadcast channel
      openmediavault discord server
    • a umount command is umount /media/0294023894022EAB or in general for OMV umount /media/[UUID] or any other modern linux system.

      Those commands will totally fail if there is a resource in use for the drive, like a shared folder or a program accessing a file from the drive
      New wiki
      chat support at #openmediavault@freenode IRC | Spanish & English | GMT+10
      telegram.me/openmediavault broadcast channel
      openmediavault discord server
    • OK, so unmounted the USB HDD, I went into fstab with nano, I deleted the two NFTS entries and now my fstab looks like this:

      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. # / was on /dev/sda1 during installation
      10. UUID=45d5cabe-bea7-4056-8386-4003fe129933 / ext4 errors=remount-ro 0 1
      11. # swap was on /dev/sda5 during installation
      12. UUID=0bc58b70-2493-435f-b00e-e82f552146c6 none swap sw 0 0
      13. /dev/sdb1 /media/usb0 auto rw,user,noauto 0 0
      14. tmpfs /tmp tmpfs defaults 0 0
      15. # >>> [openmediavault]
      16. UUID=4107a386-6776-479f-823e-d38dba9bc5b9 /media/4107a386-6776-479f-823e-d38dba9bc5b9 ext4 defaults,acl,user_xattr,noexec,us$
      17. UUID=f681cb50-2239-4b87-9006-a639de982087 /media/f681cb50-2239-4b87-9006-a639de982087 ext4 defaults,nofail,acl,user_xattr,no$
      18. # <<< [openmediavault]
      Display All


      I rebooted and confirmed the fstab, still looking like above (just to make sure I did it right). I can also confirm that I am running 1.1 (Krazlic).

      When I tried to mount the USB drive I am now getting this:

      Source Code

      1. Failed to mount '/dev/disk/by-uuid/0294023894022EAB': [mntent]: line 1 in /etc/fstab is bad mount: no such partition found
      2. Error #6000:
      3. exception 'OMVException' with message 'Failed to mount '/dev/disk/by-uuid/0294023894022EAB': [mntent]: line 1 in /etc/fstab is bad
      4. mount: no such partition found' in /usr/share/openmediavault/engined/rpc/filesystemmgmt.inc:887
      5. Stack trace:
      6. #0 [internal function]: OMVRpcServiceFileSystemMgmt->mount(Array, Array)
      7. #1 /usr/share/php/openmediavault/rpcservice.inc(125): call_user_func_array(Array, Array)
      8. #2 /usr/share/php/openmediavault/rpc.inc(79): OMVRpcServiceAbstract->callMethod('mount', Array, Array)
      9. #3 /usr/sbin/omv-engined(500): OMVRpc::exec('FileSystemMgmt', 'mount', Array, Array, 1)
      10. #4 {main}
      Display All
    • OK, I was reading through the error messages as well trying to find out what the exactly mean. I also saw that there was an error for line 1 and I tried to figure out what it was.

      ​You've or someone else


      Na, unfortunately can't blame anyone else. Must have been me.

      Not to sude to fiddle with those things like nano I probably deleted the #.

      Added the # back in, saved the fstab and am currently rebooting. Will give more feedback once the server is back...
    • So, server is back, plugged in the USB drive, shows up in the GUI as /dev/sde1 like before.

      When selecting it and then go for "mount" I am getting the following error message:

      Source Code

      1. Failed to mount '/dev/disk/by-uuid/0294023894022EAB': mount: no such partition found
      2. Error #6000:
      3. exception 'OMVException' with message 'Failed to mount '/dev/disk/by-uuid/0294023894022EAB': mount: no such partition found' in /usr/share/openmediavault/engined/rpc/filesystemmgmt.inc:887
      4. Stack trace:
      5. #0 [internal function]: OMVRpcServiceFileSystemMgmt->mount(Array, Array)
      6. #1 /usr/share/php/openmediavault/rpcservice.inc(125): call_user_func_array(Array, Array)
      7. #2 /usr/share/php/openmediavault/rpc.inc(79): OMVRpcServiceAbstract->callMethod('mount', Array, Array)
      8. #3 /usr/sbin/omv-engined(500): OMVRpc::exec('FileSystemMgmt', 'mount', Array, Array, 1)
      9. #4 {main}
    • OK, did some research and found out that I need to put /sbin/ before.

      Source Code

      1. root@pdb-matrix:~# /sbin/blkid
      2. /dev/md127: LABEL="RAID1" UUID="4107a386-6776-479f-823e-d38dba9bc5b9" TYPE="ext4"
      3. /dev/sda1: UUID="45d5cabe-bea7-4056-8386-4003fe129933" TYPE="ext4"
      4. /dev/sda5: UUID="0bc58b70-2493-435f-b00e-e82f552146c6" TYPE="swap"
      5. /dev/sdd1: LABEL="BACKUPINTERNAL" UUID="f681cb50-2239-4b87-9006-a639de982087" TYPE="ext4"
      6. /dev/sdc: UUID="85c070e3-0215-692c-f667-e7dc78abd5b2" LABEL="openmediavault:raid1" TYPE="linux_raid_member" UUID_SUB="f40370f1-2143-7d2c-18da-2f85c1c2c5b7"
      7. /dev/sdb: UUID="85c070e3-0215-692c-f667-e7dc78abd5b2" LABEL="openmediavault:raid1" TYPE="linux_raid_member" UUID_SUB="280f3d31-6b2c-07d8-8ac0-fe4757c33655"
      8. /dev/sde1: LABEL="pdb-backup-ext02-seagate-expan" UUID="0294023894022EAB" TYPE="ntfs"
    • subzero79 wrote:

      What!? no way

      try again please just blkid in the terminal

      @ berritorre:
      The command \342\200\213blkid is wrong, it is just blkid. If this doesn't wrk, please post the whole CLI output, because then there is something really weird going on in your system.
      "Glowing days. Don't cry because they are over. Smile because they happened." - Confucius

      Server: 1x 32GB SSD (system) - 5x 2TB Data - 1x 2TB Snapraid-Parity - latest OMV 1.x
      No Support through PM
      Tutorials --- Howto install OMV-Extras --- Upgrade/Update-Problems --- If autoshutdown doesn' -work
    • Solo0815 wrote:

      something really weird going on in your system.



      I'd had a chat the other in IRC with a user with similar problems and ntfs drives, not even applying the ntfs patch before it was released to public could make it work He could only get it to work by resetting the UUID in ntfs, and that means writing to mbr with dd
      New wiki
      chat support at #openmediavault@freenode IRC | Spanish & English | GMT+10
      telegram.me/openmediavault broadcast channel
      openmediavault discord server
    • writing the mbr with dd is very dangerous, if you don't know, what you are doing ;(
      Is there another solution for the "normal users"?
      "Glowing days. Don't cry because they are over. Smile because they happened." - Confucius

      Server: 1x 32GB SSD (system) - 5x 2TB Data - 1x 2TB Snapraid-Parity - latest OMV 1.x
      No Support through PM
      Tutorials --- Howto install OMV-Extras --- Upgrade/Update-Problems --- If autoshutdown doesn' -work