[Kubuntu] Sony DCR-DVDXXX doesn't mount anymore...

Bug #118330 reported by neoAKiRAz
4
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Undecided
Unassigned
linux-source-2.6.20 (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

I'm using Kubuntu. I used to just plug my Sony DCR-DVD405 camera and the device would mount automatically. This worked perfectly while I was using Edgy, and stopped working after some Edgy update. A few days ago I updated to Feisty, but the problem persists. I tried a fresh Feisty installation and it doesn't work either. I tried the Edgy Live DVD, and it DOES work.

Currently, when I plug the device, dmesg reports:

[17180063.068000] usb 5-2: new high speed USB device using ehci_hcd and address 3
[17180063.212000] usb 5-2: configuration #1 chosen from 1 choice
[17180063.328000] usbcore: registered new driver libusual
[17180063.372000] Initializing USB Mass Storage driver...
[17180063.372000] scsi2 : SCSI emulation for USB Mass Storage devices
[17180063.372000] usb-storage: device found at 3
[17180063.372000] usb-storage: waiting for device to settle before scanning
[17180063.372000] usbcore: registered new driver usb-storage
[17180063.372000] USB Mass Storage support registered.
[17180068.376000] usb-storage: device scan complete
[17180068.380000] Vendor: SONY Model: DDX-C1002 Rev: R1.0
[17180068.380000] Type: CD-ROM ANSI SCSI revision: 00
[17180068.384000] 2:0:0:0: Attached scsi generic sg2 type 5
[17180068.468000] sr0: scsi3-mmc drive: 32x/32x tray
[17180068.472000] sr 2:0:0:0: Attached scsi CD-ROM sr0

But the device is not mounted. At least it doesn't show up in /etc/mtab.
When I do it with the Edgy Live DVD Kubuntu, the output is the same, but this lines shows at the end:

[17179772.564000] UDF-fs INFO UDF 0.9.8.1 (2004/29/09) Mounting volume 'SONY_MOBILE', timestamp 2007/02/15 20:18 (1000)

And I can access the MiniDVD contents with no problems. In this case, this line shows up in /etc/mtab:

/dev/scd0 on /media/dvdrecorder type udf (ro,nosuid,nodev,uid=999,gid=999,umask=000,iocharset=utf8)

In Feisty, when I try to mount the device (which doesn't automount), I get the following output:

neoakiraz@fcksys:~$ sudo mount -t udf /dev/scd0 /media/sony
mount: block device /dev/scd0 is write-protected, mounting read-only
mount: wrong fs type, bad option, bad superblock on /dev/scd0,
       missing codepage or other error
       In some cases useful info is found in syslog - try
       dmesg | tail or so

And dmesg reports:

[ 937.778686] attempt to access beyond end of device
[ 937.778696] sr0: rw=0, want=68, limit=4
[ 937.805024] attempt to access beyond end of device
[ 937.805033] sr0: rw=0, want=2770236, limit=4
[ 937.805231] attempt to access beyond end of device
[ 937.805236] sr0: rw=0, want=2769212, limit=4
[ 937.805241] attempt to access beyond end of device
[ 937.805244] sr0: rw=0, want=2768988, limit=4
[ 937.805249] attempt to access beyond end of device
[ 937.805252] sr0: rw=0, want=2770228, limit=4
[ 937.805257] attempt to access beyond end of device
[ 937.805259] sr0: rw=0, want=2769204, limit=4
[ 937.805264] attempt to access beyond end of device
[ 937.805267] sr0: rw=0, want=2768980, limit=4
[ 937.805271] attempt to access beyond end of device
[ 937.805274] sr0: rw=0, want=2769636, limit=4
[ 937.805279] attempt to access beyond end of device
[ 937.805281] sr0: rw=0, want=2768612, limit=4
[ 937.805286] attempt to access beyond end of device
[ 937.805289] sr0: rw=0, want=2768388, limit=4
[ 937.805293] attempt to access beyond end of device
[ 937.805296] sr0: rw=0, want=2769628, limit=4
[ 937.805300] attempt to access beyond end of device
[ 937.805303] sr0: rw=0, want=2768604, limit=4
[ 937.805307] attempt to access beyond end of device
[ 937.805310] sr0: rw=0, want=2768380, limit=4
[ 937.805316] attempt to access beyond end of device
[ 937.805318] sr0: rw=0, want=2273040, limit=4
[ 937.805323] attempt to access beyond end of device
[ 937.805326] sr0: rw=0, want=2272016, limit=4
[ 937.805331] attempt to access beyond end of device
[ 937.805333] sr0: rw=0, want=2271792, limit=4
[ 937.805338] attempt to access beyond end of device
[ 937.805340] sr0: rw=0, want=2273032, limit=4
[ 937.805345] attempt to access beyond end of device
[ 937.805347] sr0: rw=0, want=2272008, limit=4
[ 937.805352] attempt to access beyond end of device
[ 937.805354] sr0: rw=0, want=2271784, limit=4
[ 937.805359] attempt to access beyond end of device
[ 937.805362] sr0: rw=0, want=2272440, limit=4
[ 937.805367] attempt to access beyond end of device
[ 937.805370] sr0: rw=0, want=2271416, limit=4
[ 937.805377] attempt to access beyond end of device
[ 937.805380] sr0: rw=0, want=2271192, limit=4
[ 937.805385] attempt to access beyond end of device
[ 937.805387] sr0: rw=0, want=2272432, limit=4
[ 937.805392] attempt to access beyond end of device
[ 937.805395] sr0: rw=0, want=2271408, limit=4
[ 937.805399] attempt to access beyond end of device
[ 937.805402] sr0: rw=0, want=2271184, limit=4
[ 937.805407] attempt to access beyond end of device
[ 937.805409] sr0: rw=0, want=1252, limit=4
[ 937.805415] attempt to access beyond end of device
[ 937.805417] sr0: rw=0, want=1028, limit=4
[ 937.805420] UDF-fs: No partition found (1)

The media I'm using is perfectly good, it is read from Windows XP, and as I said, from a fresh Kubuntu Edgy (Live DVD).
I got help in KubuntuForums, in this thread: http://kubuntuforums.net/forums/index.php?topic=3083580.0, just in case you want to see what's going on in detail. They concluded this may be a bug related to libATA, but I'm not very experienced in Linux, so I really don't know. Thanks in advance,

Bruno

Revision history for this message
neoAKiRAz (neoakiraz) wrote :

Did I do something wrong?
Is it OK to place the bug here?
Thanks!

Revision history for this message
Brian Murray (brian-murray) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description doesn't yet have enough information.
Please include as attachments the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command 'uname -a' in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command 'dmesg > dmesg.log' and attach the resulting file 'dmesg.log' to this bug report.
3. Please run the command 'sudo lspci -vvnn > lspci-vvnn.log' and attach the resulting file 'lspci-vvnn.log' to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks in advance!

Revision history for this message
neoAKiRAz (neoakiraz) wrote :

Hello. Thanks for taking a look at what I wrote. Here is the ouput to "uname -a":

Linux fcksys 2.6.20-16-generic #2 SMP Wed May 23 01:46:23 UTC 2007 i686 GNU/Linux

I attached the requested outputs too. I didn't plug and unplug the camera to generate dmesg.log, as I've already posted the result of that earlier. Thanks again. Regards,

Bruno

Revision history for this message
neoAKiRAz (neoakiraz) wrote :

Here's the other one.

Changed in linux-source-2.6.20:
assignee: brian-murray → ubuntu-kernel-team
importance: Undecided → Medium
status: Needs Info → Confirmed
Revision history for this message
neoAKiRAz (neoakiraz) wrote :

Any advance?
Sorry, I'm not sure what to do...
Did the logs give some insight? Thanks!

Revision history for this message
The Mystic (tom-aratyn) wrote :

Is this possibly a duplicate of Bug #42023?

It sounds a lot like it...

Revision history for this message
Paul Dufresne (paulduf) wrote :

No, at least I don't think so, this one have a limit=4 which seems very different than bug #42023 for which the problem seems to be around the 4GB limit of a DVD.

Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

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.

Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

Revision history for this message
Bryan Wu (cooloney) wrote :

This bug report is being closed because we received no response to the previous inquiry for information. Please reopen if this is still an issue in the current Ubuntu release, Jaunty Jackalope 9.04 - http://www.ubuntu.com/getubuntu/download. If the issue remains in Jaunty, please test the latest upstream kernel build - https://wiki.ubuntu.com/KernelMainlineBuilds . To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

Changed in linux (Ubuntu):
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.