On 13-04-2015 21:55, Jeremy O'Brien wrote: > Join the club of Brasero haters. That issue existed at least 2-3 years > ago when I used it last. Incredible. > > On Mon, Apr 13, 2015, at 16:42, Francis Gerund wrote: >> Well, I'll be [darned]! >> >> Burned another cd manually, using wodim, then verified it, as per the >> website. >> >> It worked. >> >> So it does seem to be a problem with Brasero, after all. >> >> Thanks guys. >> >> >> >> On Mon, Apr 13, 2015 at 2:51 PM, Mark Lee <mark@xxxxxxxxxxxx> wrote: >> >>> On Monday, April 13, 2015 02:28:00 PM Francis Gerund wrote: >>>> When I do: >>>> >>>> file >>>> /run/media/default/USBHD005/New_stuff/Archlinux/ >>> archlinux-2015.04.01-dual.is >>>> o >>>> >>>> I get: >>>> >>>> archlinux-2015.04.01-dual.iso: # ISO 9660 CD-ROM filesystem data >>>> 'ARCH_201504 ' (bootable) >>>> >>>> >>>> >>>> On Mon, Apr 13, 2015 at 2:04 PM, Damjan Georgievski <gdamjan@xxxxxxxxx> >>>> >>>> wrote: >>>>>> :: Triggering uevents . . . >>>>>> >>>>>> ... blk_update request: I/O error, dev sr0, sector 1226572 >>>>>> ... blk_update request: I/O error, dev sr0, sector 1226572 >>>>>> ... Buffer I/O error on dev sr0, logical block 153344, async page >>> read >>>>>> >>>>>> :: Mounting '/dev/disk/by-label/ARCH_201504' ^@ERROR: device did not >>>>>> :: show >>>>>> >>>>>> up after 30 seconds . . . >>>>> >>>>> check the label of the iso, you can do it with "file ...iso" >>>>> >>>>> although the I/O errors suggest the CD is unreadable. >>>>> >>>>> >>>>> -- >>>>> damjan >>> >>> To Damjan, >>> >>> Sounds like a bad burn. Can you try booting via USB? >>> >>> Regards, >>> Mark > Might it be because of the backend? Were you using cdrkit or cdrtools? -- Mauro Santos
