Burning dvd succedes, but can't read disk afterwards

Confirmed

is this the same as bug #37876 ? If so, this should be marked as duplicate of it and bug #37876 should be marked as confirmed by the dupe, am I right?

Probably it is the same one - couldn't find that one, when I was filling this issue.

But that one was filled under kernel as reading problem - I belive this is really burning problem as it only happens with cds burned with Dapper. I'll try to find out if running on Breezy (-ish) kernel solves anything, and post a better comment then.
AFAIK noone found out yet what exactly causes the problem (and wrote about it in some visible place)

Ok - my problem most probably is a dup of bug #37876. I can read this cd on another dapper and on windows with no problems.
So it comes down to reading problem.

Sorry for tripple (yaikes!) post.
No - not a reading problem - problem is in the recorded dvd. I've booted comletely different live distro, on 2.4 kernel, which could read my dvds burned with Breezy, but still had problems with mounting one burned with Dapper.
There's an error on the new dvd, but I still can't find what exactly causes it.

I have exacrtly the same problem described in this bug and in the http://ubuntuforums.org/showthread.php?t=182415. The same dmesg output and everyhting. I have a TOSHIBA ODD-DVD SD-R5272 drive. Everyhting worked fine in Breezy, and now I have this problem on the exact same hardware after the upgrade to Dapper. I have since tried the drive on a different machine, with an AMD processor rather than the Intel that is in the original machine, and with a differnent chipset. It burns corrupted DVDs on both machines.

Exactly the same error with TSSTcorpCD/DVDW TS-L532A (Toshiba) drive:

[17190180.620000] hdc: media error (bad sector): status=0x51 { DriveReady SeekComplete Error }
[17190180.620000] hdc: media error (bad sector): error=0x30 { LastFailedSense=0x03 }
[17190180.620000] ide: failed opcode was: unknown

I can burn successfuly, but then can't read it (anywhere) :( Tried growisofs and nerolinux - burns ok, but can't read.

Can you reproduce problem on Edgy?

I can. See https://bugs.launchpad.net/distros/ubuntu/+bug/73725

I think it is the same bug. WoW (so old bug) ;-)

Unfortunately I've managed to reproduce this problem on Edgy :(

After burning dvd image with nautilus, when I try to read it I get:

Dec 14 15:13:25 owl kernel: [17180653.892000] hdc: media error (bad sector): status=0x51 { DriveReady SeekComplete Error }
Dec 14 15:13:25 owl kernel: [17180653.892000] hdc: media error (bad sector): error=0x30 { LastFailedSense=0x03 }
Dec 14 15:13:25 owl kernel: [17180653.892000] ide: failed opcode was: unknown
Dec 14 15:13:25 owl kernel: [17180653.892000] end_request: I/O error, dev hdc, sector 0

I have TSSTcorpCD/DVDW TS-L532A (Toshiba) drive and was burning on DVD+R cd.

Now it happens with both CDs and DVDs.
Still happens in Edgy original package set on 2.6.17-10-generic as well as on Edgy with packages recompiled from Feisty (from source packs), with edgy kernel:
wodim 9:1.1.2-1 (whole cdrkit) and gnomebaker 0.6.0-6ubuntu2

dmesg same as always, dd can't copy first byte (with ibs=1 obs=1, IO error), but OTOH `wodim -toc` succeeds:

Device type : Removable CD-ROM
Version : 0
Response Format: 2
Capabilities :
Vendor_info : 'HL-DT-ST'
Identification : 'DVD-RW GWA-4040N'
Revision : '1.02'
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr).
Driver flags : MMC-3 SWABAUDIO BURNFREE
Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R
first: 1 last 1
track: 1 lba: 0 ( 0) 00:02:00 adr: 1 control: 4 mode: 1
track:lout lba: 222299 ( 889196) 49:25:74 adr: 1 control: 6 mode: -1

as well as -atip:

ATIP info from disk:
  Indicated writing power: 5
  Is not unrestricted
  Is not erasable
  Disk sub type: Medium Type B, low Beta category (B-) (4)
  ATIP start of lead in: -12520 (97:15/05)
  ATIP start of lead out: 359849 (79:59/74)
Disk type: Short strategy type (Phthalocyanine or similar)
Manuf. index: 26
Manufacturer: TDK Corporation

After updating my firmware with TS-L532A_TI94_TIER_OEM.zip from http://www.toshibaer.com/firmware/index.php?path=TS-L532A/

I can now burn DVD+R's again, but still no DVD-R's. The same media works fine in windows with nero, and DVD+R's worked fine with edgy for me before updating firmware.

Still exists with gutsy, and my last comment was premature, burning DVD's is hit/miss with any of the firmwares for my drive.

dvd+rw-tools (7.0-7)

Also check this forum:
http://ubuntuforums.org/showthread.php?t=182415

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

I had the same issue trying to burn an ISO image to DVD-R.

growisofs and cdrecord both failed to produce a proper DVD

cdrtools (10:2.01.01a33-0ubuntu2)
dvd+rw-tools (7.0-7)

cdrskin worked perfectly however.

using readcd, i found that the images burned to the drive were the right size:

-rw-r--r-- 1 radu radu 3709665280 Dec 16 03:03 sol-nv-b77-x86-dvd.iso (the original image)
-rw-r--r-- 1 radu radu 3709665280 Dec 16 03:21 sol-nv-b77-x86-dvd.iso.2 (the DVD dump from readcd)
-rw-r--r-- 1 radu radu 3709665280 Dec 16 03:24 sol-nv-b77-x86-dvd.iso.3 (another readcd dump from another DVD coasted by cdrecord)

however, they had extra bytes prepended:

% head -1 sol-nv-b77-x86-dvd.iso
CD001Solaris SOL_11_X86 f@@^"¨¨k

% head -1 sol-nv-b77-x86-dvd.iso.2
*# # *CD001Solaris SOL_11_X86 f@@^"¨¨k

The ends are all 0'd out, so I can't tell a difference there, but it appears like the 6 bytes at the beginning are to blame. The image has the right size, so I'm assuming six bytes are skipped at the end, but I don't have time to check now.

my bad, i used dvdrecord, not cdrecord.

dvdrtools (0.3.1-4)

It has been a very long time since there were any updates on this bug. Is anyone still experiencing this on a current release?

[Expired for dvdrtools (Ubuntu) because there has been no activity for 60 days.]