DVD Burner No Longer Found

DJOtaku · 11-11-2012, 04:30 PM

I'm on Fedora 17. A few days ago I noticed that when I put CDs or DVDs (blank, home made, or commercial) into my drive it would not read them. Thinking that perhaps my DVD burner had bit the dust, I swapped it with another one. I know the new one is working and connected correctly because when I turned on my computer it booted from the disk (I had an old Mythdora disk in there). But when I took out the disc and loaded up the OS, it could no longer be seen. So it's something about Fedora 17 - either a bug or something I somehow accidentally misconfigured.

One last bit of info that might be important: The DVD burner is a PATA drive.

Any ideas? Commands to run? Things to check? udev issues? I did a bit of googling, but nothing I found was helpful to my situation.

Thanks!

jv2112 · 11-12-2012, 04:40 AM

Maybe the controller on the board. Do you have another machine you could test the original dirve on ?

Do you have any spare Sata ports ? Drives are relatively cheap. You could get one for under $20 on Newegg.

DJOtaku · 11-12-2012, 12:59 PM

But if the controller was bad, wouldn't that mean it wouldn't be able to boot from disk?

I probably have a spare sata port as I have 3 drives hooked in and usually computer things are divisible by 2.

But I'd rather not spend money if I don't have to.

jv2112 · 11-13-2012, 04:26 AM

I apologize. I must of read to fast.

Have you tried inserting a disk and mannually mounting the drive ?

Code:

mount /dev/sr0 /whatever/dir/you/want/

slipjack9600 · 11-15-2012, 12:53 PM

I'm having similar problem. Just installed a SATA DVD burner in a fresh home-built computer. Brasero won't recognize when I have a blank disc in the DVD burner. It will load discs with a file system but won't allow me to burn. Tried using Xfburn instead and it says the drive is busy.

Put a brand new SATA cable on it during install, and the motherboard is brand new. I have a DVD-ROM drive that works fine (but is IDE).

Problem is continuous across Knoppix 7.0.4 and Fedora 17. DVD burner is listed in the BIOS startup. Linux does show the drive.

Using Fedora 17 w/ kernel 3.6.6-1.fc17.i686
Drive is listed here (commented to show which drive is which):

Code:

ls /dev | grep sr
sr0  #DVD burner SATA cable
sr1  #DVD-ROM IDE cable

and again here:

Code:

grep -H . /sys/block/*/device/model
/sys/block/sda/device/model:ST3120026A      
/sys/block/sr0/device/model:DVD RW AD-7240S 
/sys/block/sr1/device/model:DVD-ROM GDR8162B

and dmesg returns (truncated):

Code:

dmesg | grep cd
...
...
[    1.340157] sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray
...
[    2.105829] sr1: scsi3-mmc drive: 48x/48x cd/rw xa/form2 cdda tray

Am I missing something?

BTW just installed an IDE DVD burner into another computer on the network and same exact problem under Fedora 17.

slipjack9600 · 11-15-2012, 01:47 PM

Tried opening xfburn as root from the terminal and this is what I get:

Code:

** Message: Ignoring reader 'HL-DT-ST DVD-ROM GDR8162B' at '/dev/sr1'

** (xfburn:2451): WARNING **: There are 1 drives in your system, but none are capable of burning

when xfburn starts a window says:
"Possibly the disc(s) are in use, and cannot get accessed.

Please unmount and restart the application.

If no disc is in the drive, check that you have read and write access to the drive with the current user."

su
umount /dev/sr0
xfburn

Same problem

slipjack9600 · 11-15-2012, 05:09 PM

Still messing with it, no luck so far.

I installed gnomebaker and once it was ready to burn it output this message:

Code:

wodim: No write mode specified.
wodim: Assuming -tao mode.
wodim: Future versions of wodim may have different drive dependent defaults.
wodim: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits.
scsidev: '/dev/sr0'
devname: '/dev/sr0'
scsibus: -2 target: -2 lun: -2
Error trying to open /dev/sr0 exclusively (Device or resource busy)... retrying in 1 second.
Error trying to open /dev/sr0 exclusively (Device or resource busy)... retrying in 1 second.
Error trying to open /dev/sr0 exclusively (Device or resource busy)... retrying in 1 second.
Error trying to open /dev/sr0 exclusively (Device or resource busy)... retrying in 1 second.
Error trying to open /dev/sr0 exclusively (Device or resource busy)... giving up.
TOC Type: 0 = CD-DA
wodim: Device or resource busy. 
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.

Any suggestions welcome. Thanks.

business_kid · 11-16-2012, 02:57 PM

Quote:

cdrecord --scanbus

? You may get a number like

Quote:

4,0,0 400) 'HL-DT-ST' 'DVDRAM GSA-T40L ' 'KC07' Removable CD-ROM

slipjack9600 · 11-17-2012, 12:19 AM

Code:

[root@slipjack luke]# cdrecord --scanbus
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 outputs the same thing, but...

Code:

[root@slipjack luke]# wodim dev=help
Supported SCSI transports for this platform:

Transport name:		sg
Transport descr.:	Generic transport independent SCSI
Transp. layer ind.:	
Target specifier:	bus,target,lun
Target example:		1,2,0
SCSI Bus scanning:	supported
Open via UNIX device:	not supported

Transport name:		ATA
Transport descr.:	ATA Packet specific SCSI transport
Transp. layer ind.:	ATAPI:
Target specifier:	bus,target,lun
Target example:		ATAPI:1,2,0
SCSI Bus scanning:	supported
Open via UNIX device:	not supported

Transport name:		ATA
Transport descr.:	ATA Packet specific SCSI transport using sg interface
Transp. layer ind.:	ATA:
Target specifier:	bus,target,lun
Target example:		1,2,0
SCSI Bus scanning:	supported
Open via UNIX device:	not supported

Transport name:		RSCSI
Transport descr.:	Remote SCSI
Transp. layer ind.:	REMOTE:
Target specifier:	rscsi@host:bus,target,lun
Target example:		REMOTE:rscsi@host:1,2,0
SCSI Bus scanning:	supported
Open via UNIX device:	not supported

Not sure what I'm looking at here. thanks for the response.

business_kid · 11-17-2012, 03:11 AM

Neither am I sure what you are looking at. wodim seems to be cdrecord in disguise. The maintainer of cdrecord is a good (if wrongly opinionated) programmer but a failure in other areas (Notably polite commumnication), so many people fork his code after suggesting improvements.

Wodim takes -scanbus as an option - I have just checked.
wodim -scanbus
then
wodim dev=<3 numbers where your drive is> [OPTIONS] files

slipjack9600 · 11-17-2012, 11:15 AM

wodim -scanbus outputs same thing as cdrecord -scanbus above.

Code:

$ wodim dev=0,0,0 /home/luke/Downloads/precise-5.4.1.iso
wodim: No write mode specified.
wodim: Assuming -tao mode.
wodim: Future versions of wodim may have different drive dependent defaults.
wodim: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits.
WARNING: the deprecated pseudo SCSI syntax found as device specification.
Support for that may cease in the future versions of wodim. For now,
the device will be mapped to a block device file where possible.
Run "wodim --devices" for details.
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.

What I find interesting (if not aggravating) is that gnomebaker reports (above post) wodim output as the drive being busy, while wodim executed through command line returns no such file or directory.

Further, have a look here

Code:

$ wodim -checkdrive
Device was not specified. Trying to find an appropriate drive...
Detected CD-R drive: /dev/sr0
Using /dev/cdrom of unknown capabilities
Device type    : Removable CD-ROM
Version        : 5
Response Format: 2
Capabilities   : 
Vendor_info    : 'Optiarc '
Identification : 'DVD RW AD-7240S '
Revision       : '1.03'
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
Using generic SCSI-3/mmc   CD-R/CD-RW driver (mmc_cdr).
Driver flags   : MMC-3 SWABAUDIO BURNFREE 
Supported modes: TAO PACKET SAO SAO/R96R RAW/R16 RAW/R96P RAW/R96R

Everything is setup as /dev/sr0, including my fstab. Or is /dev/cdrom a generic part of that message? Thanks for helping a n00b.

business_kid · 11-17-2012, 01:39 PM

EDIT Bigtime:

Quote:

Cannot open SCSI driver!

That's a show stopper. Kernel Module missing? Is the cd grabbed already by something?

Quote:

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.

on /dev/sr0, I'd expect scsi, or imitation scsi. You aren't on ancient ide, are you?

slipjack9600 · 11-18-2012, 11:13 AM

No actually it's a fairly new motherboard. Asus p7p55d-e lx. Using SATA set on IDE mode on the first SATA port. Should I try to insmod something?

I do have a DVD-ROM and the hard drive on IDE. I wouldn't think that would conflict, would it?

DJOtaku · 11-18-2012, 08:37 PM

I'm essentially getting the same errors as the guy who's been repying having the same problem as me. Kernel regression in Feodra 17?

slipjack9600 · 11-18-2012, 11:38 PM

I've considered recompiling the kernel, want to save that as a last resort though because everything else works beautifully. If you figure it out please let me know and I'll do the same. Sorry if I hijacked your thread.

Edit:
Is it recommended to use the drive in AHCI mode vs. IDE mode? Support from AHCI has been available since kernel 2.6.19, I'm using 3.6.6-1. And according to dmesg the module is already loaded:

Code:

dmesg | grep ahci
[    0.704093] ahci 0000:03:00.0: version 3.0
[    0.704120] ahci 0000:03:00.0: JMB361 has only one port
[    0.704165] ahci 0000:03:00.0: AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
[    0.704167] ahci 0000:03:00.0: flags: 64bit ncq pm led clo pmp pio slum part 
[    0.704275] scsi0 : ahci