f12 k3b error

[giulianoz]

Helo,
It seems I can't burn any kind of disc (cd/dvd, audio/video/data) usgin my internal sata burner (sr0). I treied googling around and reinstalling everything from dvd+rw-tools up but the error is still there. the burner works fine with windows on the very same pc (dual boot). I tried different media and different speeds. when using an usb burner everything's fine...

any idea ?

thanks

giuliano

System
-----------------------
K3b Version: 1.0.5

KDE Version: 3.5.10-21.fc12 Fedora
QT Version: 3.3.8b
Kernel: 2.6.31.12-174.2.22.fc12.x86_64
Devices
-----------------------
HL-DT-ST DVDRAM GH22NS40 NL01 (/dev/sr0, ) [CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R, DVD-RW, DVD-R DL, DVD+R, DVD+RW, DVD+R DL] [DVD-ROM, DVD-R sequenziale, DVD-R sequenziale a doppio strato, DVD-R jump a doppio strato, DVD-RAM, DVD-RW a riscrittura limitata, DVD-RW sequenziale, DVD+RW, DVD+R, DVD+R a doppio strato, CD-ROM, CD-R, CD-RW] [SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R96R, Riscrittura limitata, Livello Jump]

HL-DT-ST DVDRAM GSA-E50L NE01 (/dev/sr1, ) [CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R, DVD-RW, DVD-R DL, DVD+R, DVD+RW, DVD+R DL] [DVD-ROM, DVD-R sequenziale, DVD-R sequenziale a doppio strato, DVD-R jump a doppio strato, DVD-RAM, DVD-RW a riscrittura limitata, DVD-RW sequenziale, DVD+RW, DVD+R, DVD+R a doppio strato, CD-ROM, CD-R, CD-RW] [SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P, RAW/R96R, Riscrittura limitata, Livello Jump]
Burned media
-----------------------
DVD-R sequenziale

K3bIsoImager
-----------------------
mkisofs print size result: 2291214 (4692406272 bytes)
Pipe throughput: 4784128 bytes read, 4779520 bytes written.

Used versions
-----------------------
mkisofs: 1.1.10
growisofs: 7.1

growisofs
-----------------------
Executing 'builtin_dd if=/dev/fd/0 of=/dev/sr0 obs=32k seek=0'
/dev/sr0: "Current Write Speed" is 16.4x1352KBps.
0/4692406272 ( 0.0%) @0x, remaining ??:?? RBU 100.0% UBU 0.0%
0/4692406272 ( 0.0%) @0x, remaining ??:?? RBU 100.0% UBU 0.0%
0/4692406272 ( 0.0%) @0x, remaining ??:?? RBU 100.0% UBU 0.0%
:-[ WRITE@LBA=100h failed with SK=5h/INVALID ADDRESS FOR WRITE]: Invalid argument
:-( write failed: Invalid argument
/dev/sr0: flushing cache
/dev/sr0: updating RMA
/dev/sr0: closing disc

growisofs command:
-----------------------
/usr/bin/growisofs -Z /dev/sr0=/dev/fd/0 -use-the-force-luke=notray -use-the-force-luke=tty -use-the-force-luke=tracksize:2291214 -dvd-compat -speed=16 -use-the-force-luke=bufsize:4m

mkisofs
-----------------------
2291214
I: -input-charset not specified, using utf-8 (detected in locale settings)
0.02% done, estimate finish Wed Mar 3 17:46:46 2010
0.04% done, estimate finish Wed Mar 3 17:46:46 2010
0.07% done, estimate finish Wed Mar 3 17:46:46 2010
0.09% done, estimate finish Wed Mar 3 17:46:46 2010

mkisofs calculate size command:
-----------------------
/usr/bin/genisoimage -gui -graft-points -print-size -quiet -volid K3b data project -volset -appid K3B THE CD KREATOR (C) 1998-2006 SEBASTIAN TRUEG AND THE K3B TEAM -publisher -preparer -sysid LINUX -volset-size 1 -volset-seqno 1 -sort /tmp/kde-giuliano/k3bTQwos5.tmp -rational-rock -hide-list /tmp/kde-giuliano/k3bTTGeKY.tmp -joliet -joliet-long -hide-joliet-list /tmp/kde-giuliano/k3b2Qjj61.tmp -no-cache-inodes -full-iso9660-filenames -iso-level 2 -path-list /tmp/kde-giuliano/k3bIOCaoV.tmp

mkisofs command:
-----------------------
/usr/bin/genisoimage -gui -graft-points -volid K3b data project -volset -appid K3B THE CD KREATOR (C) 1998-2006 SEBASTIAN TRUEG AND THE K3B TEAM -publisher -preparer -sysid LINUX -volset-size 1 -volset-seqno 1 -sort /tmp/kde-giuliano/k3b74JeRC.tmp -rational-rock -hide-list /tmp/kde-giuliano/k3bBgsL9l.tmp -joliet -joliet-long -hide-joliet-list /tmp/kde-giuliano/k3bnJGuvu.tmp -no-cache-inodes -full-iso9660-filenames -iso-level 2 -path-list /tmp/kde-giuliano/k3btd52Nd.tmp

[grungedoobie]

Having a similar problem, not just with K3B, but also with Brasero and Nautilus. Since February 2010, I've trashed 8 CD's and 3 DVD's only to get one ISO and given up on the rest. The most common error with K3B is after burning 75% or more, it decides that it doesn't have "permission" to burn the disk. If it didn't have permission, why did it even start? I've checked all the usual suspects, and nothing can be found. Brasero's most common failure is a "buffer error" or else it just freezes. Nautilus typically freezes while creating the tracks (writing text). It really stinks to not be able to use my hardware.

The Grunge

[giulianoz]

I "solved" using nero linux 4... I'll try agan when a new version of k3b (or f13) is out

[grungedoobie]

Thank you!!! I'll get on it asap!! Will let you know what happens. 8-)

---------- Post added at 05:18 PM CDT ---------- Previous post was at 10:17 AM CDT ----------

Thanks, Nero Freaked my system. <-- The drive turned out to be whacked, and Nero refused to respond in any way. It would not stop, cancel , close, or succumb to the "End Process" or "Kill" command.

[grungedoobie]

My burner died. Apparently it started dying back in February. I've done some research on the drive, and it has problems with the focus mechanism for the laser while burning. I can read discs, just not write them any more. That stinks. I've had it for almost a year and a half. It's a Sony DVD RW AD-7203A Label Flash Ram-Writer.

I have since learned that having Label Flash/Light Scribe can be cool if you want to pay the extra bucks to not use a permanent marker, but those technologies seriously decrease the life expectancy of the drive. Think I'll wait a while before looking at those again.

To anyone who wasted their time by reading my rant and especially to those who have spent their time writing the software I love, please forgive me.

Yes, I have double checked with a Fedora 12 64bit install that I put on a friends laptop, and all of the disk burning software worked flawlessly. (K3B, Brasero, and Nautilus?)

The Grunge.

[SugarHi]

Having the same problem. Both k3b and brasero are failing after writing just enough to trash the CD. tried TAO and DAO without any difference. I have reinstalled the software to no effect. Update tells me that my F12 is fully up to date. I think I may have updated myself into obsolescence.

---

solved my problem. I reinstalled all of the dependencies for the cd writer and now it is working.