Multi-Port external storage box shows only one disk

    • OMV 3.x

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

    • Multi-Port external storage box shows only one disk

      Hi there!

      Main-Problem:
      Fantec QB-35US3-6G (external storage box with 4 bays) only recognizes one drive; all other drives from the box are not available.

      Details:
      Some days ago, I startet with my OMV-Project (moving my spreaded disks from windows-platform into a new case, controlled by OMV), till now it seems to run quite perfect, but at the moment I have a problem and no clue!?
      Each time, I put more than one disk in my box, OMV has problems in showing me the "File System"-menu entry or the "Physical Disks" in the GUI (Messages: connection timeout, bad gateway), startup-prozess tell me, that it can not find some /dev/disk-by-label-dataxx-device. I turned Mr. Google on and he told me several things about "activating multiple LUN support" on, for example these links:

      ask.adaptec.com/app/answers/de…e-lun-support-in-linux%3F
      muddygoat.org/articles/multi-lun
      fantec-forum.de/index.php/Thre…latte-erkannt-solved/?l=1

      So, I'm a noob in Linux-configuration, but most/all of this information wasn't suitable, either because kernel-feature wasn't compiled or wrong distribution an so an.
      I hope somebody can tell me how to set up my box in a correct way or active multiple LUNs or some other tipps.

      Some Facts
      OMV-Version: 3.0.7
      Kernel-Version: 4.8.0-0.bpo.2-amd64
      Mainboard: GIGABYTE GA-B250M-DS3H
      External Storage-Box: Fantec QB-35US3-6G

      Thank you for any tipps and help!
    • I have the idea that the case is passing the USB controller as device, just like a USB data adapter will do. So Omv sees no unique disk id, can it be possible that all disks have the same label ? If you plug all disk enter ssh console can you post

      tree /dev/disk -a

      Install tree first. (apt-get install tree)

      Btw I don't think lun is related. That's for using block devices across the network (iscsi)
      chat support at #openmediavault@freenode IRC | Spanish & English | GMT+10
      telegram.me/openmediavault broadcast channel
      openmediavault discord server
    • No, I think label and UUID are different:

      Source Code

      1. /dev/disk
      2. ├── by-id
      3. │ ├── ata-SAMSUNG_HD204UI_S2H7J1RZ900670 -> ../../sdi
      4. │ ├── ata-SAMSUNG_HD204UI_S2H7J1RZ900670-part1 -> ../../sdi1
      5. │ ├── ata-ST1000LM024_HN-M101MBB_S2RUJ9CDA51745 -> ../../sdo
      6. │ ├── ata-ST1000LM024_HN-M101MBB_S2RUJ9CDA51745-part1 -> ../../sdo1
      7. │ ├── ata-ST2000DL003-9VT166_6YD0DDGC -> ../../sdd
      8. │ ├── ata-ST2000DL003-9VT166_6YD0DDGC-part1 -> ../../sdd1
      9. │ ├── ata-ST2000DM001-1CH164_W240V259 -> ../../sdg
      10. │ ├── ata-ST2000DM001-1CH164_W240V259-part1 -> ../../sdg1
      11. │ ├── ata-TS32GMTS800_D562490006 -> ../../sdf
      12. │ ├── ata-TS32GMTS800_D562490006-part1 -> ../../sdf1
      13. │ ├── ata-TS32GMTS800_D562490006-part2 -> ../../sdf2
      14. │ ├── ata-TS32GMTS800_D562490006-part5 -> ../../sdf5
      15. │ ├── ata-WDC_WD2002FAEX-007BA0_WD-WCAY00004190 -> ../../sda
      16. │ ├── ata-WDC_WD2002FAEX-007BA0_WD-WCAY00004190-part1 -> ../../sda1
      17. │ ├── ata-WDC_WD20EARS-00MVWB0_WD-WCAZA5626742 -> ../../sdb
      18. │ ├── ata-WDC_WD20EARS-00MVWB0_WD-WCAZA5626742-part1 -> ../../sdb1
      19. │ ├── ata-WDC_WD20EARS-00MVWB0_WD-WCAZA6247166 -> ../../sde
      20. │ ├── ata-WDC_WD20EARS-00MVWB0_WD-WCAZA6247166-part1 -> ../../sde1
      21. │ ├── ata-WDC_WD20EFRX-68AX9N0_WD-WMC1T1262475 -> ../../sdj
      22. │ ├── ata-WDC_WD20EFRX-68AX9N0_WD-WMC1T1262475-part1 -> ../../sdj1
      23. │ ├── ata-WDC_WD20EFRX-68AX9N0_WD-WMC300314841 -> ../../sdk
      24. │ ├── ata-WDC_WD20EFRX-68AX9N0_WD-WMC300314841-part1 -> ../../sdk1
      25. │ ├── ata-WDC_WD20EFRX-68EUZN0_WD-WCC4M1206500 -> ../../sdc
      26. │ ├── ata-WDC_WD20EFRX-68EUZN0_WD-WCC4M1206500-part1 -> ../../sdc1
      27. │ ├── ata-WDC_WD20EZRX-00D8PB0_WD-WMC4N2939292 -> ../../sdh
      28. │ ├── ata-WDC_WD20EZRX-00D8PB0_WD-WMC4N2939292-part1 -> ../../sdh1
      29. │ ├── usb-ST2000DL_003-9VT166_000000000000-0:2 -> ../../sdn
      30. │ ├── usb-ST2000DL_003-9VT166_000000000000-0:2-part1 -> ../../sdn1
      31. │ ├── usb-WDC_WD20_EURS-63SPKY0_000000000000-0:0 -> ../../sdl
      32. │ ├── usb-WDC_WD20_EURS-63SPKY0_000000000000-0:0-part1 -> ../../sdl1
      33. │ ├── usb-WDC_WD20_EZRX-00D8PB0_000000000000-0:1 -> ../../sdm
      34. │ ├── usb-WDC_WD20_EZRX-00D8PB0_000000000000-0:1-part1 -> ../../sdm1
      35. │ ├── wwn-0x50004cf20b946b8f -> ../../sdo
      36. │ ├── wwn-0x50004cf20b946b8f-part1 -> ../../sdo1
      37. │ ├── wwn-0x5000c50036de089b -> ../../sdd
      38. │ ├── wwn-0x5000c50036de089b-part1 -> ../../sdd1
      39. │ ├── wwn-0x5000c500538fd532 -> ../../sdg
      40. │ ├── wwn-0x5000c500538fd532-part1 -> ../../sdg1
      41. │ ├── wwn-0x50014ee003789437 -> ../../sdj
      42. │ ├── wwn-0x50014ee003789437-part1 -> ../../sdj1
      43. │ ├── wwn-0x50014ee0ae23699a -> ../../sdk
      44. │ ├── wwn-0x50014ee0ae23699a-part1 -> ../../sdk1
      45. │ ├── wwn-0x50014ee205a9bd3f -> ../../sdb
      46. │ ├── wwn-0x50014ee205a9bd3f-part1 -> ../../sdb1
      47. │ ├── wwn-0x50014ee20641eb6f -> ../../sda
      48. │ ├── wwn-0x50014ee20641eb6f-part1 -> ../../sda1
      49. │ ├── wwn-0x50014ee25eedef06 -> ../../sdc
      50. │ ├── wwn-0x50014ee25eedef06-part1 -> ../../sdc1
      51. │ ├── wwn-0x50014ee2b06313c2 -> ../../sde
      52. │ ├── wwn-0x50014ee2b06313c2-part1 -> ../../sde1
      53. │ ├── wwn-0x50014ee6048a4075 -> ../../sdh
      54. │ ├── wwn-0x50014ee6048a4075-part1 -> ../../sdh1
      55. │ ├── wwn-0x50024e90040f6167 -> ../../sdi
      56. │ └── wwn-0x50024e90040f6167-part1 -> ../../sdi1
      57. ├── by-label
      58. │ ├── data01 -> ../../sdh1
      59. │ ├── data02 -> ../../sdi1
      60. │ ├── data03 -> ../../sdk1
      61. │ ├── data04 -> ../../sdj1
      62. │ ├── data05 -> ../../sdg1
      63. │ ├── data06 -> ../../sdc1
      64. │ ├── data07 -> ../../sdd1
      65. │ ├── data08 -> ../../sda1
      66. │ ├── data09 -> ../../sdn1
      67. │ ├── data10 -> ../../sdm1
      68. │ ├── data11 -> ../../sdl1
      69. │ ├── parity -> ../../sdb1
      70. │ ├── qparity -> ../../sde1
      71. │ └── Transcend -> ../../sdo1
      72. ├── by-partuuid
      73. │ ├── 03199272-4c16-4668-beca-dd12bb7a32d6 -> ../../sda1
      74. │ ├── 0495673a-15a6-44de-b64d-e95260762e5e -> ../../sdi1
      75. │ ├── 29734b98-dd9e-4482-88ad-940e2b5a6cf7 -> ../../sdj1
      76. │ ├── 555c3ba2-bea8-4569-94dd-32a7b63d7df5 -> ../../sdd1
      77. │ ├── 7129a84f-fbc5-480a-a505-9f3cefce37b9 -> ../../sdm1
      78. │ ├── 779b1bb9-eda1-4d39-bd7e-968bc9659792 -> ../../sdg1
      79. │ ├── 7b17a3e8-1182-431d-985b-8a44d195c762 -> ../../sdl1
      80. │ ├── 877aa7c7-5d4a-4a76-9e55-cb4a228c9f81 -> ../../sdc1
      81. │ ├── 8c1af86f-9137-46bf-9835-eb59e1b3e1f5 -> ../../sde1
      82. │ ├── a08ee2ac-b5fc-40d8-b29c-b5b4b4b818d7 -> ../../sdb1
      83. │ ├── a844c4ae-6503-40d6-ba22-ae3882f68e82 -> ../../sdn1
      84. │ ├── d00773c6-2778-4471-8ca6-e8043341a669 -> ../../sdk1
      85. │ └── d66ab25f-7e65-4fda-8f91-476e42409050 -> ../../sdh1
      86. ├── by-path
      87. │ ├── pci-0000:00:14.0-usb-0:4:1.0-scsi-0:0:0:0 -> ../../sdo
      88. │ ├── pci-0000:00:14.0-usb-0:4:1.0-scsi-0:0:0:0-part1 -> ../../sdo1
      89. │ ├── pci-0000:00:14.0-usb-0:6:1.0-scsi-0:0:0:0 -> ../../sdl
      90. │ ├── pci-0000:00:14.0-usb-0:6:1.0-scsi-0:0:0:0-part1 -> ../../sdl1
      91. │ ├── pci-0000:00:14.0-usb-0:6:1.0-scsi-0:0:0:1 -> ../../sdm
      92. │ ├── pci-0000:00:14.0-usb-0:6:1.0-scsi-0:0:0:1-part1 -> ../../sdm1
      93. │ ├── pci-0000:00:14.0-usb-0:6:1.0-scsi-0:0:0:2 -> ../../sdn
      94. │ └── pci-0000:00:14.0-usb-0:6:1.0-scsi-0:0:0:2-part1 -> ../../sdn1
      95. └── by-uuid
      96. ├── 04307BCA307BC0EA -> ../../sdo1
      97. ├── 0ac71826-f8c6-480b-8dfe-2a78cf58f6dd -> ../../sdd1
      98. ├── 1bb0c893-cfc9-47c3-aa02-35ba74d31833 -> ../../sdm1
      99. ├── 31ba3f70-4e98-40c6-9840-29dee73109e5 -> ../../sdf1
      100. ├── 51fb90ae-4875-44f2-b66c-d5ff4ebce8fc -> ../../sdl1
      101. ├── 555fdb4c-5fa7-484f-8db2-07ac02136f39 -> ../../sdf5
      102. ├── 64c66095-84ea-465e-a29a-bd9036958a7c -> ../../sdk1
      103. ├── 8e34e67a-48ae-4c37-a86f-200de3d78b95 -> ../../sdn1
      104. ├── 9ff4f01a-05a2-480b-9d05-47b7d24aff35 -> ../../sdc1
      105. ├── b2378fc7-8f23-4926-831a-aececb6b49f3 -> ../../sdj1
      106. ├── c6d53fd6-4314-4722-a4d5-9928501a6d6a -> ../../sde1
      107. ├── cebfe976-b58a-4870-be46-e0b04b6c3041 -> ../../sdg1
      108. ├── dfddd815-da2e-4e2d-b4fc-8d2397f4b26e -> ../../sdh1
      109. ├── e195742e-0528-401f-a7aa-d41517b71a05 -> ../../sda1
      110. ├── f5b3db42-5a1c-44b9-b1e5-23782e26056e -> ../../sdi1
      111. └── fc9fde78-ece6-470f-851c-2e966013bbb7 -> ../../sdb1
      Display All
    • You have a lot of disks there. You can try an increase the web server timeout see if the physical disk display shows correctly


      take a look at this post

      OMV Web GUI Timeout too Low or S.M.A.R.T. Issue

      The character he points out the # needs to be replaced by a number.
      Maybe try to go 120s and test.
      chat support at #openmediavault@freenode IRC | Spanish & English | GMT+10
      telegram.me/openmediavault broadcast channel
      openmediavault discord server
    • I changed the existing values, added /etc/default/openmediavault: OMV_HTTPREQUEST_TIMEOUT and restarted all devices. Then I tried to list the content of disk09 or disk 10 (both in external box) via ssh and I got the following message which seems to be similar like the respond from GUI (by the way: even the GUI-respond starts "immediately" which means after 10 seconds):


      Source Code

      1. root@omv:~# ls /srv/dev-disk-by-label-data09/data/
      2. ls: Zugriff auf /srv/dev-disk-by-label-data09/data/ nicht möglich: Eingabe-/Ausgabefehler

      German language output which means "Access to /srv/... not possible: Input-/Outputerror.

      From other devices (for example disk08 which is internal), there's no problem from ssh to list content; tree-command like you gave me above is also working after the Input-/Outputerror-Message.

      @LUN: Lots of people have problems with for example card reader, etc. based on USB when connecting them to a linux-system; some more link-examples, hope I got the point:

      patchwork.kernel.org/patch/3691691/
      kernel.xc.net/html/linux-2.6.0-test4/sparc/SCSI_MULTI_LUN

      Ok, this information is not brand new, but I could not find this setting in OMV, so I tought it might be the problem?

      ---

      Update: I don't know why or how but this time, I got an error-dialog from GUI:


      Source Code

      1. Header:
      2. Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; blockdev --getsize64 '/dev/sdm' 2>&1' with exit code '1': blockdev: cannot open /dev/sdm: No such device or address
      3. Body:
      4. Error #0: exception 'OMV\ExecException' with message 'Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; blockdev --getsize64 '/dev/sdm' 2>&1' with exit code '1': blockdev: cannot open /dev/sdm: No such device or address' in /usr/share/php/openmediavault/system/process.inc:175 Stack trace: #0 /usr/share/php/openmediavault/system/blockdevice.inc(270): OMV\System\Process->execute(Array) #1 /usr/share/openmediavault/engined/rpc/diskmgmt.inc(83): OMV\System\BlockDevice->getSize() #2 [internal function]: OMVRpcServiceDiskMgmt->enumerateDevices(NULL, Array) #3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(124): call_user_func_array(Array, Array) #4 /usr/share/openmediavault/engined/rpc/diskmgmt.inc(118): OMV\Rpc\ServiceAbstract->callMethod('enumerateDevice...', NULL, Array) #5 [internal function]: OMVRpcServiceDiskMgmt->getList(Array, Array) #6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(124): call_user_func_array(Array, Array) #7 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('getList', Array, Array) #8 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('DiskMgmt', 'getList', Array, Array, 1) #9 {main}
      But I guess, this only means that it cannot access some device (sdm); sdm is disk10, a disk without access even from shell.

      The post was edited 2 times, last by kefawirt: Update, error-message from GUI ().

    • IO error could be the disk failing. You can try the following reboot the server without the box plugged.
      Once the server is up again plug the disk box. Wait a few seconds then run in ssh:
      dmesg

      Paste the output in web text service and put the link here

      Also see if you can list the smart values of sdn and sdm

      smartctl -a /dev/sdn
      chat support at #openmediavault@freenode IRC | Spanish & English | GMT+10
      telegram.me/openmediavault broadcast channel
      openmediavault discord server
    • Attached, you'll find the output, incl. sdm, sdn, sdo. I cannot bring you all smart-information about the disk inserted in the 4bay-box, because I got an error: Read Device Identity failed: empty IDENTIFY data.

      So, I put them one after the other in ANOTHER (only one slot) storage box; the reason is that I did not get any infos after the "attributes"-block (Read SMART Log Directory failed; Read SMART Error Log failed; Read SMART Self-test Log failed; Read SMART Selective Self-test Log failed; always with an explanation like "The waiting time for the connection has expired") when putting the disks in the 4bay-box. Hope, these smart-values are valid when located inside a box - if it's necessary, I connect them with an internal SATA-Port.

      Btw: When I shut the system down, there is a "stop job running for device 09/10/11" for minutes - only for the disks in the 4bay-box.
      Btw2: When I read smart-values from a disk in the 4bay-drive, it lasts a long time and maybe a timeout occurs. When I put the same disk into a single-slot-box, everything seems to be ok?

      Maybe I should forget about the 4bay-enclosure? It doesn't seem to be compatible with either operation system or the mainboard?!
      Files
    • Kernel: 4.8.0-0.bpo.2-amd64


      ---
      Update: Your links told me to try it with USB 2.0; so I changed the USB-Port, but the result is finally the same; with one disk, everything looks quite promising (better than with USB 3.0 - fast, no errors), but atm with more plugged drives, dmesg shows me infos like:

      Source Code

      1. [ 428.747794] sd 19:0:0:1: rejecting I/O to offline device
      2. [ 428.748053] sd 19:0:0:1: rejecting I/O to offline device
      3. [ 428.748205] sd 19:0:0:1: rejecting I/O to offline device
      4. [ 428.748343] sd 19:0:0:1: rejecting I/O to offline device
      5. [ 428.748535] sd 19:0:0:1: rejecting I/O to offline device

      The post was edited 1 time, last by kefawirt: USB 2.0 ().

    • I managed to run a live-demo of Ubuntu 17.04 on my OMV-PC; first I thought, it would work fine - I cannot write anything (guess this means, that I only have read-permissions), but for a few moment, it works fine, could send a "dmesg". But little later, it's not possible to interact with this Ubuntu-demo; not sure atm, if there's a problem with my keyboard or some services aren't run correctly?! Will have more investigations on sunday.

      Is it possible to take a look via SSH and putty on this live-view-installation or is this feature disabled on live-demo?
    • I can't remember if you can install software in live desktop you can try

      apt-get install openssh-server

      then systemctl start ssh

      BTW i took a look at smart data again and this disk

      ST2000DL003-9VT166 barracuda green serial number 5YD2ZK7B

      has lots of errors in Hardware_ECC_Recovered an Command_Timeout, this is usually problems with cable or maybe the contact sata port.
      Maybe try to keep this disk off the box or identify the position in the box it was using, could be a faulty slot there.
      chat support at #openmediavault@freenode IRC | Spanish & English | GMT+10
      telegram.me/openmediavault broadcast channel
      openmediavault discord server
    • I tried the ubuntu-live-system; the test-scenario wasn't as meaningful as I wanted it to be, but as conclusio: It seams, ubuntu accept this controller / usb-4-bay-box.

      First of all, I didn't really had much permission; even as sudo, it was not possible (for me) to write any files (folders were possible) or to access some cifs-shares or install something and so on; this is the reason why I have no dmesg-info as file atm. The system was stable, I could read the content of two disks (no ST2000DL003-9VT166) enclosured in the 4-bay-drive; in this constellation, OMV already had problems.

      What will I do next? I guess, I'll not use my 4-bay-box anymore in combination with OMV - except, I get some info how to manipulate some modules.conf-file change settings (CONFIG_SCSI_MULTI_LUN) or OMV supports my controller in future (don't know how to realize this ;)).

      @subzero79: Thanks a lot for your support and your quick responses! Even if the problem isn't solved, I learned lot of things about debian-mechanism, so time wasn't wasted at all!