On Thu, 4 Oct 2007, Paul Check wrote: > On Tuesday 02 October 2007 14:47:55 you wrote: > > On Tue, 2 Oct 2007, Paul Check wrote: > > > > If you run "fdisk -l /dev/sdh" before trying to mount the camera, what > > > > is the output? > > > > > > The device doesn't exist before the camera is plugged in, thanks to udev. > > > So, the output is nothing. > > > > That's what you get if you run fdisk before the camera is plugged in. > > But what do you get if you run fdisk after the camera is plugged in and > > before you try to mount it? > > Interestingly enough, the output is still nothing, even though the > devices /dev/sdh and /dev/sdh1 are created. > > > > > What shows up in the "dmesg" log after you plug in the camera and try > > > > to mount it? > > The output seems to be longer than dmesg gets, so here is my > edited /var/log/messages file with the relevant sections:
Okay, the log is clear enough. The camera tells the computer that it has 16007041 sectors, and an unrecoverable error occurs when the computer tries to read sector 16007040. Evidently the camera really has one less sector than it claims. This is a very common bug. A blacklist entry should fix the problem. To create I will need to see the contents of /proc/bus/usb/devices with the camera plugged in. Alternatively, the same information is present in the output from "lsusb -v". Alan Stern ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Linux-usb-users@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
