Linux
Welcome to c/linux!
Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!
Rules:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
view the rest of the comments
This doesn't really answer your question directly, but instead of going through all of your USB devices with
lsusb, you're probably going to have a much easier time just showing your storage devices withlsblk. That'll also show you the size of the storage device and block device name.I would expect you to have some entry in the
lsusboutput, but it might be that it's described as a hub, given that this is some kinda combination device. What I'd do, if you want to know what device it is inlsusboutput anddmesgdoesn't make it clear, is something like this. Unplug the device.Plug it in.
That'll show you which lines were added for the device.
EDIT: If
usb-storagewas loaded when you plugged the thing in, my guess is that it's most-likely the case that Linux can see the drive.For the dmesg I used -w to get a live feed and nothing happens. I also compared lsusb before and after and even looked at
lsblk -o NAME,SIZE,VENDOR,MODEL,SERIAL,TRAN, but there is indeed no change. usb-storage was loaded when I manually started the service (sorry, forgot to state that).Ahhh, gotcha. Yeah, then that kinda kills that line of reasoning.
It looks like past versions of the product have worked with Linux.
https://forums.linuxmint.com/viewtopic.php?t=299894
I'm a little surprised that you aren't at least seeing something showing up as a USB device in your before-after difference. Looking at this, it looks like the device uses wall power, has a DC power supply with a barrel connector. It's possible that it might not function at all without that being powered up. Are you sure that you have the barrel connector in and the plug plugged into an outlet that is hot (i.e. not, say, an outlet controlled by a light switch that is off)?
EDIT: Also, are you sure that the drive works? My past experience with JBOD drive enclosures has been that a non-functional drive, something that the drive enclosure can't talk to, won't be presented as a Mass Storage device.
There is a power LED and it is on.
Sadly I only have this one drive to test which is the whole reason why I took the Dock.
This one works flawlessly on my Linux machines, all running Debian/LMDE. Plug and play.
Do these and report back with findings:
fdisk -land see if it shows up in there.That's a thought.
It won't hurt, but if he's not seeing anything with
lsblk,fdisk -lprobably won't show it either, as they're both iterating over the block devices.Honestly, if he doesn't know that the hard drive itself functions, the drive not working would be my prime theory as to culprit. I have had drive enclosures not present a USB Mass Storage device to a computer if they can't talk to the hard drive over SATA.
Simplest solutions first 😅
I'm also leaning toward the drive being a dud, because there is no reason a drive toaster shouldn't work on Linux out of the box. I'm running Linux Mint Debian Edition on my PC and didn't configure a single thing for my toaster.