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.
I have a Sansa c250 and Slackware 11. With FC6, I mount it like this:
------------------------------
mount -t vfat /dev/sde1 usb
------------------------------
and it works allright. With Slackware I don't get the same result. This is the dmesg:
------------------------------
hub.c: new USB device 00:03.3-4, assigned address 2
scsi2 : SCSI emulation for USB Mass Storage devices
Vendor: SanDisk Model: Sansa c250 Rev: Sans
Type: Direct-Access ANSI SCSI revision: 02
Attached scsi removable disk sde at scsi2, channel 0, id 0, lun 0
SCSI device sde: 4013056 512-byte hdwr sectors (2055 MB)
sde: Write Protect is off
sde: sde1 sde2
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 2
root@localhost:~# mount -t vfat /dev/sde1 usb
mount: wrong fs type, bad option, bad superblock on /dev/sde1,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
root@localhost:~# mount -t vfat /dev/sde2 usb
mount: wrong fs type, bad option, bad superblock on /dev/sde2,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
------------------------------
Something I should have added...
This is the dmesg | tail AFTER I try mounting it the way I did above:
-----------------------------
sde: sde1 sde2
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 2
VFS: Can't find a valid FAT filesystem on dev 08:41.
FAT: bogus logical sector size 0
VFS: Can't find a valid FAT filesystem on dev 08:42.
VFS: Can't find a valid FAT filesystem on dev 08:41.
FAT: bogus logical sector size 0
VFS: Can't find a valid FAT filesystem on dev 08:42.
VFS: Can't find a valid FAT filesystem on dev 08:41.
WARNING: USB Mass Storage data integrity not assured
.
.
.
mount: wrong fs type, bad option, bad superblock on /dev/sde1,
It seems like the file system on the MP3 player has not been formatted yet, or is corrupt. There is a very simple solution to this problem, but any data (e.g. music) on the MP3 player will be deleted.
Plug the MP3 player into the USB port associated with /dev/sde.
Run the following command in a terminal:
Code:
mkfs.vfat /dev/sde
If the command isn't found, try:
Code:
mkdosfs /dev/sde
This will format the MP3 player's storage space for use. You only need to do this once. After that you should be able to mount it exactly the same way as you have been doing. Note that this will also work with any USB port, not only the one associated with /dev/sde.
However, what did work for me was updating to the newest kernel. By default slackware 11 runs on 2.4, unfortunately.
Not quite. It's as easy as typing huge26.s or test26.s at the boot screen if you want the 2.6.x kernels. And you could always install one later or compile one yourself.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.