External USB 3.0 drive is not mounting properly at reboot

    • OMV 1.0
    • External USB 3.0 drive is not mounting properly at reboot

      Hi,

      like some others in the forum I have the Problem that an external USB 3.0 drive is not mounted properly upon boot. I already set a delay of 10 in grub but this had no effect on the problem,

      My configuration is a Gigabyte BRIX w/ 8GB RAM and a 256GB transcend SSD and an external USB 3.0 HDD drive.

      On boot I get the following Messages:

      Source Code

      1. fsck.ext4: Unable to resolve 'UUID=8b136015-ed68-4f8c-a589-dd480adf1f5b'
      2. fsck died with exit status 8
      3. failed (code 8).
      4. File system check failed. A log is being saved in /var/log/fsck/checkfs if that location is writable. Please repair the file system manually. ... failed!
      5. A maintenance shell will now be started. CONTROL-D will terminate this shell and resume system boot. ... (warning).
      6. Give root password for maintenance
      7. (or type Control-D to continue):
      8. scsi 2:0:0:0: Direct-Access HGST 0000 PQ: 0 ANSI: 6
      9. sd 2:0:0:0: Attached scsi generic sg1 type 0
      10. sd 2:0:0:0: [sdb] 1953523708 512-byte logical blocks: (1.00 TB/931 GiB)
      11. sd 2:0:0:0: [sdb] Write Protect is off
      12. sd 2:0:0:0: [sdb] Mode Sense: 27 00 00 00
      13. sd 2:0:0:0: [sdb] No Caching mode page found
      14. sd 2:0:0:0: [sdb] Assuming drive cache: write through
      15. sd 2:0:0:0: [sdb] No Caching mode page found
      16. sd 2:0:0:0: [sdb] Assuming drive cache: write through
      17. sdb: sdb1 sdb2 sdb3
      18. sd 2:0:0:0: [sdb] No Caching mode page found
      19. sd 2:0:0:0: [sdb] Assuming drive cache: write through
      20. sd 2:0:0:0: [sdb] Attached SCSI disk
      Display All


      After these messages the boot stops, if I press CTRL + D the boot sequence resumes and all drives are mounted. How can I prevent pressing CTRL+D while booting?

      Best regards!

      Andy
    • That drive should be mounted nofail so that omv can continue booting. What version of OMV are you using? Did you try setting a delay in the bios/efi instead of grub?
      omv 4.1.14 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      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:

      That drive should be mounted nofail so that omv can continue booting.

      'nofail' is default mount option since long time.

      Can you post your /etc/fstab file here.
      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:

      'nofail' is default mount option since long time.

      I remember when you added it :) That is why I was shocked he had to use ctrl-d and asked what version of OMV he is using.
      omv 4.1.14 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      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!
    • Sorry for the late reply . . I am using OMV 1.1.

      Below you find my fstab:

      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. # / was on /dev/sda1 during installation
      9. UUID=bffa6b90-4752-4276-bcce-f524e316ce9e / ext4 errors=remount-ro 0 1
      10. # swap was on /dev/sda5 during installation
      11. UUID=ec059936-3964-4cbc-9a18-c13d3721ac62 none swap sw 0 0
      12. /dev/sdb1 /media/usb0 auto rw,user,noauto 0 0
      13. tmpfs /tmp tmpfs defaults 0 0
      14. # >>> [openmediavault]
      15. UUID=8b136015-ed68-4f8c-a589-dd480adf1f5b /media/8b136015-ed68-4f8c-a589-dd480adf1f5b ext4 defaults,nofail,acl,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqf$
      16. UUID=18fab38e-34fc-4eb2-b144-f163a3c0e005 /media/18fab38e-34fc-4eb2-b144-f163a3c0e005 ext4 defaults,nofail,acl,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqf$
      17. /media/8b136015-ed68-4f8c-a589-dd480adf1f5b/Multimedia /export/Multimedia none bind 0 0
      18. /media/8b136015-ed68-4f8c-a589-dd480adf1f5b/Public /export/Public none bind 0 0
      19. # <<< [openmediavault]
      Display All


      I also found out, that the speed of the external USB 3.0 drive is very very slow, do you have an idea, what can be the reason for that behaviour?

      Source Code

      1. /dev/sdb2:
      2. Timing O_DIRECT cached reads: 56 MB in 2.03 seconds = 27.55 MB/sec
      3. Timing O_DIRECT disk reads: 82 MB in 3.05 seconds = 26.84 MB/sec


      Best regards!

      Andy

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

    • Do you have the usb 3.0 plugged in a usb 3.0 port? If so, move it to a usb 2.0 port temporarily.
      omv 4.1.14 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      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!
    • I connected the HDD to a USB 2.0 port, now I wasn't force to press CTRL+D but the drives aren't mounted. I am forced to mount them manually via GUI.

      The disk speed is nearly the same as at the 3.0 port, really strange.

      Source Code

      1. /dev/sdb2:
      2. Timing O_DIRECT cached reads: 72 MB in 2.02 seconds = 35.67 MB/sec
      3. Timing O_DIRECT disk reads: 72 MB in 3.04 seconds = 23.72 MB/sec


      Andy
    • Maybe? I would upgrade to backports 3.16 kernel (installed using omv-extras) and see if it fixes the problem.
      omv 4.1.14 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      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!
    • I tried another HDD on the same port and the rates are 30% faster than with the other one. Also mounting on Startup worked without any problems. But I can not switch the drives as the first on is 1TB with lot of data and the 2nd is just 500GB. Any ideas?

      Source Code

      1. /dev/sdb2:
      2. Timing O_DIRECT cached reads: 76 MB in 2.04 seconds = 37.28 MB/sec
      3. Timing O_DIRECT disk reads: 110 MB in 3.02 seconds = 36.39 MB/sec
    • That is what I suggested a few posts ago. The 3.2 kernel doesn't seem to have very good usb 3.0 drivers.
      omv 4.1.14 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      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!
    • I tried several times booting backports but it stucks every time at the same point. Yes, DHCP is activated. I also tried with fixed values, but it was still the same.

      The Brix has also a PCI-E Wifi module included (Realtek 8723BE), but there seems to be no drivers, so I will try taking out the module tomorrow hoping that helps with 3.16.

      Regarding the USB 3.0 thing I also tried some research, but it confuses me. LSUSB is showing the 3.0 port as bus 003 but the drive to be connected on bus 001. An internal wiring error is impossible as the port is onboard.

      *lsusb*

      Source Code

      1. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
      2. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
      3. Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
      4. Bus 001 Device 002: ID 8087:07e6 Intel Corp.
      5. Bus 001 Device 003: ID 4971:1014 SimpleTech
      6. Bus 001 Device 004: ID 13d3:3410 IMC Networks
      7. Bus 001 Device 005: ID 2659:1210 Sundtek
      8. Bus 001 Device 006: ID 0425:0101 Motorola Semiconductors HK, Ltd G-Tech Wireless Mouse & Keyboard


      *usb-devices*

      Source Code

      1. T: Bus=01 Lev=02 Prnt=02 Port=00 Cnt=01 Dev#= 3 Spd=480 MxCh= 0
      2. D: Ver= 2.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
      3. P: Vendor=4971 ProdID=1014 Rev=00.00
      4. S: Manufacturer=HGST
      5. S: Product=Touro Mobile 3.0
      6. S: SerialNumber=21001312090002301604
      7. C: #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr=8mA
      8. I: If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage
      9. T: Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=5000 MxCh= 1
      10. D: Ver= 3.00 Cls=09(hub ) Sub=00 Prot=03 MxPS= 9 #Cfgs= 1
      11. P: Vendor=1d6b ProdID=0003 Rev=03.02
      12. S: Manufacturer=Linux 3.2.0-4-amd64 xhci_hcd
      13. S: Product=xHCI Host Controller
      14. S: SerialNumber=0000:00:14.0
      15. C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
      16. I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
      Display All