16GB USB Drive Not Accessible

[Christopher A. Williams]

On Mon, 2008-10-27 at 17:05 -0400, James Kosin wrote:
> Christopher A. Williams wrote:
> > I recently bought a snazzy new 16GB USB pen drive from the local store -
> > it was only $29! I have several drives that are 8GB and smaller from the
> > same store that are the same brand.
> > 
> > Imagine my surprise when:
> > * The 16GB drive is not accessible on either F9 or F10 Snap 3
> > * The 8GB drives all work just fine on both F9 and F10 Snap 3
> > * The 16GB drive works fine on Windows XP
> > * The 16GB drive also works on a Windows XP VM running on top of F9!!!
> > 
<snip...>

> > Here's the dmesg output for those who might be interested:
> > 
> > ==============================================
> > usb 1-2.3: new high speed USB device using ehci_hcd and address 13
> > usb 1-2.3: configuration #1 chosen from 1 choice
> > scsi1264 : SCSI emulation for USB Mass Storage devices
> > usb-storage: device found at 13
> > usb-storage: waiting for device to settle before scanning
> > usb 1-2.3: New USB device found, idVendor=090c, idProduct=1000
> > usb 1-2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> > usb 1-2.3: Product: USB Flash Drive
> > usb 1-2.3: Manufacturer: USB 2.0
> > usb 1-2.3: SerialNumber: AA20000000000306
> > usb-storage: device scan complete
> > scsi 1264:0:0:0: Direct-Access     USB 2.0  USB Flash Drive  1100 PQ: 0
> > ANSI: 0 CCS
> > sd 1264:0:0:0: [sdb] 31326208 512-byte hardware sectors (16039 MB)
> > sd 1264:0:0:0: [sdb] Write Protect is off
> > sd 1264:0:0:0: [sdb] Mode Sense: 43 00 00 00
> > sd 1264:0:0:0: [sdb] Assuming drive cache: write through
> > sd 1264:0:0:0: [sdb] 31326208 512-byte hardware sectors (16039 MB)
> > sd 1264:0:0:0: [sdb] Write Protect is off
> > sd 1264:0:0:0: [sdb] Mode Sense: 43 00 00 00
> > sd 1264:0:0:0: [sdb] Assuming drive cache: write through
> >  sdb: sdb1
> > sd 1264:0:0:0: [sdb] Attached SCSI removable disk
> > sd 1264:0:0:0: Attached scsi generic sg3 type 0
> > ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
> > ata5.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
> >          cdb 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
> >          res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
> > ata5.00: status: { DRDY }
> > ata5: soft resetting link
> > ata5: nv_mode_filter: 0x1&0x1f01f->0x1, BIOS=0x1f000 (0xc5000000)
> > ACPI=0x1f01f (30:600:0x13)
> > ata5.00: configured for PIO0
> > ata5: EH complete
> > ==============================================
> >
> Chris,
> 
> Looks good.  Did you try mounting the drive and see if you can get a
> directory list?

Interesting... Indeed if I manually try to mount the drive as root to a
specific mount point, it does work.

So it seems it's automount that does not work. Neither does attempting
to mount the drive manually from a Nautilus window (right-click the "USB
Drive" icon and selecting "Mount Volume", or just double-clicking it).
All i get is an error window saying "Unable to mount drive".

What's strange is that automounting my 8GB drive of the same brand (as
well as an 8GB drive of a different brand) _does_ work. I don't have to
be root and mount it to a specific point manually to get to it.

What could be causing that...?

Cheers,

Chris


-- 
======================
"Never murder a man when he's
busy committing suicide."

-- Woodrow Wilson