| View previous topic :: View next topic |
| Author |
Message |
Utoxin
Guru
Joined: 19 Apr 2002
Posts: 413
Location: American Fork, UT
|
 Posted: Tue Nov 22, 2005 6:28 pm Post subject: vfat partitions won't mount [SOLVED] |
 |
|
I've got problems. I've got an external USB harddrive that has worked for months. The other day, I had to reboot, and the drive just stopped working. I plugged it into my windows machine, and it mounted right up. I ran every disk check I can get my hands on, and they all come up clean.
The hardware is still being detected properly on Linux. But it refuses to mount.
Troubleshooting:
| Code: |
mwalker ~ # mount /mnt/usb1
mount: wrong fs type, bad option, bad superblock on /dev/lacie_drive,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
mwalker ~ # cat /etc/fstab
# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.
/dev/hda1 /boot ext2 noauto,noatime 1 1
/dev/hda3 / reiserfs defaults 0 0
/dev/hda2 none swap sw 0 0
/dev/lacie_drive /mnt/usb1 vfat auto,users,uid=1000,gid=100,dmask=007,fmask=117 0 0
# NOTE: The next line is critical for boot!
none /proc proc defaults 0 0
none /dev/shm tmpfs defaults 0 0
/dev/hdc /media/cdrom auto user,exec,noauto,managed 0 0
/dev/sda1 /media/usbdisk vfat user,exec,noauto,utf8,managed 0 0
mwalker ~ # ls -la /dev/lacie_drive
brw-rw---- 1 root disk 8, 0 Nov 22 10:59 /dev/lacie_drive
mwalker ~ # ls -la /dev/sda1
lrwxrwxrwx 1 root root 11 Nov 22 10:59 /dev/sda1 -> lacie_drive
mwalker ~ # dmesg | tail
sda: sda1
Attached scsi disk sda at scsi1, channel 0, id 0, lun 0
Attached scsi generic sg0 at scsi1, channel 0, id 0, lun 0, type 0
usb-storage: device scan complete
FAT: bogus number of FAT structure
VFS: Can't find a valid FAT filesystem on dev sda.
FAT: bogus number of FAT structure
VFS: Can't find a valid FAT filesystem on dev sda.
FAT: bogus number of FAT structure
VFS: Can't find a valid FAT filesystem on dev sda.
mwalker ~ # fsck.vfat -a /dev/sda1
dosfsck 2.11, 12 Mar 2005, FAT32, LFN
Currently, only 1 or 2 FATs are supported, not 0.
mwalker ~ # uname -a
Linux mwalker 2.6.14-gentoo-r2 #1 PREEMPT Tue Nov 22 10:32:18 MST 2005 i686 Intel(R) Pentium(R) 4 CPU 2.80GHz GenuineIntel GNU/Linux
mwalker ~ # lsmod
Module Size Used by
nvidia 3707912 8
smbfs 63480 2
snd_pcm_oss 48544 0
snd_mixer_oss 17280 1 snd_pcm_oss
snd_seq_oss 32640 0
snd_seq_midi_event 6016 1 snd_seq_oss
snd_seq 49936 4 snd_seq_oss,snd_seq_midi_event
snd_seq_device 7052 2 snd_seq_oss,snd_seq
snd_intel8x0 30304 2
snd_ac97_codec 93820 1 snd_intel8x0
snd_ac97_bus 2048 1 snd_ac97_codec
snd_pcm 82696 3 snd_pcm_oss,snd_intel8x0,snd_ac97_codec
snd_timer 21636 2 snd_seq,snd_pcm
snd 46308 13 snd_pcm_oss,snd_mixer_oss,snd_seq_oss,snd_seq,snd_seq_device,snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer
snd_page_alloc 8712 2 snd_intel8x0,snd_pcm
dm_mod 52796 0
usb_storage 31364 0
|
I was running 2.6.12-gentoo-r9 previously, but upgraded today, in the hopes that it would fix the problem.
The above drive is an actual external harddrive, but the same thing is now also happening to USB flash drive that I use. It also mounts properly in windows. I tried copying everything off the flash drive, and reformatting it, (full, not quick) but it didn't make any difference. I don't have a handy system with enough disk space to do the same thing for the USB harddrive, but I doubt it would work anyway.
Any tips? Any other information needed?
_________________
Gentoo:
1. A small fast penguin from Antarctica.
2. A small fast penguin on your computer.
Cool.
Last edited by Utoxin on Tue Nov 22, 2005 7:22 pm; edited 1 time in total |
|
| Back to top |
|
 |
j-m
Retired Dev
Joined: 31 Oct 2004
Posts: 975
|
| Posted: Tue Nov 22, 2005 6:54 pm Post subject: |
|
|
| I'd suggest that you have a look at it with fdisk -l; these USB sticks are very often partitioned in a wrong way - or even not at all and Windows formats the whole device, not the partition. If the output looks weird, delete all partitions, create just one and format it to vfat. Then try again. |
|
| Back to top |
|
|
Akhouk
Guru
Joined: 23 May 2003
Posts: 476
Location: The Two Niles, Africa
|
| Posted: Tue Nov 22, 2005 6:58 pm Post subject: |
|
|
The dmesg output from your post...is that for the lacie external drive or the usb pen drive? As it is saying that it is attached to /dev/sda not to /dev/lacie.
I think there might be a confusion with your device names and symlinks.
_________________
AMD 64 3500+, 2Gb RAM DDR400, 2 x 180Gb SATA, 256Mb Nvidia |
|
| Back to top |
|
|
Utoxin
Guru
Joined: 19 Apr 2002
Posts: 413
Location: American Fork, UT
|
| Posted: Tue Nov 22, 2005 7:03 pm Post subject: |
|
|
The dmesg is for the Lacie drive. And it's correct. It's been working that way for ages. The device itself registers as /dev/sda. The first partition is registered as /dev/lacie_drive, with a symlink at /dev/sda1, for sanity.
As for the fdisk -l output:
| Code: |
mwalker ~ # fdisk -l /dev/sda
Disk /dev/sda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 9729 78148161 b W95 FAT32
|
I know about the odd formatting on USB devices, and I specifically reformatted this after I got it. It's been working for over a year in this configuration.
Addendum:
Concerning the device filenames. I'm using udev. Here's the rules file for my two main USB devices:
| Code: |
BUS=="usb",SYSFS{serial}=="1069F009023006011104",NAME="lexar_drive",SYMLINK="%k"
BUS=="usb",SYSFS{serial}=="10000E000665D01A",NAME="lacie_drive",SYMLINK="%k"
|
_________________
Gentoo:
1. A small fast penguin from Antarctica.
2. A small fast penguin on your computer.
Cool. |
|
| Back to top |
|
|
j-m
Retired Dev
Joined: 31 Oct 2004
Posts: 975
|
| Posted: Tue Nov 22, 2005 7:08 pm Post subject: |
|
|
| Well, I'm sorry but according to your dmesg output the filesystem is pretty much borked... did you try to repartition and reformat the drive again? Also, for troubleshooting try to mount the thing with normal device entry, not some aliases created by custom udev rules. |
|
| Back to top |
|
|
Utoxin
Guru
Joined: 19 Apr 2002
Posts: 413
Location: American Fork, UT
|
| Posted: Tue Nov 22, 2005 7:16 pm Post subject: |
|
|
Thanks, j-m. Tried turning off the udev rule, and it's working now. I'm baffled as to why that would make a difference, and it throws a big wrench into my attempts to easy the annoyances of dealing with USB drives and changing names. :/
Any suggestions on a better way to set up the udev rules?
_________________
Gentoo:
1. A small fast penguin from Antarctica.
2. A small fast penguin on your computer.
Cool. |
|
| Back to top |
|
|
j-m
Retired Dev
Joined: 31 Oct 2004
Posts: 975
|
| Posted: Tue Nov 22, 2005 7:20 pm Post subject: |
|
|
| Utoxin wrote: | Thanks, j-m. Tried turning off the udev rule, and it's working now. I'm baffled as to why that would make a difference, and it throws a big wrench into my attempts to easy the annoyances of dealing with USB drives and changing names. :/
Any suggestions on a better way to set up the udev rules? |
I'm not an expert on writing udev rules. There have been significant changes lately wrt these rules and their parsing (udev ebuild points this out when upgrading).
Please, read the docs and adjust them accordingly. If those rules are one year old then they are pretty much guaranteed to break with >=udev-070. |
|
| Back to top |
|
|
btlee
Apprentice
Joined: 03 Sep 2004
Posts: 168
Location: San Francisco
|
| Posted: Tue Nov 22, 2005 7:23 pm Post subject: |
|
|
did you built native language support in the kernel?
If you made it modules, check if the modules was loaded.
In your message, there is no clue if the modules is loaded.
The same thing is applied to FAT supported.
_________________
AMD64 3200+, 2G/160G+250G
DELL 700m, 1.8GHz, 2G/80G
iBook G3-500Mhz, 640M/100G |
|
| Back to top |
|
|
Utoxin
Guru
Joined: 19 Apr 2002
Posts: 413
Location: American Fork, UT
|
| Posted: Tue Nov 22, 2005 7:23 pm Post subject: |
|
|
Was in the process of reading some docs while I waited to see if you had an answer of your own. Came up with the following that works as intended:
| Code: |
BUS=="usb",SYSFS{serial}=="1069F009023006011104",KERNEL=="sd?1",NAME="%k",SYMLINK="lexar_drive"
BUS=="usb",SYSFS{serial}=="10000E000665D01A",KERNEL=="sd?1",NAME="%k",SYMLINK="lacie_drive"
|
Basically, let it use the default kernel names for the devices, and set up a symlink for the static name I want it to use. It works now, with either the kernel name or the static name.
Thanks for your time.
_________________
Gentoo:
1. A small fast penguin from Antarctica.
2. A small fast penguin on your computer.
Cool. |
|
| Back to top |
|
|
Headrush
Watchman
Joined: 06 Nov 2003
Posts: 5597
Location: Bizarro World
|
| Posted: Tue Nov 22, 2005 7:27 pm Post subject: |
|
|
Your udev rules are creating device nodes for the entire drive, not partitions.
Here is my custom udev rules for external USB drive: | Code: | | BUS="usb", SYSFS{idVendor}="067b", SYSFS{idProduct}="3507", NAME="usbHD%n", SYMLINK="%k" |
Some mount mechanisms have trouble when the device node is a symlink, hence why the original node name is a symlink and my device name is the "real" device node. (Obviously you already know that, but to help others)
You'll have to change your /etc/fstab to use lexar_drive1, for the partition. (Or whatever partition scheme you use)
Edit: You just beat me. Use the %n instead if ?1 and you will get the links for all partitions. I know if you use pmount, atleast as of version 0.9.3-r1, the reference to a hard drive in /etc/pmount.allow has to be a "real" device node, not a symlink. |
|
| Back to top |
|
|
Utoxin
Guru
Joined: 19 Apr 2002
Posts: 413
Location: American Fork, UT
|
| Posted: Tue Nov 22, 2005 7:32 pm Post subject: |
|
|
I use automount, and it's working perfectly with my rules. As far as the nodes are concerned, the only difference is that /dev/sda1 is a real node now, instead of a symlink to /dev/lacie_drive. Instead, the static name is now a symlink to the kernel assigned node.
_________________
Gentoo:
1. A small fast penguin from Antarctica.
2. A small fast penguin on your computer.
Cool. |
|
| Back to top |
|
|
Headrush
Watchman
Joined: 06 Nov 2003
Posts: 5597
Location: Bizarro World
|
| Posted: Tue Nov 22, 2005 7:39 pm Post subject: |
|
|
| Utoxin wrote: | | I use automount, and it's working perfectly with my rules. As far as the nodes are concerned, the only difference is that /dev/sda1 is a real node now, instead of a symlink to /dev/lacie_drive. Instead, the static name is now a symlink to the kernel assigned node. |
Glad its working. If you switch to pmount remember this, and then you wouldn't have to create any /etc/fstab rules.  |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
