[Bug 225187] New: Writing to MPIO FL-400 Corrupts Filesystem on Device
https://bugzilla.novell.com/show_bug.cgi?id=225187 Summary: Writing to MPIO FL-400 Corrupts Filesystem on Device Product: openSUSE 10.2 Version: RC 4 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: jfunk@funktronics.ca QAContact: qa@suse.de I have an MPIO FL-400 MP3 player, which is accessed through usb-storage. When I plug it in, I get the following in dmesg: usb 5-6: new high speed USB device using ehci_hcd and address 18 usb 5-6: new device found, idVendor=2735, idProduct=1012 usb 5-6: new device strings: Mfr=1, Product=2, SerialNumber=3 usb 5-6: Product: FL400 usb 5-6: Manufacturer: MPIO usb 5-6: SerialNumber: F3BB16A822914D6B usb 5-6: configuration #1 chosen from 1 choice scsi17 : SCSI emulation for USB Mass Storage devices usb-storage: device found at 18 usb-storage: waiting for device to settle before scanning Vendor: MPIO Model: FL400 Rev: 1.00 Type: Direct-Access ANSI SCSI revision: 00 SCSI device sdd: 2038016 512-byte hdwr sectors (1043 MB) sdd: Write Protect is off sdd: Mode Sense: 00 c0 00 00 sdd: assuming drive cache: write through sd 17:0:0:0: ioctl_internal_command return code = 8000002 : Current: sense key: No Sense Additional sense: No additional sense information SCSI device sdd: 2038016 512-byte hdwr sectors (1043 MB) sdd: Write Protect is off sdd: Mode Sense: 00 c0 00 00 sdd: assuming drive cache: write through sdd: unknown partition table sd 17:0:0:0: Attached scsi removable disk sdd sd 17:0:0:0: Attached scsi generic sg4 type 0 usb-storage: device scan complete sd 17:0:0:0: ioctl_internal_command return code = 8000002 : Current: sense key: No Sense Additional sense: No additional sense information This last message repeats until I unplug the device. If I transfer files to it normally or through Amarok, sync, then unmount, they disappear. The device does not see them, and when I plug it in again, they are gone. If I run fsck on the device it claims it has 2 different FATs, and it doesn't fix the filesystem. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=225187 mhorvath@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |jfunk@funktronics.ca ------- Comment #1 from mhorvath@novell.com 2006-12-01 07:46 MST ------- Try to 'eject' the device, instead of umount. Please attach output of the fsck. Thank you. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=225187 jfunk@funktronics.ca changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Info Provider|jfunk@funktronics.ca | Resolution| |WONTFIX ------- Comment #2 from jfunk@funktronics.ca 2006-12-06 15:44 MST ------- I bought the device for my girlfriend, who hated it. I ended up bringing it back and got a Samsung instead, which does work fine, except for an issue I'll submit in a different bug. Since I haven't been able to find anyone else with the problem after much Googling, I'll just close the bug. -- 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, or are watching someone who is.
participants (1)
-
bugzilla_noreply@novell.com