LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 11-04-2010, 12:09 AM   #1
stf92
Senior Member
 
Registered: Apr 2007
Location: Buenos Aires.
Distribution: Slackware
Posts: 4,442

Rep: Reputation: 76
cdrecord and some of its warnings.


kernel 2.6.21.5, Slackware 12.0
cdrecord 2.01

Hi:
Code:
# cdrecord -multi -dao -vv driveropts=burnfree \
dev=1001,0,0 -data chess_lib.iso
This is the command line I used to run cdrecord. Afterwards,
I ran 'cdrecord -media-info' on the same disc and, as a result, I got the messages contained in the file I am adjoining. There, two consecutive warnings can be seen, which I quote:
Quote:
WARNING: Phys disk size 1823462 differs from rzone size 0! Prerecorded disk?
WARNING: Phis start: 196608 Phys end: 2020099
The disk, after recording, however, is both readable by GNU/linux and another O.S. What is the meaning of those warnings and what are its possible implications? I would like to know. Thanks.

P.S.: I now regret not having specified 'speed=some_moderate_speed'. But this is quite a different matter.
Attached Files
File Type: txt typescript.txt (1.6 KB, 11 views)
 
Old 11-04-2010, 10:17 AM   #2
H_TeXMeX_H
LQ Guru
 
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,928
Blog Entries: 2

Rep: Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301
I don't think this means anything other than it is detecting that the disk is prerecorded and telling you how much is left for burning. At the end, when you don't want to add any more, you can probably get rid of the warning if you fixate the disk.
 
1 members found this post helpful.
Old 11-04-2010, 05:38 PM   #3
stf92
Senior Member
 
Registered: Apr 2007
Location: Buenos Aires.
Distribution: Slackware
Posts: 4,442

Original Poster
Rep: Reputation: 76
Thank you very much for your reply. I get confused by the term "prerecorded". I thought that if I buy a disk it can be either blank or prerecorded. For instance, RCA Victor releases prerecorded CDs. Now, if I burn some files onto a blank CD, I get a recorded disk, I would say. All these are pure assumptions but, according to them, how can I get a prerecorded disk starting from a blank one?

Last edited by stf92; 11-04-2010 at 05:40 PM.
 
Old 11-05-2010, 09:11 AM   #4
H_TeXMeX_H
LQ Guru
 
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,928
Blog Entries: 2

Rep: Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301
From man page:
Quote:
-multi Allow multi session CDs or multi border DVDs to be made. This
flag needs to be present on all sessions of a multi session or
multi border disk, except you want to create a session on a CD
that will be the last session on the CD media.

For CD media, the fixation will be done in a way that allows the
CD/DVD/BluRay-Recorder to append additional sessions later. This
is done by generation a TOC with a link to the next program
area. The so generated media is not 100% compatible to manufac-
tured CDs (except for CDplus). Use only for recording of multi
session CDs.

...

-fix The disk will only be fixated (i.e. a TOC for a CD-Reader will
be written). This may be used, if for some reason the disk has
been written but not fixated. This option currently does not
work with old TEAC drives (CD-R50S and CD-R55S).
After you write the DVD, it will be detected as "prerecorded" or already recorded, but with the ability to append data. Now, you may or may not be able to permanently fixate the disk depending on media type. It doesn't matter that much tho, only for 100% compatibility.
 
1 members found this post helpful.
Old 11-05-2010, 04:21 PM   #5
stf92
Senior Member
 
Registered: Apr 2007
Location: Buenos Aires.
Distribution: Slackware
Posts: 4,442

Original Poster
Rep: Reputation: 76
H_TeXMeX_H: thanks for your answer. You must have cdrecord > 2.01. My manual is less explicit. It's been most kind of you to explain the meaning of "prerecorded". I am used to write only CDs, and never had got a message like that quoted in post #1.

Cdrecord always warns me saying "there are unsettled issues with Linux-2.5 and newer". And I run under 2.6. Some day I'll upgrade cdrecord althou as a rule the program must not be newer than the O.S. if downwards compatibility is taken for granted. But let's assume these "unsettled issues" do not affect the DVD recording in my particular case. Althou cdrecord man has many things to say about Philips drives and I happen to be using one.

Getting back to the point, -media-info, for this DVD, gives
data type: standard
disk status: complete
session status: complete.

But I think it SHOULD say
disk status: incomplete/appendable
session status: empty,

[QUESTION #1: shouldn't it?]

given that I used the option -multi. However I must take into consideration what you have just said:
Quote:
Now, you may or may not be able to permanently fixate the disk depending on media type.
I know that, for CDs, I may choose between permanently fixating the disk or not. I take "disk fixation" as synonymous with "disk closing" (this perhaps being a friendly term not belonging to the tech jargon) and with the action of writing a lead out area. Hence, according to you, for DVDs, in at least one of its specifications, DVD-R or DVD+R, there is not such an option. Either the disk is always fixated or it can never be fixated at all. Adding the information given by -media-info (see above), it seems that the former applies. [QUESTION #2: Am I right?]

In connection with multi-session recording it may be interesting to read an LQ post written by cdrecord's author. There, after explaining that "the multi-border [= multi-session] status for DVD+R is unknown", he says
Quote:
If you like to use multi-border with DVDs, I still recommend to use DVD- media as this is even typically more compatible with different drives.
And this is what I did. To use DVD-R as the target. And I wrote pure data. I even specified -data.

Well, if you made your way up to this point in the post, my compliments. Please do no think I am cheerfully relying on LQ. Right now I am busily skimming throu the ECMA-279 standard in an attempt at getting acquainted with optical discs authoring concepts and terminology. All the best.

Last edited by stf92; 11-05-2010 at 04:30 PM.
 
Old 11-06-2010, 06:14 AM   #6
H_TeXMeX_H
LQ Guru
 
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,928
Blog Entries: 2

Rep: Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301
1) Probably, but there's not much documentation on what that output actually means.

2) I can't be sure, but I think in your case there is no way to permanently close the disk. You can try.
 
Old 11-08-2010, 06:31 AM   #7
JZL240I-U
Senior Member
 
Registered: Apr 2003
Location: Germany
Distribution: openSuSE Tumbleweed-KDE, Mint 21, MX-21, Manjaro
Posts: 4,629

Rep: Reputation: Disabled
Jörg Schilling (author of cdrecord) had a dispute with the kernel "hackers" with much flaming etc. When the dust settled he changed the license of cdrecord and made it produce the "error" message.

The maintainers of the debian distribution then made a fork of the old cdrecord and named it "wodim". If you need more details have a look at Wikipedia (or google ).
 
1 members found this post helpful.
Old 11-08-2010, 06:40 AM   #8
H_TeXMeX_H
LQ Guru
 
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,928
Blog Entries: 2

Rep: Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301
Quote:
Originally Posted by JZL240I-U View Post
Jörg Schilling (author of cdrecord) had a dispute with the kernel "hackers" with much flaming etc. When the dust settled he changed the license of cdrecord and made it produce the "error" message.

The maintainers of the debian distribution then made a fork of the old cdrecord and named it "wodim". If you need more details have a look at Wikipedia (or google ).
I heard about that, but I didn't know this was what it was about. I think he has done this multiple times tho, about different things, and how the kernel is very wrong.
 
Old 11-08-2010, 06:46 AM   #9
JZL240I-U
Senior Member
 
Registered: Apr 2003
Location: Germany
Distribution: openSuSE Tumbleweed-KDE, Mint 21, MX-21, Manjaro
Posts: 4,629

Rep: Reputation: Disabled
Quote:
Originally Posted by H_TeXMeX_H View Post
I heard about that, but I didn't know this was what it was about. I think he has done this multiple times tho, about different things, and how the kernel is very wrong.
That may well be but this is the most prominent case AFAIK.
 
Old 11-11-2010, 10:26 AM   #10
Matir
LQ Guru
 
Registered: Nov 2004
Location: San Jose, CA
Distribution: Debian, Arch
Posts: 8,507

Rep: Reputation: 128Reputation: 128
Moved to Slackware forum at the request of the OP.
 
Old 11-13-2010, 02:19 AM   #11
stf92
Senior Member
 
Registered: Apr 2007
Location: Buenos Aires.
Distribution: Slackware
Posts: 4,442

Original Poster
Rep: Reputation: 76
Thanks, JZL240I-U.

After having done some thinking, I had decided not taking any notice of those messages. And this, because several disks burned by Nero, a program tested by millions of users (running under MS Windows), were reported the same as I quoted in post #1.

Now your post has confirmed me in that decision while at the same time provided information of the utmost importance to me given that I have switched to mkisofs and cdrecord a long time ago. All the best, Enrique.

Last edited by stf92; 11-13-2010 at 02:27 AM.
 
Old 11-15-2010, 02:45 AM   #12
JZL240I-U
Senior Member
 
Registered: Apr 2003
Location: Germany
Distribution: openSuSE Tumbleweed-KDE, Mint 21, MX-21, Manjaro
Posts: 4,629

Rep: Reputation: Disabled
You're welcome. Have a nice week .
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] How to handle warnings T. Jump Linux - Newbie 6 10-18-2010 06:15 PM
c warnings kpachopoulos Programming 1 08-25-2006 06:45 AM
Gdk warnings BroX Slackware 5 03-13-2006 05:06 PM
What do these warnings mean (re cdrom)? tigerflag Linux - Hardware 4 03-24-2005 06:14 PM
removing warnings h/w Programming 6 01-26-2004 05:06 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 01:36 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration