Hard Drive Dock Not Accessible
Clyde last edited by Clyde
Care to elaborate on that limit? USB can address up to 127 devices, and the official RPi documentation on USB only vaguely mentions general limits that should be circumventable by a powered usb hub. If your dock has its own power supply (which dock hasn't?), power consumption shouldn't be an issue here.
@Clyde Somebody kindly suggested that the 3B+ had a limit of 6 USB devices connected at any one time, and that the Pi4 was capable of supporting a great deal more..?
Yes, the dock has its own power supply, and seems to read any combination of drives on Win10 PC just fine, but not when using Retropie. That appears to be the only circumstance in which a red warning light appears on the dock itself. However, take out the 5tb, and the 3tb is read without issue.
In lack of explicit reasons for that advice, I suspect those 6 devices were power related. However, the effect you described seems strange. What does the manual of the doc say about the warning light?
Alas, I'm (very, very) far from being an expert in these things. So, if you want to dive deeper into this rather than just wait for the Pi 4 and hope that this will fix your problem, I can only recommend further research and give you some links to start from:
TL;DR: A powered USB hub may help if a device has problems although it should be within the limits, especially HDDs.
@Clyde It is very strange. This is the second dock, too, as I was advised by the stockist to return the original, as it was possibly defective. More or less, the same problem transpiring with the new unit, though. Rated for use with Mac, PC, and Linux.
It always seems to be the addition of the 5tb that creates an issue. I wondered if the drive labels or signatures could be causing a conflict, but this doesn’t seem to be the case, as the dock, with all drives inserted, works as I believe it should, on a Win10 machine.
Instruction manual is not at all clear, and manufacturers haven’t responded to a support request. Basically, the dock has four slots for either a 3.5 or 2.5 sata. Each slot has a 6tb capacity. To the side of the unit are five indicator lights. One is power/standby, and the other four are indicators for each slot. A blue status light seems to indicate power to the drive/good connection. Each corresponding light will flicker red whenever the drive is being read/written, though is permanently illuminated with the addition of the 5tb, and neither drive is recognised in file manager. There is a physical ‘clone mode’ toggle on the reverse which is set to PC mode, in mind for purely reading data, as opposed to backing up.
I wonder if the dock also requires a USB 3.0 socket for maximum efficiency. Another potential ray of hope for the Pi4. Just waiting on a memory card. Also, thank you again for your time on this, much appreciated!
Thanks for the details and good luck with the Pi 4. 👍
@Clyde No joy with the Pi4, sadly. Tried using LibreElec, but same issue persists. Gah.
Did you try the dock with other computers and/or operating systems?
@Clyde Yes, Win10 machine seems to work with all drives connected...
Clyde last edited by Clyde
No, i meant other machines than your Win 10 machine and the Pis, preferably a very different one (e.g. a PC with Win 7 or Linux, a Mac etc.)
@Clyde No, I’m afraid that’s all I have.
Ultimately, the best workaround for this was to switch from RetroPie to OpenElec which seems to read external hard drives differently. I think, the Kodi version for RetroPie assigns very specific paths to each external disk, whereas OpenElec focuses more on each drive’s name and can presumably reassign media paths on the fly.
The upshot of using OpenElec in this instance is that one drive can be removed from the dock and the media paths remain unaffected. In my experience, RetroPie appears to require all media to stay in exactly the same path as it was from the start, which often leads to repeated re-scraping.
Even though I’m grateful to now have Kodi working for my needs, I do really miss being able to exit into RetroPie. I’ve been considering a dual-boot, but would far prefer keeping RetroPie as the front-end.
My best hope is to request an update for how the RetroPie Kodi port connects to external media. Is this possible? Which version of Kodi does RetroPie use?
I’d be so grateful if this added functionality could be considered.
@mitu Thanks for the quick reply! Does that mean the media-path-issue I’m struggling with is due to how RetroPie links to files? If there’s any chance a fix could be looked into, I’d certainly request it, but what are the chances it could happen, at all?
@pen2paper From the looks of it, the issue is not Kodi, but rather the discs not being recognized/brought on-line by Linux. If the discs work plugged in directly, but not through the dock, then the issue is with the dock's operation, not RetroPie/Kodi.
@mitu Again, the drives do work fine through OpenElec, and the file path issue isn’t present there either..?
@pen2paper You could look for differences in the behaviour of RetroPie and OpenElec. Here're some console commands for a start (everything behind
#is just a comment).
Enter these two after you did connect and switch on the dock:
mount # This shows the mounted file systems to see if the drive(s) got mounted, and where.
dmesg # shows the system messages. Look what happened to the drive(s) there.
Enter the following command before you connect the dock, and let it run while you connect and switch on the dock. There should be messages coming up while the system regognizes the drive(s). Stop the command with
tail -f /var/log/syslog
Again, the drives do work fine through OpenElec,
OpenELEC uses its own Linux distribution (JeOS), unlike RetroPie, which uses Raspbian, a Debian derivative. Find out why the drives don't work in a standard Raspbian system and you'll find out why they don't work with RetroPie/Kodi on RetroPie.
@mitu I’d be happy to keep looking into this further (though I’m no expert, I’m afraid) — the most intriguing aspect for me so far, isn’t that the dock doesn’t seem to work at all through RetroPie, but rather that OpenElec doesn’t seem to be as strict as regard drive paths. My instinct, is that is where the issue lies. Would it be helpful to share the logs as suggested above by Clyde? If so, I’ll try as soon as I can. Anything else I could try in the meantime?
Would it be helpful to share the logs as suggested above by Clyde?
Yes, to diagnose the issue, the system logs are the first place to look.
You might want to add some other details about your hardware and setup - what docs are we talking about (vendor/model), what discs are you using, are you fully up-to-date with RetroPie/Rasbian ?
@mitu Bizarrely, as I was running Clyde’s last recommended command (before turning on the drives, whilst running RetroPie), all three drives on the dock began to work. Then, on attempting to exit Kodi back to Emulation Station, everything froze, forcing me to remote reset through Terminal. When I did, all drive paths were ‘scrambled’ again, and no media was available (“This file is no longer available. Would you like to remove it from the library?”).
I think, the reason the file paths have changed is that one of the three HDDs in the dock has disappeared again in File Manager. The drives are healthy and all work fine with OpenElec and Win10. So close, but so frustrating!
I did see a few “Failed to start firstname.lastname@example.org” notifications among others, and even with the drives recognised, I can foresee encountering similar issues in the future as regard the drive paths being so strict, so would still be keen to raise the issue as a potential bug. That particular functionality on OpenElec would be great to bring over somehow, but I cannot tell you how grateful I am to have had RetroPie back even for a few moments. Thank you so much for your help.
In terms of security, would it be possible to DM the logs, as I can see IP addresses, etc?