[TriLUG] Problem w/ mounting digital camera

[David A. Cafaro]

Glad it helped.  Yeah, definitely a design defect ;-).  A friend and I
fought long and hard on that one trying to see if there was some other
simple thing we were missing.  In the end a bug report was filed, but
haven't checked up on it in ages (actually not sure I could even find it
if I wanted to check).


On Fri, 2004-01-02 at 14:30, Andrew Perrin wrote:
> That did it, thanks. That seems like a bug to me, though -- if the medium
> supports switching sizes, then the driver should either support it or
> squeal when it happens.
> 
> ap
> 
> ----------------------------------------------------------------------
> Andrew J Perrin - http://www.unc.edu/~aperrin
> Assistant Professor of Sociology, U of North Carolina, Chapel Hill
> clists at perrin.socsci.unc.edu * andrew_perrin (at) unc.edu
> 
> 
> On Fri, 2 Jan 2004, David A. Cafaro wrote:
> 
> > Seen this happen for other USB devices.  Try unloading and reloading the
> > modules (usb-scsi, etc..) that come up for that device.  For some reason
> > it likes to cache the information on USB scsi devices as far as size.
> > This only seems to come up on devices with interchangeable media
> > (including USB hard drives when you swap the hard drive inside).  Beyond
> > that haven't come up with a good solution yet.
> >
> >
> > On Fri, 2004-01-02 at 13:57, Andrew Perrin wrote:
> > > Greetings, and happy new year all.
> > >
> > > Got a new toy, a Fuji FinePix A310 digital camera. The xD card it came
> > > with (a 16MB one) works just great, mounting under linux as /dev/sde1 as a
> > > vfat device.  But I bought a bigger (128M) card, and now I get:
> > >
> > > mount -tvfat /dev/sde1 /mnt/camera/
> > > mount: wrong fs type, bad option, bad superblock on /dev/sde1,
> > >        or too many mounted file systems
> > >
> > >
> > > The log shows:
> > >
> > > Jan  2 13:45:58 joehill kernel: FAT: bogus logical sector size 65535
> > > Jan  2 13:45:58 joehill kernel: VFS: Can't find a valid FAT filesystem on
> > > dev 08:41.
> > >
> > >
> > > Perhaps more intriguingly, take a look at what fdisk thinks:
> > >
> > > fdisk /dev/sde
> > >
> > > Command (m for help): p
> > >
> > > Disk /dev/sde: 16 MB, 16384000 bytes
> > > 16 heads, 32 sectors/track, 62 cylinders
> > > Units = cylinders of 512 * 512 = 262144 bytes
> > >
> > >    Device Boot      Start         End      Blocks   Id  System
> > > /dev/sde1   *           1         500      127976+   6  FAT16
> > >
> > >
> > >
> > > ...so it thinks it's a 16M disk with a 128M partition on it, which might
> > > explain why it's "bogus." But how do I get this to work right? Any
> > > suggestions are welcome.
> > >
> > > Running kernel 2.4.20, debian testing/unstable.
> > >
> > > Thanks!
> > > Andy
> > >
> > > ----------------------------------------------------------------------
> > > Andrew J Perrin - http://www.unc.edu/~aperrin
> > > Assistant Professor of Sociology, U of North Carolina, Chapel Hill
> > > clists at perrin.socsci.unc.edu * andrew_perrin (at) unc.edu
> > --
> > David A. Cafaro <dac(at)cafaro.net>
> > Sys Admin to User: "You did what?!?"
> >
> > --
> > TriLUG mailing list        : http://www.trilug.org/mailman/listinfo/trilug
> > TriLUG Organizational FAQ  : http://trilug.org/faq/
> > TriLUG Member Services FAQ : http://members.trilug.org/services_faq/
> > TriLUG PGP Keyring         : http://trilug.org/~chrish/trilug.asc
> >
-- 
David A. Cafaro <dac(at)cafaro.net>
Sys Admin to User: "You did what?!?"