PDA

View Full Version : USB stick and drive not showing in nautilus


kevin tough
2nd March 2009, 12:35 AM
Hi,

the first version I installed of 11 was a 64 bit version (where was the CD Pen when I needed it). The install worked after some changes in grub.conf. Fedora 11 figured out the mistake (wrong DVD) and has installed ...git3.fc11.i586 followed by ...git4.fc11.i586
Now in dmesg, I think, the USB drive has been correctly found but it does not show in nautilus. In the menu System -> Preferences I do not find the old/missing item "Hardware". Here it was possible to select some options for removable media.

Here is the log in dmesg:

sd 12:0:0:0: [sdc] Attached SCSI disk
sd 12:0:0:0: Attached scsi generic sg3 type 0
usb 2-1: USB disconnect, address 5
usb 2-1: new high speed USB device using ehci_hcd and address 6
usb 2-1: New USB device found, idVendor=1058, idProduct=0704
usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 2-1: Product: External HDD
usb 2-1: Manufacturer: Western Digital
usb 2-1: SerialNumber: 5758453730384A3546383138
usb 2-1: configuration #1 chosen from 1 choice
scsi13 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 6
usb-storage: waiting for device to settle before scanning
usb-storage: device scan complete
scsi 13:0:0:0: Direct-Access WD 3200BMV External 1.05 PQ: 0 ANSI: 4
sd 13:0:0:0: [sdc] 625142448 512-byte hardware sectors: (320 GB/298 GiB)
sd 13:0:0:0: [sdc] Write Protect is off
sd 13:0:0:0: [sdc] Mode Sense: 21 00 00 00
sd 13:0:0:0: [sdc] Assuming drive cache: write through
sd 13:0:0:0: [sdc] 625142448 512-byte hardware sectors: (320 GB/298 GiB)
sd 13:0:0:0: [sdc] Write Protect is off
sd 13:0:0:0: [sdc] Mode Sense: 21 00 00 00
sd 13:0:0:0: [sdc] Assuming drive cache: write through
sdc: sdc1
sd 13:0:0:0: [sdc] Attached SCSI disk
sd 13:0:0:0: Attached scsi generic sg3 type 0
[kevin@AmilioXi2550Ket ~]$

Any comments on how to check this further would be greatly appreciated.
Would you consider this a bug to report?

Namaste,

Kevin Tough

P.S. In my Console the text is now in black with a red background but I can't change it in the Console GUI. Any ideas?

kevin tough
3rd March 2009, 08:13 AM
Yep, updated to ...git5.fc11 and the problem is fixed.

Thanx Fedora Team

DrewP
15th May 2009, 07:00 PM

After testing compatibility with about a dozen USB keys I have one key that produces huge quantities of messages similar to the one in the original post. I have tested that key on multiple PCs with Windows, Fedora 10, Fedora 11 Preview Live CD and one PC with Fedora 11 Live preview installed and with all updates to date installed. The only common factor in the failures is Fedora 11 and that one USB key.

The most recent build I tested with was:
$ uname -a
Linux c400.hogwarts.local 2.6.29.3-140.fc11.i686.PAE #1 SMP Tue May 12 10:44:10 EDT 2009 i686 i686 i386 GNU/Linux


This is what happened when I plugged it in and about a minute later pulled it out again


May 15 17:24:32 c400 kernel: usb 1-1: new full speed USB device using uhci_hcd and address 3
May 15 17:24:32 c400 kernel: usb 1-1: New USB device found, idVendor=1307, idProduct=0163
May 15 17:24:32 c400 kernel: usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
May 15 17:24:32 c400 kernel: usb 1-1: Product: USB Mass Storage Device
May 15 17:24:32 c400 kernel: usb 1-1: Manufacturer: USBest Technology
May 15 17:24:32 c400 kernel: usb 1-1: SerialNumber: 00000000000107
May 15 17:24:32 c400 kernel: usb 1-1: configuration #1 chosen from 1 choice
May 15 17:24:32 c400 kernel: scsi3 : SCSI emulation for USB Mass Storage devices
May 15 17:24:37 c400 kernel: scsi 3:0:0:0: Direct-Access Ut163 USB2FlashStorage 0.00 PQ: 0 ANSI: 2
May 15 17:24:37 c400 kernel: sd 3:0:0:0: [sdb] 501760 512-byte hardware sectors: (256 MB/245 MiB)
May 15 17:24:37 c400 kernel: sd 3:0:0:0: [sdb] Write Protect is off
May 15 17:24:37 c400 kernel: sd 3:0:0:0: [sdb] Assuming drive cache: write through
May 15 17:24:38 c400 kernel: sd 3:0:0:0: [sdb] 501760 512-byte hardware sectors: (256 MB/245 MiB)
May 15 17:24:38 c400 kernel: sd 3:0:0:0: [sdb] Write Protect is off
May 15 17:24:38 c400 kernel: sd 3:0:0:0: [sdb] Assuming drive cache: write through
May 15 17:24:38 c400 kernel: sdb: sdb1
May 15 17:24:38 c400 kernel: sd 3:0:0:0: [sdb] Attached SCSI removable disk
May 15 17:24:38 c400 kernel: sd 3:0:0:0: Attached scsi generic sg1 type 0
May 15 17:24:38 c400 kernel: sd 3:0:0:0: [sdb] 501760 512-byte hardware sectors: (256 MB/245 MiB)
May 15 17:24:38 c400 kernel: sd 3:0:0:0: [sdb] Write Protect is off
May 15 17:24:38 c400 kernel: sd 3:0:0:0: [sdb] Assuming drive cache: write through
May 15 17:24:38 c400 kernel: sd 3:0:0:0: [sdb] 501760 512-byte hardware sectors: (256 MB/245 MiB)
May 15 17:24:38 c400 kernel: sd 3:0:0:0: [sdb] Write Protect is off
May 15 17:24:38 c400 kernel: sd 3:0:0:0: [sdb] Assuming drive cache: write through
May 15 17:24:38 c400 kernel: sdb:Dev sdb: unable to read RDB block 0
May 15 17:24:38 c400 kernel: unable to read partition table
May 15 17:24:38 c400 kernel: sd 3:0:0:0: [sdb] 501760 512-byte hardware sectors: (256 MB/245 MiB)
May 15 17:24:38 c400 kernel: sd 3:0:0:0: [sdb] Write Protect is off
May 15 17:24:38 c400 kernel: sd 3:0:0:0: [sdb] Assuming drive cache: write through
May 15 17:24:38 c400 kernel: sd 3:0:0:0: [sdb] 501760 512-byte hardware sectors: (256 MB/245 MiB)
May 15 17:24:38 c400 kernel: sd 3:0:0:0: [sdb] Write Protect is off
May 15 17:24:38 c400 kernel: sd 3:0:0:0: [sdb] Assuming drive cache: write through
May 15 17:24:38 c400 kernel: sdb: sdb1
May 15 17:24:40 c400 kernel: sd 3:0:0:0: [sdb] 501760 512-byte hardware sectors: (256 MB/245 MiB)
.
~ 1200 lines omitted for brevity
.
May 15 17:25:26 c400 kernel: sd 3:0:0:0: [sdb] Write Protect is off
May 15 17:25:26 c400 kernel: sd 3:0:0:0: [sdb] Assuming drive cache: write through
May 15 17:25:26 c400 kernel: sdb:Dev sdb: unable to read RDB block 0
May 15 17:25:26 c400 kernel: unable to read partition table
May 15 17:25:26 c400 kernel: sd 3:0:0:0: [sdb] 501760 512-byte hardware sectors: (256 MB/245 MiB)
May 15 17:25:26 c400 kernel: sd 3:0:0:0: [sdb] Write Protect is off
May 15 17:25:26 c400 kernel: sd 3:0:0:0: [sdb] Assuming drive cache: write through
May 15 17:25:26 c400 kernel: sd 3:0:0:0: [sdb] 501760 512-byte hardware sectors: (256 MB/245 MiB)
May 15 17:25:26 c400 kernel: sd 3:0:0:0: [sdb] Write Protect is off
May 15 17:25:26 c400 kernel: sd 3:0:0:0: [sdb] Assuming drive cache: write through
May 15 17:25:26 c400 kernel: sdb: sdb1
May 15 17:25:27 c400 kernel: sd 3:0:0:0: [sdb] Unhandled error code
May 15 17:25:27 c400 kernel: sd 3:0:0:0: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK,SUGGEST_OK
May 15 17:25:27 c400 kernel: end_request: I/O error, dev sdb, sector 501696
May 15 17:25:27 c400 kernel: Buffer I/O error on device sdb, logical block 62712
May 15 17:25:27 c400 kernel: usb 1-1: USB disconnect, address 3
May 15 17:25:27 c400 kernel: scsi 3:0:0:0: [sdb] Unhandled error code
May 15 17:25:27 c400 kernel: scsi 3:0:0:0: [sdb] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK,SUGGEST_OK
May 15 17:25:27 c400 kernel: end_request: I/O error, dev sdb, sector 501696
May 15 17:25:27 c400 kernel: Buffer I/O error on device sdb, logical block 62712
May 15 17:25:27 c400 kernel: scsi 3:0:0:0: rejecting I/O to dead device
May 15 17:25:27 c400 kernel: scsi 3:0:0:0: rejecting I/O to dead device
May 15 17:25:27 c400 kernel: scsi 3:0:0:0: rejecting I/O to dead device
May 15 17:25:27 c400 kernel: scsi 3:0:0:0: [sdb] READ CAPACITY failed
May 15 17:25:27 c400 kernel: scsi 3:0:0:0: [sdb] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK,SUGGEST_OK
May 15 17:25:27 c400 kernel: scsi 3:0:0:0: [sdb] Sense not available.
May 15 17:25:27 c400 kernel: scsi 3:0:0:0: rejecting I/O to dead device
May 15 17:25:27 c400 kernel: scsi 3:0:0:0: [sdb] Write Protect is off
May 15 17:25:27 c400 kernel: scsi 3:0:0:0: [sdb] Assuming drive cache: write through
May 15 17:25:27 c400 usb_id[13650]: unable to access '/devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1:1.0/host3/target3:0:0/3:0:0:0/block/sdb'
May 15 17:25:27 c400 usb_id[13675]: unable to access '/devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1:1.0/host3/target3:0:0/3:0:0:0/block/sdb'
May 15 17:25:27 c400 usb_id[13701]: unable to access '/devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1:1.0/host3/target3:0:0/3:0:0:0/block/sdb'
.
~ 75 lines omitted for brevity
.
May 15 17:25:37 c400 usb_id[16161]: unable to access '/devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1:1.0/host3/target3:0:0/3:0:0:0/block/sdb'
May 15 17:25:37 c400 usb_id[16185]: unable to access '/devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1:1.0/host3/target3:0:0/3:0:0:0/block/sdb'


As stated earlier this only happened with one key which was a no-name freebie I was given at a trade show and this problem is no big deal for me. However I did eventually lose some data while testing it and had to re-format it (problem was still there after re-formatting) so it might be a big deal for someone else.

For interest the key is this: (discovered with a Fedora 10 box)

$ lsub
Bus 001 Device 015: ID 1307:0163 Transcend Information, Inc. 512MB/1GB Flash Drive
.
.
# lshw
.
.
*-usb
description: Mass storage device
product: USB Mass Storage Device
vendor: USBest Technology
physical id: 5
bus info: usb@1:5
logical name: scsi14
version: 1.00
serial: 00000000000107
capabilities: usb-2.00 scsi emulated scsi-host
configuration: driver=usb-storage maxpower=80mA speed=480.0MB/s
*-disk
description: SCSI Disk
physical id: 0.0.0
bus info: scsi@14:0.0.0
logical name: /dev/sdb
size: 245MiB (256MB)
capabilities: partitioned partitioned:dos
configuration: signature=91f72d24
*-volume
description: Windows FAT volume
vendor: mkdosfs
physical id: 1
bus info: scsi@14:0.0.0,1
logical name: /dev/sdb1
logical name: /media/USBKEY243MB
version: FAT32
serial: acb9-a5d6
size: 243MiB
capacity: 243MiB
capabilities: primary fat initialized
configuration: FATs=2 filesystem=fat label=USBKEY243MB mount.fstype=vfat mount.options=rw,nosuid,nodev,uid=501,fmask=0022,d mask=0022,codepage=cp437,iocharset=ascii,utf8 state=mounted
.
.

(Note the USB ID is for a 512MB/1GB Flash Drive but this key is only 256 MB. (Is this how manufacturers dispose of keys that don't pass quality control?)

Does anyone else see the same thing?

There is a similar problem here: http://forums.fedoraforum.org/showthread.php?t=219351

jfprieur
15th May 2009, 08:35 PM
This is a known bug on some USB keys

https://bugzilla.redhat.com/show_bug.cgi?id=494932

DrewP
16th May 2009, 04:22 AM
This is a known bug on some USB keys

https://bugzilla.redhat.com/show_bug.cgi?id=494932

Thanks - that bug describes my experience exactly. In fact one of the contributors reported the problem with exactly the same model of key.