Hdd going missing. Getting Communication Failure

    • OMV 2.x
    • Resolved

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

    • Hdd going missing. Getting Communication Failure

      I have been following a few guides to set up my OMV.
      I have a number of drives and since yesterday when I updated through the update manager, I have been getting two distinct issues. First is that this particular ntfs external hdd goes missing at boot time, shows up in the gui lists under storage/physical drives, storage/file systems.
      I then copy some files from it into the pool and a little bit afterwards, the hdd disappears.
      When I browsed through some of the hdd related forum posts, they advise running some scripts which I did. They also advised updating the kernel to the latest so I did that as well.
      I am now running 3.1.6 and have also installed the backports although I have no clue what that does. It was just advise I saw in the forums that seemed to help.
      My suspicion is that my fstab is not correct but I don't know how to repair it.
      When I go into the storage function, there are two hdd missing and again I think it is the fstab.
      I suspect that if I correct the missing errors, the other issues will resolve itself - at least I hope so.
      So here are the codes I have run:

      Source Code

      1. omv-mkconf fstab
      2. mount -a


      I don't know the result of that becuase I am stil getting the errors when I reboot.

      I ran blkid and got this:


      Source Code

      1. root@omv:~# blkid
      2. /dev/sda1: UUID="36925b35-1ff6-4a4b-bfbd-eee22a79b644" TYPE="ext4"
      3. /dev/sda5: UUID="e61448b7-cd92-4cff-9c14-e9aa2fd2ead0" TYPE="swap"
      4. /dev/sr0: LABEL="ESYNIC" TYPE="iso9660"
      5. /dev/sdf1: LABEL="PassportVMS" UUID="F474B7AA74B76DCC" TYPE="ntfs"
      6. /dev/sdg1: LABEL="MyBook500GB" UUID="3E027FB3027F6F31" TYPE="ntfs"
      7. /dev/sdj1: LABEL="PassportHDD" UUID="01D05435239BD740" TYPE="ntfs"
      8. /dev/sdb1: LABEL="Horntekk3" UUID="db5d0e3c-b56f-4e00-9f7d-a2965c3bc1b9" TYPE="ext4"
      9. /dev/sdc1: LABEL="Horntekk2" UUID="b0e1c7dc-56ad-48ca-a980-e59231da4036" TYPE="ext4"
      10. /dev/sdd1: LABEL="Horntekk1" UUID="b0f7900f-891b-47a4-b1ab-2956e09300ee" TYPE="ext4"
      11. /dev/sde1: LABEL="Horntekk4" UUID="c6dce86b-f3ee-4251-b33a-d76a8f95707d" TYPE="ext4"
      12. /dev/sdh1: LABEL="My Passport" UUID="54D8D96AD8D94ABE" TYPE="ntfs"
      13. /dev/sdi1: LABEL="WDGreenUSB" UUID="74cc1a04-7b0b-4a00-8fe1-3f2c98538ed6" TYPE="ext4"
      Display All


      From this, the hdd does not show up in the list.

      I ran dmesg | tail and got this:

      Source Code

      1. [ 210.735033] sd 14:0:0:0: Attached scsi generic sg15 type 0
      2. [ 210.735763] sd 14:0:0:0: [sdk] 732566645 4096-byte logical blocks: (3.00 TB/2.72 TiB)
      3. [ 210.736761] sd 14:0:0:0: [sdk] Write Protect is off
      4. [ 210.736767] sd 14:0:0:0: [sdk] Mode Sense: 28 00 00 00
      5. [ 210.737893] sd 14:0:0:0: [sdk] No Caching mode page found
      6. [ 210.737938] sd 14:0:0:0: [sdk] Assuming drive cache: write through
      7. [ 210.738764] sd 14:0:0:0: [sdk] 732566645 4096-byte logical blocks: (3.00 TB/2.72 TiB)
      8. [ 210.804539] sdk: sdk1
      9. [ 210.806263] sd 14:0:0:0: [sdk] 732566645 4096-byte logical blocks: (3.00 TB/2.72 TiB)
      10. [ 210.808635] sd 14:0:0:0: [sdk] Attached SCSI disk



      I ran cat /etc/fstab and got these:

      Source Code

      1. cat /etc/fstab
      2. # /etc/fstab: static file system information.
      3. #
      4. # Use 'blkid' to print the universally unique identifier for a
      5. # device; this may be used with UUID= as a more robust way to name devices
      6. # that works even if disks are added and removed. See fstab(5).
      7. #
      8. # <file system> <mount point> <type> <options> <dump> <pass>
      9. # / was on /dev/sda1 during installation
      10. UUID=36925b35-1ff6-4a4b-bfbd-eee22a79b644 / ext4 errors=remount-ro 0 1
      11. # swap was on /dev/sda5 during installation
      12. UUID=e61448b7-cd92-4cff-9c14-e9aa2fd2ead0 none swap sw 0 0
      13. /dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0
      14. # >>> [openmediavault]
      15. /dev/disk/by-uuid/54D8D96AD8D94ABE /media/54D8D96AD8D94ABE ntfs defaults,nofail 0 2
      16. /dev/disk/by-uuid/F474B7AA74B76DCC /media/F474B7AA74B76DCC ntfs defaults,nofail 0 2
      17. /dev/disk/by-uuid/1EC8EA4AC8EA1FAF /media/1EC8EA4AC8EA1FAF ntfs defaults,nofail 0 2
      18. /dev/disk/by-uuid/3E027FB3027F6F31 /media/3E027FB3027F6F31 ntfs defaults,nofail 0 2
      19. UUID=b0e1c7dc-56ad-48ca-a980-e59231da4036 /media/b0e1c7dc-56ad-48ca-a980-e59231da4036 ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
      20. UUID=a356eaa4-6d13-4d84-8559-bf75a2f0153a /media/a356eaa4-6d13-4d84-8559-bf75a2f0153a ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
      21. UUID=c6dce86b-f3ee-4251-b33a-d76a8f95707d /media/c6dce86b-f3ee-4251-b33a-d76a8f95707d ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
      22. UUID=b0f7900f-891b-47a4-b1ab-2956e09300ee /media/b0f7900f-891b-47a4-b1ab-2956e09300ee ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
      23. /dev/disk/by-uuid/01D05435239BD740 /media/01D05435239BD740 ntfs defaults,nofail 0 2
      24. UUID=74cc1a04-7b0b-4a00-8fe1-3f2c98538ed6 /media/74cc1a04-7b0b-4a00-8fe1-3f2c98538ed6 ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
      25. UUID=db5d0e3c-b56f-4e00-9f7d-a2965c3bc1b9 /media/db5d0e3c-b56f-4e00-9f7d-a2965c3bc1b9 ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
      26. none /media/632148d8-b738-4587-b75a-60041ffae832 aufs br:/media/b0e1c7dc-56ad-48ca-a980-e59231da4036=rw:/media/b0f7900f-891b-47a4-b1ab-2956e09300ee=rw:/media/c6dce86b-f3ee-4251-b33a-d76a8f95707d=rw:/media/F474B7AA74B76DCC=rw:/media/3E027FB3027F6F31=rw:/media/01D05435239BD740=rw:/media/74cc1a04-7b0b-4a00-8fe1-3f2c98538ed6=rw:/media/db5d0e3c-b56f-4e00-9f7d-a2965c3bc1b9=rw,sum,create=tdp 0 0
      27. # <<< [openmediavault]
      Display All


      I also ran cat /etc/openmediavault/config.xml. The results were so long I could not post this so I attached it as part of the code.txt.

      Initially I enabled NFS and after browsing some forum posts, it appears that at times NFS creates communication failure errors so I disabled it and deleted the share. The communication failure stooped and restarted.
      Initially when I get the communication failure error, I reboot and it goes away. Now it does not go away and stays.

      I also took screen shots of the omv gui with the errors.





      "C:\Users\User\SkyDrive\NOOBS Pi\NAS Storage File Systems- Later.JPG"





      Can anyone help me repair the damage? I don't want to reinstall the OMV all over.
      The hdd that goes missing is the HDDZ800BACKUP disk.
      I need the ntfs disks because I have a windows pc that I use frequently. The OMV was to centralise all my data in one place.
      Please can you help?
      Images
      • NAS Storage Communication Failure.JPG

        107.16 kB, 1,282×733, viewed 228 times
      • NAS Storage File Systems- Later.JPG

        165.15 kB, 1,282×733, viewed 224 times
      • NAS Storage File Systems.JPG

        92.03 kB, 1,066×533, viewed 205 times
      • NAS Storage Physical Disks.JPG

        69.75 kB, 1,073×527, viewed 176 times
      Files
      • Code.txt

        (70.06 kB, downloaded 325 times, last: )
      I have donated. have you?
      OMV 2.2 running on HP Gen 8 G1610T server, 16GB RAM + Xeon E3-1220
    • Lspci code ran

      I also ran the lspci code and got the following:

      Source Code

      1. root@omv:~# lspci
      2. 00:00.0 Host bridge: Intel Corporation 4 Series Chipset DRAM Controller (rev 03)
      3. 00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03)
      4. 00:02.1 Display controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03)
      5. 00:03.0 Communication controller: Intel Corporation 4 Series Chipset HECI Controller (rev 03)
      6. 00:03.2 IDE interface: Intel Corporation 4 Series Chipset PT IDER Controller (rev 03)
      7. 00:03.3 Serial controller: Intel Corporation 4 Series Chipset Serial KT Controller (rev 03)
      8. 00:19.0 Ethernet controller: Intel Corporation 82567LM-3 Gigabit Network Connection (rev 02)
      9. 00:1a.0 USB controller: Intel Corporation 82801JD/DO (ICH10 Family) USB UHCI Controller #4 (rev 02)
      10. 00:1a.1 USB controller: Intel Corporation 82801JD/DO (ICH10 Family) USB UHCI Controller #5 (rev 02)
      11. 00:1a.2 USB controller: Intel Corporation 82801JD/DO (ICH10 Family) USB UHCI Controller #6 (rev 02)
      12. 00:1a.7 USB controller: Intel Corporation 82801JD/DO (ICH10 Family) USB2 EHCI Controller #2 (rev 02)
      13. 00:1b.0 Audio device: Intel Corporation 82801JD/DO (ICH10 Family) HD Audio Controller (rev 02)
      14. 00:1c.0 PCI bridge: Intel Corporation 82801JD/DO (ICH10 Family) PCI Express Port 1 (rev 02)
      15. 00:1c.1 PCI bridge: Intel Corporation 82801JD/DO (ICH10 Family) PCI Express Port 2 (rev 02)
      16. 00:1d.0 USB controller: Intel Corporation 82801JD/DO (ICH10 Family) USB UHCI Controller #1 (rev 02)
      17. 00:1d.1 USB controller: Intel Corporation 82801JD/DO (ICH10 Family) USB UHCI Controller #2 (rev 02)
      18. 00:1d.2 USB controller: Intel Corporation 82801JD/DO (ICH10 Family) USB UHCI Controller #3 (rev 02)
      19. 00:1d.7 USB controller: Intel Corporation 82801JD/DO (ICH10 Family) USB2 EHCI Controller #1 (rev 02)
      20. 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a2)
      21. 00:1f.0 ISA bridge: Intel Corporation 82801JD (ICH10D) LPC Interface Controller (rev 02)
      22. 00:1f.2 SATA controller: Intel Corporation 82801JD/DO (ICH10 Family) SATA AHCI Controller (rev 02)
      23. 00:1f.3 SMBus: Intel Corporation 82801JD/DO (ICH10 Family) SMBus Controller (rev 02)
      Display All
      I have donated. have you?
      OMV 2.2 running on HP Gen 8 G1610T server, 16GB RAM + Xeon E3-1220
    • Those ntfs drives are they permanent drives ? If they are, consider to switch them to ext4.
      Depending on the system specs it could be normal to have timeout issues with web framework trying to parse information for a large number of drives.
      you can try increasing the timeout value, I can't remember now but I can try to give you the hint later for changing that in the terminal.
      chat support at #openmediavault@freenode IRC | Spanish & English | GMT+10
      telegram.me/openmediavault broadcast channel
      openmediavault discord server
    • Yes the ntfs drives are permanent drives to be used with the windows pc.
      I was planning on centralising the data from them into ext4 drives but I have been unable because they keep disappearing.
      Also I am now getting Ngnix related errors as follows:


      <html>
      <head><title>502 Bad Gateway</title></head>
      <body bgcolor="white">
      <center><h1>502 Bad Gateway</h1></center>
      <hr><center>nginx</center>
      </body>
      </html>
      <!-- a padding to disable MSIE and Chrome friendly error page -->
      <!-- a padding to disable MSIE and Chrome friendly error page -->
      <!-- a padding to disable MSIE and Chrome friendly error page -->
      <!-- a padding to disable MSIE and Chrome friendly error page -->
      <!-- a padding to disable MSIE and Chrome friendly error page -->
      <!-- a padding to disable MSIE and


      So disable Ngnix for now?
      I also read somewhere here that a wrong email id can create these issues so I want to switch off the the bit that emails me - can't remember where they are but I am working through the menu.
      I have donated. have you?
      OMV 2.2 running on HP Gen 8 G1610T server, 16GB RAM + Xeon E3-1220
    • I rebooted because I could not get any work done with the error.
      I am now getting this new error:


      Failed to execute command 'omv-mkconf remoteshare 2>&1': ntfs-3g: Failed to access volume '/dev/disk/by-uuid/1EC8EA4AC8EA1FAF': No such file or directory ntfs-3g 2012.1.15AR.5 external FUSE 29 - 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-2011 Jean-Pierre Andre Copyright (C) 2009 Erik Larsson Usage: ntfs-3g [-o option[,...]] Options: ro (read-only mount), remove_hiberfile, 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 Retrying with upper case share name mount error(6): No such device or address Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)


      Error #4000:
      exception 'OMVException' with message 'Failed to execute command 'omv-mkconf remoteshare 2>&1': ntfs-3g: Failed to access volume '/dev/disk/by-uuid/1EC8EA4AC8EA1FAF': No such file or directory

      ntfs-3g 2012.1.15AR.5 external FUSE 29 - 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-2011 Jean-Pierre Andre
      Copyright (C) 2009 Erik Larsson

      Usage: ntfs-3g [-o option[,...]] <device|image_file> <mount_point>

      Options: ro (read-only mount), remove_hiberfile, 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
      Retrying with upper case share name
      mount error(6): No such device or address
      Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)' in /usr/share/openmediavault/engined/module/remoteshare.inc:101
      Stack trace:
      #0 /usr/share/openmediavault/engined/rpc/config.inc(180): OMVModuleRemoteShare->applyConfig()
      #1 [internal function]: OMVRpcServiceConfig->applyChanges(Array, Array)
      #2 /usr/share/php/openmediavault/rpcservice.inc(125): call_user_func_array(Array, Array)
      #3 /usr/share/php/openmediavault/rpcservice.inc(158): OMVRpcServiceAbstract->callMethod('applyChanges', Array, Array)
      #4 /usr/share/openmediavault/engined/rpc/config.inc(224): OMVRpcServiceAbstract->callMethodBg('applyChanges', Array, Array)
      #5 [internal function]: OMVRpcServiceConfig->applyChangesBg(Array, Array)
      #6 /usr/share/php/openmediavault/rpcservice.inc(125): call_user_func_array(Array, Array)
      #7 /usr/share/php/openmediavault/rpc.inc(79): OMVRpcServiceAbstract->callMethod('applyChangesBg', Array, Array)
      #8 /usr/sbin/omv-engined(500): OMVRpc::exec('Config', 'applyChangesBg', Array, Array, 1)
      #9 {main}
      I have donated. have you?
      OMV 2.2 running on HP Gen 8 G1610T server, 16GB RAM + Xeon E3-1220
    • Ok. What I have done is disable all but the necessary services.
      I have also disabled the notifications so hopefully, the communication error will stop.
      I will appreciate some assistance with the hdd problem as it keeps happening.
      I need to have access to the ntfs hdd to copy the files to ext4 before I can stop using them.
      Any ideas?
      I have donated. have you?
      OMV 2.2 running on HP Gen 8 G1610T server, 16GB RAM + Xeon E3-1220
    • I apologise. I thought they had been answered.
      Oh I didn't see that. Yes they are connected to the NAS box via a powered hub. Actually 4 of these drives are connected via this powered hub. Another two are connected to the NAS box via usb ports at the back of the box. The problematic ones are connected via both methods i.e. via the hub and via the ports at the back. There is no consistency. I have however ordered another powered hub to see if I can separate them.
      The drives in question are these drives: amazon.co.uk/gp/product/B00YRB…oh_aui_detailpage_o09_s00 (WD Ultra 2TB external drive) and the 3TB version although the 3TB has not given any problematic indication.
      Thanks for your time. I appreciate it.
      I have donated. have you?
      OMV 2.2 running on HP Gen 8 G1610T server, 16GB RAM + Xeon E3-1220

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

    • Well i would try to separate them from the hub. Keep two in the hub, and place another two in another non shared usb port on the back or whatever
      Try testing them moving them around, the hub might not supply enough amperage so disks come an go.
      chat support at #openmediavault@freenode IRC | Spanish & English | GMT+10
      telegram.me/openmediavault broadcast channel
      openmediavault discord server
    • You were right. I had already purchased another powered hub so I split them into two groups. Now I can see all the hdds. Thanks.
      Please I need to ask. Is there a detailed how to set up Nginx? There were some options I don't get and each time I try to set it up, I get the same communication errors.
      Or should I mark this solved and open another thread?
      Once again, many thanks. I appreciate the assistance.
      I have donated. have you?
      OMV 2.2 running on HP Gen 8 G1610T server, 16GB RAM + Xeon E3-1220
    • I'm sorry I didn't see this. I was so frustrated I eventually re-installed OMV although I am still getting problems with my USB/ext4 mounted drives but I have not installed the NginX plugin. I am having too many issues with OMV to go further than install and reinstall.
      Thanks anyway.
      I have donated. have you?
      OMV 2.2 running on HP Gen 8 G1610T server, 16GB RAM + Xeon E3-1220