Bug 440830

Summary: Fails to automount NTFS-formatted USB disk
Product: [openSUSE] openSUSE 11.1 Reporter: Per Ångström <per_angstrom>
Component: HotplugAssignee: E-mail List <kde-maintainers>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <qa-bugs>
Severity: Major    
Priority: P5 - None CC: vuntz
Version: Factory   
Target Milestone: ---   
Hardware: x86-64   
OS: Other   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: output of lshal with drive attached

Description Per Ångström 2008-11-01 12:19:53 UTC 
I have an NTFS-formatted USB disk that works fine when I plug it in under OpenSUSE 10.3 and 11.0. However, under 11.1 Beta 3 the disk is not properly recognized and cannot be mounted. 

Other hotplugged devices, such as VFAT-formatted USB sticks and memory cards, and DVD:s are mounted properly.

The error message displayed by Dolphin:
"An error occurred while accessing 'WD Passport', the system responded: org.freedesktop.Hal.Device.UnknownFailure: TODO: have to rethink extra options"

Output of lshal -m:
13:08:24.939: usb_device_1058_702_575845393037303439313939 added
13:08:24.967: usb_device_1058_702_575845393037303439313939_if0 added
13:08:24.974: usb_device_1058_702_575845393037303439313939_if0_scsi_host added
13:08:25.963: usb_device_1058_702_575845393037303439313939_if0_scsi_host_0 added
13:08:25.966: usb_device_1058_702_575845393037303439313939_if0_scsi_host_0_scsi_device_lun0 added
13:08:26.005: usb_device_1058_702_575845393037303439313939_if0_scsi_host_0_scsi_device_lun0_scsi_generic added
13:08:26.084: storage_serial_WD_2500BEV_External_575845393037303439313939_0_0 added
13:08:26.202: volume_uuid_F0EA4C40EA4C04F6 added

/var/log/messages:
Nov  1 13:08:24 linux-f4vp kernel: usb 8-1: new high speed USB device using ehci_hcd and address 14
Nov  1 13:08:24 linux-f4vp kernel: usb 8-1: configuration #1 chosen from 1 choice
Nov  1 13:08:24 linux-f4vp kernel: scsi12 : SCSI emulation for USB Mass Storage devices
Nov  1 13:08:24 linux-f4vp kernel: usb-storage: device found at 14
Nov  1 13:08:24 linux-f4vp kernel: usb-storage: waiting for device to settle before scanning
Nov  1 13:08:24 linux-f4vp kernel: usb 8-1: New USB device found, idVendor=1058, idProduct=0702
Nov  1 13:08:24 linux-f4vp kernel: usb 8-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov  1 13:08:24 linux-f4vp kernel: usb 8-1: Product: External HDD
Nov  1 13:08:24 linux-f4vp kernel: usb 8-1: Manufacturer: Western Digital
Nov  1 13:08:24 linux-f4vp kernel: usb 8-1: SerialNumber: 575845393037303439313939
Nov  1 13:08:25 linux-f4vp kernel: scsi 12:0:0:0: Direct-Access     WD       2500BEV External 1.04 PQ: 0 ANSI:
4
Nov  1 13:08:25 linux-f4vp kernel: sd 12:0:0:0: [sdg] 488397168 512-byte hardware sectors: (250GB/232GiB)
Nov  1 13:08:25 linux-f4vp kernel: sd 12:0:0:0: [sdg] Write Protect is off
Nov  1 13:08:25 linux-f4vp kernel: sd 12:0:0:0: [sdg] Mode Sense: 21 00 00 00
Nov  1 13:08:25 linux-f4vp kernel: sd 12:0:0:0: [sdg] Assuming drive cache: write through
Nov  1 13:08:25 linux-f4vp kernel: sd 12:0:0:0: [sdg] 488397168 512-byte hardware sectors: (250GB/232GiB)
Nov  1 13:08:25 linux-f4vp kernel: sd 12:0:0:0: [sdg] Write Protect is off
Nov  1 13:08:25 linux-f4vp kernel: sd 12:0:0:0: [sdg] Mode Sense: 21 00 00 00
Nov  1 13:08:25 linux-f4vp kernel: sd 12:0:0:0: [sdg] Assuming drive cache: write through
Nov  1 13:08:25 linux-f4vp kernel:  sdg: sdg1
Nov  1 13:08:25 linux-f4vp kernel: sd 12:0:0:0: [sdg] Attached SCSI disk
Nov  1 13:08:25 linux-f4vp kernel: sd 12:0:0:0: Attached scsi generic sg8 type 0
Nov  1 13:08:25 linux-f4vp kernel: usb-storage: device scan complete
Nov  1 13:08:26 linux-f4vp vol_id[7592]: get buffer off 0x0(0), len 0x200
Nov  1 13:08:26 linux-f4vp vol_id[7592]: read sbbuf len:0x200
Nov  1 13:08:26 linux-f4vp vol_id[7592]: get buffer off 0x0(0), len 0x200
Nov  1 13:08:26 linux-f4vp vol_id[7592]: probing at offset 0x0, size 0x3a38b2e000
Nov  1 13:08:26 linux-f4vp vol_id[7592]: probing at offset 0x3a38b10000, size 0x3a38b2e000
Nov  1 13:08:26 linux-f4vp vol_id[7592]: get buffer off 0x3a38b10000(250059227136), len 0x800
Nov  1 13:08:26 linux-f4vp vol_id[7592]: read seekbuf off:0x3a38b10000 len:0x800
Nov  1 13:08:26 linux-f4vp vol_id[7592]: probing at offset 0x3a38b2c000, size 0x3a38b2e000
Nov  1 13:08:26 linux-f4vp vol_id[7592]: get buffer off 0x3a38b2c000(250059341824), len 0x800
Nov  1 13:08:26 linux-f4vp vol_id[7592]: read seekbuf off:0x3a38b2c000 len:0x800
Nov  1 13:08:26 linux-f4vp vol_id[7592]: probing at offset 0x0, size 0x3a38b2e000
Nov  1 13:08:26 linux-f4vp vol_id[7592]: get buffer off 0x0(0), len 0x800
Nov  1 13:08:26 linux-f4vp vol_id[7592]: read sbbuf len:0x800
Nov  1 13:08:26 linux-f4vp vol_id[7592]: probing at offset 0x1000, size 0x3a38b2e000
Nov  1 13:08:26 linux-f4vp vol_id[7592]: get buffer off 0x1000(4096), len 0x800
Nov  1 13:08:26 linux-f4vp vol_id[7592]: read sbbuf len:0x1800
Nov  1 13:08:26 linux-f4vp vol_id[7592]: probing at offset 0x0, size 0x3a38b2e000
Nov  1 13:08:26 linux-f4vp vol_id[7592]: get buffer off 0x3a38b2de00(250059349504), len 0x200
Nov  1 13:08:26 linux-f4vp vol_id[7592]: read seekbuf off:0x3a38b2de00 len:0x200
Nov  1 13:08:26 linux-f4vp vol_id[7592]: probing at offset 0x0, size 0x3a38b2e000
Nov  1 13:08:26 linux-f4vp vol_id[7592]: get buffer off 0x3a38b2dc00(250059348992), len 0x200
Nov  1 13:08:26 linux-f4vp vol_id[7592]: read seekbuf off:0x3a38b2dc00 len:0x200
Nov  1 13:08:26 linux-f4vp vol_id[7592]: probing at offset 0x0, size 0x3a38b2e000
Nov  1 13:08:26 linux-f4vp vol_id[7592]: get buffer off 0x3a38b2de00(250059349504), len 0x200
Nov  1 13:08:26 linux-f4vp vol_id[7592]: read seekbuf off:0x3a38b2de00 len:0x200
Nov  1 13:08:26 linux-f4vp vol_id[7592]: get buffer off 0x3a38b2de00(250059349504), len 0x200
Nov  1 13:08:26 linux-f4vp vol_id[7592]: probing at offset 0x0, size 0x3a38b2e000
Nov  1 13:08:26 linux-f4vp vol_id[7592]: get buffer off 0x3a38b2de00(250059349504), len 0x200
Nov  1 13:08:26 linux-f4vp vol_id[7592]: probing at offset 0x0, size 0x3a38b2e000
Nov  1 13:08:26 linux-f4vp vol_id[7592]: get buffer off 0x3a38b2dc00(250059348992), len 0x200
Nov  1 13:08:26 linux-f4vp vol_id[7592]: read seekbuf off:0x3a38b2dc00 len:0x200
Nov  1 13:08:26 linux-f4vp vol_id[7592]: probing at offset 0x0, size 0x3a38b2e000
Nov  1 13:08:26 linux-f4vp vol_id[7592]: get buffer off 0x3a38b26200(250059317760), len 0x200
Nov  1 13:08:26 linux-f4vp vol_id[7592]: read seekbuf off:0x3a38b26200 len:0x200
Nov  1 13:08:26 linux-f4vp vol_id[7592]: get buffer off 0x3a38b0e200(250059219456), len 0x200
Nov  1 13:08:26 linux-f4vp vol_id[7592]: read seekbuf off:0x3a38b0e200 len:0x200
[read sequence repeated ad nauseam]
Comment 1 Per Ångström 2008-11-03 20:08:16 UTC 
Clarification: This seems to be a problem with Dolphin. In fact, I can mount the same drive in Nautilus without any problems, and with write permissions, too.
Comment 2 JP Rosevear 2008-11-11 21:04:53 UTC 
Attach lshal output with drive attached please.
Comment 3 Per Ångström 2008-11-11 21:35:03 UTC 
Created attachment 251431 [details]
output of lshal with drive attached

The device that cannot be mounted by Dolphin is "WD_2500BEV_External".
Comment 4 JP Rosevear 2008-11-12 22:08:04 UTC 
The drive is ntfs rather than vfat.

Based on the hal code in hal-storage-mount.c:handle_mount I think the 'uid=' option is being passed in when it shouldn't be.  However uid is listed as a valid option in the lshal output.

Danny?

See also bug https://bugs.kde.org/show_bug.cgi?id=157378
Comment 5 Vincent Untz 2008-11-12 22:23:04 UTC 
So, we have this for the ntfs-3g volume in the hal output:

volume.mount.valid_options = {'ro', 'sync', 'dirsync', 'noatime', 'nodiratime', 'noexec', 'quiet', 'remount', 'exec', 'uid=', 'gid=', 'umask=', 'utf8', 'locale='} (string list)

In /usr/share/hal/fdi/policy/10osvendor/21-storage-ntfs-3g.fdi, we do:

<append key="volume.mount.valid_options" type="strlist">locale=</append>

So, hrm, I guess that would explain the thing? We shouldn't have all those options in volume.mount.valid_options. I don't know enough about fdi files, though.

Note that the bug is reported against beta3, and the fdi file might not be there in beta3...
Comment 6 Danny Al-Gaaf 2008-11-12 22:28:51 UTC 

*** This bug has been marked as a duplicate of bug 442178 ***