Pioneer DVR-109 does not recognize recordable DVDs

juicy-one · 07-16-2006, 06:32 PM

Hi everyone!

After two full days of endless internet searching to try and solve this problem I am starting to get desperate and thought I would try posting a question.

After some recent problems with the windows 2000 OS on my machine I switched over to linux, installing the Debian distribution (kernel 2.4.27-2-386). Everything is great except I can't burn DVDs (I can read them no problem).

The DVD burner is a Pioneer DVR-109, and when I run growisofs -Z /dev/hdc -R -J /files I get the error message: ":-( /dev/hdc: media is not recognized as recordable DVD: 0" regardless of whether the drive is empty or contains a recordable DVD. I have tried a number of different brands of media, all of which worked fine with windows, but none of which work now. The funny thing is the drive doesn't even seem to spin them before deciding they're no good. I also tried installing cdrecord-ProDVD and that gives a similar error message.

Trying to find a solution, the first thing I came across was in some documentation for the DVD+RW-tools which told me to route the IDE drive through ide-scsi emulation, which I did, but still no joy. (I switched it off again afterwards to go back to using /dev/hdc instead of /dev/scd0)

I then found out that the drive's firmware needed to be upgraded from 1.40, so I flashed it with version 1.58. The drive is still reading DVDs after the firmware upgrade, but still won't burn.

Then I came across a post about using hdparm to check/change settings for the drive. I switched on 32-bit IO support, and unmaskirq, and switched off the readonly flag. Still getting the same error message though!? Tried again with the ide-scsi emulation but it didn't help.

Here is the output of hdparm /dev/hdc:
/dev/hdc:
IO_support = 1 (32-bit)
unmaskirq = 1 (on)
using_dma = 1 (on)
keepsettings = 1 (on)
readonly = 0 (off)
readahead = 8 (on)
HDIO_GETGEO failed: Invalid argument

Not sure what the error message is about, but I gather some people have their drives working while still getting it. BTW I also tried changing the readahead to 256 but it wouldn't accept the change.

Here is the output of hdparm -i /dev/hdc:
/dev/hdc:

Model=PIONEER DVD-RW DVR-109, FwRev=1.58, SerialNo=
Config={ Fixed Removeable DTR<=5Mbs DTR>10Mbs nonMagnetic }
RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0
BuffType=13395, BuffSize=64kB, MaxMultSect=0
(maybe): CurCHS=0/0/0, CurSects=0, LBA=yes, LBAsects=0
IORDY=on/off, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 *udma2
AdvancedPM=no
Drive conforms to: device does not report version:

* signifies the current active mode

Has anyone got any suggestions for something to try here?? PLEASE?

Tom.

Bruce Hill · 07-17-2006, 04:40 AM

Same drive works fine here:

Code:

root@silas:~# hdparm -i /dev/hda

/dev/hda:

 Model=PIONEER DVD-RW DVR-109, FwRev=1.17, SerialNo=
 Config={ Fixed Removeable DTR<=5Mbs DTR>10Mbs nonMagnetic }
 RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0
 BuffType=13395, BuffSize=64kB, MaxMultSect=0
 (maybe): CurCHS=0/0/0, CurSects=0, LBA=yes, LBAsects=0
 IORDY=on/off, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120}
 PIO modes:  pio0 pio1 pio2 pio3 pio4
 DMA modes:  mdma0 mdma1 mdma2
 UDMA modes: udma0 udma1 udma2 udma3 *udma4
 AdvancedPM=no
 Drive conforms to: device does not report version:

 * signifies the current active mode

But it's never been run with a 2.4 kernel:

Code:

mingdao@silas:~$ uname -a
Linux silas 2.6.17.4 #2 PREEMPT Sat Jul 8 08:04:29 CST 2006 i686 athlon-4 i386 GNU/Linux

This is the command I use to burn .iso images to the drive:

Code:

To burn an iso to DVD

growisofs -dvd-compat -Z /dev/hda=image.iso

juicy-one · 07-17-2006, 06:54 PM

Thanks Chinaman.

I guess I will try upgrading to a 2.6 kernel when I have a bit of time then (I presume it's a fairly lengthy process if you've never done it before??).

Do you reckon it's likely to fix the problem with recognizing media though?

Bruce Hill · 07-17-2006, 08:14 PM

Tom,

Forgive me, but I forgot Welcome to LQ!

For the 2.4 kernel you need to run that drive as a generic SCSI device. But you know, it is NOT a SCSI device, it's an ATAPI-IDE drive.

The problem arose when Jörg Schilling, the developer of cdrecord, decided he wasn't going to change with the Linux kernel. Linus Torvalds decided that 'generic scsi' was just plain wrong for ATAPI devices and decided the kernel would use them in the dev structure, i.e., /dev/hdc, etc. But Schilling behaved like a little child, and would not only fix his app, but gave the kernel developers a whole lot of trouble. So finally, around linux-2.6.8 or so, Linus and Jens Axebode had to hack his cdrecord app to make it work.

Therefore, in the 2.6 kernels we now use ATAPI devices with dev names, not SCSI names. You can see my two DVD burners here:

Code:

mingdao@silas:~$ dmesg | grep -i atapi
hda: PIONEER DVD-RW DVR-109, ATAPI CD/DVD-ROM drive
hdc: TSSTcorpCD/DVDW TS-H552U, ATAPI CD/DVD-ROM drive
hda: ATAPI 40X DVD-ROM DVD-R CD-R/RW drive, 2000kB Cache, UDMA(66)
hdc: ATAPI 48X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)

What Linux distribution are you using?

Kwan Lowe has written about the most extensive Kernel Rebuild Guide I've seen. If you follow it, you should be able to boot into your present kernel, or the new kernel, without any problems.

Kernel building is a very special function of Linux. You can't do it with Windoze or Mac OS. You can strip out every driver (kernel module) in the system that you're not using, and have a smaller, faster running kernel.

I think if you put the proper append line in "/etc/lilo.conf"

Code:

append="hdd=ide-scsi"

you can use that drive as a SCSI device with the 2.4 kernel. Then you will also need "/etc/fstab" setup to link whatever your device is emulated as a SCSI device. I haven't done this in over two years, so I'm a bit rusty.

If you want to stick with a 2.4 kernel, just post the output of these commands
dmesg | grep -i atapi
cat /etc/lilo.conf
cat /etc/fstab
and I'll read up and help you -- if someone more familiar doesn't show up first.

juicy-one · 07-17-2006, 10:55 PM

Thanks again for the detailed response (and the welcome)!

I'm using the Debian (Sarge) distro.

I'm using grub rather than lilo, so I added hdc=ide-scsi to /boot/grub/menu.lst:

Code:

# menu.lst - See: grub(8), info grub, update-grub(8)
#            grub-install(8), grub-floppy(8),
#            grub-md5-crypt, /usr/share/doc/grub
#            and /usr/share/doc/grub-doc/.

## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
default         0

## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout         5

# Pretty colours
color cyan/blue white/blue

## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line)  and entries protected by the
# command 'lock'
# e.g. password topsecret
#      password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret

#
# examples
#
# title         Windows 95/98/NT/2000
# root          (hd0,0)
# makeactive
# chainloader   +1
#
# title         Linux
# root          (hd0,1)
# kernel        /vmlinuz root=/dev/hda2 ro
#

#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST

### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below

## DO NOT UNCOMMENT THEM, Just edit them to your needs

## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specifiv kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
# kopt=root=/dev/hda1 ro

## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,0)

## should update-grub create alternative automagic boot options
## e.g. alternative=true
##      alternative=false
# alternative=true

## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
##      lockalternative=false
# lockalternative=false

## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
##      altoptions=(recovery mode) single
# altoptions=(recovery mode) single

## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
##      howmany=7
# howmany=all

## should update-grub create memtest86 boot option
## e.g. memtest86=true
##      memtest86=false
# memtest86=true

## ## End Default Options ##

title           Debian GNU/Linux, kernel 2.4.27-2-386
root            (hd0,0)
kernel          /boot/vmlinuz-2.4.27-2-386 root=/dev/hda1 ro hdc=ide-scsi
initrd          /boot/initrd.img-2.4.27-2-386
savedefault
boot

title           Debian GNU/Linux, kernel 2.4.27-2-386 (recovery mode)
root            (hd0,0)
kernel          /boot/vmlinuz-2.4.27-2-386 root=/dev/hda1 ro single
initrd          /boot/initrd.img-2.4.27-2-386
savedefault
boot

### END DEBIAN AUTOMAGIC KERNELS LIST

This seems to have worked to make /dev/hdc = /dev/scd0.

I also updated the fstab to route scd0 to cdrom0:

Code:

# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    defaults        0       0
/dev/hda1       /               ext3    defaults,errors=remount-ro 0       1
/dev/hda5       none            swap    sw              0       0
/dev/scd0        /media/cdrom0  iso9660 ro,user,noauto  0       0

I can now read files fom a DVD in the drive by looking at /media/cdrom0, but I still get the same error message when I try to burn to scd0!?

Here is the output when there is a blank DVD in the drive:

Code:

growisofs -dvd-compat -Z /dev/scd0=/home/josst/Desktop/genBackup.iso
:-( /dev/scd0: media is not recognized as recordable DVD: 0

Here is the output when there is an already burnt DVD in the drive:

Code:

growisofs -dvd-compat -Z /dev/scd0=/home/josst/Desktop/genBackup.iso
WARNING: /dev/scd0 already carries isofs!
About to execute 'builtin_dd if=/home/josst/Desktop/genBackup.iso of=/dev/scd0 obs=32k seek=0'
/dev/scd0: "Current Write Speed" is 12.3x1385KBps.
:-[ WRITE@LBA=0h failed with SK=5h/ASC=21h/ACQ=02h]: Input/output error
:-( write failed: Input/output error

So it does seem to be checking what is on the disc, but doesn't like the media (the already burnt media is the same brand though, and was burnt previously using this very same drive, but under windows!).

Anyway I'm totally bamboozled by it. Maybe I should try building the 2.6 Kernel. At least I will probably learn a lot from doing it!

Cheers!

Bruce Hill · 07-18-2006, 02:51 AM

I don't have an answer at the moment. Have you searched Google <Linux> with your error message?

Other suggestions until I get some rest and can think better:

Try the app K3B. If it's not in Sarge, it should be in the repository of apps. Run K3B setup first.

See if you can update dvd+rw-tools -- I've heard of others having similar problems and updating fixed it.

What type of medium are you using? DVD-R(W), DVD+R(W) ?

Have a look at dvd+rw-tools rather than cdrecord-ProDVD.

juicy-one · 07-18-2006, 05:37 AM

OK I installed K3B, and ran the K3BSetup, but when I try to burn a DVD I get the same growisofs error message about the media not being recognized (when I force it to run). Looks like a nice user-friendly program though, I'll definitely come back to it once I get the burner working correctly!!

I think the idea about upgrading the dvd+rw-tools is a good one!

I downloaded dvd+rw-tools_6.1-2 and tried to install, but found that it depends on libc6 >= 2.3.5-1.

I downloaded libc6_2.3.6-15 and attempted to install it but found that it conflicts with initrd-tools (version 0.1.81.1), which is apparently required by kernel-image-2.4.27-2-386 so I'm just a tad reluctant to remove it!!

So now I'm stuck there I guess... what version of dvd+rw-tools do you use chinaman?? Know of any ways to deal with conflicting software packages??

I've tried using Imation CD-R media (which work no problem), as well as Verbatim DVD-R and no-name DVD+R (neither of which work). Maybe I should try getting a different type of DVD+R and see if that works... I reckon the chances are pretty slim though.

And yeah I spent ages Google searching before I came here and started bothering your good self!

Cheers

Tom.

Bruce Hill · 07-18-2006, 06:46 AM

Tom,

You're not bothering me. We're all volunteers, and if we don't want to help we just go on.

I'm using dvd+rw-tools-6.1, but this is Slackware and you've got Debian. So we have different apps and libs already.

I think that "apt-get" or "synaptics" or something is supposed to solve dependencies in Debian, but I only used it a short time a few years ago, so can't really say.

Can you post the entire log of the error from K3B?

And yes, don't remove initrd-tools. Don't mess with those things until you know what you're doing. You could easily hose your whole system and have to reinstall, unless a good Debian person could come along and help you.

Hang in there -- someone of us will help you get it working.

Bruce

juicy-one · 07-25-2006, 09:28 PM

I was away for a few days, got back yesterday and installed a 2.6 kernel and dvd+rw-tools-6.1, but STILL get the ":-( /dev/hdc: media is not recognized as recordable DVD: 0" error message. I really need to try burning some different media I think, I'll go buy some later today... weird that the media works with windows but not with linux though.

Bruce Hill · 07-25-2006, 09:38 PM

Can you post the entire log of the error from K3B?

juicy-one · 07-26-2006, 10:41 PM

OK when I first hit the burn button I get a window popping up which says:

Code:

Found media: No Media
Please insert an empty or appendable Double Layer DVD+/-R medium into drive
PIONEER DVD-RW DVR-109 (dev/hdc).

Obviously I already have some media in the drive, so I hit the "Force" button... and I then get:

Code:

Waiting for media...
Forced by user. Growisofs will be called without further tests.
Using growisofs 6.1 - Copyright (C) Andy Polyakov <appro@fy.chal...
Starting writing...
:-( /dev/hdc: media not recognized as recordable DVD: 0
Fatal error at startup: Wrong medium type
mkisofs did not exit cleanly.
Error while writing ISO image

The debugging output is as follows:

Code:

System
-----------------------
K3b Version: 0.12.14

KDE Version: 3.5.2
QT Version:  3.3.6
Kernel:      2.6.17.6
Devices
-----------------------
PIONEER DVD-RW  DVR-109 1.58 (/dev/hdc, ) at /mnt/dvd [CD-R; CD-RW; CD-ROM; DVD-ROM; DVD-R; DVD-RW; DVD-R DL; DVD+R; DVD+RW; DVD+R DL] [DVD-ROM; DVD-R Sequential; DVD-R Dual Layer Sequential; DVD-R Dual Layer Jump; DVD-RW Restricted Overwrite; DVD-RW Sequential; DVD+RW; DVD+R; DVD+R Double Layer; CD-ROM; CD-R; CD-RW] [SAO; TAO; RAW; SAO/R96P; SAO/R96R; RAW/R16; RAW/R96P; RAW/R96R; Restricted Overwrite; Layer Jump]

K3b
-----------------------
Size of filesystem calculated: 49632

Used versions
-----------------------
growisofs: 6.1

growisofs
-----------------------
:-( /dev/hdc: media is not recognized as recordable DVD: 0

growisofs command:
-----------------------
/usr/bin/growisofs -Z /dev/hdc=/dev/fd/0 -use-the-force-luke=notray -use-the-force-luke=tty -use-the-force-luke=tracksize:49632 -dvd-compat -speed=6.1 -use-the-force-luke=bufsize:32m 

mkisofs
-----------------------
49632

mkisofs command:
-----------------------
/usr/bin/mkisofs -gui -graft-points -volid Gen Backup -volset  -appid K3B THE CD KREATOR (C) 1998-2005 SEBASTIAN TRUEG AND THE K3B TEAM -publisher  -preparer  -sysid LINUX -volset-size 1 -volset-seqno 1 -sort /tmp/kde-root/k3bFrwOaa.tmp -rational-rock -hide-list /tmp/kde-root/k3bqIZa3b.tmp -joliet -hide-joliet-list /tmp/kde-root/k3btuuNEb.tmp -full-iso9660-filenames -iso-level 2 -path-list /tmp/kde-root/k3bN3yx7a.tmp

Thanks for sticking with me on this one

I'm going to go shopping this afternoon and get a different brand of media. Will let you know how it goes!

juicy-one · 07-27-2006, 01:00 AM

AHAH!! Problem solved

I went and bought some better quality DVD+R media and now growisofs seems to be working fine, so I'm very happy to have the problem finally solved, although now I have the problem of trying to work out what to do with the 100+ blank discs I have that are no good to me anymore! I'm told they are good at keeping the birds away if you hang them from the branches of your fruit trees...

Anyway at least if anyone else out there is having the same problem and comes across this they will know what to do.

Thanks Chinaman - appreciate your help.

Bruce Hill · 07-27-2006, 02:19 AM

Since they worked in Windoze (or am I mistaken?), at least
you can use them there. I don't know exactly, but sometimes
Windoze itself, and programs, don't check things that Linux
systems check. I have a motherboard, and IDE0 will not work
under Linux; but it works under Windoze. We even sent the
board to Asus in Chengdu, China (I'd prefer in Taiwan), and
they couldn't fix it.

The problem with Windoze not checking is that you get more
corrupt data.

Something else you might consider. That first error message:

Quote:

Please insert an empty or appendable Double Layer DVD+/-R medium into drive
PIONEER DVD-RW DVR-109 (dev/hdc).

said it was looking for a dual layer DVD. Perhaps that filesystem
of 49632 bytes(?) is too large? Try burning something smaller,
say 4.7 GB or under.

juicy-one · 07-30-2006, 03:03 AM

Yeah that is correct, those discs worked fine with the "Deep Burner" software running under windows 2000. I don't have windows anymore though, I couldn't get it to boot anymore and I don't have any discs to re-install. Not that I'm worried! Linux is working really well for me, the DVD burning was the only issue I had and now that's solved...

I was also a bit perplexed by the error message asking for a double layer DVD medium. I was only trying to burn something ~100 mb though, and it selected that as the disc size by default. Setting a smaller size doesn't seem to make any difference to the error message though... I think it is just the default error message when it can't find the medium.

Cheers