[Bug 440830] New: Fails to automount NTFS-formatted USB disk
https://bugzilla.novell.com/show_bug.cgi?id=440830 User 1kfmm4x02@sneakemail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=440830#c1 Summary: Fails to automount NTFS-formatted USB disk Product: openSUSE 11.1 Version: Factory Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Hotplug AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: 1kfmm4x02@sneakemail.com QAContact: qa@suse.de Found By: Other 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] -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=440830 User 1kfmm4x02@sneakemail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=440830#c1 --- Comment #1 from Per Ångström <1kfmm4x02@sneakemail.com> 2008-11-03 13:08:16 MST --- 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. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=440830 Andreas Jaeger <aj@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |kde-maintainers@suse.de -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=440830 User jpr@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=440830#c2 JP Rosevear <jpr@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |1kfmm4x02@sneakemail.com --- Comment #2 from JP Rosevear <jpr@novell.com> 2008-11-11 14:04:53 MST --- Attach lshal output with drive attached please. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=440830 User 1kfmm4x02@sneakemail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=440830#c3 --- Comment #3 from Per Ångström <1kfmm4x02@sneakemail.com> 2008-11-11 14:35:03 MST --- Created an attachment (id=251431) --> (https://bugzilla.novell.com/attachment.cgi?id=251431) output of lshal with drive attached The device that cannot be mounted by Dolphin is "WD_2500BEV_External". -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=440830 User jpr@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=440830#c4 JP Rosevear <jpr@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Info Provider|1kfmm4x02@sneakemail.com |dkukawka@novell.com --- Comment #4 from JP Rosevear <jpr@novell.com> 2008-11-12 15:08:04 MST --- 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 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=440830 User vuntz@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=440830#c5 Vincent Untz <vuntz@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vuntz@novell.com --- Comment #5 from Vincent Untz <vuntz@novell.com> 2008-11-12 15:23:04 MST --- 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... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=440830 User dkukawka@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=440830#c6 Danny Kukawka <dkukawka@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Info Provider|dkukawka@novell.com | Resolution| |DUPLICATE --- Comment #6 from Danny Kukawka <dkukawka@novell.com> 2008-11-12 15:28:51 MST --- *** This bug has been marked as a duplicate of bug 442178 *** https://bugzilla.novell.com/show_bug.cgi?id=442178 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com