Bug 249272

*** Bug 249132 has been marked as a duplicate of this bug. ***

Created attachment 159797 [details]
fragments from /var/log/messages

First of all, see my note in
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=249132

Now, some update. USB drive with vfat FS and ATA CD/DVD with ISO FS connected
with ATA/USB adapter can be mounted automatically. However, ATA drive with vfat
FS connected with ATA/USB adapter is not mounted automatically but can be
mounted manually. See attachment with fragments from /var/log/messages

I repeat: I can't mount vfat manually. mount command says that fs type is wrong.
fs autodetection does not work either.

I also run 2.6.22.1 kernel (stock 2.6.22.1-27.fc7) and as follows from my 
messages, I see completely different behavior. Just a simple test, could you 
please try these commands as root:

modprobe vfat ; cat /proc/filesystems

What do you have in the output?

You know what? I ran cat /proc/filesystems before and after modprobe vfat.
Before there was no vfat and after it was present. So why vfat module does not
start automatically?

But that didn't help. Though vfat is present in /proc/filesystems I can't mount
it anyway.

Here's dmesg | tail

sd 8:0:0:0: [sdb] Mode Sense: 00 00 00 00
sd 8:0:0:0: [sdb] Assuming drive cache: write through
 sdb: sdb1
sd 8:0:0:0: [sdb] Attached SCSI removable disk
sd 8:0:0:0: Attached scsi generic sg3 type 0
hfs: unable to find HFS+ superblock
FAT: invalid media value (0x01)
VFS: Can't find a valid FAT filesystem on dev sdb.
FAT: invalid media value (0x01)
VFS: Can't find a valid FAT filesystem on dev sdb

(In reply to comment #5)
> You know what? I ran cat /proc/filesystems before and after modprobe vfat.
> Before there was no vfat and after it was present. So why vfat module does not
> start automatically?

This is normal. vfat as many other modules is loaded automatically on demand. 
When not in use for some time, modules are unloaded to free memory.

My question was just to check if vfat is enabled in kernel configuration. Since 
vfat module present, this part seems OK.

Regarding your dmesg output, I think we need to wait what kernel maintainers 
say...

Could you please try this command:

sfdisk -l /dev/sdb

(Don't try other options in sfdisk!!!)

And what did you try to mount manually? /dev/sdb or /dev/sdb1?

Oh, shoooooot!!! I didn't notice that sdb1 was present (hmmm.. I don't remember
flash drives had /dev/sdxn format. But perhaps that was changed in latest
kernel). sdb1 mounts normally. But wny automatic mount does not work?

This is not a kernel, this is just common USB drives layout. They all have 
partition table just like hard drives. Regarding automatic mount, I think this 
is the problem with some USB stuff in kernel. Something works, something 
doesn't.

I'm really surprised by status of Fedora 7 really... There is no well working 
kernel yet: 2.6.21 suffers from bug in libata module which strikes the disk 
head every shutdown, in 2.6.22 this bug was fixed but usb stuff seems heavily 
broken. If I knew that I would expect more stable Fedora update before 
upgrading from FC5. Let's see what kernel maintainers say but I'm afraid I will 
do next Fedora major upgrade in 5-6 months after F9 release to settle things 
down.

The Source, there will be a new kernel 2.6.22.1-33.fc7 in testing soon. You 
also can get it here right now: http://koji.fedoraproject.org/packages/kernel/
2.6.22.1/33.fc7/i686/kernel-2.6.22.1-33.fc7.i686.rpm (make sure you will paste 
entire link as it very long and can brake here in bugzilla page). With this new 
kernel some problem is solved, some not (see https://bugzilla.redhat.com/
bugzilla/show_bug.cgi?id=249132 for more info). You may try it to check if your 
mount vfat bug is fixed.

Hmm, sorry for testing... Does bugzilla allow html in the message? This is a 
link to the <a href=http://koji.fedoraproject.org/packages/kernel/
2.6.22.1/33.fc7/i686/kernel-2.6.22.1-33.fc7.i686.rpm>new kernel</a>

Nope...

Some update regarding automatic mounting problem... I tested 2.6.22.1-33.fc7 
kernel and unfortunately it does not mount Nokia E65 phone automatically (see 
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=249132#c5). It mounts USB 
flash memory. ATA hard drive connected over ATA-USB adapter: it is mounted 
automatically when the drive is connected first time. If I then unmount it 
choosing "Safely remove" in the KDE drive icon, remove the USB cable, then 
connect it again, the kernel recognizes the drive and partition but it is not 
automatically mounted. If I disconnect the USB cable, remove the power from the 
drive, then power-on it again and connect USB cable, it is again mounted 
automatically. Any idea?

It seems there is a solution for this problem in a discussion regarding bug 
#249161: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=249161

Duplicate bug?

I'm 99% this is a dupe of bug 249282 so closing as such.

*** This bug has been marked as a duplicate of 249282 ***