Problem burning/mounting discs, ruled out hardware issue
SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Problem burning/mounting discs, ruled out hardware issue
This is a problem that I've known about for a while, but since I don't burn cds that often I haven't worried about it. But I need to do a lot of burning soon, so I want to try to resolve this.
When I try to burn a disc, it goes through the motions - says its burning, has an xfer rate, says Burning Complete when its finished. The disc even has the visible circle where data was written.
But the disc is unusable after burning. If I tell it to Verify Data after burning (I use K3B), the software just freezes when it begins the verification. Inserting the disc and trying to read it just results in a lot of bad sounds from the cd tray, with the disc speeding up and slowing down.
I can write discs from Windows on virtual box using the same drive, so I know it isn't a problem with the drive itself. I think most likely its a problem with my fstab:
dev=/dev/sr0 - for the first optical drive
fs=32M - set a (high!) fifo buffer size of 32MiB
-v - verbose output
-eject - take a guess what that does
I can write discs from Windows on virtual box using the same drive
Considering the above is true, this appears to be a simple software/options problem. I'm using K3B Version 2.0.80, with cdrecord Cdrecord-ProDVD-ProBD-Clone 3.01a02, on 32bit, and 64bit, with SATA and PATA recorders.
There are known issues with some chipsets and libata. Plus some weird issues certain optical drives and Linux.
For completeness and to help the search engines -
Optical Drive Model, and is it PATA or SATA?
Last edited by disturbed1; 10-17-2011 at 11:26 AM.
I've never had this issue myself but it does help to create a group "burning" just to be safe and then add your users to the group as needed. K3b seems to be very picky about this.
For most isos I usually just have it burn them using the default settings but on the lowest possible speeds (usually 4x/6x/8x if supported) due to the fact some disks can handle high speed burns but often not due to hardware being a variable in quality.
I often will click Verify Writes and let it run and it runs without issue. Low speed burning is probably your best bet here.
Also if you burn a CD/DVD for storage purposes use the default Linux+Windows option for burning method so it writes as a normal data disk.
Stock Xfce? Or Robby's Xfce 4.8.x?
Some people have some issues with Xfce 4.8.x, depending on if they're using startx from init 3, or a different DM besides KDM. Seems the problem has to do with the way policy-kit/udisks/something is initialized.
Starting Xfce from KDM has never showed an issue here.
Did you ever try cdrecord from the command line? Did it work?
I couldn't get a disc to mount to copy an image but I downloaded Puppy Linux and tried to burn it.
Command and output were:
sh-4.1$ cdrecord dev=/dev/sr0 fs=32M -v -eject lupu-528.iso
cdrecord: No write mode specified.
cdrecord: Assuming -sao mode.
cdrecord: If your drive does not accept -sao, try -tao.
cdrecord: Future versions of cdrecord may have different drive dependent defaults.
Cdrecord-ProDVD-ProBD-Clone 3.01a02 (x86_64-unknown-linux-gnu) Copyright (C) 1995-2010 Joerg Schilling
TOC Type: 1 = CD-ROM
scsibus: -2 target: -2 lun: -2
Warning: Open by 'devname' is unintentional and not supported.
Linux sg driver version: 3.5.27
Using libscg version 'schily-0.9'.
SCSI buffer size: 64512
Device type : Removable CD-ROM
Version : 5
Response Format: 2
Vendor_info : 'HL-DT-ST'
Identifikation : 'DVDRAM GT30N '
Revision : 'AS02'
Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM.
Profile: DVD-R/DL layer jump recording
Profile: DVD-R/DL sequential recording
Profile: DVD-RW sequential recording
Profile: DVD-RW restricted overwrite
Profile: DVD-R sequential recording
Profile: CD-R (current)
Profile: Removable Disk
Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr).
Driver flags : MMC-3 SWABAUDIO BURNFREE
Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R LAYER_JUMP
Drive buf size : 327680 = 320 KB
cdrecord: Warning: Cannot read drive buffer.
cdrecord: Warning: The DMA speed test has been skipped.
FIFO size : 33554432 = 32768 KB
Track 01: data 129 MB
Total size: 148 MB (14:41.94) = 66146 sectors
Lout start: 148 MB (14:43/71) = 66146 sectors
Current Secsize: 2048
ATIP info from disk:
Indicated writing power: 5
Disk Is not unrestricted
Disk Is not erasable
Disk sub type: Medium Type A, high Beta category (A+) (3)
ATIP start of lead in: -11634 (97:26/66)
ATIP start of lead out: 359846 (79:59/71)
Disk type: Short strategy type (Phthalocyanine or similar)
Manuf. index: 3
Manufacturer: CMC Magnetics Corporation
Capacity Blklen/Sparesz. Format-type Type
359846 2048 0x00 Unformated or Blank Media
Blocks total: 359846 Blocks current: 359846 Blocks remaining: 293700
Starting to write CD/DVD/BD at speed 24 in real SAO mode for single session.
Last chance to quit, starting real write 0 seconds. Operation starts.
Waiting for reader process to fill input buffer ... input buffer ready.
BURN-Free is ON.
Turning BURN-Free off
Sending CUE sheet...
cdrecord: WARNING: Drive returns wrong startsec (0) using -150
Writing pregap for track 1 at -150
Starting new track at sector: 0
Track 01: 129 of 129 MB written (fifo 100%) [buf 71%] 15.3x.
Track 01: Total bytes read/written: 135467008/135467008 (66146 sectors).
Writing time: 92.692s
Average write speed 9.5x.
Min drive buffer fill was 68%
Fixating time: 6.357s
cdrecord: fifo had 2134 puts and 2134 gets.
cdrecord: fifo was 0 times empty and 1602 times full, min fill was 99%.
Same result with this burn. Disk written but unusable.
We see far too many people having problems with RITEK, CMC, RICOH media etc and I can assure you that it isn't just fluke when we suggest the user give Verbatims a try and their issues magically disappear!