No puedo quemar DVD's doble capa con K3B
DesconectadoSaludos cordiales a todos.
Tengo una DVD Samsung, puedo quemar dvds de una sola capa sin problemas, pero cuando intento quemar un dvd doble capa, este se detiene, al llegar al 55%,y k3b dice en su interfaz: "No se puede fijar el disco", "El disco aun puede ser legible", y se cancela la grabación, a continuación les dejo el log de k3b, y la salida del comando "demesg | tail", espero me puedan ayudar, gracias anticipadas por sus esfuerzos:
4.1x.
Track 01: 4074 of 7360 MB written (fifo 99%) [buf 98%] 4.2x.
Track 01: 4075 of 7360 MB written (fifo 100%) [buf 98%] 4.1x.
/usr/bin/wodim: faio_wait_on_buffer for writer timed out.
Errno: 5 (Input/output error), write_g1 scsi sendcmd: no error
CDB: 2A 00 00 1F D7 E9 00 00 1F 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 72 0B 00 00 00 00 00 0E 09 0C 00 00 00 02 00 00
Sense Key: 0x0 No Additional Sense, Segment 11
Sense Code: 0x00 Qual 0x02 (end-of-partition/medium detected) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 270.858s timeout 200s
/usr/bin/wodim: A write error occured.
/usr/bin/wodim: Please properly read the error message above.
Errno: 5 (Input/output error), prevent/allow medium removal scsi sendcmd: fatal error
CDB: 1E 00 00 00 00 00
cmd finished after 0.000s timeout 200s
Track 01: data 7360 MB
Total size: 8452 MB (837:26.80) = 3768510 sectors
Lout start: 8453 MB (837:28/60) = 3768510 sectors
Current Secsize: 2048
HINT: use dvd+rw-mediainfo from dvd+rw-tools for information extraction.
Blocks total: 4173824 Blocks current: 4173824 Blocks remaining: 405314
Errno: 5 (Input/output error), test unit ready scsi sendcmd: fatal error
CDB: 00 00 00 00 00 00
cmd finished after 0.000s timeout 200s
write track data: error after 4273948672 bytes
Writing time: 1124.699s
Average write speed 5.3x.
Min drive buffer fill was 95%
Fixating...
Errno: 5 (Input/output error), flush cache scsi sendcmd: fatal error
CDB: 35 00 00 00 00 00 00 00 00 00
cmd finished after 0.000s timeout 200s
/usr/bin/wodim: Cannot fixate disk.
Trouble flushing the cache
Fixating time: 0.000s
Errno: 5 (Input/output error), prevent/allow medium removal scsi sendcmd: fatal error
CDB: 1E 00 00 00 00 00
cmd finished after 0.000s timeout 200s
/usr/bin/wodim: fifo had 67511 puts and 67320 gets.
/usr/bin/wodim: fifo was 0 times empty and 36917 times full, min fill was 89%.
cdrecord command:
-----------------------
/usr/bin/wodim -v gracetime=2 dev=/dev/sr1 speed=8 -sao driveropts=burnfree -data -tsize=3768510s -
mkisofs
-----------------------
3768510
Warning: -follow-links does not always work correctly; be careful.
I: -input-charset not specified, using utf-8 (detected in locale settings)
55.53% done, estimate finish Sun Apr 24 09:26:14 2011
mkisofs calculate size command:
-----------------------
/usr/bin/genisoimage -gui -graft-points -print-size -quiet -volid Iron_Man_II -volset -appid K3B THE CD KREATOR (C) 1998-2010 SEBASTIAN TRUEG AND MICHAL MALEK -publisher -preparer -sysid LINUX -volset-size 1 -volset-seqno 1 -sort /tmp/kde-nelfi/k3bys2400.tmp -no-cache-inodes -udf -iso-level 1 -path-list /tmp/kde-nelfi/k3bdp2400.tmp -dvd-video -f /tmp/kde-nelfi/k3bVideoDvd0
mkisofs command:
-----------------------
/usr/bin/genisoimage -gui -graft-points -volid Iron_Man_II -volset -appid K3B THE CD KREATOR (C) 1998-2010 SEBASTIAN TRUEG AND MICHAL MALEK -publisher -preparer -sysid LINUX -volset-size 1 -volset-seqno 1 -sort /tmp/kde-nelfi/k3bcP2400.tmp -no-cache-inodes -udf -iso-level 1 -path-list /tmp/kde-nelfi/k3bhP2400.tmp -dvd-video -f /tmp/kde-nelfi/k3bVideoDvd0]
[] ? fsnotify_modify+0x5a/0x61
[ 1320.518366] [] ? getnstimeofday+0x4d/0xc9
[ 1320.518372] [] ? do_gettimeofday+0xf/0x29
[ 1320.518378] [] ? sys_ioctl+0x41/0x58
[ 1320.518385] [] ? sysenter_do_call+0x12/0x28
[ 1345.000079] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 1345.000091] sr 2:0:0:0: [sr1] CDB: Write(10): 2a 00 00 1f d7 e9 00 00 1f 00
[ 1345.000112] ata3.00: cmd a0/01:00:00:00:f8/00:00:00:00:00/a0 tag 0 dma 63488 out
[ 1345.000115] res 40/00:02:00:0c:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
[ 1345.000120] ata3.00: status: { DRDY }
dmesg | tail
[ 1345.000120] ata3.00: status: { DRDY }
[ 1350.040017] ata3: link is slow to respond, please be patient (ready=0)
[ 1355.024032] ata3: soft resetting link
[ 1360.220024] ata3: link is slow to respond, please be patient (ready=0)
[ 1365.036027] ata3: SRST failed (errno=-16)
[ 1365.036039] ata3: soft resetting link
[ 1370.232025] ata3: link is slow to respond, please be patient (ready=0)
[ 1375.048020] ata3: SRST failed (errno=-16)
[ 1375.048032] ata3: soft resetting link
[ 1380.244024] ata3: link is slow to respond, please be patient (ready=0)
dmesg | tail
[ 1370.232025] ata3: link is slow to respond, please be patient (ready=0)
[ 1375.048020] ata3: SRST failed (errno=-16)
[ 1375.048032] ata3: soft resetting link
[ 1380.244024] ata3: link is slow to respond, please be patient (ready=0)
[ 1410.092027] ata3: SRST failed (errno=-16)
[ 1410.092040] ata3: soft resetting link
[ 1415.120028] ata3: SRST failed (errno=-16)
[ 1415.120038] ata3: reset failed, giving up
[ 1415.120044] ata3.00: disabled
[ 1415.120094] ata3: EH complete
]
PD: Si falta alguna información por favor decírmelo.
- Inicie sesión o regístrese para enviar comentarios
- 1303 lecturas
¿Que versión del paquete 'dvd+rw-tools' estás usando ahora mismo?
¿Que versión del paquete 'dvd+rw-tools' estás usando ahora mismo?
StrayCat, gracias por tu repuesta. La versión de "dvd+rw-tools", que estoy usando es la 7.1-6, y tengo la Debian estable Squeeze.
No se parece como si no fuese capaz de escribir sobre la segunda capa, ¿tienes mas logs de anteriores grabaciones? ¿se para con el mismo numero de bytes escritos?
¿Probaste a reducir la velocidad e grabación? esto ultimo es para descartar.
A mi me ocurria algo similar pero al grabar dvds en el portatil y el problema era que al grabar a velocidad maxima y al grabar 4,7 gigas se calentaba mucho y me daba error de dma, al desactivar el dma para dicha unidad me funcionó correctamente la grabación de dvd, aclaro que los cds me los copiaba todos correctamente siempre, y los dvds me fallaba siempre si lo ponia a maxima velocidad con el dma activado
Esto me llama la atención
faio_wait_on_buffer for writer timed out.Parece que se para esperando que se llene el buffer de la grabadora pero que este se quede vacio, prueba a bajar la velocidad
Esto me llama la atención
faio_wait_on_buffer for writer timed out.Parece que se para esperando que se llene el buffer de la grabadora pero que este se quede vacio, prueba a bajar la velocidad
Tigreci, k3b en la velocidad solo me da esta opciones:
"auto, ignorar, 16x, mas..."
y en el modo de grabación:
"auto y DAO"
k3b graba los dvds a todo lo que admite el medio, 16x 8x, etc. he grabado un dvd de 4.7 Gb, y lo ha hecho bien este es el log:
Devices
-----------------------
BENQ DVD DD DW1620 B7H9 (/dev/sr1, CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R, DVD-RW, DVD+R, DVD+RW, DVD+R DL) [DVD-ROM, DVD-R secuencial, DVD-RW secuencial, DVD+RW, DVD+R, DVD+R doble capa, CD-ROM, CD-R, CD-RW] [SAO, TAO, RAW, SAO/R96R, RAW/R16, RAW/R96R, Sobrescritura restringida]
<?php7]
TSSTcorp CDDVDW SH-S223C SB05 (/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 secuencial, DVD-R doble capa secuencial, DVD-R doble capa salteado, DVD-RAM, DVD-RW sobrescritura restringida, DVD-RW secuencial, DVD+RW, DVD+R, DVD+R doble capa, CD-ROM, CD-R, CD-RW] [SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P, RAW/R96R, Sobrescritura restringida, Salto de capa] [%7] System
-----------------------
K3b Version: 2.0.1
KDE Version: 4.4.5 (KDE 4.4.5)
QT Version: 4.6.3
Kernel: 2.6.32-5-686
Used versions
-----------------------cdrecord: 1.1.11
cdrecord
-----------------------scsidev: '/dev/sr0'
devname: '/dev/sr0'
scsibus: -2 target: -2 lun: -2
Linux sg driver version: 3.5.27
Wodim version: 1.1.11
SCSI buffer size: 64512
Beginning DMA speed test. Set CDR_NODMATEST environment variable if device
communication breaks or freezes immediately after that.
TOC Type: 1 = CD-ROM
Driveropts: 'burnfree'
Device type : Removable CD-ROM
Version : 5
Response Format: 2
Capabilities :
Vendor_info : 'TSSTcorp'
Identification : 'CDDVDW SH-S223C '
Revision : 'SB05'
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
Current: 0x0011 (DVD-R sequential recording)
Profile: 0x002B (DVD+R/DL)
Profile: 0x001B (DVD+R)
Profile: 0x001A (DVD+RW)
Profile: 0x0016 (DVD-R/DL layer jump recording)
Profile: 0x0015 (DVD-R/DL sequential recording)
Profile: 0x0014 (DVD-RW sequential recording)
Profile: 0x0013 (DVD-RW restricted overwrite)
Profile: 0x0012 (DVD-RAM)
Profile: 0x0011 (DVD-R sequential recording) (current)
Profile: 0x0010 (DVD-ROM)
Profile: 0x000A (CD-RW)
Profile: 0x0009 (CD-R)
Profile: 0x0008 (CD-ROM)
Profile: 0x0002 (Removable disk)
Using generic SCSI-3/mmc DVD-R(W) driver (mmc_mdvd).
Driver flags : SWABAUDIO BURNFREE
Supported modes: PACKET SAO
Drive buf size : 1048576 = 1024 KB
FIFO size : 12582912 = 12288 KB
Speed set to 22160 KB/s
Track 01: data 4454 MB
Total size: 5116 MB (506:52.42) = 2280932 sectors
Lout start: 5116 MB (506:54/32) = 2280932 sectors
Current Secsize: 2048
HINT: use dvd+rw-mediainfo from dvd+rw-tools for information extraction.
Blocks total: 2298496 Blocks current: 2298496 Blocks remaining: 17564
Starting to write CD/DVD at speed 17.0 in real SAO mode for single session.
Last chance to quit, starting real write in 2 seconds.
1 seconds.
0 seconds. Operation starts.
Waiting for reader process to fill input buffer ... input buffer ready.
Performing OPC...
Sending CUE sheet...
Starting new track at sector: 0
Track 01: 0 of 4454 MB written.
Track 01: 1 of 4454 MB written (fifo 99%) [buf 93
?>
0.0x.
Track 01: 2 of 4454 MB written (fifo 99%) [buf 87%] 6.6x.
Track 01: 3 of 4454 MB written (fifo 98%) [buf 87%] 7.2x.
Track 01: 4452 of 4454 MB written (fifo 100%) [buf 94%] 16.9x.
Track 01: 4453 of 4454 MB written (fifo 100%) [buf 94%] 16.4x.
Track 01: 4454 of 4454 MB written (fifo 100%) [buf 94%] 16.7x.
Track 01: Total bytes read/written: 4671348736/4671348736 (2280932 sectors).
Writing time: 340.392s
Average write speed 9.9x.
Min drive buffer fill was 13%
Fixating...
Fixating time: 9.085s
/usr/bin/wodim: fifo had 73579 puts and 73579 gets.
/usr/bin/wodim: fifo was 0 times empty and 6342 times full, min fill was 57%.
cdrecord command:
-----------------------
/usr/bin/wodim -v gracetime=2 dev=/dev/sr0 speed=16 -sao driveropts=burnfree -data -tsize=2280932s -
Espero esto sea de ayuda, y gracias por todo.
Encontre esto
KDE >= 3.2 - KDE is the great window manager, the powerful desktop, the very powerful c++ library K3b is based on, and a lot of programs.QT >= 3.2 KDE 3.2 requires the QT library version 3.2, a cross-platform GUI development toolkit. Since K3b is a threaded application QT needs to be compiled with threading support enabled.
cdrecord/mkisofs - Cdrecord creates home-burned CDs with a CD-R/CD-RW recorder.
dvd+rw-tools - The DVD+RW-Tools are used to burn and format DVD+R(W) and DVD-R(W) media. To enable all K3b DVD burning features version >= 7.0 is required.
Extraido de http://k3b.plainblack.com/requirements
Esto lo encontre en http://fy.chalmers.se/~appro/linux/DVD+RW/
Burning BD-R/DVD±R implies extra limitations:Needless to say that you have only one shot with -Z option:-)
Unlike DVD+RW, DVD±R media does have notion of multiple sessions. However! Not all legacy units can "see" beyond the first one. Few DVD-ROM units are capable of DVD-R multiborder playback, even fewer support DVD+R multisessioning. In other words your DVD burner might be the only unit in your vicinity capable to access data added at different occasions.
Even if your DVD unit does "sense" multiple sessions, Linux kernel [2.4] sometimes fails to pull that information from the drive:-( Till the problem is looked into and resolved you can work it around by reloading corresponding driver, most likely 'rmmod sr_mod'.
Linux kernel 2.6<10 users might experience problems mounting multisession media with last session starting beyond 2.2GB boundary. As fast-acting remedy I can suggest to route your unit through ide-scsi, the way it was under 2.4. Even though it's declared unsupported it actually still works in 2.6 (I for one still use it).
If you go for BD-R/DVD±R multisessioning, you have to use mkisofs from cdrtools-2.0 or later or apply this patch.
And when it comes to DVD+R Double Layer and DVD-R Dual Layer recordings, growisofs applies yet another limitation, purely artificial. Taking into consideration Double Layer media prices growisofs is programmed to refuse to perform unappendable recordings which are less than 1/2 of blank capacity and to advice to use single layer media instead.
DVD-R Dual Layer multisessioning is not supported for a reason discussed on the -RW companion page. Once again, as of the moment of this writing DVD-R Dual Layer recordings come out unappendable and can not be grown.
And once again, do keep in mind that 4.7GB are salesman's GB, i.e. 10003 and not 10243. If translated to "real" GB, single layer DVD±R[W] capacity is not larger than 4.4GiB, and BD - not larger than 23.3GiB! It should also be noted that earlier growisofs versions did not check if there is enough space on media to accommodate the data set to be burned, meaning that it was your sole responsibility to make sure "overburn" condition is not raised. As of version 5.2 growisofs performs the necessary checks for you and refuses to start recording if "overburn" condition appears to be unavoidable. This behaviour can be overridden with -overburn command-line option.
Encontre esto otro https://bugs.kde.org/show_bug.cgi?id=214115
Re: growisofsMon Jul 05, 2010 9:15 pm
I recommend to use cdrecord for writing DVD+R/DL.
The latest cdrtools version is 3.00
http://cdrecord.berlios.de
Me acabo de dar cuenta que k3b esta utilizando wodim, porque no cambias el programa de grabación que utiliza por debajo por ¿growiso? al parecer wodim hace tiempo que tiene problemas con grabacion de dvds de doble capa
Gracias por la respuesta Tigreci. dvd+rw-tools >= 7.1-6 en Squeeze, bueno he reemplazado wodim con cdrskin, y lo probare a ver como va, y les cuento los resultados
Saludos a todos otra vez.
He reemplazado wodim con cdrskin, y k3b no me reconocía cdrskin, incluso instale la versión de k3b y cdrskin de testing, en mi squeeze estable, a ver que sucedía, y mas de los mismo k3b seguía mostrándome el siguiente mensaje:
"No se puede encontrar el ejecutable cdrecord K3b usa en realidad cdrecord para grabar CD. Solución: Instalar el paquete cdrtools que contiene cdrecord.".
pues lo que hice al ver la negativa de k3b, fue hacer un enlace simbólico de /usr/bin/cdrskin a /usr/bin/cdrecord, mi pregunta es la siguiente:
¿Esta bien hacer esto, o me podría traer efector secundarios?
Gracias de antemano por las respuestas.
No creo que pueda tener mas efectos secundarios que si utilizas otro front end de grabacion de cds que utilice cdrecord, si ambos utilizaran los mismos parametros no deberia dar problemas.