burncd error

Joe Talbott josepht at cstone.net
Thu Jun 14 07:42:01 PDT 2007


On Wed, Jun 13, 2007 at 08:08:13PM -0700, Matthew Dillon wrote:
> 
> :I get the following error when I try to burn a CD with burncd:
> :
> :next writeable LBA 0
> :writing from file /home/josepht/tar-files/Minix-IDE-3.1.2a.iso size
> :417792 KB
> :
> :only wrote -1 of 32768 bytes err=30
> :
> :I believe this is EROFS.  Here's the relevant dmesg lines:
> 
>     Synchronize to the latest HEAD, make sure you do a full build/install
>     of the kernel, world, and also do a make upgrade.   Also note that
>     when burning a CD you have to use the raw CD device (e.g. /dev/acd0,
>     not /dev/acd0c).
> 
>     I had a similar error in an earlier HEAD, and I did fix it.
> 

I sync'ed to HEAD and enabled NATA in the process.  Did a full
build/install kernel, world, and did a make upgrade.  I am now getting
this error:

josepht at tin$ sudo burncd -v  -s 10 -f /dev/acd0 data
~/tar-files/Minix-IDE-3.1.2a.iso 
adding type 0x08 file /home/josepht/tar-files/Minix-IDE-3.1.2a.iso
size 417792 KB 208896 blocks 
next writeable LBA 1424
addr = 1424 size = 427819008 blocks = 208896
writing from file /home/josepht/tar-files/Minix-IDE-3.1.2a.iso size
417792 KB
written this track 1120 KB (0%) total 1120 KB
only wrote -1 of 32768 bytes err=5

The non-zero LBA is due to me trying this command several times on the
same blank disk.  I am assuming that this is not causing the problem
and don't want to waste a bunch of disks testing this out.  If this
could be causing my problem let me know and I'll try a brand new blank
disk.

Here are the relevant lines from dmesg:

atapci0: <Intel ICH7M SATA300 controller> port
0x18b0-0x18bf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 irq 18 at device
31.2 on pci0
ata0: <ATA channel 0> on atapci0
ad1: 76319MB <TOSHIBA MK8032GSX AS112M> at ata0-master SATA150
ata1: <ATA channel 1> on atapci0
acd0: DVDR <PIONEER DVD-RW DVR-K16A/1.63> at ata1-master UDMA33

(my HDD changed from ad0 to ad1 which I assume is from switching to
NATA).

There are no errors in dmesg from the failed burn attempt.

Thanks,
Joe





More information about the Bugs mailing list