I have a dual layer dvd burner, and dual layer DVD media. Running fc22 64 bit.
Burning an 8.2GB file to the medium dies at byte 4060348416 with Track 01: 3872 of 7740 MB written (fifo 99%) [buf 100%] 2.0x.cdrecord: Input/output error. write_g1: scsi sendcmd: no error CDB: 2A 00 00 1E 40 80 00 00 10 00 status: 0x2 (CHECK CONDITION) Sense Bytes: F1 00 04 00 1E 3D E0 0A 00 32 7F 13 09 90 00 00 Sense Key: 0x4 Hardware Error, deferred error, Segment 0 Sense Code: 0x09 Qual 0x90 (track following error) [No matching qualifier] Fru 0x0 Sense flags: Blk 1981920 (valid) cmd finished after 1.151s timeout 200s
write track data: error after 4060348416 bytes cdrecord: A write error occured. cdrecord: Please properly read the error message above. Writing time: 1512.651s (00:25:12.651) Average write speed 3.9x. Min drive buffer fill was 4% Total of 1 possible drive buffer underruns predicted. Fixating... Fixating time: 0.002s (00:00:00.002) cdrecord: fifo had 124040 puts and 123913 gets. cdrecord: fifo was 2 times empty and 69171 times full, min fill was 0%.
The kernel detects the drive as follows: May 05 18:16:28 localhost kernel: sr 1:0:0:0: [sr0] scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray
So, it seems the drive does not handle dual layer media????
What does your kernel say about your dual layer dvd burner?
On Thu, May 05, 2016 at 06:54:36PM -0600, jd1008 wrote:
I have a dual layer dvd burner, and dual layer DVD media. Running fc22 64 bit.
I burn dual layer DVDs successfully with K3B. Doesn't K3B use cdrecord as its back end?
Burning an 8.2GB file to the medium dies at byte 4060348416 with Track 01: 3872 of 7740 MB written (fifo 99%) [buf 100%] 2.0x.cdrecord: Input/output error. write_g1: scsi sendcmd: no error CDB: 2A 00 00 1E 40 80 00 00 10 00 status: 0x2 (CHECK CONDITION) Sense Bytes: F1 00 04 00 1E 3D E0 0A 00 32 7F 13 09 90 00 00 Sense Key: 0x4 Hardware Error, deferred error, Segment 0 Sense Code: 0x09 Qual 0x90 (track following error) [No matching qualifier] Fru 0x0 Sense flags: Blk 1981920 (valid) cmd finished after 1.151s timeout 200s
write track data: error after 4060348416 bytes cdrecord: A write error occured. cdrecord: Please properly read the error message above. Writing time: 1512.651s (00:25:12.651) Average write speed 3.9x. Min drive buffer fill was 4% Total of 1 possible drive buffer underruns predicted. Fixating... Fixating time: 0.002s (00:00:00.002) cdrecord: fifo had 124040 puts and 123913 gets. cdrecord: fifo was 2 times empty and 69171 times full, min fill was 0%.
The kernel detects the drive as follows: May 05 18:16:28 localhost kernel: sr 1:0:0:0: [sr0] scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray
So, it seems the drive does not handle dual layer media????
What does your kernel say about your dual layer dvd burner?
users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: http://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Perhaps. I have not checked. But, I found out that the version of cdrecord I have is an old version from Jörg Schilling and I think now that that was the cause. I switched over to wodim, and all is well.
On 05/05/2016 10:51 PM, Fred Smith wrote:
On Thu, May 05, 2016 at 06:54:36PM -0600, jd1008 wrote:
I have a dual layer dvd burner, and dual layer DVD media. Running fc22 64 bit.
I burn dual layer DVDs successfully with K3B. Doesn't K3B use cdrecord as its back end?
Burning an 8.2GB file to the medium dies at byte 4060348416 with Track 01: 3872 of 7740 MB written (fifo 99%) [buf 100%] 2.0x.cdrecord: Input/output error. write_g1: scsi sendcmd: no error CDB: 2A 00 00 1E 40 80 00 00 10 00 status: 0x2 (CHECK CONDITION) Sense Bytes: F1 00 04 00 1E 3D E0 0A 00 32 7F 13 09 90 00 00 Sense Key: 0x4 Hardware Error, deferred error, Segment 0 Sense Code: 0x09 Qual 0x90 (track following error) [No matching qualifier] Fru 0x0 Sense flags: Blk 1981920 (valid) cmd finished after 1.151s timeout 200s
write track data: error after 4060348416 bytes cdrecord: A write error occured. cdrecord: Please properly read the error message above. Writing time: 1512.651s (00:25:12.651) Average write speed 3.9x. Min drive buffer fill was 4% Total of 1 possible drive buffer underruns predicted. Fixating... Fixating time: 0.002s (00:00:00.002) cdrecord: fifo had 124040 puts and 123913 gets. cdrecord: fifo was 2 times empty and 69171 times full, min fill was 0%.
The kernel detects the drive as follows: May 05 18:16:28 localhost kernel: sr 1:0:0:0: [sr0] scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray
So, it seems the drive does not handle dual layer media????
What does your kernel say about your dual layer dvd burner?
users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: http://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
On Sat, 7 May 2016 08:41:42 -0600 jd1008 wrote:
I switched over to wodim, and all is well.
That's the exact opposite of all my experiences with wodim. I always dig up the "real" cdrecord from Schilling and build it in each new fedora I install. It is the only way I get trouble free CD/DVD/Blu-Ray writing to work.
On 2016-05-07 at 10:50:03 Tom Horsley wrote:
On Sat, 7 May 2016 08:41:42 -0600 jd1008 wrote:
I switched over to wodim, and all is well.
That's the exact opposite of all my experiences with wodim. I always dig up the "real" cdrecord from Schilling and build it in each new fedora I install. It is the only way I get trouble free CD/DVD/Blu-Ray writing to work.
On my F23 system cdrecord is a symbolic link to wodim.
On 05/07/2016 09:00 AM, Erik P. Olsen wrote:
On 2016-05-07 at 10:50:03 Tom Horsley wrote:
On Sat, 7 May 2016 08:41:42 -0600 jd1008 wrote:
I switched over to wodim, and all is well.
That's the exact opposite of all my experiences with wodim. I always dig up the "real" cdrecord from Schilling and build it in each new fedora I install. It is the only way I get trouble free CD/DVD/Blu-Ray writing to work.
On my F23 system cdrecord is a symbolic link to wodim.
Yes that is true, because people had so gotten used to "cdrecord", that the wodim project simply took a version of cdrecord and hacked it into wodim. I have read enough technical jargon about how wrong wodim is, and how right Schilling's cdrecord is. But the bottom line to the user is that it has to work.
On Sat, May 7, 2016 at 9:06 AM, jd1008 jd1008@gmail.com wrote:
On 05/07/2016 09:00 AM, Erik P. Olsen wrote:
On 2016-05-07 at 10:50:03 Tom Horsley wrote:
On Sat, 7 May 2016 08:41:42 -0600 jd1008 wrote:
I switched over to wodim, and all is well.
That's the exact opposite of all my experiences with wodim. I always dig up the "real" cdrecord from Schilling and build it in each new fedora I install. It is the only way I get trouble free CD/DVD/Blu-Ray writing to work.
On my F23 system cdrecord is a symbolic link to wodim.
Yes that is true, because people had so gotten used to "cdrecord", that the wodim project simply took a version of cdrecord and hacked it into wodim. I have read enough technical jargon about how wrong wodim is, and how right Schilling's cdrecord is. But the bottom line to the user is that it has to work.
Or fail gracefully, i.e. in this case fail before it starts writing media that'll end up being a coaster. I suggest filing a bug.
-
Chris Murphy -
Ed Greshko -
Erik P. Olsen -
Fred Smith -
JD -
Tom Horsley