CDROM drive no longer working, unable to mount.

[Jaidee]

After a recent Fiesty update, I am unable to browse my CDROM drive. My fstab looks like this:

# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
#proc /proc proc defaults 0 0
# /dev/hda1
UUID=7591daee-e328-49df-be74-a58a0b87a981 / ext3 defaults,erro$
# /dev/hda3
UUID=08235939-5dff-46f1-85eb-64d89446b2da /home ext3 defaults $
# /dev/hda2
UUID=d816620a-167b-4048-9156-2f60aea7f4cc none swap sw $
/dev/cdrom /media/cdrom0 udf,iso9660 user,noauto 0 0

I think /dev/cdrom used to be /dev/hdc, I changed it because there is no /dev/hdc.

Here's my fdisk -l:

Disk /dev/sda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot Start End Blocks Id System
/dev/sda1 1 1912 15358108+ 83 Linux
/dev/sda2 9475 9729 2048287+ 82 Linux swap / Solaris
/dev/sda3 1913 9474 60741765 83 Linux

Partition table entries are not in disk order

No sign of the CDROM there. (There is a disk in the drive.)

I did one of these:

sudo /etc/init.d/dbus restart

which gives an interesting output in dmesg:

[50113.460000] cdrom: This disc doesn't have any tracks I recognize!
[50113.760000] ADDRCONF(NETDEV_UP): eth1: link is not ready
[50125.496000] eth0: no IPv6 routers present
[50127.520000] isofs_fill_super: bread failed, dev=sr0, iso_blknum=16, block=16

I hope you can help, I'm currently without CD input!

[Brian Murray (brian-murray)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. Could you please add the full output of 'dmesg' as an attachment to your bug report? Thanks in advance.

[Jaidee (jdjh)]

Many thanks for the help, I've included my full dmesg as an attachment.

[Jaidee (jdjh)]

And also the lshw output.

[Conn O Griofa (psyke83)]

Hi,

This part of Jaidee's log may be the trouble:

[ 7.452000] ata2.00: 12 bytes trailing data
[ 7.452000] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
[ 7.452000] ata2.00: (BMDMA stat 0x5)
[ 7.452000] ata2.00: cmd a0/01:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 0x12 data 254 in
[ 7.452000] res 51/51:03:00:00:00/00:00:00:00:00/a0 Emask 0x3 (HSM violation)
[ 7.452000] ata2: soft resetting port

OT: Since 2.6.20-12, my IDE devices have been renamed from hd* to s*, I'm not sure if this is a bug or feature. What I have observed, however, is that Feisty's alternative install CD (from at least Herd 4) caused my drives to be identified as s*, but the livecd didn't.

[Super Gab (go-supergab)]

I don't really if this is related or not. I run feisty on a MacBook Black 1st gen.

Since I upgraded from edgy to feisty my HFS+ partition is getting mounted automatically and I have two DVD±RW drives in nautilus.

In my /etc/fstab I have no entry for the HFS+ partition and one entry for the DVD±RW drive.

So my guess (since I don't know the internals) is the system is now automatically detecting and mounting "internal" hard disk partitions and disk drives and not only external (USB/firewire) ones.

What I did is to simply remove the DVD±RW line in my /etc/fstab and everything is working just fine. Here is my fstab:

$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/sda3
UUID=61b37907-4abf-49d3-904b-51000369e4c2 / ext3 defaults,errors=remount-ro 0 1
# /dev/sda4
UUID=8f51cee9-ec60-4f57-a80f-6bc91886c45b /home ext3 defaults 0 2
# /dev/sda5
UUID=01456d1f-1635-4a09-b8f9-b6a2cc82e384 none swap sw 0 0

[Jaidee (jdjh)]

I can confirm that even after removal of the CDROM line from my fstab, I still get a shortcut on my desktop to "CD-ROM Disc", whether there is a CD-ROM in the tray or not. CDs are still unreadable though, when I double-click the CD-ROM Disc icon I am taken to the burning screen, and it's not a blank disc.

[Mark Perris (mark-perris)]

I have a similar problem here. I have a single IDE device (my CDRW) and a SATA HDD on a 3rd party expension board. I have not attempted to edit fstab myself as I am unfamiliar with it.

I now have two cdrom drives listed, one of which is unmountable, the other works fine.

I wonder if this is related to the following recent kernel upstream changes:
# <GROUP> Synced drivers/ata/
# ACPI support for IDE devices
# ide-acpi support warning fix
# Disable NMI watchdog by default properly
# devres: device resource management
# sort the devres mess out
# Add pci class code for SATA & AHCI, and replace some magic numbers.
# PCI: allow multiple calls to pcim_pin_device()
# devres: release resources on device_del()

my fstab:
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/sda1
UUID=1da9a2d2-54ab-4177-b09e-d04d673be75f / ext3 defaults,error
s=remount-ro 0 1
# /dev/sda5
UUID=c6a21d97-1643-4253-a6e9-fa06eb3cad76 none swap sw
  0 0
/dev/hda /media/cdrom0 udf,iso9660 user,noauto 0 0

If I can be of any further help, let me know.

[Ben Collins (ben-collins)]

Please provide "lspci -vv" and "lspci -vvn" output.

[Jaidee (jdjh)]

Attached requested outputs.

[Rajeev Nair (rajeev)]

i confirm this

Plays dvd and data cd but no vcd for me

strange ha

[chris_van_ackeren (chris-van-ackeren)]

I have similar errors, both CDs and DVDs show up as blank media with tracks that can't be read. Let me know if you need anything else from me.

[amesenbrink (am-pcguy)]

Upgraded to Feisty 7.04, encountered this problem. I was unable to bun CD/DVD's with Dapper I hoped for better support but now I can't even read cd's.

What info do you need? I get an error that says:
mount: block device /dev/cdrom is write-protected, mounting read-only

mount: not a directory

When I try to mount a cdrom. Mount is a directory.

I have a Toshiba A135 Laptop.

[Mike Durham (mdurhamesq)]

I can't read data files from my DVD drive.
If I insert an unencoded DVD, it shows correctly on the desktop.
If I inspect the DVD with Nautilus, all files are shown correctly, types, size etc.
If I inspect one file (say a VOB) with a hex editor, all data appears as 00 Hex (zeros).
I am unable to copy files from the DVD, I get an I/O error message.
I have one 7.04 system upgraded from Edgy that originaly worked ok but now doesn't.
I also have a clean install of 7.04 that exhibits exactly the same problem, i.e. can't read DVD's.
Reading/writing C/D's appears to be no problem.
I've tried DVD+RW and DVD-R with the same result.

I noticed in the clean install, the fstab file contained the line:
/dev/hdc /media/cdrom0 udf,iso9660 user,noauto 0 0
But, there is no "/dev/hdc" so I changed it to "/dev/scd0", this made no difference to the reading problem but it did mount the DVD in the correct place, i.e. "/media/cdrom0" whereas before it got mounted in "/media"

Why would the clean install use "/dev/hdc" when it doesn't exist?

Needless to say, I can't play DVD's either.

[IT VENUE (howardh)]

I am also having the same issue as users above on Gateway Laptop MX6550
But I am able to mount drives in VMware session running XP

Current work around to copy files from VMware session into temp directory.

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

howard@M3rX:~$ dmesg | tail
[29106.124000] APIC error on CPU0: 40(40)
[29264.108000] APIC error on CPU0: 40(40)
[29479.780000] Unknown OutputIN= OUT=eth0 SRC=169.254.7.210 DST=169.254.255.255 LEN=256 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=138 DPT=138 LEN=236
[29479.996000] Unknown OutputIN= OUT=eth0 SRC=169.254.7.210 DST=169.254.255.255 LEN=233 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=138 DPT=138 LEN=213
[29479.996000] Unknown OutputIN= OUT=vmnet1 SRC=192.168.105.1 DST=192.168.105.255 LEN=256 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=138 DPT=138 LEN=236
[29479.996000] Unknown OutputIN= OUT=vmnet1 SRC=192.168.105.1 DST=192.168.105.255 LEN=233 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=138 DPT=138 LEN=213
[29529.996000] Unknown OutputIN= OUT=vmnet8 SRC=192.168.59.1 DST=192.168.59.255 LEN=256 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=138 DPT=138 LEN=236
[29529.996000] Unknown OutputIN= OUT=vmnet8 SRC=192.168.59.1 DST=192.168.59.255 LEN=233 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=138 DPT=138 LEN=213
[29545.036000] Unable to identify CD-ROM format.

[Raja B (raja-b)]

Same issue for me, have noticed that on 6.10 the HDD and DVD drives are correctly identified as Master and Slave while on Feisty, both are identified as SCSI and as master drives, not sure if this affects anything. Have gone back to 6.10 but still having issues with VCD.

[Sandy Armstrong (sanfordarmstrong)]

I'm also getting "Unable to identify CD-ROM format" in dmesg since upgrading to Feisty. I will attach the relevant output files.

[rcaelius (caelius)]

I am experiencing a similar problem on PS3 hardware, in that the drive read DVD / CDROM / BLU-RAY disks anymore. The read errors that occur cause the CDROM to go offline.
CDROM reported as /dev/sr0 in dmesg under edgy and still reports as /dev/sr0 under feisty 7.04. Haven't changed fstab after upgrade.

---- snip dmesg------------
sr 0:0:0:0: rejecting I/O to offline device
Device not ready. Make sure there is a disc in the drive.
---snip-----------

--- snip lshw ---------------
     *-scsi:0
          physical id: 5
          logical name: scsi0
          capabilities: emulated
        *-cdrom UNCLAIMED
             description: SCSI CD-ROM
             physical id: 0.0.0
             bus info: scsi@0:0.0.0
----snip----------------------

[rcaelius (caelius)]

After a reboot the CDROM actually reports as this in lshw
------snip lshw --------------------------
     *-scsi:0
          physical id: 5
          logical name: scsi0
          capabilities: emulated
        *-cdrom
             description: DVD reader
             product: PS-SYSTEM 302R
             vendor: SONY
             physical id: 0.0.0
             bus info: scsi@0:0.0.0
             logical name: /dev/cdrom
             logical name: /dev/dvd
             logical name: /dev/scd0
             logical name: /dev/sr0
             version: 4074
             capabilities: removable audio dvd
           *-disc
                physical id: 0
                logical name: /dev/cdrom
----------snip--------------------

[amesenbrink (am-pcguy)]

I had so many problems after the Upgrade to Feisty I installed Feisty from scratch. CD-Rom is working fine after fresh install.

Here is my /etc/fstab:
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/sda3
UUID=b14e1ff8-ee1b-48d6-b3ae-48b4ca4e8cca / ext3 defaults,errors=remount-ro 0 1
# /dev/sda5
UUID=f7b8af84-11af-4449-90f0-0132318543ed none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0

If there is anything else that might help let me know I will post it.

[Sandy Armstrong (sanfordarmstrong)]

I'm sorry, I stated earlier that I had upgraded to Feisty, but I actually did a fresh install.

[Shone (zarej)]

I have the same problem in my fstab was
/dev/hdc /media/cdrom0 udf,iso9660 user,noauto 0 0
then I change /dev/hdc to /dev/scd0
but mount doesnt working.
When I try manually to mount this happened
$ sudo mount /dev/scd0
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

then i try $ dmesg | tail
[ 4441.868625] end_request: I/O error, dev sr0, sector 64
[ 4441.940601] sr 1:0:0:0: SCSI error: return code = 0x08000002
[ 4441.940609] sr0: Current: sense key: Hardware Error
[ 4441.940612] Additional sense: Logical unit communication CRC error (Ultra-DMA/32)
[ 4441.940619] end_request: I/O error, dev sr0, sector 64
[ 4457.012348] sr 1:0:0:0: SCSI error: return code = 0x08000002
[ 4457.012356] sr0: Current: sense key: Hardware Error
[ 4457.012359] Additional sense: Logical unit communication CRC error (Ultra-DMA/32)
[ 4457.012367] end_request: I/O error, dev sr0, sector 64
[ 4457.012486] isofs_fill_super: bread failed, dev=sr0, iso_blknum=16, block=16

[Dax Solomon Umaming (knightlust)]

I'd like to confirm this. Seems to be related to Bug #43589

[yioan (yioann)]

I have exactly the same problem after I upgraded my Dell c640 laptop from Edgy to Feisty. The cdrom is completely inaccessible. If I try to mount it manually, I get the wrong fs error message.

[yioan (yioann)]

hello,

I have noticed that if acpi is disabled, then dvd/cdrom drive works properly, but this does not comprise a complete solution since it causes other problems. For example, in my laptop after I have set the acpi=off, sound card is not working.

[Sandy Armstrong (sanfordarmstrong)]

Can read:
* DVD Movies
* Self-burned data CDs

Can't read:
* Self-burned data DVDs (you know, backups and other important stuff...)

Booting with acpi=off made no difference for me.

[Kevin Fries (kevin-kevinfries)]

I am having the same issue. My drive reads fine in Windows. I can boot from the drive. I can use the drive in Edgy. The only system that does not seem to be able to read from the drive is Feisty.

I created a Feisty CD, and burned it on my Dell D620 (also running Feisty). I rebooted the machine and the disk came up. I ran the self check, and the disk reported no errors. I then went to my desktop, and tried to read it, and it would not read. After following several fix attempts posted on launchpad and UbuntuForums, I decided to try and install from a clean install. This CD would not install. It boots, it comes up with the menu, but when I try to check integrity of the disk, it gives me an error:

/bin/sh: can't access tty: Job control turned off
(initrdram)

I know the drive is good since it works in Windows. The CD is able to bootstrap the system. The problem only occurs once Feisty is loaded.

Attached please find all my diagnostics. Notice in the dmesg, that everything is fine with the drive until it tries to read the disk. However, this disk works great in another Feisty machine.

One noted difference between my laptop and desktop... the laptop loads the CD/DVD from IDE and the desktop is treating it as SCSI (sata). Not sure what difference that makes, since the SATA driver seems to work fine on the hard drive. But it was just an observation.

Any help would be greatly appreciated.

[Mike Durham (mdurhamesq)]

Why is the 'Importance' of this bug marked 'medium'? I and many others haven't been able to read/write CD/DVD's for over a month, I would call that very important. Other more trivial bugs get a higher importance, I wonder why.
Is there any hope of getting this problem fixed or do I have to buy another brand of burner?
Cheers, Mike

[Daniel Sutil (daniel-sutil)]

Hello,

I don't know if that works for you, but I have this problem and I fix it
booting with kernel 2.6.17. That solves my problem menwhile the ubuntu team
fix the problem, because I don't want to buy another cdrom.

On 5/25/07, Mike Durham <email address hidden> wrote:
>
> Why is the 'Importance' of this bug marked 'medium'? I and many others
> haven't been able to read/write CD/DVD's for over a month, I would call that
> very important. Other more trivial bugs get a higher importance, I wonder
> why.
> Is there any hope of getting this problem fixed or do I have to buy
> another brand of burner?
> Cheers, Mike
>
> --
> CDROM drive no longer working, unable to mount.
> https://bugs.launchpad.net/bugs/94119
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Un saludo,

Daniel Sutil

[Daniel Sutil (daniel-sutil)]

Hello,

I don't know if that works for you, but I have this problem and I fix it
booting with kernel 2.6.17. That solves my problem menwhile the ubuntu team
fix the problem, because I don't want to buy another cdrom.
>
>
>
>
>
> On 5/25/07, Mike Durham <email address hidden> wrote:
> >
> > Why is the 'Importance' of this bug marked 'medium'? I and many others
> > haven't been able to read/write CD/DVD's for over a month, I would call that
> > very important. Other more trivial bugs get a higher importance, I wonder
> > why.
> > Is there any hope of getting this problem fixed or do I have to buy
> > another brand of burner?
> > Cheers, Mike
> >
> > --
> > CDROM drive no longer working, unable to mount.
> > https://bugs.launchpad.net/bugs/94119
> > You received this bug notification because you are a direct subscriber
> > of the bug.
> >
>
>
>
> --
> Un saludo,
>
> Daniel Sutil
>

--
Un saludo,

Daniel Sutil

[EdinburghRob (robert-hutchison)]

Hi Daniel,

how did you go about installing the old kernel (newbie here)

Is there any way of downloading it as binaries. I gave compiling my own kernel a try, but my system is old and low on disk space and ran out halfway through.

Thanks,

Rob

[Daniel Sutil (daniel-sutil)]

Hello,

you can install the kernel you want as "binary", with the package manager,
search for "image"

On 5/25/07, EdinburghRob <email address hidden> wrote:
>
> Hi Daniel,
>
> how did you go about installing the old kernel (newbie here)
>
> Is there any way of downloading it as binaries. I gave compiling my own
> kernel a try, but my system is old and low on disk space and ran out
> halfway through.
>
> Thanks,
>
> Rob
>
> --
> CDROM drive no longer working, unable to mount.
> https://bugs.launchpad.net/bugs/94119
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Un saludo,

Daniel Sutil

[Shone (zarej)]

I solved the problem by installing 2.6.17-11 kernel from repos. It isn't in feisty repositourims it's in edgy so I download it from http://packages.ubuntu.com and I change my /boot/grub/menu.lst to point on this kernel.

[EdinburghRob (robert-hutchison)]

Thanks to Daniel for the tip :-)

I installed 2.6.17-10 kernel. Wasn't able to figure out to use http://packages.ubuntu.com like Shone, so I copied the kernel files + module directory from my laptop that's till running Edgy, changed /boot/grub/menu.1st, and changed my /etc/fstab (I don't know if I needed to change the fstab)

Shone's approach is probably less hassle.

Rob

[Paul Webster (pjwebster)]

I saw the "Unable to identify CD-ROM format." problem when trying to use a PC magazine cover DVD on my laptop running feisty's 2.6.20-15-generic kernel. Rather than downgrade, try the following:

sudo mount -t udf /dev/scd0 /media/cdrom0/

where "/dev/scd0" is your CDROM device and "/media/cdrom0" is your desired mountpoint

[yioan (yioann)]

...it does not work for me...

Yiannis

On 5/26/07, Paul Webster <email address hidden> wrote:
> I saw the "Unable to identify CD-ROM format." problem when trying to use
> a PC magazine cover DVD on my laptop running feisty's 2.6.20-15-generic
> kernel. Rather than downgrade, try the following:
>
> sudo mount -t udf /dev/scd0 /media/cdrom0/
>
> where "/dev/scd0" is your CDROM device and "/media/cdrom0" is your
> desired mountpoint
>
> --
> CDROM drive no longer working, unable to mount.
> https://bugs.launchpad.net/bugs/94119
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
__________
Y. Ioannou
**************

[yioan (yioann)]

...Problem Resolved for my dell c640 laptop!

I have installed the latest kernel in the repository (i.e. apt-get install linux-image-2.6.20-16-386) and after the restart everything works fine. I don't know why the linux-386 metapackage that is already installed uses the linux-image-2.6.20-15-386 package.

[Koppie (senatorkoppie)]

Well I was able to upgrade my kernel . . . but it doesn't look like it's ready for primetime. My wireless card & graphics card stopped working. Maybe that's why it's not an official upgrade yet!

Still waiting for a real solution.

[beom beotiger (beotiger)]

Relax, guys!
There is no need in all that dmesg and lspci or recompiling your kernel.
Just run this command:
$ cat /proc/filesystems
and watch output for strings like 'iso9660' and 'udf'.
If at least one of these is missing, then you need to modprobe it, like this:
$ sudo modprobe udf
This adds support for any CD/DVD-ROM into your system.

[termitor (termitor)]

the bug is corrected why the news 2.6.20-16 on
00:00.0 RAM memory: nVidia Corporation MCP61 Memory Controller (rev a1)
00:01.0 ISA bridge: nVidia Corporation MCP61 LPC Bridge (rev a2)
00:01.1 SMBus: nVidia Corporation MCP61 SMBus (rev a2)
00:01.2 RAM memory: nVidia Corporation MCP61 Memory Controller (rev a2)
00:01.3 Co-processor: nVidia Corporation MCP61 SMU (rev a2)
00:02.0 USB Controller: nVidia Corporation MCP61 USB Controller (rev a2)
00:02.1 USB Controller: nVidia Corporation MCP61 USB Controller (rev a2)
00:04.0 PCI bridge: nVidia Corporation MCP61 PCI bridge (rev a1)
00:05.0 Audio device: nVidia Corporation MCP61 High Definition Audio (rev a2)
00:06.0 IDE interface: nVidia Corporation MCP61 IDE (rev a2)
00:07.0 Bridge: nVidia Corporation MCP61 Ethernet (rev a2)
00:09.0 PCI bridge: nVidia Corporation MCP61 PCI Express bridge (rev a2)
00:0b.0 PCI bridge: nVidia Corporation MCP61 PCI Express bridge (rev a2)
00:0c.0 PCI bridge: nVidia Corporation MCP61 PCI Express bridge (rev a2)
00:0d.0 VGA compatible controller: nVidia Corporation GeForce 6100 nForce 430 (rev a2)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control

and PIONEER DVD-RW DVR-110D

good job !

[Sandy Armstrong (sanfordarmstrong)]

Fixed for me in 2.6.20-16. Thanks!

[Daniel Sutil (daniel-sutil)]

Also fixed for me in kernel 2.6.20-16.

On 5/31/07, Sanford Armstrong <email address hidden> wrote:
>
> Fixed for me in 2.6.20-16. Thanks!
>
> --
> CDROM drive no longer working, unable to mount.
> https://bugs.launchpad.net/bugs/94119
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Un saludo,

Daniel Sutil

[Sitsofe Wheeler (sitsofe)]

Hmm. The fix for this bug appears to have caused breakage for others over in Bug #116996 ...

[Koppie (senatorkoppie)]

Am I the only person who still has this problem?

Here's what I've tried:

- edited entry in /etc/fstab
- removed entry in /etc/fstab (DVD will still mount without the entry in fstab--interesting)
- modprobed udf & iso9660
- upgraded kernel to 2.6.20-16
- manually mounted: sudo mount -t udf /dev/scd0 /media/cdrom0/
- turned off ACPI (it's a desktop so that's ok)

My symptoms: DVD will mount, I can browse the directories using Konqueror, but I can't copy files and it won't play the DVD in Kaffeine. I also noticed this problem after I installed Fiesty (fresh install). I know it worked before because I used the same DVD+-RW to burn the Fiesty disk image in the first place! And it still works in Windows.

I've attached all my error outputs in a single file: /etc/fstab, dmesg, lshw, lspci -vv, lspci -vvn

Did I miss something?

Thanks in advance!

[Mike Durham (mdurhamesq)]

Koppie, you are not alone. My system has the same problems as yours. I thought the new kernel would fix it, but it didn't.
I upgraded on another partition to Gutsy which had the same problems, but after a kernel update (2.6.22) I can read/write CD/DVD's.
Cheers, Mike

[termitor (termitor)]

hum, the bug is more bizarre now,

so :
I'm reboot, if the first media is a audio cd , sound juicer bugi
i'm change the media for a dvd or some cd rom (no audio) it's work
and no i'm change for the same audio cd , it's work now.

message informe about probleme of DMA ... no more info sorry
(sorry again for my bad english)

Bien a vous.

[Jack Jowett (jjjiom)]

I have the same symptoms as everyone else. The CD device isn't recognized. Looking at properties, the location, size & owner are unknown. Access is read only. Volume file system is udf & not mounted. I can't change these reading and if I could, not sure it would help.
I have looked at bug reports #62896, 66254, 44233, & 6415 plus comments at Ubuntu Form-Absolute beginners talk and since going to Feisty, the ablity to burn a CD & DVD isn't available.
This problem has been in existence for a period of time and hopefully it will be correct shortly.

Burning a CD:
Prior to my installation of Ubuntu 7.04 (Feisty Fawn ) a month ago, both devices worked with Windows (don't want to use) and Fedora 6 (problems).
 When I try to burn a CD with C/D / DVD creator, the following messages appeared:
(1) Reload a rewritable or blank disk (it can read size of file) and (2) writing files to disk.
When I right click on CD-RW/DVD RW Drive:
 This message appears: Cannot mount volume. Invalid mount option when attempting to mount the volume 'UDF Volume'.
Doesn't work with Keb either.

[markusl (markus-mnslaker)]

I upgraded from Edgy to Feisty and was able to use my two CD-Rom drives successfully. I then reinstalled Feisty from scratch and had two problems. The first is that /etc/fstab mentioned /dev/hdc and /dev/hdd, but those devices don't exist. I updated /etc/fstab to refer to /dev/scd0 and /dev/scd1:

msl@edward:~$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/hda1
UUID=a6f5a82d-25c3-4497-9603-fe5ad2c54fd2 / ext3 defaults,errors=remount-ro 0 1
# /dev/hda5
UUID=e9c7490a-9474-4e80-8c67-e7d367cabdc8 none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/scd1 /media/cdrom1 udf,iso9660 user,noauto 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto 0 0
/dev/sdb2 /mnt/b ext3 user,noauto 0 0
/mnt/b/backups/hda1-20070528.img /mnt/oldhome ext3 loop,user,noauto 0 0
msl@edward:~$

This gave me access to /media/cdrom1. But I still can't use /media/cdrom0, my CD-Rom burner, when I'm booted into Feisty. It looks like quite a low-level problem:

msl@edward:~$ sudo hd /dev/scd0
00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
00005000
msl@edward:~$

(The CD in the drive when I ran this command was a Feisty desktop CD.) dmesg includes this:

[ 731.533053] sr 1:0:0:0: SCSI error: return code = 0x08000002
[ 731.533059] sr0: Current: sense key: Hardware Error
[ 731.533062] Additional sense: Logical unit communication CRC error (Ultra-DMA/32)
[ 731.533069] end_request: I/O error, dev sr0, sector 96
[ 731.533072] printk: 2 messages suppressed.
[ 731.533075] Buffer I/O error on device sr0, logical block 12
[ 731.533081] Buffer I/O error on device sr0, logical block 13
[ 731.533085] Buffer I/O error on device sr0, logical block 14
[ 731.533088] Buffer I/O error on device sr0, logical block 15
[ 731.533091] Buffer I/O error on device sr0, logical block 16
[ 731.537557] sr 1:0:0:0: SCSI error: return code = 0x08000002
[ 731.537563] sr0: Current: sense key: Hardware Error
[ 731.537566] Additional sense: Logical unit communication CRC error (Ultra-DMA/32)
[ 731.537573] end_request: I/O error, dev sr0, sector 136
[ 731.537577] Buffer I/O error on device sr0, logical block 17
[ 731.539603] sr 1:0:0:0: SCSI error: return code = 0x08000002
[ 731.539607] sr0: Current: sense key: Hardware Error
[ 731.539610] Additional sense: Logical unit communication CRC error (Ultra-DMA/32)
[ 731.539616] end_request: I/O error, dev sr0, sector 144
[ 731.539619] Buffer I/O error on device sr0, logical block 18
[ 731.539624] Buffer I/O error on device sr0, logical block 19
[ 731.539628] Buffer I/O error on device sr0, logical block 20
[ 731.539631] Buffer I/O error on device sr0, logical block 21
[ 734.091041] ISO 9660 Extensions: Microsoft Joliet Level 3
[ 734.093195] sr 1:0:0:0: SCSI error: return code = 0x08000002
[ 734.093200] sr0: Current: sense key: Hardware Error
[ 734.093203] Additional sense: Lo...

[yioan (yioann)]

Hello,

I would like to note that after the last update, my cd-rom broke again
and it does not work. Whenever the cdrom is mapped to /dev/scd, it
simply does not work. Whenever it is mapped to /dev/hdc, it works. I
suppose that different modules are used access the cdrom each time.
Does anyone know how can I disable scd mode access (what is that? scsi
access?)?

regards,
Yiannis

[Daniel Sutil (daniel-sutil)]

Hello,

with the last update to kernel 2.6.20-16 my cdrom broke again as before. Going back to kernerl 2.6.20-15 works ok with no problem.

Yioan: The scd unit is created to access with the SATA driver as I know. The older hdc is to use with the IDE driver. As I know the hdc access is going deprecated because the SATA access works better even my cdrom is not a SATA unit but IDE unit.

[Steve Feinstein (sfein1000)]

I've had the same problem. Fails when using scd0 and works with hdc. A recent kernel update worked (looks like it switched back to hdc) and the most recent update has caused it to fail again (switched back to sdc0). So now can't burn. I can even load most CDs. Once a CDRW is placed in drive, drive is totally unusable until a reboot.

My cd drive is IDE. I do have a SATA hard drive, but it uses IDE, not a SATA card.

I'll have to see if I can download the correct kernel (maybe copy my Edgy kernel over).

CD drive is fine under Windows and Edgy

[Tzadik Vanderhoof (tzadik-vanderhoof)]

Is it safe to install on older kernel and continue to use Feisty? If so,
how do I do it?

Also... won't Ubuntu try to keep updating it if I do that?

On 6/20/07, Steve Feinstein <email address hidden> wrote:
>
> I've had the same problem. Fails when using scd0 and works with hdc. A
> recent kernel update worked (looks like it switched back to hdc) and the
> most recent update has caused it to fail again (switched back to sdc0).
> So now can't burn. I can even load most CDs. Once a CDRW is placed in
> drive, drive is totally unusable until a reboot.
>
> My cd drive is IDE. I do have a SATA hard drive, but it uses IDE, not a
> SATA card.
>
> I'll have to see if I can download the correct kernel (maybe copy my
> Edgy kernel over).
>
> CD drive is fine under Windows and Edgy
>
> --
> CDROM drive no longer working, unable to mount.
> https://bugs.launchpad.net/bugs/94119
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

--
Tzadik

[Daniel Sutil (daniel-sutil)]

Hello,

for me, works ok with kernel 2.6.20-15 not with 2.6.20-16.

Tzadik Vanderhoof, I think that you should try the earlier version that works
for me.

El Miércoles, 20 de Junio de 2007, Tzadik Vanderhoof escribió:
> Is it safe to install on older kernel and continue to use Feisty? If so,
> how do I do it?
>
> Also... won't Ubuntu try to keep updating it if I do that?
>
> On 6/20/07, Steve Feinstein <email address hidden> wrote:
> >
> > I've had the same problem. Fails when using scd0 and works with hdc. A
> > recent kernel update worked (looks like it switched back to hdc) and the
> > most recent update has caused it to fail again (switched back to sdc0).
> > So now can't burn. I can even load most CDs. Once a CDRW is placed in
> > drive, drive is totally unusable until a reboot.
> >
> > My cd drive is IDE. I do have a SATA hard drive, but it uses IDE, not a
> > SATA card.
> >
> > I'll have to see if I can download the correct kernel (maybe copy my
> > Edgy kernel over).
> >
> > CD drive is fine under Windows and Edgy
> >
> > --
> > CDROM drive no longer working, unable to mount.
> > https://bugs.launchpad.net/bugs/94119
> > You received this bug notification because you are a direct subscriber
> > of a duplicate bug.
> >
>
>
> --
> Tzadik
>
> --
> CDROM drive no longer working, unable to mount.
> https://bugs.launchpad.net/bugs/94119
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Steve Feinstein (sfein1000)]

From my setup. 2.6.20-15 doesn't work. It looks like 2.6.20-16.something did work. The newest 2.6.20-16 does not (I think it is at 29 or 28). Unfortunately I don't see a way of getting the prior version at that level (not that I remember which I upgraded from). It only seems to be at the 15 or 16 level.

[Tzadik Vanderhoof (tzadik-vanderhoof)]

Hi Steve....

Do you mind telling me how to install an older kernel (or link to a page
that explains it)? I've never done that before.

Thanks,

Tzadik

On 6/20/07, Steve Feinstein <email address hidden> wrote:
>
> >From my setup. 2.6.20-15 doesn't work. It looks like
> 2.6.20-16.something did work. The newest 2.6.20-16 does not (I think it
> is at 29 or 28). Unfortunately I don't see a way of getting the prior
> version at that level (not that I remember which I upgraded from). It
> only seems to be at the 15 or 16 level.
>
> --
> CDROM drive no longer working, unable to mount.
> https://bugs.launchpad.net/bugs/94119
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

--
Tzadik

[Steve Feinstein (sfein1000)]

I found a semi-older version that is working. See my question at:
http://ubuntuforums.org/showthread.php?t=486073

to see if I did a bad move.

For developers, the date seems to be that on 5/30 a kernel upgrade came for 2.6.20-16 which reverted back to using hdc. This works for my cd burner. On 6/7 a new kernel upgrade came for 2.6.20-16 which went back to using scd0 and my cd does not work anymore.

I copied the 5/30 version of initrd.img-2.6.20-16-generic to the boot folder. I did not change anything else (except reboot), the drive reverted back to hdc and cd works again.

Steve

[Shone (zarej)]

For people who don't know how to install an older kernel from edgy:

Go to http://packages.ubuntu.com/edgy/base/linux-image-2.6.17-11-generic and chose your architecture (etc. i386) in Download linux-image-2.6.17-11-generic section. In next page just click on link and download it. Then do double click on downloaded file to install package.

When package was installed go and edit your /boot/grub/menu.lst to point on this kernel. You should do
$sudo gedit /boot/grub/menu.lst

and put up from these lines:
title Ubuntu, kernel 2.6.20-16-generic
root (hd0,5)
kernel /boot/vmlinuz-2.6.20-16-generic root=UUID=c21c4f6a-f36a-408b-aace-1deea4387a9b ro quiet splash
initrd /boot/initrd.img-2.6.20-16-generic
quiet
savedefault

these lines:
title Ubuntu, kernel 2.6.17-11-generic
root (hd0,5)
kernel /boot/vmlinuz-2.6.17-11-generic root=UUID=c21c4f6a-f36a-408b-aace-1deea4387a9b ro quiet splash
initrd /boot/initrd.img-2.6.17-11-generic

your root (hd0,5) and UUID for disks will be different from mine so you must just change it for you.

You need also to change in your /etc/fstab line for cdrom
$sudo gedit /etc/fstab

and change scd0 to hdb, hdc or hdd to be something like this line:
/dev/hdc /media/cdrom0 udf,iso9660 user,noauto 0 0

After reboot choose Ubuntu, kernel 2.6.17-11-generic and all should work.

You may have a problem if you can't load X. You just need to install nvidia or ati drivers again for new kernel. You may also need linux-restricted-modules package from http://packages.ubuntu.com but it's not usually necessarily

[Koppie (senatorkoppie)]

For everyone who's still having this problem, those of you who have tried everything and it still won't work . . . I have the solution.

Upgrade to Gutsy Gibbon.

I just upgraded to Tribe 2. Just replaced every instance of "feisty" to "gusty" in /etc/apt/sources.list and ran "sudo apt-get update; sudo apt-get dist-upgrade" a bunch of times. It was a little rocky, which is to be expected when it's a beta and you're upgrading by hand, but so far Gutsy has been a pleasure to use, and very stable! The best part: my DVD+-RW started working again, all on its own. It might have something to do with the new kernel: 2.6.22-7!

Anyway it's too bad the Fawn never was able to play my DVDs, but it doesn't matter now that the Gibbon is here!

[Tzadik Vanderhoof (tzadik-vanderhoof)]

That definitely sounds like an awesome solution... thanks!

I will probably hold off a few days and would appreciate hearing from anyone
else who was tried this solution.

On 7/1/07, Koppie <email address hidden> wrote:
>
> For everyone who's still having this problem, those of you who have
> tried everything and it still won't work . . . I have the solution.
>
> Upgrade to Gutsy Gibbon.
>
> I just upgraded to Tribe 2. Just replaced every instance of "feisty" to
> "gusty" in /etc/apt/sources.list and ran "sudo apt-get update; sudo apt-
> get dist-upgrade" a bunch of times. It was a little rocky, which is to
> be expected when it's a beta and you're upgrading by hand, but so far
> Gutsy has been a pleasure to use, and very stable! The best part: my
> DVD+-RW started working again, all on its own. It might have something
> to do with the new kernel: 2.6.22-7!
>
> Anyway it's too bad the Fawn never was able to play my DVDs, but it
> doesn't matter now that the Gibbon is here!
>
> --
> CDROM drive no longer working, unable to mount.
> https://bugs.launchpad.net/bugs/94119
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

--
Tzadik

[Shone (zarej)]

Thanks Koppie it works.
I just download linux-image-2.6.22-7-generic_2.6.22-7.14_i386.deb from http://packages.ubuntu.com and install it without upgrading the whole system.

[Adam (adam.russell)]

Kubuntu Feisty Fawn
kernel 2.6.20-16-generic
LG DVDRAM internal, ATAPI, 8X DVD-R, 4X DVD-RW, 8X DVD+R, 4X DVD+RW, 3X DVD-RAM, 32X CD read, 24X CD-R, 16X CD-RW

Using K3b, I am unable to successfully burn a DVD. I get no errors during the burn, but I am unable to mount the burned DVD. I am also unable to mount a movie DVD via Konqueror. I must mount or pmount the DVD manually.

List of similar bug reports:
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.15/+bug/37876
https://bugs.launchpad.net/ubuntu/+source/dvdrtools/+bug/46966
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/94119
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/121246

[Tzadik Vanderhoof (tzadik-vanderhoof)]

Did you try installing 2.6.22-7 as indicaated in a previous entry for this
bug?

On 7/17/07, gomek <email address hidden> wrote:
>
> Kubuntu Feisty Fawn
> kernel 2.6.20-16-generic
> LG DVDRAM internal, ATAPI, 8X DVD-R, 4X DVD-RW, 8X DVD+R, 4X DVD+RW, 3X
> DVD-RAM, 32X CD read, 24X CD-R, 16X CD-RW
>
> Using K3b, I am unable to successfully burn a DVD. I get no errors
> during the burn, but I am unable to mount the burned DVD. I am also
> unable to mount a movie DVD via Konqueror. I must mount or pmount the
> DVD manually.
>
> List of similar bug reports:
> https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.15/+bug/37876
> https://bugs.launchpad.net/ubuntu/+source/dvdrtools/+bug/46966
> https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/94119
> https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/121246
>
> --
> CDROM drive no longer working, unable to mount.
> https://bugs.launchpad.net/bugs/94119
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

--
Tzadik

[Adam (adam.russell)]

I've always been told to avoid installing packages from different releases. With my luck, fglrx would break if I were to install the gutsy kernel. Until gutsy is released, installing that kernel seems to be just a workaround, and a workaround is not really what I was seeking. Thank you for your suggestion, though. =)

[jprovostla (jprovostla)]

Hey Shone,
Where did you find the linux-image-2.6.22-7-generic_2.6.22-7.14_i386.deb in http://packages.ubuntu.com???
I've been trying to locate it within that website and just can't find it???
Thanks, J.

[Adam (adam.russell)]

@jprovostla

http://packages.ubuntu.com/gutsy/base/linux-image-2.6.22-8-generic
http://packages.ubuntu.com/gutsy/misc/linux-restricted-modules-2.6.22-8-generic

Scroll down and click on i386.

http://mirrors.kernel.org/ubuntu/pool/main/l/linux-source-2.6.22/linux-image-2.6.22-8-generic_2.6.22-8.18_i386.deb
http://mirrors.kernel.org/ubuntu/pool/restricted/l/linux-restricted-modules-2.6.22/linux-restricted-modules-2.6.22-8-generic_2.6.22.2-8.4_i386.deb

[termitor (termitor)]

Nor the kernel 2.6.17, 2.6.20 or 2.6.22 of edgy feisty gutsy do not solve my problem.
It is still worse under gutsy, or the drawer of the cdrom is closed immediately as soon as I open it.

This bug is critical for a number of people, because they cannot fully used their computer, it should be solved absolutely.

Bien a vous

(tr by google, sorry for that)

[Tzadik Vanderhoof (tzadik-vanderhoof)]

Definitely... I have had to go back to Dapper :(

On 7/31/07, termitor <email address hidden> wrote:
>
> Nor the kernel 2.6.17, 2.6.20 or 2.6.22 of edgy feisty gutsy do not solve
> my problem.
> It is still worse under gutsy, or the drawer of the cdrom is closed
> immediately as soon as I open it.
>
> This bug is critical for a number of people, because they cannot fully
> used their computer, it should be solved absolutely.
>
> Bien a vous
>
> (tr by google, sorry for that)
>
> --
> CDROM drive no longer working, unable to mount.
> https://bugs.launchpad.net/bugs/94119
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

--
Tzadik

[termitor (termitor)]

IRQPOLL solve this bug for me , please test this solution.

sudo gedit /boot/grub/menu.lst (or nano, ...)
add irqpoll on this ligne
# kopt=root=UUID=aed3ffb0-5cd6-4710-8b7c-e8f492537cf1 ro to
result

# kopt=root=UUID=aed3ffb0-5cd6-4710-8b7c-e8f492537cf1 ro irqpoll

sudo update-grub

and reboot your computer

Bien a vous.

[Tzadik Vanderhoof (tzadik-vanderhoof)]

Did you also update the kernel, or you just added irqpoll?

On 7/31/07, termitor <email address hidden> wrote:
>
> IRQPOLL solve this bug for me , please test this solution.
>
> sudo gedit /boot/grub/menu.lst (or nano, ...)
> add irqpoll on this ligne
> # kopt=root=UUID=aed3ffb0-5cd6-4710-8b7c-e8f492537cf1 ro to
> result
>
> # kopt=root=UUID=aed3ffb0-5cd6-4710-8b7c-e8f492537cf1 ro irqpoll
>
> sudo update-grub
>
> and reboot your computer
>
>
> Bien a vous.
>
> --
> CDROM drive no longer working, unable to mount.
> https://bugs.launchpad.net/bugs/94119
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

--
Tzadik

[Adam (adam.russell)]

The problem still exists in Gutsy with the new kernel for me.

[Tzadik Vanderhoof (tzadik-vanderhoof)]

I tried IRQPOLL ... it didn't help.

[Robert Hrovat (robi-hipnos)]

I also have this problem.

IRQPOLL didn't work for me too.

It is so sad I can read burned DVDs everywhere but not on device that burned them :-(

At first I thought burner died, bought new one and same thing started to happen within few months. Last week I did fresh install of Gutsy Tribe 5 and problem is still there.

After putting burned DVD in drive, /var/log/messages shows output:

Sep 11 21:39:09 willow kernel: [ 141.700000] attempt to access beyond end of device
Sep 11 21:39:09 willow kernel: [ 141.700000] hdc: rw=0, want=68, limit=4
Sep 11 21:39:09 willow kernel: [ 141.708000] attempt to access beyond end of device
Sep 11 21:39:09 willow kernel: [ 141.708000] hdc: rw=0, want=1252, limit=4
Sep 11 21:39:09 willow kernel: [ 141.708000] attempt to access beyond end of device
Sep 11 21:39:09 willow kernel: [ 141.708000] hdc: rw=0, want=1028, limit=4
Sep 11 21:39:09 willow kernel: [ 141.708000] UDF-fs: No partition found (1)
Sep 11 21:39:09 willow kernel: [ 141.732000] attempt to access beyond end of device
Sep 11 21:39:09 willow kernel: [ 141.732000] hdc: rw=0, want=68, limit=4
Sep 11 21:39:09 willow kernel: [ 141.732000] isofs_fill_super: bread failed, dev=hdc, iso_blknum=16, block=16

Please, please fix this bug as linux not being able to read media, that previously burned, is a serious bug.

[Shone (zarej)]

At my friend's comp. cdrom didn't working even ubuntu install cd can't install system until I put the following line as kernel parameter:

all_generic_ide=1

After that cdrom works normally. This may not help you but you should try. My friend has problem with sata controller and this solved problem.

[Robert Hrovat (robi-hipnos)]

all_generic_ide does not work with me. I've noticed it changed devices from /dev/hda to /dev/sr0 /dev/scd0 /dev/sg0 but none of them can't mount DVD.

[Robert Hrovat (robi-hipnos)]

I took DVD burned on home machine (with this bug present) to machine at work, also with Gutsy, where it mounted and worked like it should.

In terminal I wrote: dvd+rw-mediainfo /dev/hdc

And I got the following (note the difference under Track status):

INQUIRY: [Optiarc ][DVD RW AD-7170A ][1.02]
GET [CURRENT] CONFIGURATION:
 Mounted Media: 11h, DVD-R Sequential
 Media ID: MCC 03RG20
 Current Write Speed: 6.1x1385=8467KB/s
 Write Speed #0: 6.1x1385=8467KB/s
 Write Speed #1: 5.1x1385=7056KB/s
 Write Speed #2: 4.1x1385=5645KB/s
 Write Speed #3: 3.1x1385=4234KB/s
 Write Speed #4: 2.0x1385=2822KB/s
 Write Speed #5: 1.0x1385=1411KB/s
GET [CURRENT] PERFORMANCE:
 Write Performance: 7.0x1385=9695KB/s@0 -> 18.0x1385=24930KB/s@2297888
 Speed Descriptor#0: 00/2297888 R@16.0x1385=22160KB/s W@18.0x1385=24930KB/s
 Speed Descriptor#1: 03/2297888 R@16.0x1385=22160KB/s W@16.0x1385=22160KB/s
 Speed Descriptor#2: 03/2297888 R@12.0x1385=16620KB/s W@12.0x1385=16620KB/s
 Speed Descriptor#3: 00/2297888 R@8.0x1385=11080KB/s W@8.0x1385=11080KB/s
 Speed Descriptor#4: 00/2297888 R@8.0x1385=11080KB/s W@6.0x1385=8310KB/s
 Speed Descriptor#5: 00/2297888 R@5.0x1385=6925KB/s W@4.0x1385=5540KB/s
READ DVD STRUCTURE[#10h]:
 Media Book Type: 00h, DVD-ROM book [revision 0]
 Legacy lead-out at: 2298496*2KB=4707319808
:-[ READ DVD-R STRUCTURE failed with SK=3h/ASC=02h/ACQ=00h]: Input/output error
READ DISC INFORMATION:
 Disc status: complete
 Number of Sessions: 1
 State of Last Session: complete
 Number of Tracks: 1
READ TRACK INFORMATION[#1]:
 Track State: complete,damaged <--- work machine showed only word complete
 Track Start Address: 0*2KB
 Free Blocks: 0*2KB
 Track Size: 1*2KB
FABRICATED TOC:
 Track#1 : 14@0
 Track#AA : 14@2297888
 Multi-session Info: #1@0
READ CAPACITY: 0*2048=0

So why does it say "damaged" at home???

[Robert Hrovat (robi-hipnos)]

Since I *really* need to read media, not just be able to burn them, I gave up exploring and bought a new drive. I keept the old one connected to check if this thing will be fixed.

[Tzadik Vanderhoof (tzadik-vanderhoof)]

all_generic_ide worked for me on my Dapper installation!

After I tried that, even though I had previously tried to solve the problem
by upgrading to Gutsy without success, I tried Gutsy again, this time as a
fresh install from a CD (Tribe 5). Now the CD and DVD both work with Gutsy,
even without all_generic_ide.

[Lizerazu (lizerazu-mailing-lists)]

I've been having the same issue on my Gateway 200ARC. Dapper/Edgy have worked fine but in my upgrade to Feisty I lost my cdrom drive. I believe it is the same issue reported above. I then tried to install Feisty from CD but it will not even boot so I haven't been able to do that. I have tried Gutsy Tribe 5 and still have the same issue. It tries to boot but ends up with a blinking cursor in the top left. I notice that when I hit my power button Gutsy Tribe 5 shutdown and asked me to remove my CD before rebooting.

[Tzadik Vanderhoof (tzadik-vanderhoof)]

FYI... you should know when I boot Feisty or Gutysy from the CD, it freezes
a long time (around 5 minutes) near the beginning of the boot process. You
should try it again and just leave it for a long time before giving up.
Once the freezing is over (on my machine) it boots normally, so it may be
the same thing for you.

On 9/26/07, Lizerazu <email address hidden> wrote:
>
> I've been having the same issue on my Gateway 200ARC. Dapper/Edgy have
> worked fine but in my upgrade to Feisty I lost my cdrom drive. I believe
> it is the same issue reported above. I then tried to install Feisty from
> CD but it will not even boot so I haven't been able to do that. I have
> tried Gutsy Tribe 5 and still have the same issue. It tries to boot but
> ends up with a blinking cursor in the top left. I notice that when I hit
> my power button Gutsy Tribe 5 shutdown and asked me to remove my CD
> before rebooting.
>
> --
> CDROM drive no longer working, unable to mount.
> https://bugs.launchpad.net/bugs/94119
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

--
Tzadik

[Robert Hrovat (robi-hipnos)]

This is crazy! Now the new drive acts the same as the old one. Unable to mount anything I put in. Could someone please check this or at least give directions how to find out what's causing this bug.

[Tzadik Vanderhoof (tzadik-vanderhoof)]

I have just done a fresh install of the final Gutsy, and it's still not working. When inserting a CD, /var/log/messages gets:

sr 1:0:1:0: [sr1] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
sr 1:0:1:0: [sr1] Sense Key : Hardware Error [current]
sr 1:0:1:0: [sr1] Add. Sense: Logical unit communication CRC error (Ultra-DMA/32)
end_request: I/O error, dev sr1, sector 64
isofs_fill_super: bread failed, dev=sr1, iso_blknum=16, block=16

and it won't mount.

[Tzadik Vanderhoof (tzadik-vanderhoof)]

I just tried with all_generic_ide=1 in Gutsy and it's working.

[Leann Ogasawara (leannogasawara)]

Hi All,

This bug hasn't had any recent activity and I'd like to try to find some sort of resolution for those who may still have an issue with their CD/DVD drives. It seems there are comments here that this was fixed in Feisty for some, fixed in Gutsy for others, or is still an issue. It's difficult for developers to debug when there exist multiple conflicting statements like those. It's likely people here are experiencing slightly different bugs. For the kernel team it is helpful if bug reports target one specific issue against a specific set of hardware.

For those of you who are still experiencing issues, 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 . If you are still experiencing issues, if you could please open a new bug report with the following debugging information included that would be great - https://wiki.ubuntu.com/KernelTeamBugPolicies . We can easily mark bugs as duplicates of one another later on.

Jaidee, since you are the original bug reporter, can you comment if this is still an issue for you? Thanks.

[Jan Saenz (janfsd)]

I am getting this problem since I upgrade to Hardy. This bug maybe the same as: https://bugs.launchpad.net/ubuntu/+bug/228624

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

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

[Stefan Bader (smb)]

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. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.