Created attachment 398245 [details] brasero.1.log Description of problem: When brasero burns an ISO CD image, the resulting disc produces kernel I/O errors when loaded into a LiteOn iHAS424 DVD/CD burner. These errors do not occur with a CD burned with "wodim -dao". It appears that brasero is burning disc images with tao instead of dao, and this is confirmed by the brasero log: BraseroBurn: (at burn-libburn-common.c:218) BraseroLibburn TAO pre-track 01 : get_nwa(0)=1, d=0 , demand=204472320 , cap=736966656 Version-Release number of selected component (if applicable): brasero-2.29.91-2.fc13.x86_64 wodim-1.1.10-1.fc13.x86_64 How reproducible: Always. Steps to Reproduce: 1. Download and verify an ISO CD image: http://serverbeach1.fedoraproject.org/pub/alt/stage/13-Alpha.RC4/Fedora/x86_64/iso/Fedora-13-Alpha-x86_64-netinst.iso http://serverbeach1.fedoraproject.org/pub/alt/stage/13-Alpha.RC4/Fedora/x86_64/iso/Fedora-13-Alpha-x86_64-CHECKSUM $ md5sum -c Fedora-13-Alpha-x86_64-CHECKSUM 2. Use brasero to burn it to a CDR. 3. Use wodim to burn it to another CDR: $ wodim -v -dao dev=/dev/cdrom Fedora-13-Alpha-x86_64-netinst.iso 4. Open a terminal window and run: $ su -c 'tail -f /var/log/messages' 5. Insert each disc in turn into the optical drive and watch for error messages. 6. Verify the integrity of each disc by mounting it, and then by booting it and running the media check. Actual results: The disc burned by brasero produces error messages. The disc burned by "wodim -dao" does not produce error messages. No errors occur with a different optical drive (details to follow). Expected results: The disc burned by brasero does not produce error messages. Additional info: Example error messages from /var/log/messages. Sector 399360 appears to be near the last sector of the CD image (399360×512 = 204472320, which the size reported by "ls -l"). Mar 6 11:41:38 spruce kernel: end_request: I/O error, dev sr0, sector 399360 Mar 6 11:41:38 spruce kernel: Buffer I/O error on device sr0, logical block 49920 Mar 6 11:41:39 spruce kernel: sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Mar 6 11:41:39 spruce kernel: sr 1:0:0:0: [sr0] Sense Key : Illegal Request [current] Mar 6 11:41:39 spruce kernel: Info fld=0x18601 Mar 6 11:41:39 spruce kernel: sr 1:0:0:0: [sr0] Add. Sense: Illegal mode for this track Mar 6 11:41:39 spruce kernel: sr 1:0:0:0: [sr0] CDB: Read(10): 28 00 00 01 86 00 00 00 02 00 Mar 6 11:41:39 spruce kernel: end_request: I/O error, dev sr0, sector 399360 [stephent@spruce fedora]$ ls -l Fedora-13-Alpha-x86_64-netinst.iso -rw-rw-r--. 1 stephent stephent 204472320 Feb 25 16:28 Fedora-13-Alpha-x86_64-netinst.iso [stephent@spruce tmp]$ su -c 'hdparm -I /dev/sr0' Password: /dev/sr0: ATAPI CD-ROM, with removable media Model Number: ATAPI iHAS424 Y Firmware Revision: ZL1U Transport: Serial, ATA8-AST, SATA 1.0a, SATA II Extensions, SATA Rev 2.5, SATA Rev 2.6 Standards: Likely used CD-ROM ATAPI-1 Configuration: DRQ response: 50us. Packet size: 12 bytes cache/buffer size = unknown Capabilities: LBA, IORDY(can be disabled) DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5 Cycle time: min=120ns recommended=120ns PIO: pio0 pio1 pio2 pio3 pio4 Cycle time: no flow control=120ns IORDY flow control=120ns Commands/features: Enabled Supported: * Power Management feature set * PACKET command feature set * DEVICE_RESET command * NOP cmd * Gen1 signaling speed (1.5Gb/s) * Host-initiated interface power management * Phy event counters Device-initiated interface power management * Software settings preservation [stephent@spruce tmp]$
No errors occur with the optical drive in my Asus Z91E laptop. I believe the drive is a Toshiba. [stephent@maple ~]$ sudo hdparm -I /dev/cdrom [sudo] password for stephent: /dev/cdrom: ATAPI CD-ROM, with removable media Model Number: TSSTcorpCDW/DVD TS-L462A Serial Number: 75W3210010 Firmware Revision: AS30 Standards: Likely used CD-ROM ATAPI-1 Configuration: DRQ response: 50us. Packet size: 12 bytes cache/buffer size = unknown Capabilities: LBA, IORDY(can be disabled) DMA: sdma0 sdma1 sdma2 mdma0 mdma1 mdma2 udma0 udma1 *udma2 Cycle time: min=120ns recommended=120ns PIO: pio0 pio1 pio2 pio3 pio4 Cycle time: no flow control=227ns IORDY flow control=120ns [stephent@maple ~]$
The ScanDisc test from Nero DiscSpeed (4.11.5.0) also shows that the last sectors of CDs burned by brasero are bad. The test was done on my Asus Z91E laptop booted into Windows XP.
(In reply to comment #2) > The ScanDisc test from Nero DiscSpeed (4.11.5.0) also shows that the last > sectors of CDs burned by brasero are bad. "readom -c2scan" will scan for CD errors in Linux. Be sure to umount the volume first. These tests were done with a LiteOn iHAS424 DVD/CD burner and F12. [stephent@walnut ~]$ rpm -qf /usr/bin/readom wodim-1.1.10-1.fc12.x86_64 # disc burned with brasero [stephent@walnut ~]$ sudo umount /dev/cdrom [stephent@walnut ~]$ readom -c2scan dev=/dev/cdrom Read speed: 8467 kB/s (CD 48x, DVD 6x). Write speed: 8467 kB/s (CD 48x, DVD 6x). Capacity: 99842 Blocks = 199684 kBytes = 195 MBytes = 204 prMB Sectorsize: 2048 Bytes Copy from SCSI (1,0,0) disk to file '/dev/null' end: 99842 Errno: 5 (Input/output error), read_cd scsi sendcmd: no error CDB: BE 00 00 01 85 E5 00 00 1D FA 00 00 status: 0x2 (CHECK CONDITION) Sense Bytes: F0 00 05 00 01 86 01 0A 00 00 00 00 64 00 00 00 Sense Key: 0x5 Illegal Request, Segment 0 Sense Code: 0x64 Qual 0x00 (illegal mode for this track) Fru 0x0 Sense flags: Blk 99841 (valid) cmd finished after 0.081s timeout 40s readom: Input/output error. Cannot read source disk readom: Retrying from sector 99813. ............................. readom: Input/output error. Error on sector 99841 not corrected. Total of 1 errors. readom: -noerror set, continuing ... addr: 99842 Time total: 51.611sec Read 257990.17 kB at 4998.7 kB/sec. Max corected retry count was 0 (limited to 10). The following 1 sector(s) could not be read correctly: 99841 Total of 1 hard read errors. C2 errors total: 0 bytes in 0 sectors on disk C2 errors rate: 0.000000% C2 errors on worst sector: 0, sectors with 100+ C2 errors: 0 [stephent@walnut ~]$ # disc burned with "wodim -dao" [stephent@walnut ~]$ sudo umount /dev/cdrom [stephent@walnut ~]$ readom -c2scan dev=/dev/cdrom Read speed: 8467 kB/s (CD 48x, DVD 6x). Write speed: 8467 kB/s (CD 48x, DVD 6x). Capacity: 99840 Blocks = 199680 kBytes = 195 MBytes = 204 prMB Sectorsize: 2048 Bytes Copy from SCSI (1,0,0) disk to file '/dev/null' end: 99840 addr: 99840 cnt: 27 Time total: 50.784sec Read 257985.00 kB at 5080.0 kB/sec. Total of 0 hard read errors. C2 errors total: 0 bytes in 0 sectors on disk C2 errors rate: 0.000000% C2 errors on worst sector: 0, sectors with 100+ C2 errors: 0 [stephent@walnut ~]$
See also: Bug 504892 - Live CD will "end_request: I/O error, dev sr0", unable to boot
I have the exact same issue! Each time an iso is written to a cd-r, then upon booting from it, then there are "sense errors" shown on screen about "Illegal mode for this track"! I have a LG GSA-4167b CD/DVD burner, and with other burning-apps i've tested on a friends Windows XP box, then there's no issues! (With the same discs! - Verbatim Crystal AZO!) Btw, since Brasero is merely a GUI frontend to different console-apps(and optionally, libburnia), then i'm thinking that maybe the error is comming from those instead? (However, the wodim tests above seems to indicate otherwise?). The log posted above seems to indicate that libburnia(libburn-common.c listed in log) is being used, but i'm using the standard console tools through Brasero i.e. using Brasero by default without changing anything, but am experiencing the exact same thing. Btw, even though there are error shown when booting the faulty discs, then they continue to run nonetheless. Is it the same for you, or are the discs stopping to run completelly? This is an annoying issue, as I have just discovered this now, and have e.g. installed my OS(Zenwalk), with such a bad disc, and am now thinking about if the resulting install is flawed in some way? I don't have access to the Brasero buglist, so could someone else please kindly submit a bug-report about this to them, as it's IMHO a prety severe issue/bug. Thanks in advance! Martin.
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.