MP3 player mounted as read-only

[rhi]

When I stick in my USB MP3 player (CMX MP3 805), it is mounted read-only. However, in case that I enable the hardware write-lock it is mounted as read/write and produces I/O errors when writing. I.e. it is mounted exactly reversely - ro without hardware write lock and rw with hardware write lock.

However, the system recognizes the write lock status correctly:

richard@inode1:~$ dmesg | tail -n4
[ 9031.661027] SCSI device sda: 4085248 512-byte hdwr sectors (2092 MB)
[ 9031.662186] sda: Write Protect is off
[ 9031.662190] sda: Mode Sense: 03 00 00 00
[ 9031.662193] sda: assuming drive cache: write through
richard@inode1:~$ mount | grep sda
/dev/sda1 on /media/disk type vfat (ro,nosuid,nodev,shortname=mixed,uid=1000,utf8,umask=077)

Ubuntu 6.10 i386

[rhi (rhi-deactivatedaccount)]

BTW, a workaround is to remount the stick every time with -o remount,rw

[Marco Rodrigues (gothicx)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description didn't include enough information.

Please include the information requested from [WWW] https://help.ubuntu.com/community/DebuggingUSBStorage as separate attachments.

[rhi (rhi-deactivatedaccount)]

On the given page https://help.ubuntu.com/community/DebuggingUSBStorage there is no information requested?

What do you need, USB IDs?

BTW, at a friend's place, automounting works correctly with this device. He uses Gentoo and KDE, so I think this is either an Ubuntu or a Gnome issue.

[rhi (rhi-deactivatedaccount)]

I found out that the MP3 player is mounted two times: first when I plug it in, it is mounted read-only, then I unmount it (using eject), then it is mounted again! read-write, then I unmount it again and only now I can pull it out.

Maybe this by hardware design. The player isn't the best quality.

[thaipole (jordan1245)]

I think, that have to be fixed. On Windows XP I plug my player in and write very easy on it! That is a standard operation, that have to be easy. (I'm not a native speaker, sorry :))

I "fixed" it so: Create a user with root rights only for wirte on the player.

[Sergio Zanchetta (primes2h)]

The 18 month support period for Edgy Eft 6.10 has reached it's end of life. As a result, we are closing the linux-source-2.6.17 Edgy Eft kernel task.

[Sergio Zanchetta (primes2h)]

Hardy Heron 8.04 was recently released. It would be helpful if you could test the new release and verify if this is still an issue - http://www.ubuntu.com/getubuntu/download . You should be able to test your bug using the LiveCD. Please let us know your results. Thanks.

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Michele Mangili (mangilimic)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!