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.
Greets all. I posted this question a few days back in the hardware section, but my reply was never answered so I thought i'd try the fellow slackers.
I recompiled my kernel (2.6.17.13), almost a half a dozen times, and got everything there and working except the ability to mount my thumb drives. I included Scsi Disk, Scsi Device Support, USB Filesystem support, FAT & NTFS support, and USB Storage support in the kernel config., yet still can't mount the drive. It gives me the "bad superblock or fs" error. I've tested my thumb drive on my mac to make sure it's fine, and it is. lsmod reports that the usb_storage module is loaded, fs support is compiled in, and lsusb shows the Sandisk Cruzer present. Any ideas??
Oh hey. You were in that forum no? I apollogize "uselpa". You must've come back at a very brief moment in time. I had my laptop sitting here on the desk beside my monitor (my mac). I don't own a router so I was on LQ with the mac and working here at the desk. I recompiled the kernel yet again, because I noticed I was missing one of the SCSI options. I did it and when I first typed the mount command, it sat there doing nothing for a minute (like it was frozen briefly) then no output, just a blinking cursor. I thought it had worked and was excited about it, so I wanted to respond with my thanks and etc. A few minutes later, I went to access /mnt/thumb and it was empty. I tried to unmount, then re-mount and all was a failure
I hope you did not take offense friend, I would never speak like that.
Anyways, I'm on my mac now, so i'll have to type across what happens.
fdisk -l /dev/sda
Device Boot Start End Blocks Id System
/dev/sda1 * 1 3936 1007600 e W95 FAT16 (LBA
The command I used:
mount -t vfat /dev/sda /mnt/thumb
mount: wrong fs type, bad option, bad superblock on /dev/sda,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
Which I didn't see anything of use. Confusing no? FAT & NTFS support are compiled in, as well as all of the aformentioned SCSI options, USB Storage, Devices and etc. It's apparent between that fdisk and lsusb that the system can see what the device is and identify it, but can't mount it. By the by, I get the same output from using "auto" in the mount as well.
Thanks for your help
--Queue
Last edited by crasslogic; 01-23-2007 at 10:13 AM.
Well there must be something wrong with your thumbdrive, because it works fine for me:
Code:
root@slackw:~$ fdisk -l /dev/sda
Disk /dev/sda: 1048 MB, 1048576000 bytes
33 heads, 61 sectors/track, 1017 cylinders
Units = cylinders of 2013 * 512 = 1030656 bytes
Device Boot Start End Blocks Id System
/dev/sda1 1 1017 1023580 e W95 FAT16 (LBA)
root@slackw:~$ mount /dev/sda1 mountpoint/
root@slackw:~$ mount
/dev/hda1 on / type ext3 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
usbfs on /proc/bus/usb type usbfs (rw,devgid=10,devmode=0666)
/dev/hda3 on /mnt/win type vfat (rw,gid=100,umask=002)
tmpfs on /dev/shm type tmpfs (rw,size=144m)
/dev/sda1 on /root/mountpoint type vfat (rw)
As root, try the mount command without the -t option (as I did).
I did. It makes no sense that everything is there yet it doesn't work. I wonder if there's a module that isn't loading. It's ok, I tried the thumb drive again on the mac and on my Slax live CD and it mounts fine. I do believe i'm going to do a fresh install with the test26.s kernel, and recompile it just to include all of the ACPI options and leave it. It'll be a lot bigger than necessary but grand total kernel recompiles now is 17. I've read almost every "help" in the menuconfig to make sure I would need or not need something.
Oh well, thanks for your help. I'm just going to start over. I don't need the world's fastest bootup time afterall, i'd rather the system work
Take care.
--Queue
Thanks for your attempts to help and concern. I got fed up with it and wiped the system, did a fresh install with the huge26.s kernel, then recompiled it and took out only the things I know 100% do not apply to my system, and anything even questionable, left in. My kernel may have a bit more than needed, but it's ok.
Everything works fine now, including the thumb drive. There was no reason for it not to work from what I could tell, but oh well. Sometimes perhaps starting from square one is the best solution. Take care.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.