On Sat, 2005-02-05 at 10:21 -0500, Alan Stern wrote:
> On Sat, 5 Feb 2005, Jason Grant wrote:
> 
> The extract from your system log doesn't show anything going wrong.  Could 
> it be that your flash drive simply has an empty partition table, hence no 
> partition 1?  What does fdisk -l /dev/sdX show?
> 

'fdisk -l /dev/sdc' returns nothing.  'fdisk /dev/sdc' returns 'Unable
to read /dev/sdc'.

The log doesn't show anything wrong, however it also doesn't include a
lot of information that is produced when my working drive is plugged in.
I'm guessing that the full sequence as initiated by hotplug is bailing
somewhere, but I don't know how to debug it.  For example, if my device
was not supported, or if there are partitioning issues, can I turn on
extra logging to see this?

The log info from my good flash drive is shown below - note how the bad
drive doesn't include the information like '...Write Protect..." and
"... sdb: sdb1 ...", so I think the logging is indicative that something
*is* going wrong.

Thanks,

Jason


----  Logging from good drive, showing expected additional info ----
Feb  6 10:05:02 talby kernel:   Vendor: USB       Model: FLASH DISK
Rev: 0426
Feb  6 10:05:02 talby kernel:   Type:   Direct-Access
ANSI SCSI revision: 02
Feb  6 10:05:02 talby kernel: SCSI device sdb: 64000 512-byte hdwr
sectors (33 MB)
Feb  6 10:05:02 talby kernel: sdb: Write Protect is off
Feb  6 10:05:02 talby kernel: sdb: assuming drive cache: write through
Feb  6 10:05:02 talby kernel: SCSI device sdb: 64000 512-byte hdwr
sectors (33 MB)
Feb  6 10:05:02 talby kernel: sdb: Write Protect is off
Feb  6 10:05:02 talby kernel: sdb: assuming drive cache: write through
Feb  6 10:05:02 talby kernel:  sdb: sdb1
Feb  6 10:05:02 talby kernel: Attached scsi removable disk sdb at scsi3,
channel 0, id 0, lun 0
Feb  6 10:05:03 talby scsi.agent[20305]: disk
at /devices/pci0000:00/0000:00:1d.3/usb5/5-1/5-1:1.0/host3/target3:0:0/3:0:0:0
Feb  6 10:05:03 talby fstab-sync[20332]: added mount
point /media/usbdisk for /dev/sdb1
Feb  6 10:05:03 talby kernel: FAT: utf8 is not a recommended IO charset
for FAT filesystems, filesystem will be case sensitive!
Feb  6 10:05:03 talby kernel: SELinux: initialized (dev sdb1, type
vfat), uses genfs_contexts




-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users

Reply via email to