Bug 768863

Summary: Fedora not able to mount usb hard drive
Product: [Fedora] Fedora Reporter: Anshaj <anshaj>
Component: halAssignee: Richard Hughes <hughsient>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 16CC: hughsient
Target Milestone: ---   
Target Release: ---   
Hardware: ia64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-13 14:38:18 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Anshaj 2011-12-19 08:24:44 UTC 
Description of problem:
I have usb hard drive (vendor fujitsu).  Fedora is not able to mount this hard drive. It has vfat file system.

I see following error in logs

Dec 19 15:51:24 unforgiven dbus-daemon[910]: ** Message: No devices in use, exit
Dec 19 15:52:23 unforgiven kernel: [  837.844096] usb 3-2: new high speed USB device number 2 using xhci_hcd
Dec 19 15:52:23 unforgiven kernel: [  837.857103] xhci_hcd 0000:06:00.0: WARN: short transfer on control ep
Dec 19 15:52:23 unforgiven kernel: [  837.858082] xhci_hcd 0000:06:00.0: WARN: short transfer on control ep
Dec 19 15:52:23 unforgiven kernel: [  837.859229] xhci_hcd 0000:06:00.0: WARN: short transfer on control ep
Dec 19 15:52:23 unforgiven kernel: [  837.860352] xhci_hcd 0000:06:00.0: WARN: short transfer on control ep
Dec 19 15:52:23 unforgiven kernel: [  837.860459] usb 3-2: New USB device found, idVendor=1bcf, idProduct=0c31
Dec 19 15:52:23 unforgiven kernel: [  837.860460] usb 3-2: New USB device strings: Mfr=2, Product=3, SerialNumber=1
Dec 19 15:52:23 unforgiven kernel: [  837.860462] usb 3-2: Product: USB to Serial-ATA bridge
Dec 19 15:52:23 unforgiven kernel: [  837.860463] usb 3-2: Manufacturer: Sunplus Innovation Technology.
Dec 19 15:52:23 unforgiven kernel: [  837.860465] usb 3-2: SerialNumber: FFFFFFF0FF00000000F908F972CDFF
Dec 19 15:52:23 unforgiven kernel: [  837.861575] xhci_hcd 0000:06:00.0: WARN: short transfer on control ep
Dec 19 15:52:23 unforgiven kernel: [  837.862448] xhci_hcd 0000:06:00.0: WARN: short transfer on control ep
Dec 19 15:52:23 unforgiven mtp-probe: checking bus 3, device 2: "/sys/devices/pci0000:00/0000:00:1c.7/0000:06:00.0/usb3/3-2"
Dec 19 15:52:24 unforgiven mtp-probe: bus: 3, device: 2 was not an MTP device
Dec 19 15:52:24 unforgiven kernel: [  837.962563] Initializing USB Mass Storage driver...
Dec 19 15:52:24 unforgiven kernel: [  837.962803] scsi6 : usb-storage 3-2:1.0
Dec 19 15:52:24 unforgiven kernel: [  837.962910] usbcore: registered new interface driver usb-storage
Dec 19 15:52:24 unforgiven kernel: [  837.962911] USB Mass Storage support registered.
Dec 19 15:52:25 unforgiven kernel: [  838.965378] scsi 6:0:0:0: Direct-Access     FUJITSU  MJA2250BH G2          PQ: 0 ANSI: 4
Dec 19 15:52:25 unforgiven kernel: [  838.966034] sd 6:0:0:0: Attached scsi generic sg2 type 0
Dec 19 15:52:25 unforgiven kernel: [  838.966605] sd 6:0:0:0: [sdb] 488397168 512-byte logical blocks: (250 GB/232 GiB)
Dec 19 15:52:25 unforgiven kernel: [  838.972830] sd 6:0:0:0: [sdb] Write Protect is off
Dec 19 15:52:25 unforgiven kernel: [  838.979077] sd 6:0:0:0: [sdb] No Caching mode page present
Dec 19 15:52:25 unforgiven kernel: [  838.979080] sd 6:0:0:0: [sdb] Assuming drive cache: write through
Dec 19 15:52:25 unforgiven kernel: [  838.992293] sd 6:0:0:0: [sdb] No Caching mode page present
Dec 19 15:52:25 unforgiven kernel: [  838.992296] sd 6:0:0:0: [sdb] Assuming drive cache: write through
Dec 19 15:52:25 unforgiven kernel: [  839.013338]  sdb: sdb1
Dec 19 15:52:25 unforgiven kernel: [  839.031699] sd 6:0:0:0: [sdb] No Caching mode page present
Dec 19 15:52:25 unforgiven kernel: [  839.031702] sd 6:0:0:0: [sdb] Assuming drive cache: write through
Dec 19 15:52:25 unforgiven kernel: [  839.031704] sd 6:0:0:0: [sdb] Attached SCSI disk
Dec 19 15:52:25 unforgiven ata_id[2342]: HDIO_GET_IDENTITY failed for '/dev/sdb': Invalid argument


Version-Release number of selected component (if applicable):
Linux unforgiven 3.1.5-1.fc16.x86_64 #1 SMP Fri Dec 9 18:11:10 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux

How reproducible:

insert usb hard drive and it doesnt get mounted

Steps to Reproduce:
1.
2.
3.
  
Actual results:

No icon for opening files

Expected results:
Fedora should be able to mount usb hard drive.

Additional info:
Comment 1 Fedora End Of Life 2013-01-16 13:44:30 UTC 
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 2 Fedora End Of Life 2013-02-13 14:38:20 UTC 
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.