Bug 124673

Fedore Core (both 1 and 2, standard installations) doesn't seam to 
fork with USB 2.0 flash devices. I have a Transcent 128Mb flash stick 
and it works perfectly on Mac and Windows. 
 
When I plug it in I see the following in the /var/log/messages: 
----------------------------------------- 
May 26 16:20:36 dim kernel: usb 1-1: new full speed USB device using 
address 6 
May 26 16:20:36 dim kernel: scsi4 : SCSI emulation for USB Mass 
Storage devices 
May 26 16:20:36 dim kernel:   Vendor: JetFlash  Model: 
TS128MJF2B        
Rev: 2.00 
May 26 16:20:36 dim kernel:   Type:   Direct-
Access                      
ANSI SCSI revision: 02 
May 26 16:20:36 dim kernel: SCSI device sda: 256000 512-byte hdwr 
sectors (131 MB) 
May 26 16:20:36 dim kernel: sda: assuming Write Enabled 
May 26 16:20:36 dim kernel: sda: assuming drive cache: write through 
May 26 16:20:36 dim kernel:  sda: sda1 sda2 sda3 sda4 
May 26 16:20:36 dim kernel: Attached scsi removable disk sda at 
scsi4, channel 0, id 0, lun 0 
May 26 16:20:36 dim scsi.agent[2262]: disk 
at /devices/pci0000:00/0000:00:07.2/usb1/1-1/1-1:1.0/host4/4:0:0:0 
May 26 16:22:20 dim kernel: Buffer I/O error on device sda1, logical 
block 0 
May 26 16:22:20 dim kernel: Buffer I/O error on device sda1, logical 
block 1 
May 26 16:22:20 dim kernel: Buffer I/O error on device sda1, logical 
block 2 
May 26 16:22:20 dim kernel: Buffer I/O error on device sda1, logical 
block 3 
May 26 16:22:20 dim kernel: Buffer I/O error on device sda1, logical 
block 4 
----------------------------------------------- 
 
Also the /mnt/flash directory is being created automatically and it's 
empty. 
I've experimented several days trying to get it work. I've tried 
mounting the devices like /dev/sda1, sda2, 3.., sdb1, ...,  etc. It's 
just says  
/dev/sda1: Input/output error 
mount: /dev/sda1: can't read superblock 

I've finally found the ability to mount the device manually:
mount /dev/sda /mnt/flash

HOWEVER : It is still not understood WHY the Transcend device with 
chip TS128MJF2A inside is autodetected and automounted as /dev/sda1 
BUT device with chip TS128MJF2B inside couldn't mount automatically, 
(should be mounted manually as /dev/sda).

Could someone please explain the difference between those two devices?

Is it a X-in-1 Cardreader? perhaps
# modprobe scsi_mod max_luns=6
helps. It worked for me.

No, it's a simple USB flash trinket-like storage, it's not a card 
reader.
As I said:
Case 1:
Device with chip TS128MJF2A automounts on insertion as /dev/sda1 
to /mnt/flash
BUT:
Case 2:
Device with chip TS128MJF2B tries to automount also (i.e. it writes 
absolutely the same line to the /etc/fstab as in case 1), but in fact 
it COULD NOT mount. 
To mount it you have to:
- manually insert similar line to fstab, particularly 
changing /dev/sda1 to /dev/sda.
- create /mnt/flash1 directory
- mount the device

Of course, I wrote a script which does that. What I'm asking is:
1) Please try to correct this incomprehensible behaviour in the next 
releases of kernel.
2) Why those two very similar devices are treated differently by the 
kernel?
3) When working in *nix would be as pleasantly as on Mac or Windows ?

Fedora Core 2 has now reached end of life, and no further updates will be
provided by Red Hat.  The Fedora legacy project will be producing further kernel
updates for security problems only.

If this bug has not been fixed in the latest Fedora Core 2 update kernel, please
try to reproduce it under Fedora Core 3, and reopen if necessary, changing the
product version accordingly.

Thank you.