LITE-ON Blu-Ray Drive is not recognized

[Chris Eagan]

It seems that the drive is completely invisible to the system. I am currently running Ubuntu Feisty Fawn.

The manufacturer is LITE-ON.
The drive has the model number LH-2B1S.
The drive uses an SATA interface to connect to the mainboard.
The drive supports reading and writing of CD's, DVD's, and Blu-Ray discs.

The website for the drive is http://us.liteonit.com/us/index.php?option=com_content&task=view&id=197&Itemid=191

[Brian Murray (brian-murray)]

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 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!

[Chris Eagan (ceagan)]

ceagan@dagobah:~$ uname -a
Linux dagobah 2.6.20-14-generic #2 SMP Mon Apr 2 20:37:49 UTC 2007 i686 GNU/Linux

My dmesg output right now won't have all the information you need in it because it is filled with these lines:

[16031.232042] VFS: busy inodes on changed media.
[16033.295601] VFS: busy inodes on changed media.
[16033.352728] VFS: busy inodes on changed media.
[16035.407094] VFS: busy inodes on changed media.
[16035.450356] VFS: busy inodes on changed media.
[16037.516501] VFS: busy inodes on changed media.
[16037.550935] VFS: busy inodes on changed media.
[16039.599210] VFS: busy inodes on changed media.
[16039.638915] VFS: busy inodes on changed media.
[16041.694619] VFS: busy inodes on changed media.

I will attach my messages file which should have all that information.

[Chris Eagan (ceagan)]

Here is the lspci -vvnn output

[Chris Eagan (ceagan)]

Is there anything more that I can do to help get this fixed? I will be happy to provide any needed information and rebuild a patched kernel to test any changes. Thanks very much for the help.

The intention I had was to use the drive for backups but without it functioning, it is difficult to back anything up.

[Launchpad Janitor (janitor)]

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!

[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.

[Chris Eagan (ceagan)]

I tested the drive with the Intrepid Ibex Alpha 6 and it does not appear to be recognized. I tried putting in a regular CD and a blank BD disk and nothing appeared on the desktop.

[ivanorellana (ivanorellana)]

I would like to offer my help to test the drive. I have Ubuntu 8.10 installed and I'm having the same problem. "cat /proc/scsi/scsi" does not seem to show the drive.

[Launchpad Janitor (janitor)]

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.

[Chris Eagan (ceagan)]

Update to this bug: The drive appear to be partially working with the Ubuntu 9.04

Reading : Yes
Writing : Yes
Erasing : No
Re-Writing : Waiting on Erasing feature

See Bug #364204 for discussion on the erasing issue.

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Triaged a while ago but has not had any updated comments for quite some time. Please let us know if this issue remains in the current Ubuntu release, http://www.ubuntu.com/getubuntu/download . If the issue remains, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Chris Eagan (ceagan)]

I am burning a disc on it using Brasero right now on Ubuntu 9.10 - the Karmic Koala, so I am satisfied that the issue is fixed.

[Jeremy Foshee (jeremyfoshee)]

Chris,

[Jeremy Foshee (jeremyfoshee)]

Chris,
    I am glad this issue is resolved for you. I have marked the bug Fix Released.

Thanks!

~JFo