Ubuntu
linux-source-2.6.20 package

Mis-mounting of DVD+/-RW/RAM Drive

Bug #94796 reported by Sean Seago on 2007-03-22

Affects		Status	Importance	Assigned to	Milestone
	linux (Ubuntu)	Invalid	Undecided	Unassigned
	linux-source-2.6.20 (Ubuntu)	Won't Fix	Undecided	Ben Collins

Bug Description

First the hardware:

Panasonic/Matsushita UJ-830B in the UltraBay of an IBM/Lenovo ThinkPad Dock II. Feisty is running on a ThinkPad T43 18XX (Intel Chipset and onboard 915 graphics).
I have seen this device reported as hda in error logs (which is obviously wrong).

The situation:
The drive was unusable in Kubuntu Edgy. The drive was properly detected (according to dmesg output) in Edgy but errors saying something to the effect of the drive being confused (?) were constant.
Output for Ubuntu Feisty is...
"[ 5304.216000] hda: drive not ready for command
[ 5304.216000] hda: status error: status=0x7f { DriveReady DeviceFault SeekComplete DataRequest CorrectedError Index Error }
[ 5304.216000] hda: status error: error=0x7f { IllegalLengthIndication EndOfMedia AbortedCommand MediaChangeRequested LastFailedSense=0x07 }
[ 5304.216000] ide: failed opcode was: unknown
[ 5304.216000] hda: drive not ready for command
[ 5306.220000] hda: status error: status=0x7f { DriveReady DeviceFault SeekComplete DataRequest CorrectedError Index Error }
[ 5306.220000] hda: status error: error=0x7f { IllegalLengthIndication EndOfMedia AbortedCommand MediaChangeRequested LastFailedSense=0x07 }
[ 5306.220000] ide: failed opcode was: unknown
[ 5306.220000] hda: drive not ready for command
[ 5306.220000] hda: status error: status=0x7f { DriveReady DeviceFault SeekComplete DataRequest CorrectedError Index Error }
[ 5306.220000] hda: status error: error=0x7f { IllegalLengthIndication EndOfMedia AbortedCommand MediaChangeRequested LastFailedSense=0x07 }
[ 5306.220000] ide: failed opcode was: unknown
[ 5306.220000] hda: drive not ready for command
[ 5306.220000] hda: status error: status=0x7f { DriveReady DeviceFault SeekComplete DataRequest CorrectedError Index Error }
[ 5306.220000] hda: status error: error=0x7f { IllegalLengthIndication EndOfMedia AbortedCommand MediaChangeRequested LastFailedSense=0x07 }"
..."

The drive shows up as being mounted with an Audio CD even when no CD is present. If the drive is not present during boot, all is well (no error messages) and the drive is never mounted (even with a CD inserted). However, if the drive is present at boot, GNOME reports an Audio CD and Rhythmbox tries to access the drive to no avail.

This Installation is in a business environment and is the only non-MS desktop installation in this company. I'm doing what I can to help resolve Bug #1, thus the reason for this report.
If you need any further info from me, don't hesitate to ask--and I promise I'll be more concise.

ProblemType: Bug
Architecture: i386
Date: Thu Mar 22 10:08:59 2007
DistroRelease: Ubuntu 7.04
Uname: Linux 49UFF111 2.6.20-12-generic #2 SMP Wed Mar 21 20:55:46 UTC 2007 i686 GNU/Linux

Tags:

Revision history for this message

Ben Collins (ben-collins) wrote on 2007-03-23:

Why do you think hda is wrong? Anyway, can you attach dmesg output and lspci -vv, lspci -vvn output (do not paste into comment, use the web interface to attach it).

Thanks

Changed in linux-source-2.6.20:
assignee:	nobody → ben-collins
status:	Unconfirmed → Needs Info

Revision history for this message

foepaw (foepaw) wrote on 2007-07-16:

dmesg, lspci -vv, and lspci -vvn output Edit (158.2 KiB, text/plain)

I am having a very similar problem with the Matshita UJ-851S in my Compaq Presario V6110US running Ubuntu Feisty Fawn (kernel 2.6.20-16-generic). With no media present in the drive GNOME will mount the drive and either report that a CD containing both data and music has been detected or launch Sound Juicer. Should I switch to any virtual terminal "hda: drive not ready for command" is infinitely echoed to the screen. Resetting the drive with "hdparm -w /dev/hda" provides a temporary solution. Output from dmesg, lspci -vv, and lspci -vvn is attached.

Revision history for this message

Launchpad Janitor (janitor) wrote on 2008-08-11: 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 on 2008-08-29:

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

Jonathan Thomas (echidnaman) wrote on 2008-11-12:

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!