Forums

Resolved
0 votes
Does anyone know if the BMB has a USB version limitation? I've a WD Elements 107C external drive that works quite happily when plugged into a USB 2 port, but is unrecognised when plugged into a USB 3 port. I can see the drive using cfdisk and it's initialised (which I did whilst it was plugged into a USB 2 port) from a shell, so I know it's been recognised by the kernel.
Saturday, June 01 2019, 08:09 AM
Share this post:
Responses (4)
  • Accepted Answer

    Wednesday, June 05 2019, 09:01 AM - #Permalink
    Resolved
    0 votes
    Nick Howitt wrote:

    Other thread

    Beat me to it :)
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, June 05 2019, 07:25 AM - #Permalink
    Resolved
    0 votes
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, June 05 2019, 07:13 AM - #Permalink
    Resolved
    0 votes
    Dave, it turns out that USB3 was a red-herring. The problem was actually down to the number of buses BMB could detect - it wasn't setup to detect buses in the range 10-99. All covered in the thread 'Recommended way to debug' - which was a request from me so I could investigate the issue.
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, June 04 2019, 09:44 PM - #Permalink
    Resolved
    0 votes
    Does it fail to recognize the device after a reboot and having never attached to the other device? I ask because there is a potential issue with locked UUIDs from it being disconnected. That is, connected to USB 2.0, removed without dismount, connected to USB 3.0.

    Let me know if it is still an issue after a fresh restart and only connected to USB 3.0. There should not be a limitation.
    The reply is currently minimized Show
Your Reply