nautilus-cd-burner asks for a blank disk when one is in the drive

[Ted Reed]

Trying to burn a data DVD on both DVD-R and DVD+R disks, nautilus-cd-burner
refuses to burn, giving an error message that tells me to insert a blank disk
larger than 4.4GB in size. (The DVD-R/+R are 4.7)

I saw another bug that looked similar, but that's about the fact that ncb
doesn't warn for using the wrong format. I'm pretty sure that my burner supports
both. It should support every dvd-recordable format except dvd-ram and dvd-rw
(but does support dvd+rw). hal-device-manager supports this.

http://bugzilla.gnome.org/show_bug.cgi?id=171486: http://bugzilla.gnome.org/show_bug.cgi?id=171486

[Ted Reed (treed)]

Further investigation:

Burn4Free works fine in windows with the same disk ncb refused, so it's not a
hardware issue.

I tried cdrecord, and it tells me that it doesn't support dvd writing. I thought
this might be the problem, but getting dvd-tools or whatever package has
dvdrecord wasn't any better:

[22:15] [ben:/home/treed]% dvdrecord -dev=/dev/hdd -dao /tmp/image.iso
dvdrtools v0.1.5
[...]
dvdrecord: WARNING: Data may not fit on current disk.
dvdrecord: Notice: Most recorders cannot write CD's >= 90 minutes.
dvdrecord: Notice: Use -ignsize option to allow >= 90 minutes.
dvdrecord: Notice: Use -overburn option to write more than the official disk
capacity.
dvdrecord: Notice: Most CD-writers do overburning only on DAO mode.

So then I tried (the sudo is required otherwise it complains about not being
able to set RR-scheduler or some such):

[22:17] [ben:/home/treed]% sudo dvdrecord -overburn -ignsize -dev=/dev/hdd -dao
/tmp/image.iso
dvdrtools v0.1.5
Portions (c) 2002-2003 Ark Linux <email address hidden>
dvdrtools patched by Julien Delange for Debian
Note that you have to reports bug to the debian maintainer
Please ask Debian for support, and not ask the original author
This program is free software; you can redistribute it and/or modify it under
the terms of the GNU General Public License as published by the Free Software
Foundation; either version 2, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY
WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR
A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with
this program; see the file COPYING. If not, write to the Free Software
Foundation, 59 Temple Place, Suite 330, Boston, MA 02111-1307, USA.
Based on:
Cdrecord 1.11a15 (i386-pc-linux-gnu) Copyright (C) 1995-2001 J\uffffrg Schilling
scsidev: '/dev/hdd'
devname: '/dev/hdd'
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.7'
Device type : Removable CD-ROM
Version : 0
Response Format: 2
Capabilities :
Vendor_info : '_NEC '
Identifikation : 'DVD_RW ND-3500AG'
Revision : '2.16'
Device seems to be: Generic mmc2 DVD.
Using generic SCSI-3/mmc DVD-R(W) driver (mmc_mdvd).
Driver flags : SWABAUDIO BURNFREE
Supported modes: PACKET SAO
dvdrecord: WARNING: Data may not fit on current disk.
dvdrecord: Notice: Overburning active. Trying to write more than the official
disk capacity.
Starting to write CD/DVD at speed 1 in write mode for single session.
Last chance to quit, starting real write in 0 seconds. Operation starts.
trackno=0
dvdrecord: Success. reserve track: scsi sendcmd: no error
CDB: 53 00 00 00 00 00 23 39 66 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 05 00 00 00 00 0A 00 00 00 00 24 00 00 00
Sense Key: 0x5 Illegal Request, Segment 0
Sense Code: 0x24 Qual 0x00 (invalid field in cdb) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 0.000s timeout 200s
dvdrecord: Cannot open new session.

[Sebastien Bacher (seb128)]

Do you use warty or hoary ? Do you know how to rebuild a package ? There is a
./list_cddrives in the build directory to run which is useful to debug such issues.

[Ted Reed (treed)]

I'm using hoary, and yes, I studied to be a DD but never bothered applying.
Which package do I find that in? cdrtools or dvdrtools?

[Sebastien Bacher (seb128)]

nautilus-cd-burner, it's directly in the sources

[Ted Reed (treed)]

[16:02] [ben:/home/treed/code/nautilus-cd-burner-2.10.0]% ./list_cddrives
name: ATAPI DVD-ROM 16XMax device: /dev/hdc max_speed_read: 48
type: CD Drive/DVD Drive
media type: Couldn't open media
media size: -0.00 MiB
CD-Recorder/SCSI devices only: max_speed_write: 0 id: /dev/hdc

name: _NEC DVD_RW ND-3500AG device: /dev/hdd max_speed_read: 48
type: CD Recorder/DVD-RW/DVD+R/DVD+RW/CD Drive/DVD Drive
media type: DVD-R, or DVD-RAM (blank)
media size: 4489.25 MiB
CD-Recorder/SCSI devices only: max_speed_write: 48 id: /dev/hdd

[Sebastien Bacher (seb128)]

what is the size of the iso file to record ?

[Ted Reed (treed)]

-rw-r--r-- 1 treed treed 4.5G 2005-03-22 21:58 /tmp/image.iso

I'm pretty sure that it's incorrectly reading the size of the disk though.
Windows had no issues whatsoever writing a comparably sized iso.

[Ted Reed (treed)]

name: _NEC DVD_RW ND-3500AG device: /dev/hdd max_speed_read: 48
type: CD Recorder/DVD-RW/DVD+R/DVD+RW/CD Drive/DVD Drive
media type: DVD-R, or DVD-RAM (has-data)
media size: 0.00 MiB
CD-Recorder/SCSI devices only: max_speed_write: 48 id: /dev/hdd

That's with the disk I burned under windows in the drive. Seems really odd.

[Sebastien Bacher (seb128)]

thanks for the comments, I've opened a bug upstream with that:
http://bugzilla.gnome.org/show_bug.cgi?id=171486

[Sebastien Bacher (seb128)]

Upstream comment:

"Hardware vendors list media sizes using a decimal (base 10) notation. For
example, a common DVD disc can hold 4.7GB == 4,700,000,000 bytes. In binary
(base 2) units this is 4,700,000,000 / 1024 **3 (approx. 4.4 GiB).

I don't really see anything wrong here."

Maybe you are using a cd overburning with windows ? Can change
"/apps/nautilus-cd-burner/overburn" with gconf-editor and try again ?

[Sebastien Bacher (seb128)]

no reply, bug closed. Feel free to reopen with the asked information if that's
still an issue for you.

[Endolith (endolith)]

Has the error message been changed? If it still says "Insert a blank disk" when it really means "You're trying to burn more than any disk can hold", then that's a legitimate bug. See Bug 160793.

[Sebastien Bacher (seb128)]

the issue described in this bug is a different one, don't reopen a bug only because you have a somewhat similar issue