On Mon, Jul 30, 2007 at 08:42:42PM -0700, Andrew Sackville-West wrote: > On Mon, Jul 30, 2007 at 05:34:13PM -0500, Mike McCarty wrote: > > Andrew Sackville-West wrote: > >> what is the output of tail -f /var/log/syslog > > > > See below... > > > >> when started before plugging the device in until after its plugged and > >> settled. If this a regular flash memory stick/card? For example, my camera > >> uses > >> bog-standard compact flash cards (about 1.25 inches square by 1/8 in > >> thick) and they plug into a standard card reader and mount as > > > > This is a FLASH card for a Sony camera. It is smaller than you describe, > > 2 inches long, 7/8 inch wide, and 1/8 inch thick (approx). It is a > > Sandisk 128 MB card. You may see one here: > > > > http://www.amazon.com/SanDisk-128-MB-Memory-Stick/dp/B0000630TK > > > >> /dev/sda1 as a vfat device. Is that what we're trying to do? or is it > >> some proprietary format device that doesn't plug into a standard > >> cardreader? > > > > I don't own a digital camera, so I can't answer that. It mounts fine > > using the Dazzle USB card reader dock, with Windows XP; the same > > hardware (dock and card) does not mount with Debian. > > > > Jul 30 14:40:51 localhost -- MARK -- > > Jul 30 15:00:51 localhost -- MARK -- > > Jul 30 15:02:01 localhost /USR/SBIN/CRON[25028]: (postgres) CMD (if ! pidof > > /usr/lib/postgresql/bin/pg_autovacuum > /dev/null && [ -x > > /usr/lib/postgresql/bin/do.maintenance ]; then > > /usr/lib/postgresql/bin/do.maintenance -a; fi) > > Jul 30 15:17:01 localhost /USR/SBIN/CRON[25309]: (root) CMD ( run-parts > > --report /etc/cron.hourly) > > Jul 30 15:40:51 localhost -- MARK -- > > Jul 30 16:00:51 localhost -- MARK -- > > Jul 30 16:17:01 localhost /USR/SBIN/CRON[26175]: (root) CMD ( run-parts > > --report /etc/cron.hourly) > > Jul 30 16:40:51 localhost -- MARK -- > > Jul 30 16:55:04 localhost kernel: hub.c: new USB device 00:07.2-2.3, > > assigned address 23 > > Jul 30 16:55:04 localhost kernel: WARNING: USB Mass Storage data integrity > > not assured > > Jul 30 16:55:04 localhost kernel: USB Mass Storage device found at 23 > > Jul 30 16:55:04 localhost hal.hotplug[27795]: could not get mountpoint for > > sysfs > > Jul 30 16:55:07 localhost usb.agent[27796]: usb-storage: already > > loaded > > Jul 30 16:55:15 localhost kernel: SCSI device sdc: 502784 512-byte hdwr > > sectors (257 MB) > > Jul 30 16:55:15 localhost kernel: sdc: Write Protect is off > > Jul 30 16:55:15 localhost kernel: /dev/scsi/host3/bus0/target0/lun0: p1 > > Jul 30 16:55:39 localhost kernel: usb.c: USB disconnect on device > > 00:07.2-2.3 address 23 > > Jul 30 16:55:39 localhost hal.hotplug[27849]: could not get mountpoint for > > sysfs > > Jul 30 16:55:58 localhost kernel: hub.c: new USB device 00:07.2-2.3, > > assigned address 24 > > Jul 30 16:55:58 localhost kernel: WARNING: USB Mass Storage data integrity > > not assured > > Jul 30 16:55:58 localhost kernel: USB Mass Storage device found at 24 > > Jul 30 16:55:58 localhost hal.hotplug[27883]: could not get mountpoint for > > sysfs > > Jul 30 16:56:01 localhost usb.agent[27884]: usb-storage: already > > loaded > > Jul 30 16:57:17 localhost kernel: sdc: Unit Not Ready, sense: > > Jul 30 16:57:17 localhost kernel: Info fld=0xa00 (nonstd), Current 00:00: > > sense key Not Ready > > Jul 30 16:57:17 localhost kernel: sdc : READ CAPACITY failed. > > Jul 30 16:57:17 localhost kernel: sdc : status = 1, message = 00, host = 0, > > driver = 08 > > Jul 30 16:57:17 localhost kernel: Info fld=0xa00 (nonstd), Current sd00:00: > > sense key Not Ready > > Jul 30 16:57:17 localhost kernel: sdc : block size assumed to be 512 bytes, > > disk size 1GB. > > Jul 30 16:57:17 localhost kernel: sdc: test WP failed, assume Write Enabled > > Jul 30 16:57:17 localhost kernel: /dev/scsi/host3/bus0/target0/lun0: I/O > > error: dev 08:20, sector 0 > > Jul 30 16:57:17 localhost kernel: I/O error: dev 08:20, sector 0 > > Jul 30 16:57:17 localhost kernel: unable to read partition table > > based on this I would see what you can see in the partition table: > > fdisk -ul /dev/sdc > > and I'd say you've probably got a corrupted partition table and the > device and windows happens to be broken in the right ways to make it > still work for them. On the assumption that the camera has its own > built in format option (mine does anyway...) then there's probably no > harm, but take a bit-for-bit copy of the original partition table (dd) > so you can recreate it later if you need to. some of th windows thumb drives make use of the whole drive as a parition - there is no partition table you mount the whole drive > > hth > > A
Attachment:
signature.asc
Description: Digital signature