ONE removable device not mounting in Slackware w/ XFCE
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Simplify it down a bit. First mount it manually and see if that works.
Before it is plugged in run "lsblk". Then plug it in and run "lsblk" again. Look at the difference. This will tell you its device name (e.g. sdb) and what partitions it might have (.e.g. sdb1).
Once you know this information you can switch to root and try mounting it by hand, e.g.
Code:
# mount /dev/sdb1 /mnt/tmp
(Switch the device information which what you found on your own system).
Do this work? If it did, look at the line in "/etc/mtab" for this device and report back what it says, e.g. "/dev/sdb1 /mnt/tmp ext4 rw 0 0".
I guess I can try manually mounting now with the highlighted info in Slackware?
And here's lsblk:
Code:
@crunchbang:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 111.8G 0 disk
├─sda1 8:1 0 74.5G 0 part
├─sda2 8:2 0 32.6G 0 part /
├─sda3 8:3 0 1K 0 part
└─sda5 8:5 0 4.7G 0 part [SWAP]
sr0 11:0 1 1024M 0 rom
sdb 8:16 1 15G 0 disk /media/COWON X9
FYI: The MP3 player is also not detected in Slackware on my laptop. (It is detected in #! on both the desktop and laptop; and not detected in Slackware on either)
You might have to compare the udev rules that comes as presets in Crunchbang with the Slackware's ones.
This might be a useful resource in order to troubleshoot your problem.
Thanks, but I'm pretty new/clueless at this....so I don't think that would make sense to me.
I did mount my other MP3 player in Slackware, and then checked "lsblk" and "/etc/mtab/", and it looked similar to Crunchbang- i.e. /dev/sdb1...
I tried manually mounting /dev/sdb1 when the problem Cowon player was attached, and just got a message that "the special device /dev/sdb1 doesn't exist".
As long as the player is in MSC mode, the type of filesystem it uses shouldn't matter, right? (I was thinking maybe for some reason it's filesystem isn't supported/can't be recognized by Slackware....)
bash-4.2# lsusb
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
bash-4.2# lsusb
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
*Sigh*
My fault. I should have specified "Please run the command 'lsusb' as root when the player in question is plugged in."
My fault. I should have specified "Please run the command 'lsusb' as root when the player in question is plugged in."
Usually I also like to see the -t option used in lsusb to see what driver is being used also
as root with the usb device plugged in included with lsusb readout
Code:
lsusb -t
and just for giggles
Code:
lsusb -v
since it is only a key stroke and sumguy has nothing pressing him not to supply extra info in this thread.
By the way. Those command readouts would be very helpful in Crunchbang since crunchbang will most definitely show what drivers are being used on the mp3 player.
Last edited by rokytnji; 06-20-2014 at 11:01 PM.
Reason: Sunburnt and Tired.
Actually, fellers[sic], the problem MP3 player was plugged in and charging when I ran lsusb.
And I actually ran the -v option the first time I did lsusb....but I didn't post the output of that, since it was quite long, and not asked for....but tomorrow I'll post the output of lsusb -v for both Slack and #!.
Would it also help if I were to post the output of that command while my other player is connected? (The one which is recognized)- just for comparison?
Thanks for all the help so far, everyone! Gotta LOVE this forum! You guys should be getting paid!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.