LinuxQuestions.org - 'Error trying to open /dev/scd0 exclusively' in RH9 cdrecord

- Linux - Software (https://www.linuxquestions.org/questions/linux-software-2/)

- - 'Error trying to open /dev/scd0 exclusively' in RH9 cdrecord - help? (https://www.linuxquestions.org/questions/linux-software-2/error-trying-to-open-dev-scd0-exclusively-in-rh9-cdrecord-help-81191/)

'Error trying to open /dev/scd0 exclusively' in RH9 cdrecord - help?

Lo all.

Can''t find any help about this at all, but it seems to have happened to other people.

Just recently installed RH9 and got all the updates I needed. When I try making a cd using cdrecord (i.e., xroast or gnometoaster) I get an error saying:

"Error trying to open /dev/scd0 exclusively... will retry in 1 second"

Eventually it just ends with "...bailing out..."

This happens regardless of whether I'm root or not and I have no clue what the problem is. Don't mind editing anything, I just don't know which things I need to change.

Any required info, I'll put it up ASAP.

Thanks very much.

Thom

Its because you have mounted the drive
try unmounting it

umount /mnt/cdrom

this should work.
otherwise try running as root
also check if you are using the correct device

try cdrecord -scanbus

you should get a list where the name of your cd-writer will be listed followed by 3 numbers
for me its 0,0,0

so then when running cdrecord
use
cdrecord dev=0,0,0

tmadhavan>seems to have happened to other people.
Speaking as one of the 'other people' I have exactly the same problem as you. I find that Gnome's Go/CD Creator works almost as well as 'doze's right-click/send to/CDROM, but only when there's a blank CD in the drive, otherwise I get the old "...bailing out...". Using 650MB of storage to copy 1kB of file is a bit wasteful when I have to use a new disc each time...

Remember siedren, you are speaking to newbies here so if your method, which didn't work for me (it didn't give an error but it also didn't write the files to a non-blank CD), needs me to first click redhat/preferences/cd properties and change things in there, then you had better specify that. Same with changes to /etc/XF86Config .

ps. I am also having problems writing to my floppy. Once again it goes through the motions but if I transfer the floppy to a 'doze box the files aren't there. Also, Nautilus claims to be 'unable to unmount the volume' 15 minutes after it claimed that it had finished copying files there because 'the device is busy'. I know its only an AMD 1800+...

(This is for tmadhavan) I also use the xcdroast and gnome-toaster... in gui... when u use it and insert a blank cd... the guid generally automatically mounts the cd to the system... and when u try to write to a mounted cdrom using xcdroast or gnome-toaster... it requires an unmounted cdrom... to write... this is the reason why u gett retrying in 1 second and bails out after 10 seconds...

(This is for verstapp) regarding writing to floppy the floppy is not automounted in gui... it has to be mounted and then only can u write to it....so mount it first and then try to write a file to it....

hitesh>and then try to write a file to it...
try to write to it?!
It sounds as if you are having almost as much trouble as I am.
Just tried again -
insert disk
right-click on desktop
hover over Disks menu item, click on Floppy
Floppy icon appears on desktop
right-click on it, click Open
'floppy' window opens
right-click copy file in home window, right-click paste file in 'floppy' window
drive light goes on for a second
right-click on 'floppy' icon, eject, 'device is busy'
right-click on desktop, disks, floppy, 'device is busy'
take floppy out of drive anyway, move to 'doze machine. Needless to say the file hasn't been copied to it.

Please point out to me the thing that I am doing incorrectly.

Sorry for five posts. The server was having problems keeping up - the administrators have decided that you can only post once every 22 seconds - and I'm afraid I hit the Send button more often than I should have. A Delete button next to the Edit and Quote buttons would have solved my problem.

If you are having trouble using your cd-writer, I stronly suggest that you give K3B a try !!! K3B is the best.

Anyway.... as you said....

Quote:

I find that Gnome's Go/CD Creator works almost as well as 'doze's right-click/send to/CDROM, but only when there's a blank CD in the drive, otherwise I get the old "...bailing out..."

This is common sense. If you have a cd in which you cannot write to then obviously you wont be able to write to it. You should insert a cd which is either fully blank, or one which can be appended to (multi session cd). Read the cdwriting howto at tldp for more info.

To use cdrecord, your cd should not be mounted. When you insert a cd, a program called autorun which runs in the background checks the drive and mounts it, if it can. Therefore even if a cd is multisession it will be mounted and you will not be able to write to it.

To solve this issue, I usually kill autorun, before I do any cd-writing business OR you can unmount your cd and then start writing.

To Kill Autorun:
The command 'ps ex' should list all the programs that are running. Get the process id and then enter the command 'kill <processid>'

All the cd-writing front-ends in linux use cdrecord or cdrdao as their backend. So this information applies to all of them.

About the floppy problem. I use mtools (mcopy, mdir etc...) I dont use the floppy very much so I am satisfied with the command line tools. Take a look at mtools. Its very easy. Works just like the dos commands but with an 'm' in from of it.

Happy burning !!!

this is for verstapp>
for mounting the flopppy in gui you have to right click on the desktop then clik on the disks there you wil find floppy... then whne u get the icon of floppy you have toi right clik on the icon and clik on mount to mount the floppy... after mounting it you can copy the files quite as normally ... after copying don't eject the floppy (manually)... just close all the window which are using the floppy drive and then right clik on the floppy icon on the desktop and clik on umount.... thereby copying the things on to the floppy.. to checkthat it has been copied... just mount the floppy again...

hello im allso having a problem with the cdrecord command i have created a directory in which to store my wav files iv became root user and typed cdrecord -v dev=0,0,0 -audio *.wav the feedback i get from typing this is as followsCdrecord 2.0 (i686-pc-linux-gnu) Copyright (C) 1995-2002 J?rg Schilling
TOC Type: 0 = CD-DA
scsidev: '0,0,0'
scsibus: 0 target: 0 lun: 0
Linux sg driver version: 3.1.24
Using libscg version 'schily-0.7'
cdrecord: Warning: using inofficial libscg transport code version (schily - Red
Hat-scsi-linux-sg.c-1.75-RH '@(#)scsi-linux-sg.c 1.75 02/10/21 Copyright
1997 J. Schilling').
atapi: 1
Device type : Removable CD-ROM
Version : 0
Response Format: 1
Vendor_info : 'ATAPI '
Identifikation : 'CD-RW 52XMax '
Revision : '150D'
Device seems to be: Generic mmc CD-RW.
Using generic SCSI-3/mmc CD-R driver (mmc_cdr).
Driver flags : MMC-3 SWABAUDIO BURNFREE
Supported modes: TAO PACKET SAO RAW/R96R
Drive buf size : 1658880 = 1620 KB
FIFO size : 4194304 = 4096 KB
cdrecord: Bad audio track size 35407872 for track 01.
cdrecord: Audio tracks must be at least 705600 bytes and a multiple of 2352.
cdrecord: See -pad option.
i would appreciate any help

The error message explains it all. The audio track should be a multiple of 2352 bytes and one or more of the audio files you want to burn is not. So you have to add the option -pad to the command and cdrecord will add zeros to the end of the audio file so that it becomes a mutliple of 2352 bytes. This will not affect the audio at all, except increase the length by about less than a second.

Just append -pad to the command and everything should work fine

seidren i can not thank you enough it worked im now in full flow recording cds for every one thanks

Some more tips for your audio cd recording experience.

Try using normalize. It is a program that will change the volume level of the audio files so that they all sound at the same volume. This is very useful when burning cd with music files from different albums and they have totally different volume levels.

Also try using k3b. I think it is the best cd burning front end ever created.

helo iv used cdrecord command succesfully lots of times now but recently iv not been able to i keep getting this error [root@master wav]# cdrecord -pad dev=0,0,0 -audio *.wav
Cdrecord 2.0 (i686-pc-linux-gnu) Copyright (C) 1995-2002 J?rg Schilling
scsidev: '0,0,0'
scsibus: 0 target: 0 lun: 0
Linux sg driver version: 3.1.24
Using libscg version 'schily-0.7'
Device type : Removable CD-ROM
Version : 0
Response Format: 1
Vendor_info : 'ATAPI '
Identifikation : 'CD-RW 52XMax '
Revision : '150D'
Device seems to be: Generic mmc CD-RW.
Using generic SCSI-3/mmc CD-R driver (mmc_cdr).
Driver flags : MMC-3 SWABAUDIO BURNFREE
Supported modes: TAO PACKET SAO RAW/R96R
cdrecord: Input/output error. start/stop unit: scsi sendcmd: no error
CDB: 1B 00 00 00 01 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 15.774s timeout 40s
cdrecord: Drive needs to reload the media to return to proper status.
Starting to write CD/DVD at speed 52 in real TAO mode for single session.
Last chance to quit, starting real write 0 seconds. Operation starts.
cdrecord: Input/output error. read track info: scsi sendcmd: no error
CDB: 52 01 00 00 00 FF 00 00 1C 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 240s

i would appreciate any help on this matter thank you

I think there is something wrong with the tracks you have provided. Probably they are not in the correct format or not in the directory. Check for permissions also.

Also try reducing the speed to something like 16x or 8x (probably because your cd doesnt support high speed writing)

hello its me again master thats a joke aint it ok what i have done now is iv checked the permisions they are fine now i typed "cdrecord -pad speed=24 dev=0,0,0 -audio *.wav
you will notice this time i have told it what speed to use, the error message i get still seems to be the same [root@master wav]# cdrecord -pad speed=24 dev=0,0,0 -audio *.wav
Cdrecord 2.0 (i686-pc-linux-gnu) Copyright (C) 1995-2002 J?rg Schilling
scsidev: '0,0,0'
scsibus: 0 target: 0 lun: 0
Linux sg driver version: 3.1.24
Using libscg version 'schily-0.7'
Device type : Removable CD-ROM
Version : 0
Response Format: 1
Vendor_info : 'ATAPI '
Identifikation : 'CD-RW 52XMax '
Revision : '150D'
Device seems to be: Generic mmc CD-RW.
Using generic SCSI-3/mmc CD-R driver (mmc_cdr).
Driver flags : MMC-3 SWABAUDIO BURNFREE
Supported modes: TAO PACKET SAO RAW/R96R
cdrecord: Drive needs to reload the media to return to proper status.
Starting to write CD/DVD at speed 52 in real TAO mode for single session.
Last chance to quit, starting real write 0 seconds. Operation starts.
cdrecord: Input/output error. read track info: scsi sendcmd: no error
CDB: 52 01 00 00 00 FF 00 00 1C 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 240s
[root@master wav]#
now why is it that if you look at the feedback it says Starting to write CD/DVD at speed 52
if iv told it to use 24 im just stabing in the dark any more help appreciated thanks for your help seidren

oops sorry thought i would just say i did check they were all in the wav format

GOD!!! This is really weird. (I wasnt joking ;))
The only final reason I can come up with for this to happen is that the cd is screwed up. Try a new cd if you can. (Are you using a CD-RW?)

I also noticed this

Quote:

cdrecord: Drive needs to reload the media to return to proper status.

Only put the cd in just before you run cdrecord.

Also check if you are running the program Autorun.
Do a

Code:

ps -A x

then from the output find the pid of Autorun, and kill it.

Code:

kill -9 <pid>

Then run cdrecord.

If you still get the problem. I would gladly suggest you to give a try with K3B.
Its the best cdwriting frontend ever.

Let me know of your progress

hello me again ok i opend a terminal and typed
ps -A x
the feedback i got was
ps -A x
PID TTY STAT TIME COMMAND
1 ? S 0:04 init
2 ? SW 0:00 [keventd]
3 ? SW 0:00 [kapmd]
4 ? SWN 0:00 [ksoftirqd_CPU0]
9 ? SW 0:00 [bdflush]
5 ? SW 0:00 [kswapd]
6 ? SW 0:00 [kscand/DMA]
7 ? SW 0:02 [kscand/Normal]
8 ? SW 0:00 [kscand/HighMem]
10 ? SW 0:00 [kupdated]
11 ? SW 0:00 [mdrecoveryd]
15 ? SW 0:00 [kjournald]
72 ? SW 0:00 [khubd]
776 ? SW 0:00 [kjournald]
1181 ? S 0:00 /sbin/dhclient -1 -q -lf /var/lib/dhcp/dhclient-eth0.leases -pf /var/run/dh
1259 ? S 0:05 syslogd -m 0
1263 ? S 0:02 klogd -x
1281 ? SW 0:00 [portmap]
1316 ? S 0:00 /usr/sbin/apmd -p 10 -w 5 -W -P /etc/sysconfig/apm-scripts/apmscript
1354 ? S 0:00 /usr/sbin/snmpd -s -l /dev/null -P /var/run/snmpd -a
1363 ? R 0:03 /usr/sbin/snmptrapd -s -u /var/run/snmptrapd.pid
1388 ? S 0:00 [TUX date]
1389 ? SW 0:00 [TUX logger]
1390 ? S 0:00 [TUX manager]
1391 ? S 0:00 [TUX worker 0]
1392 ? S 0:00 [async IO 0/1]
1393 ? S 0:00 [async IO 0/2]
1394 ? S 0:00 [async IO 0/3]
1395 ? S 0:00 [async IO 0/4]
1396 ? S 0:00 [async IO 0/5]
1397 ? S 0:00 [async IO 0/6]
1398 ? S 0:00 [async IO 0/7]
1399 ? S 0:00 [async IO 0/8]
1400 ? S 0:00 [async IO 0/9]
1401 ? S 0:00 [async IO 0/10]
1402 ? S 0:00 [async IO 0/11]
1403 ? S 0:00 [async IO 0/12]
1404 ? S 0:00 [async IO 0/13]
1405 ? S 0:00 [async IO 0/14]
1406 ? S 0:00 [async IO 0/15]
1407 ? S 0:00 [async IO 0/16]
1408 ? S 0:00 [async IO 0/17]
1409 ? S 0:00 [async IO 0/18]
1410 ? S 0:00 [async IO 0/19]
1411 ? S 0:00 [async IO 0/20]
1412 ? S 0:00 [async IO 0/21]
1413 ? S 0:00 [async IO 0/22]
1414 ? S 0:00 [async IO 0/23]
1415 ? S 0:00 [async IO 0/24]
1416 ? S 0:00 [async IO 0/25]
1417 ? S 0:00 [async IO 0/26]
1418 ? S 0:00 [async IO 0/27]
1419 ? S 0:00 [async IO 0/28]
1420 ? S 0:00 [async IO 0/29]
1421 ? S 0:00 [async IO 0/30]
1422 ? S 0:00 [async IO 0/31]
1423 ? S 0:00 [async IO 0/32]
1436 ? S 0:00 xinetd -stayalive -pidfile /var/run/xinetd.pid
1455 ? S 0:00 [sendmail]
1464 ? S 0:00 [sendmail]
1474 ? S 0:00 /usr/bin/spamd -d -c -a
1483 ? S 0:00 gpm -t ps/2 -m /dev/psaux
1502 ? S 0:00 crond
1513 ? S 0:00 cupsd
1543 ? S 0:00 /usr/bin/perl /usr/lib/cups/filter/cupsomatic 1 master (stdin) 1 cpi=12 lpi
1544 ? R 0:03 parallel:/dev/lp0 1 master (stdin) 1 cpi=12 lpi=7 page-bottom=36 page-left=
1558 ? S 0:00 sh -c gs '-dPARANOIDSAFER' '-dBATCH' '-dNOPAUSE' '-sOutputFile=/dev/fd/3' '
1560 ? S 0:00 gs -dPARANOIDSAFER -dBATCH -dNOPAUSE -sOutputFile=/dev/fd/3 -sDEVICE=omni -
1574 ? S 0:03 [xfs]
1583 ? S 0:00 /usr/bin/lisa --config=/etc/lisarc
1601 ? S 0:00 [atd]
1627 ? S 0:00 /usr/sbin/saslauthd -m /var/run/saslauthd/mux -a shadow
1641 ? S 0:00 rhnsd --interval 240
1656 tty1 S 0:00 /sbin/mingetty tty1
1657 tty2 S 0:00 /sbin/mingetty tty2
1658 tty3 S 0:00 /sbin/mingetty tty3
1659 tty4 S 0:00 /sbin/mingetty tty4
1660 tty5 S 0:00 /sbin/mingetty tty5
1661 tty6 S 0:00 /sbin/mingetty tty6
1662 ? SW 0:00 [gdm-binary]
1705 ? S 0:00 [gdm-binary]
1816 ? S 0:00 oafd --ac-activate --ior-output-fd=10
2173 ? R 2:05 /usr/X11R6/bin/X :0 -auth /var/gdm/:0.Xauth vt7
2182 ? S 0:00 /bin/sh /usr/bin/startkde
2225 ? S 0:00 /usr/bin/ssh-agent /usr/share/apps/switchdesk/Xclients.kde
2267 ? S 0:00 kdeinit: Running...
2270 ? S 0:00 kdeinit: dcopserver --nosid
2273 ? S 0:00 kdeinit: klauncher
2275 ? S 0:01 kdeinit: kded
2289 ? R 0:04 /usr/bin/artsd -F 10 -S 4096 -s 60 -m artsmessage -l 3 -f
2291 ? S 0:00 kdeinit: knotify
2292 ? S 0:00 kwrapper ksmserver
2294 ? S 0:00 kdeinit: ksmserver
2295 ? S 0:06 kdeinit: kwin -session 117f000001000107625475400000176840000_1081715985_454
2297 ? R 0:04 kdeinit: kdesktop
2299 ? S 0:10 kdeinit: kicker
2301 ? S 0:03 /usr/bin/autorun -l --interval=1000 --cdplayer=/usr/bin/kscd
2305 ? S 0:00 kdeinit: kwrited
2306 ? S 0:00 /usr/bin/pam-panel-icon --sm-client-id 117f00000100010762547600000017684000
2307 ? S 0:00 [pam_timestamp_c]
2308 ? S 0:00 gnomecc-single-shell --sm-config-prefix /gnomecc-single-shell-VtBuQk/ --sm-
2310 ? S 0:00 gnome-name-service
2313 ? S 0:02 kdeinit: kmix -session 117f000001000107675426400000179440015_1081715984_520
2314 ? S 0:00 nspluginviewer -session 117f000001000107921125700000037710025_1081715984_72
2322 ? S 0:00 kalarmd --login
2548 ? S 0:00 kdeinit: kio_file file /tmp/ksocket-master/klauncherv2nepa.slave-socket /tm
2551 ? S 0:00 kdeinit: kio_uiserver
2961 ? S 0:00 wombat --oaf-activate-iid=OAFIID:Bonobo_Moniker_wombat_Factory --oaf-ior-fd
2970 ? S 0:00 bonobo-moniker-xmldb --oaf-activate-iid=OAFIID:Bonobo_Moniker_xmldb_Factory
3017 ? S 0:00 evolution-alarm-notify --oaf-activate-iid=OAFIID:GNOME_Evolution_Calendar_A
3408 ? S 0:01 kdeinit: konsole
3409 pts/1 S 0:00 /bin/bash
3473 ? S 0:15 /usr/lib/mozilla-1.4.2/mozilla-bin -UILocale en-US
3508 ? S 0:00 esd -terminate -nobeeps -as 2 -spawnfd 30
3539 pts/1 R 0:00 ps -A x
now i can only see the 1 autorun there on line 2301 so i then typed
kill -2301 <pid>
the feed back was
ash: syntax error near unexpected token `newline'
allso im using cdr not w ihave tried using a different cd but i get the same error

no no you are supposed to type...

kill -9 2301

-9 is the signal and 2301 is the process id.