Find the answer to your Linux question:
Results 1 to 3 of 3
Hello I cant burn anything with this drive: DVD-RW DVR-K13AS Pioneer (SCSI bus is 0,0,0). Whatever I try I got this output: Code: cdrecord: Cannot load media with this drive! ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Linux User
    Join Date
    Sep 2003
    Posts
    254

    Problem with cdrecord


    Hello
    I cant burn anything with this drive: DVD-RW DVR-K13AS Pioneer (SCSI bus is 0,0,0).
    Whatever I try I got this output:
    Code:
    cdrecord: Cannot load media with this drive!
    cdrecord: Try to load media by hand.
    Then it hangs up
    Few infos:
    Code:
    cdrecord -version
    Cdrecord-Clone 2.01.01a01 (x86_64-unknown-linux-gnu) Copyright (C) 1995-2004 Joerg Schilling
    NOTE: this version of cdrecord is an inofficial (modified) release of cdrecord
          and thus may have bugs that are not present in the original version.
          Please send bug reports and support requests to <cdrtools@packages.debian.org>.
          The original author should not be bothered with problems of this version.
    
    cdrecord&#58; Warning&#58; Running on Linux-2.6.8-9-amd64-k8
    cdrecord&#58; There are unsettled issues with Linux-2.5 and newer.
    cdrecord&#58; If you have unexpected problems, please try Linux-2.4 or Solaris.
    cdrecord&#58; Warning&#58; Linux-2.6.8 introduced incompatible interface changes.
    cdrecord&#58; Warning&#58; SCSI transport does no longer work for suid root programs.
    cdrecord&#58; Warning&#58; if cdrecord fails, try to run it from a root account
    Here is the output of cdrecord dev=help
    Code:
    Transport name&#58;         sg
    Transport descr.&#58;       Generic transport independent SCSI
    Transp. layer ind.&#58;
    Target specifier&#58;       bus,target,lun
    Target example&#58;         1,2,0
    SCSI Bus scanning&#58;      supported
    Open via UNIX device&#58;   not supported
    
    Transport name&#58;         pg
    Transport descr.&#58;       SCSI transport for ATAPI over Parallel Port
    Transp. layer ind.&#58;
    Target specifier&#58;       bus,target,lun
    Target example&#58;         1,2,0
    SCSI Bus scanning&#58;      supported
    Open via UNIX device&#58;   not supported
    
    Transp. layer ind.&#58;     ATAPI&#58;
    Target specifier&#58;       bus,target,lun
    Target example&#58;         ATAPI&#58;1,2,0
    SCSI Bus scanning&#58;      supported
    Open via UNIX device&#58;   not supported
    
    Transport name&#58;         ATA
    Transport descr.&#58;       ATA Packet specific SCSI transport using sg interface
    Transp. layer ind.&#58;     ATA&#58;
    Target specifier&#58;       bus,target,lun
    Target example&#58;         1,2,0
    SCSI Bus scanning&#58;      supported
    Open via UNIX device&#58;   not supported
    
    Transport name&#58;         RSCSI
    Transport descr.&#58;       Remote SCSI
    Transp. layer ind.&#58;     REMOTE&#58;
    Target specifier&#58;       rscsi@host&#58;bus,target,lun
    Target example&#58;         REMOTE&#58;rscsi@host&#58;1,2,0
    SCSI Bus scanning&#58;      supported
    Google doesn't give me any tricks and I don't know now what I should do: upgrade the firmware of the drive?or...?
    Thx for any help

  2. #2
    Linux User
    Join Date
    Aug 2005
    Location
    Peterborough, UK
    Posts
    379
    First of all, make sure that you have the latest version of cdrecord.

    Then you can try mounting the drive by hand, as the error suggests (though I doubt that'll work with unformatted media)

    Or, if you can, try using 'k3b' (or a GNOME equivalent) and see if it throws up the same sort of error. If it doesn't, you need to work out what CLI options it is passing to cdrecord. If it does, then I must say I'm stumped...
    \"I am, after all,\" said Pooh, \"a bear of very little brain.\"
    MY PC: Athlon XP64 3000+ on a Asus K8V-X mobo w/1GB of non-descript RAM. AGP - GeForce 2 MX400. PCI - Creative Live! 5.1 soundcard. 140 GB and 120 GB SATA WD drives.

  3. #3
    Linux User
    Join Date
    Jan 2005
    Location
    Arizona
    Posts
    288
    What command are you issuing, exactly?

    So you're setting a boot parameter similar to hdc=ide-scsi? hdc would be substituted for whichever IDE location your burner is on. If not, try prepending your dev with ATAPI, such as dev=ATAPI:0,0,0
    If you are passing a SCSI emulation parameter and are using a 2.6 kernel, try removing it from your boot loader's config (and reloading lilo, if relevant) and using the ATAPI dev.
    Also, if not using SCSI emulation you can often just point to the /dev device. For example, I use dev=/dev/hdc, and I figure dev=/dev/cdroms/cdrom0 would also work. It might be /dev/cdrom or /dev/cdrw, or any number of /dev/hdX locations, though hdc is most common due to the finickiness of older CDRW and IDE controllers.

    I should also mention that cdrecord's -scanbus switch doesn't work unless I define the proper dev. That's without SCSI emulation, I don't like cruft in my kernel

    I recently used thus guide to setup some aliases, but it also offers some good guidance in finding your hardware and such.
    http://www.yolinux.com/TUTORIALS/Lin...ialCDBurn.html

    edit: prepend ATAPI, not append
    Michael Salivar

    Man knows himself insofar as he knows the world, becoming aware of it only in himself, and of himself only within it.
    --Goethe

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •