Problem mounting usb flash drive with 2.6.12.2 kernel
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.
Problem mounting usb flash drive with 2.6.12.2 kernel
I did a kernel recompile to 2.6.12.2 recently from the 2.4. Everything went great, after some initial hiccoughs, now I'm using the 2.6.12.2 daily.
Trouble is, I recently tried mounting my usb flash drive
# mount /mnt/usb
then I get;
Code:
mount: you must specify the filesystem type
This procedure works fine for the 2.4 kernel which I kept. The filesystem type is set to auto, but I've also tried vfat and a couple of others in desperation.
SCSI device sdb: 501759 512-byte hdwr sectors (257 MB)
sdb: Write Protect is off
sdb: Mode Sense: 03 00 00 00
sdb: assuming drive cache: write through
SCSI device sdb: 501759 512-byte hdwr sectors (257 MB)
sdb: Write Protect is off
sdb: Mode Sense: 03 00 00 00
sdb: assuming drive cache: write through
sdb: sdb1
Attached scsi removable disk sdb at scsi1, channel 0, id 0, lun 0
# less /var/log/messages
Code:
Jul 23 09:53:50 myhost kernel: usb 2-2: new full speed USB device using uhci_hcd
and address 2
Jul 23 09:53:51 myhost kernel: scsi1 : SCSI emulation for USB Mass Storage devic
es
Jul 23 09:53:56 myhost kernel: Vendor: SanDisk Model: Cruzer Micro Rev:
0.3
Jul 23 09:53:56 myhost kernel: Type: Direct-Access ANSI
SCSI revision: 02
Jul 23 09:53:56 myhost kernel: SCSI device sdb: 501759 512-byte hdwr sectors (25
7 MB)
Jul 23 09:53:56 myhost kernel: sdb: Write Protect is off
Jul 23 09:53:56 myhost kernel: SCSI device sdb: 501759 512-byte hdwr sectors (25
7 MB)
Jul 23 09:53:56 myhost kernel: sdb: Write Protect is off
Jul 23 09:53:56 myhost kernel: sdb: sdb1
Jul 23 09:53:56 myhost kernel: Attached scsi removable disk sdb at scsi1, channe
l 0, id 0, lun 0
The usb and scsi sections of the config file are obviously a bit large, so I won't post them just now. The output of lsmod does show usb_storage ohci_hcd and ehci_hcd though.
Cheers for any help with this, I'm sure it's a common enough problem, but I just can't think what I left out during the kernel compile. Just to remind everyone, everything works fine with the 2.4 kernel with the same general settings.
one more question: Is is usually considered safe to just plug and unplug the usb flash drive whenever you want to? I know that windows can get unstable if you do this and was just wondering what the acceptable protocol for performing this transition under Linux was. Obviously I'd unmount the device first
it's not like you are unpluging the device without unmounting it first, right?
Yes, that's right, but the light stays on even after unmounting it. I suppose that's what I'm concerned about. When you stop the device under windows, if you do it correctly that is, the light goes out, then you can unplug it. Don't worry, I'm not highly strung or anything, I just like to do things right, that's all.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.