What is the correct way to automount a usb 3.0 external hard disk on an already running server?

    • OMV 3.x
    • Resolved
    • What is the correct way to automount a usb 3.0 external hard disk on an already running server?

      As the title say, I'm trying to understand the correct way to auto mount a couple of hard disks mounted as ntfs and ext4 to a server already running, without the need to reboot (so I guess no fstab).

      I'm thinking to install usbmount package:

      Source Code

      1. usbmount/oldstable 0.0.22 all
      2. automatically mount and unmount USB mass storage devices

      I'm looking to be able to automount external hard disk of 1tb and up through usb2.0\3.0 to use in conjunction with usbbackup plugin and standalone to transfer files between omv and the hard disk.


      But it seems to not support ntfs out of the box (maybe achievable through the conf file)

      Am I missing some other way to correctly do it? I thought omv would automount by itself, for using it with usbbackup plugin, but it does not, it doesn't see my external hard disk at all if plugged through usb3.0.
      Any help on the matter would be very appreciated.

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

    • the usbbackup plugin does automount on plug, and unmount on job termination. Strange that it doesn't pick up. Does dmesg show the disk on plug?

      The other option would be to use autofs, which triggers the mount command on folder access. Obviously the disk needs to be present to work,
      New wiki
      chat support at #openmediavault@freenode IRC | Spanish & English | GMT+10
      telegram.me/openmediavault broadcast channel
      openmediavault discord server
    • Hi @subzero79

      I tried to reboot omv and replug the external 1tb hard drive onto the usb 3.0 port formatted with ext4 once booted up.

      here's my lsusb and dmesg grep, strange enough lsusb shows as everything is empty

      Source Code

      1. root@omv:~# lsusb
      2. Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
      3. Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
      4. Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
      5. Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
      6. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
      7. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
      8. Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
      9. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
      10. root@omv:~# dmesg | grep -i usb
      11. [ 1.508970] ACPI: bus type USB registered
      12. [ 1.509026] usbcore: registered new interface driver usbfs
      13. [ 1.509048] usbcore: registered new interface driver hub
      14. [ 1.510535] usbcore: registered new device driver usb
      15. [ 1.512095] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
      16. [ 1.513100] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
      17. [ 1.513501] xhci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 1
      18. [ 1.515043] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
      19. [ 1.515046] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
      20. [ 1.515048] usb usb1: Product: xHCI Host Controller
      21. [ 1.515050] usb usb1: Manufacturer: Linux 4.9.0-0.bpo.3-amd64 xhci-hcd
      22. [ 1.515052] usb usb1: SerialNumber: 0000:00:10.0
      23. [ 1.515287] hub 1-0:1.0: USB hub found
      24. [ 1.515498] xhci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 2
      25. [ 1.517115] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
      26. [ 1.517171] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003
      27. [ 1.517173] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
      28. [ 1.517175] usb usb2: Product: xHCI Host Controller
      29. [ 1.517177] usb usb2: Manufacturer: Linux 4.9.0-0.bpo.3-amd64 xhci-hcd
      30. [ 1.517179] usb usb2: SerialNumber: 0000:00:10.0
      31. [ 1.517408] hub 2-0:1.0: USB hub found
      32. [ 1.518284] xhci_hcd 0000:03:00.0: new USB bus registered, assigned bus number 3
      33. [ 1.579006] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002
      34. [ 1.579008] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
      35. [ 1.579010] usb usb3: Product: xHCI Host Controller
      36. [ 1.579012] usb usb3: Manufacturer: Linux 4.9.0-0.bpo.3-amd64 xhci-hcd
      37. [ 1.579014] usb usb3: SerialNumber: 0000:03:00.0
      38. [ 1.579268] hub 3-0:1.0: USB hub found
      39. [ 1.579483] xhci_hcd 0000:03:00.0: new USB bus registered, assigned bus number 4
      40. [ 1.579507] ehci-pci 0000:00:12.2: new USB bus registered, assigned bus number 5
      41. [ 1.579536] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.
      42. [ 1.579572] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003
      43. [ 1.579574] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
      44. [ 1.579578] usb usb4: Product: xHCI Host Controller
      45. [ 1.579580] usb usb4: Manufacturer: Linux 4.9.0-0.bpo.3-amd64 xhci-hcd
      46. [ 1.579581] usb usb4: SerialNumber: 0000:03:00.0
      47. [ 1.579774] hub 4-0:1.0: USB hub found
      48. [ 1.591857] ehci-pci 0000:00:12.2: USB 2.0 started, EHCI 1.00
      49. [ 1.592066] usb usb5: New USB device found, idVendor=1d6b, idProduct=0002
      50. [ 1.592069] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
      51. [ 1.592071] usb usb5: Product: EHCI Host Controller
      52. [ 1.592073] usb usb5: Manufacturer: Linux 4.9.0-0.bpo.3-amd64 ehci_hcd
      53. [ 1.592074] usb usb5: SerialNumber: 0000:00:12.2
      54. [ 1.592354] hub 5-0:1.0: USB hub found
      55. [ 1.592860] ehci-pci 0000:00:13.2: new USB bus registered, assigned bus number 6
      56. [ 1.607854] ehci-pci 0000:00:13.2: USB 2.0 started, EHCI 1.00
      57. [ 1.608108] usb usb6: New USB device found, idVendor=1d6b, idProduct=0002
      58. [ 1.608111] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
      59. [ 1.608113] usb usb6: Product: EHCI Host Controller
      60. [ 1.608115] usb usb6: Manufacturer: Linux 4.9.0-0.bpo.3-amd64 ehci_hcd
      61. [ 1.608116] usb usb6: SerialNumber: 0000:00:13.2
      62. [ 1.608413] hub 6-0:1.0: USB hub found
      63. [ 1.610517] ohci-pci 0000:00:12.0: new USB bus registered, assigned bus number 7
      64. [ 1.671936] usb usb7: New USB device found, idVendor=1d6b, idProduct=0001
      65. [ 1.671940] usb usb7: New USB device strings: Mfr=3, Product=2, SerialNumber=1
      66. [ 1.671942] usb usb7: Product: OHCI PCI host controller
      67. [ 1.671944] usb usb7: Manufacturer: Linux 4.9.0-0.bpo.3-amd64 ohci_hcd
      68. [ 1.671946] usb usb7: SerialNumber: 0000:00:12.0
      69. [ 1.672289] hub 7-0:1.0: USB hub found
      70. [ 1.672731] ohci-pci 0000:00:13.0: new USB bus registered, assigned bus number 8
      71. [ 1.735935] usb usb8: New USB device found, idVendor=1d6b, idProduct=0001
      72. [ 1.735939] usb usb8: New USB device strings: Mfr=3, Product=2, SerialNumber=1
      73. [ 1.735941] usb usb8: Product: OHCI PCI host controller
      74. [ 1.735943] usb usb8: Manufacturer: Linux 4.9.0-0.bpo.3-amd64 ohci_hcd
      75. [ 1.735945] usb usb8: SerialNumber: 0000:00:13.0
      76. [ 1.736285] hub 8-0:1.0: USB hub found
      77. [ 186.212924] usb 2-1: new SuperSpeed USB device number 2 using xhci_hcd
      78. [ 186.238548] usb 2-1: device descriptor read/8, error -71
      79. [ 186.343498] usb 2-1: new SuperSpeed USB device number 2 using xhci_hcd
      80. [ 186.364567] usb 2-1: device descriptor read/8, error -71
      81. [ 197.395298] usb 2-1: device not accepting address 3, error -62
      82. [ 208.403079] usb 2-1: device not accepting address 4, error -62
      83. [ 219.410874] usb 2-1: device not accepting address 5, error -62
      84. [ 219.438798] usb usb2-port1: unable to enumerate USB device
      85. root@omv:~#
      Display All
    • Wek wrote:

      strange enough lsusb shows as everything is empty
      If this is not an USB-C port but type A you most probably simply should blame the guys who invented this crappy connector. Get some alcohol, get cotton swabs, clean the SuperSpeed data lines, try again. If it still not works, check/replace cables/connectors.

      Alternatively connect the external disk to an USB2 port, the mechanical design of the Hi-Speed data lines is magnitudes less error prone compared to the SS/SS+ type A mess.
    • @subzero79 and @tkaiser

      Now it's even more strange..I was playing around with the other usb ports...after I plugged it to the usb2.0 automount worked out...so I thought maybe was the 3.0 usb damaged so I plugged it back to the 3.0 and now lsusb shows it aswell on the same 3.0 even so does usbbackup plugin ?(

      Source Code

      1. root@omv:~# lsusb
      2. Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
      3. Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
      4. Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
      5. Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
      6. Bus 002 Device 007: ID 067b:2773 Prolific Technology, Inc.
      7. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
      8. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
      9. Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
      10. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
      Display All
    • Wek wrote:

      I thought maybe was the 3.0 usb damaged
      You didn't answer whether it's a type A or C receptacle. At least I consider USB3-A being broken by design, it's a constant source of trouble, just search the forum for 'USB3 receptacle crappiness' ;)

      Please take this seriously, I would expect your next post dealing with 'xhci reset' dmesg output and maybe already data corruption.
    • @tkaiser sorry I just forgot to answer your question it's a type A usb, the hardware on that server is not really ultimate generation :D so type c unfortunately is excluded.

      I'm taking it seriously by the way don't worry I'm looking up what you posted

      Little edit:

      I think I found out what's going on, the external usb hard drive is one with an external power aswell, I noticed that if I FIRST plug the usb in and then Turn the switch on it works, it doesn't if I first turn it on and then insert the usb into the port...does it make any sense?

      I didn't thought about that because all my external hard drives are self powered through usb port but this one.
      But shouldn't it be the same when to plug in the usb?

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

    • Wek wrote:

      But shouldn't it be the same when to plug in the usb?
      Please look at your dmesg output above, the bridge appears at the USB bus but then $something goes wrong. I've no Prolific USB-to-SATA bridges around and therefore also no experiences with them since AFAIK they still have none that is UAS capable (USB Attached SCSI) which is a basic requirement for me to keep CPU utilization low and performance up (though doesn't matter that much with HDDs anyway).