Support #9848

BUG? Pass-through of 2 same USB external HDD

Added by [email protected] almost 5 years ago. Updated almost 5 years ago.

Status:

Closed

Assignee:

Mario Kaack

% Done:

Description

I think I may have found a possible bug when attempting to attach 2 of the
exact same external drives.

See posting:
https://antsle.com/forum/topic/pass-through-usb-1-of-2-external-usb-seen/

https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon
Virus-free.
www.avast.com
https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

History

#1 Updated by Mario Kaack almost 5 years ago

Kirk,

Thanks for the input. I see William answered your forum post.

We do hope to release a fix soon.

#2 Updated by [email protected] almost 5 years ago

Thank you. I’ll eagerly watch for the next release. I don’t want to buy a different brand drive.

-Kirk

On May 28, 2019, at 4:01 PM, [email protected] wrote:

Hi there and thank you for contacting antsle support!

Kirk,

Thanks for the input. I see William answered your forum post.

We do hope to release a fix soon.

https://brainosaur.com/tickets/4678/87d12ae958199130be071e8daf74f234

Thanks you,

antsle, Inc.
Customer Support Team

#3 Updated by Mario Kaack almost 5 years ago

Kirk,

Not sure this will be in the next release but here is some info on the issue and a work around.

Currently the .xml for the antlet is using the USBs vendor and product ID. If using identical USBs, these ID's are the same. So, we need to use the bus and device numbers to be more specific about each device.

For now you could edit the xml of the antlet to reference the bus and device for each usb.

First connect to the antsle's command line: https://docs.antsle.com/login/

Get the Bus and Device numbers with the 'lsusb' command

root@myantsle:~ # lsusb
Bus 001 Device 006: ID 0781:5595 SanDisk Corp.
Bus 001 Device 005: ID 0781:5595 SanDisk Corp.
Then edit the xml for the antlet

EDITOR=nano virsh edit ANTLET_NAME

Add the following ' tag. Replace the bus and device numbers with those displayed when you ran the 'lsusb' command.

<hostdev mode='subsystem' type='usb' managed='yes'>
    <source>
        <address bus='1' device='5'/>
     </source>
</hostdev>
<hostdev mode='subsystem' type='usb' managed='yes'>
    <source>
        <address bus='1' device='6'/>
     </source>
</hostdev>

*This workaround does create another bug though - with this edit we can no longer open the antlet details in antMan!

#4 Updated by [email protected] almost 5 years ago

Excellent. Thanks! I'll give it a try and only use it when needed, then
revert back. Since it exposes another bug.

-Kirk

On Thu, May 30, 2019 at 9:02 AM [email protected] wrote:

Hi there and thank you for contacting antsle support!

Kirk,

Not sure this will be in the next release but here is some info on the
issue and a work around.

Currently the .xml for the antlet is using the USBs vendor and product ID.
If using identical USBs, these ID's are the same. So, we need to use the
bus and device numbers to be more specific about each device.

For now you could edit the xml of the antlet to reference the bus and
device for each usb.

First connect to the antsle's command line: https://docs.antsle.com/login/

Get the Bus and Device numbers with the 'lsusb' command

root@myantsle:~ # lsusb
Bus 001 Device 006: ID 0781:5595 SanDisk Corp.
Bus 001 Device 005: ID 0781:5595 SanDisk Corp.
Then edit the xml for the antlet

EDITOR=nano virsh edit ANTLET_NAME

Add the following ' tag. Replace the bus and device numbers with those
displayed when you ran the 'lsusb' command.

*This workaround does create another bug though - with this edit we can no
longer open the antlet details in antMan!

https://brainosaur.com/tickets/4678/87d12ae958199130be071e8daf74f234

Thanks you,

antsle, Inc.
Customer Support Team

Add a comment

antsle support

Previous tickets