USB 3.0 Drive not mounting

    • OMV 2.x

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

    • USB 3.0 Drive not mounting

      This worked yesterday. I have an external USB 3.0 drive I am trying to use to backup data. It was connected yesterday, and did backup some files. I was using rsync to copy from the data drive to this USB drive. I was getting i/o erros, so was trying the cp command to try and copy the files. All of a sudden the drive unmounts itself and now I am getting errors trying to mount it.

      Aug 3 09:17:45 openmediavault kernel: [82062.157366] EXT4-fs warning (device sdu1): ext4_end_bio:250: I/O error -5 writing to inode 21757975 (offset 1492402176 size 126976 starting block 1091681)
      Aug 3 09:17:45 openmediavault kernel: [82062.157431] EXT4-fs warning (device sdu1): ext4_end_bio:250: I/O error -5 writing to inode 21757975 (offset 1492525056 size 126976 starting block 1091711)
      Aug 3 09:17:45 openmediavault kernel: [82062.157498] EXT4-fs warning (device sdu1): ext4_end_bio:250: I/O error -5 writing to inode 21757975 (offset 1492647936 size 126976 starting block 1091741)
      Aug 3 09:17:45 openmediavault kernel: [82062.157562] EXT4-fs warning (device sdu1): ext4_end_bio:250: I/O error -5 writing to inode 21757975 (offset 1492770816 size 126976 starting block 1091771)
      Aug 3 09:17:45 openmediavault kernel: [82062.157655] EXT4-fs warning (device sdu1): ext4_end_bio:250: I/O error -5 writing to inode 21757975 (offset 1492893696 size 126976 starting block 1091801)
      Aug 3 09:17:45 openmediavault kernel: [82062.157724] EXT4-fs warning (device sdu1): ext4_end_bio:250: I/O error -5 writing to inode 21757975 (offset 1493016576 size 126976 starting block 1091831)
      Aug 3 09:17:45 openmediavault kernel: [82062.157746] EXT4-fs warning (device sdu1): ext4_end_bio:250: I/O error -5 writing to inode 21757975 (offset 1493139456 size 32768 starting block 1091839)
      Aug 3 09:17:45 openmediavault kernel: [82062.449509] JBD2: Detected IO errors while flushing file data on sdu1-8
      Aug 3 09:17:46 openmediavault kernel: [82062.801790] xhci_hcd 0000:04:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff88081262f8c0
      Aug 3 09:17:46 openmediavault kernel: [82062.801795] xhci_hcd 0000:04:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff88081262f900
    • I tried. Keeps saying it is mounted or in use.

      root@openmediavault:/media/1b93e728-c5cb-4fb0-b1e3-401e2fdf0e45# fsck.ext4 -f /dev/sdu1
      e2fsck 1.42.5 (29-Jul-2012)
      Warning! /dev/sdu1 is mounted.
      fsck.ext4: No such file or directory while trying to open /dev/sdu1
      Possibly non-existent device?
      root@openmediavault:/media/1b93e728-c5cb-4fb0-b1e3-401e2fdf0e45# umount /dev/sdu1
      umount: /media/c750116e-5331-4aaf-b493-029383305939: device is busy.
      (In some cases useful info about processes that use
      the device is found by lsof(8) or fuser(1))

      Does not show in OMV as being mounted.
    • You either need to stop the services using the drive (lsof will tell you which ones) and unmount it -or- boot another distro like systemrescuecd and fsck it.
      omv 4.1.11 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.11
      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!
    • Aaaaannnnd the saga continues. Overnight the drive quit showing up in OMV Physical drives and file systems. However, I can see the share and work with it in windows. I removed the drive, the reconnected it and got the same errors. Again I could not see it in OMV, but the share returned with all the data in place. How is that possible??
    • So as a work around, I have a scheduled task that runs daily just before I want to copy data to the USB 3.0 drive. It restarts the USB bus which in turn fixes the drive mount issue. The only other thing I wish I could figure out was how to run an hourly task to monitor the USB ports for the drop out of this drive, and then run the remount script. I know how to reset the USB ports, just not how to check for the drive not functioning.