LinuxQuestions.org - cannot erase a cd (or get the burner working)

- Linux - Hardware (https://www.linuxquestions.org/questions/linux-hardware-18/)

- - cannot erase a cd (or get the burner working) - ubuntu (https://www.linuxquestions.org/questions/linux-hardware-18/cannot-erase-a-cd-or-get-the-burner-working-ubuntu-567676/)

cannot erase a cd (or get the burner working) - ubuntu

Hello,

I am trying to get my cdburner working. Its a Freecom model and connected as the secondary IDE slave after my DVD ROM.

Currently the various GNOME burning utilities reveal it as:-

_NEC NR-7700A

at

/dev/hdd (the DVD rom is on hdc).

Im running Ubuntu 7.04 - 2.6.20-16-generic

DMESG shows:-

Code:

dmesg | grep hdd

[  53.159629]    ide1: BM-DMA at 0xfc08-0xfc0f, BIOS settings: hdc: DMA, hdd: DMA

[  61.086769] hdd: _NEC NR-7700A, ATAPI CD/DVD-ROM drive

[  61.282684] hdd: ATAPI 32X CD-ROM CD-R/RW drive, 2048kB Cache, UDMA(33)

Both the GUI tools and CDRECORD all give errors along the lines of the following when I try to blank a cd or do anything like :-

Code:

cdrecord -v -force blank=fast dev=/dev/hdd

Code:

TOC Type: 1 = CD-ROM

scsidev: '/dev/hdd'

devname: '/dev/hdd'

scsibus: -2 target: -2 lun: -2

Error trying to open /dev/hdd exclusively (Device or resource busy)... retrying in 1 second.

Error trying to open /dev/hdd exclusively (Device or resource busy)... retrying in 1 second.

Error trying to open /dev/hdd exclusively (Device or resource busy)... retrying in 1 second.

Error trying to open /dev/hdd exclusively (Device or resource busy)... retrying in 1 second.

Error trying to open /dev/hdd exclusively (Device or resource busy)... giving up.

scsidev: 'ATA:/dev/hdd'

devname: 'ATA:/dev/hdd'

scsibus: -2 target: -2 lun: -2

wodim: No such file or directory. 

Cannot open SCSI driver!

For possible targets try 'wodim --devices' or 'wodim -scanbus'.

For possible transport specifiers try 'wodim dev=help'.

For IDE/ATAPI devices configuration, see the file README.ATAPI.setup from

the wodim documentation.

wodim --devices gave me the following:-

Code:

Beginning native device scan. This may take a while if devices are busy...

Error trying to open /dev/hdc exclusively (Device or resource busy)... retrying in 1 second.

Error trying to open /dev/hdc exclusively (Device or resource busy)... retrying in 1 second.

Error trying to open /dev/hdc exclusively (Device or resource busy)... retrying in 1 second.

Error trying to open /dev/hdc exclusively (Device or resource busy)... retrying in 1 second.

Error trying to open /dev/hdc exclusively (Device or resource busy)... giving up.

Error trying to open /dev/hdd exclusively (Device or resource busy)... retrying in 1 second.

Error trying to open /dev/hdd exclusively (Device or resource busy)... retrying in 1 second.

Error trying to open /dev/hdd exclusively (Device or resource busy)... retrying in 1 second.

Error trying to open /dev/hdd exclusively (Device or resource busy)... retrying in 1 second.

Error trying to open /dev/hdd exclusively (Device or resource busy)... giving up.

wodim: Overview of accessible drives (0 found) :

I googled a bit and tried using cdrecord - for example a guide at this address suggested the following approach:-

http://www.michaelminn.com/?linux/command_line.html

cdrecord -v -force blank=fast dev=0,0,0

I tried this and also tried giving it /dev/hdd as an address but the errors still remain the same.

Can anyone advise me about this ...

Many Thanks.

Max.

cdrecord has the switch (can't remember what it is, but --help should tell it, or the manpage) that makes it search & display the available drives that it can use for burning. Run that first, see if it shows your hdd (or equivalent). If it does display for example hdd then make sure the disc is not mounted and that you have privileges to use the device.

I assume you already tried that as root, though.

Are you sure it's still an hd? Most distros on 2.6.20+ kernels refer to optical drives as scd nowadays.

I think the switch b0uncer is referring to is -scanbus. I think you device switch needs the ATAPI option, lik this:

dev=ATAPI:0,0,0

If yours is hdc it might be 0,1,0 indicating the secondary master, but scanbus will tell you what it is.

You can also try to force a generic driver. Mine works best with

driver=generic-mmc

Quote:

dmesg | grep hdd
[ 53.159629] ide1: BM-DMA at 0xfc08-0xfc0f, BIOS settings: hdc: DMA, hdd: DMA
[ 61.086769] hdd: _NEC NR-7700A, ATAPI CD/DVD-ROM drive
[ 61.282684] hdd: ATAPI 32X CD-ROM CD-R/RW drive, 2048kB Cache, UDMA(33)

Were the drives really both assigned to hdd?

Hmmmm, well the utilities like gnomebaker and commandline apps like 'mount' all say that it's on /dev/hdd ... ? Could it be somewhere else despite this?

Something else I considered was that maybe I should make the cd burner the Secondary Master rather than the slave ... This may make it /dev/hdc which might sort the problem out. It's a bit of a crappy approach to the problem but worth a try I suppose...

Whatever the case I will and check out what is on sdc just to be sure (this will have to be tomorrow now im afraid as im working nights this week :( )

Bouncer, I will try the cdrecord switch option too and see if I have any luck...

Will try and post back in a day or two ...

CD burner problem hacked with umount

Quote:

Originally Posted by maxvonseibold (Post 2816611)

utilities like gnomebaker ...

I suspect you are dealing with a similar scenario that generated the same message for me:

"Error trying to open /dev/hdc exclusively (Device or resource busy)... retrying in 1 second."

while I was attempting to use Gnomebaker.

My solution/hack follows:

start Gnomebaker
Open terminal as root

umount /dev/hdc

go back to Gnomebaker, select tools > then copy DVD

Copy / burn functions worked fine afterwards until I loaded a different CD / DVD to copy, then I repeated the above umount command with success.

I'd appreciate it if someone was to enlighten me on the exact details of why this works for me, and how to get beyond this hack to smooth functionality.

Thanks.