Okay so you have the same problem as I. Now hold onto your hat for the answer, this is really wild.
The simple version is that the usbkey is being recognized as having a CUMANA/ADFS partition. It seems that 1 in 256 usbkeys will have this problem. This is a very high number but most kernels do not have CONFIG_ACORN_PARTITION_CUMANA enabled by default. The newer kernels, like my 2.6.15.1, do have this obscure partition type on by default. My recommendation: Exchange the usbkey for a new one. There is a 255 to 1 chance that the replacement, even the same brand, will be okay. You can also just recompile your kernel and remove the cumana support but one day you may want to use the usbkey on another machine that you will discover has this obscure partition type enabled in its kernel and you will be usb-diskless, so to speak. That will not be a happy day. Read this link for the details: http://www.mail-archive.com/linux-fsdevel%40vger.kernel.org/msg01426.html Happy day, Chaim Below is a quote of the main content from that link: "Solution: You have enabled CONFIG_ACORN_PARTITION_CUMANA. Don't. Details: In partitions/check.c the adfspart_check_CUMANA routine is called earlier than msdos_partition(). This routine adfspart_check_CUMANA() does an adfs_partition() test to see whether the thing is an adfs partition. That test does adfs_checkbblk() which checks a checksum. The probability that random garbage will pass this test is 1 in 256. Disable CONFIG_ACORN_PARTITION_CUMANA unless you actually have an Acorn and Cumana partitions. Remarks: With low frequency people stumble over this problem. Typically they enable all possible partition types and do not read any help texts for the various types, so adding warnings would not help. Of course it is a bug that the kernel starts doing random partition recognition. These USB devices all have a DOS-type partition table. Certainly msdos_partition() should be tried first for them. And earlier already, it is bad that block_dev.c:do_open() does an automatic rescan_partitions(). Every now and then I mumble about these things, and usually Linus disagrees. However, these days we have udev and partx and blockdev --rereadpt. I do not really see any reason why the kernel should do automatic partition guessing for any disk encountered. (That is just as bad as automatic mounting for any filesystems seen.) I suppose we should slowly stop doing that, at least for all non-rootfs disks. Andries" On Sunday 07 May 2006 11:16, Avraham Rosenberg wrote: > From [EMAIL PROTECTED] Sat May 6 10:02:28 2006 > Date: Sat, 6 May 2006 10:02:28 +0300 > From: Avraham Rosenberg <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Cc: linux-il@linux.org.il > Subject: [EMAIL PROTECTED]: Re: problem with usb2.0 usbkey with kernel > 2.6.8] Message-ID: <[EMAIL PROTECTED]> > Mime-Version: 1.0 > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > User-Agent: Mutt/1.5.9i > Status: RO > Content-Length: 2635 > Lines: 74 > > ----- Forwarded message from avraham <[EMAIL PROTECTED]> ----- > > From: avraham <[EMAIL PROTECTED]> > To: Chaim Keren Tzion <[EMAIL PROTECTED]> > Cc: linux-il@linux.org.il > Subject: Re: problem with usb2.0 usbkey with kernel 2.6.8 > > On Sun, Apr 30, 2006 at 11:45:14PM +0300, Chaim Keren Tzion wrote: > > This sound very much like a problem I had/have. Does the dmesg show > > anything like this "[CUMANA/ADFS]" after connecting the disk-on-key? > >.... > > > > -- > > Chaim Keren Tzion > > [EMAIL PROTECTED] > > +972-54-811-9234 > > Hi Chaim, > Thanks for the input. The messages I got... > .... > Cheers, Avraham > > ----- End forwarded message ----- > > Hi Chaim, > I tried to answer you with the old computer, but the message > apparently did not get out (I had inserted a wrong address in the > configuration of exim, by mistake). > Here is the messages I receive now (debian amd64, kernel 2.6) > upon inserting: > new high speed USB device using address 3 > scsi3 : SCSI emulation for USB Mass Storage devices > Vendor: Kingston Model: DataTraveler 2.0 Rev: 1.04 > Type: Direct-Access ANSI SCSI revision: 02 > SCSI device sdb: 1001472 512-byte hdwr sectors (513 MB) > sdb: assuming Write Enabled > sdb: assuming drive cache: write through > /dev/scsi/host3/bus0/target0/lun0: [CUMANA/ADFS] p1<5>Attached > scsi removable disk sdb at scsi3, channel 0, id 0, lun 0 > then: > [EMAIL PROTECTED]:~$ su -c mount -t vfat /dev/sdb /usbkey > Password: > FAT: invalid media value (0xb9) > VFS: Can't find a valid FAT filesystem on dev sdb. > mount: wrong fs type, bad option, bad superblock on /dev/sdb, > missing codepage or other error > In some cases useful info is found in syslog - try > dmesg | tail or so > > [EMAIL PROTECTED]:~$ dmesg | tail > scsi3 : SCSI emulation for USB Mass Storage devices > Vendor: Kingston Model: DataTraveler 2.0 Rev: 1.04 > Type: Direct-Access ANSI SCSI revision: 02 > SCSI device sdb: 1001472 512-byte hdwr sectors (513 MB) > sdb: assuming Write Enabled > sdb: assuming drive cache: write through > /dev/scsi/host3/bus0/target0/lun0: [CUMANA/ADFS] p1<5>Attached scsi > removable disk sdb at scsi3, channel 0, id 0, lun 0 > USB Mass Storage device found at 3 > FAT: invalid media value (0xb9) > VFS: Can't find a valid FAT filesystem on dev sdb. > > [EMAIL PROTECTED]:~$ su -c dosfsck -a /dev/sdb (following a messsage posted > some time ago by Shlomo Solomon <[EMAIL PROTECTED]>) > Password: > dosfsck 2.11, 12 Mar 2005, FAT32, LFN > Currently, only 1 or 2 FATs are supported, not 191. > > The hexcode reported by fdisk is e ( W95 FAT16 (LBA) ) > > No problems with the same device with kernel 2.4.27 (debian > 3.1r1). > > Cheers, Avraham -- Chaim Keren Tzion [EMAIL PROTECTED] +972-54-811-9234 ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
