O que há de errado com a gravação de DVD?

0

Eu não tinha gravado nenhum DVD há algum tempo e hoje eu precisava gravar 3 deles de 3 arquivos iso diferentes. 2 muito pequenos (alguns Kb) e um muito grande (8G, camada dupla). Todos eles falharam em segundos de iniciar em dois sistemas kubuntu diferentes usando o K3b. Os pequenos tinham erros de E / S não especificados, o maior:

Burned media
DVD+R Dual Layer

Devices
HL-DT-ST DVD+-RW GS40N A100 (/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 Sequential, DVD-R Dual Layer Sequential, DVD-R Dual Layer Jump, DVD-RAM, DVD-RW Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, DVD+R Dual Layer, CD-ROM, CD-R, CD-RW] [SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P, RAW/R96R, Restricted Overwrite, Layer Jump] [%7]

System
K3b Version: 2.0.2 KDE Version: 4.13.3 QT Version:  4.8.6 Kernel:      3.13.0-35-generic

Used versions
growisofs: 7.1

growisofs
Executing 'builtin_dd if=/dev/fd/0 of=/dev/sr0 obs=32k seek=0' /dev/sr0: splitting layers at 1987888 blocks /dev/sr0: "Current Write Speed" is 4.1x1352KBps.
          0/8142389248 ( 0.0%) @0x, remaining ??:?? RBU 100.0% UBU   0.0%
=== last message repeated 18 times. === :-[ WRITE@LBA=0h failed with SK=0h/ASC=00h/ACQ=03h]: Input/output error :-( write failed: Input/output error

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=4gms -use-the-force-luke=tracksize:3975776 -use-the-force-luke=dao:3975776 -dvd-compat -speed=6 -use-the-force-luke=bufsize:32m

Foi meu último DVD de dupla camada ...

Talvez eu deva adicionar o seguinte do dmesg:

warning: 'growisofs' uses 32-bit capabilities (legacy support in use)
ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
CDB: 
Write(10): 2a 00 00 00 00 00 00 00 10 00
ata4.00: cmd a0/01:00:00:00:80/00:00:00:00:00/a0 tag 30 dma 32768 out
         res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
ata4.00: status: { DRDY }
ata4: hard resetting link
ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata4.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
ata4.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
ata4.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
ata4.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
ata4.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
ata4.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
ata4.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
ata4.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
ata4.00: configured for UDMA/100
ata4: EH complete
ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
CDB: 
Start/Stop Unit: 1b 00 00 00 02 00
ata4.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 16
         res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
ata4.00: status: { DRDY }
ata4: hard resetting link
ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata4.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
ata4.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
ata4.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
ata4.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
ata4.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
ata4.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
ata4.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
ata4.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
ata4.00: configured for UDMA/100
ata4: EH complete
    
por dargaud 17.09.2014 / 20:25

1 resposta

0

% bl0ck_qu0te%

Isso indica problemas de hardware com a conexão SATA para a unidade.

Tradicionalmente, aconselha-se verificar o cabeamento e a energia fornecem. Mas eu vejo vestígios na web, que outro hardware ruim (por exemplo, rede) pode causar isso:    link

(Digite a mensagem de erro acima no Google para ver vários outros  relatórios com diferentes teorias sobre o motivo.)

Tenha um bom dia :)

Thomas

    
por Thomas Schmitt 18.09.2014 / 08:13