FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora User

 
 
LinkBack Thread Tools
 
Old 01-19-2008, 12:50 AM
"D. Hugh Redelmeier"
 
Default I just wanted to burn a CD from a .iso

I'm knee deep in bugs/problems.

I just wanted to burn a .iso file to a CD. (Why is another sad
story.) On my desktop F7 x86_64 system.

I tried k3b, my normal tool. Tools: Burn CD Image. When I clicked
"Start", it hung, not even updating the window damage.

Why? ps shows that it was hung awaiting a process doing lsof on /dev/sr0.

strace showed that the lsof was doing a stat on an NFS mount point. I
have not idea why that would hang (but I could repeat it). I have no
ideas why lsof cared about the mount point. Two more mysteries.

I decided to burn the .iso using a script that I'd written a while
back. A wrapper for cdrecord. That failed too. It put out an
endlessly repeating stream of warnings (with no newlines):

Unable to open this SCSI ID. Trying to map to old ATA syntax.This
workaround will disappear in the near future. Fix your
configuration.Unable to open this SCSI ID. Trying to map to old ATA
syntax.This workaround will disappear in the near future. Fix your
configuration.

This script used to work on this machine. I don't know when it
stopped. The actual cdrecord command was:
cdrecord -v dev=2,0,0 speed=8 -dao driveropts=burnfree --padsize=128k InitialHDD.iso

The messages from that command, up until the repeated messages, were:
TOC Type: 1 = CD-ROM
scsidev: '2,0,0'
scsibus: 2 target: 0 lun: 0
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.

Another mystery: what is wodim? That one is easy: wodim is a fork of
cdrecord. So I was actually using wodim.


OK, what does "wodim --devices" say?
Segmentation fault

Another mystery. I wonder what the segfault is about. gdb says that
it is in strlen. But the stack dump isn't very useful without the
debug info:
#0 0x0000003602c77180 in strlen () from /lib64/libc.so.6
#1 0x0000003602c460bb in vfprintf () from /lib64/libc.so.6
#2 0x0000003602ce4228 in __vsnprintf_chk () from /lib64/libc.so.6
#3 0x0000003602ce416b in __snprintf_chk () from /lib64/libc.so.6
#4 0x0000000000437680 in list_devices ()
#5 0x000000000040cef4 in main ()

So: let's load the debuginfo package. Even though wodim's rpm is in
updates, the -debuginfo package is missing. Another mystery.

There is another cdrecord command that can find drives:
# wodim -scanbus
scsibus2:
2,0,0 200) 'HP ' 'DVD Writer 740b ' 'HI24' Removable CD-ROM
2,1,0 201) 'TSSTcorp' 'DVD-ROM TS-H352C' 'HP01' Removable CD-ROM
2,2,0 202) *
2,3,0 203) *
2,4,0 204) *
2,5,0 205) *
2,6,0 206) *
2,7,0 207) *

This seems to suggest that dev=2,0,0 should be correct, but we already
know it is not. Another mystery.

The cdrecord command worked when I used dev=/dev/scd0.

The script had another failure. It ended with "eject /dev/cdwriter".
There is no /dev/cdwriter on my machine. I'm sure that I've had that
pathname on my machines for years. I wonder why it went away.
Another mystery.

I decided, like a good citizen, to report the wodim problems. It
turns out that the bugzilla doesn't think that F7 has a "wodim"
component, even though that is the name of the .rpm that it came in.
Apparently cdrkit is the appropriate component name. Another
surprise.c

https://bugzilla.redhat.com/show_bug.cgi?id=429385

https://bugzilla.redhat.com/show_bug.cgi?id=429386

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
 
Old 01-19-2008, 01:44 AM
Robert L Cochran
 
Default I just wanted to burn a CD from a .iso

D. Hugh Redelmeier wrote:

I'm knee deep in bugs/problems.

I just wanted to burn a .iso file to a CD. (Why is another sad
story.) On my desktop F7 x86_64 system.

I tried k3b, my normal tool. Tools: Burn CD Image. When I clicked
"Start", it hung, not even updating the window damage.

Are you sure the drive is working? Did you put a writable CD or DVD in
the drive? And if you are writing to DVD, is the DVD the proper type, of
+R or -R?


Have you run `mount` to see the optical drive device?

I don't often need to burn a CD or DVD -- today was my first time in a
while that I've done it. I much prefer using flash drives to transport
files. Capacities are generally larger, and flash drives seem less prone
to damage than CD/DVD media.


If I must burn a DVD, I like to use growisofs.

Bob Cochran

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
 
Old 01-19-2008, 01:49 AM
"Michael Schwendt"
 
Default I just wanted to burn a CD from a .iso

On 19/01/2008, D. Hugh Redelmeier <hugh@mimosa.com> wrote:
> I'm knee deep in bugs/problems.
>
> I just wanted to burn a .iso file to a CD. (Why is another sad
> story.) On my desktop F7 x86_64 system.
>
> I tried k3b, my normal tool.

There are alternative graphical burning programs, e.g. brasero. Just
in case you didn't know.

> Tools: Burn CD Image. When I clicked
> "Start", it hung, not even updating the window damage.
>
> Why? ps shows that it was hung awaiting a process doing lsof on /dev/sr0.
>
> strace showed that the lsof was doing a stat on an NFS mount point. I
> have not idea why that would hang (but I could repeat it). I have no
> ideas why lsof cared about the mount point. Two more mysteries.

Well, k3b includes quite a complex filesystem browser, which does much
more than just displaying your home directory. If mounted fs are
inaccessible, that can cause problems then.

> I decided to burn the .iso using a script that I'd written a while
> back. A wrapper for cdrecord. That failed too. It put out an
> endlessly repeating stream of warnings (with no newlines):
>
> Unable to open this SCSI ID. Trying to map to old ATA syntax.This
> workaround will disappear in the near future. Fix your
> configuration.Unable to open this SCSI ID. Trying to map to old ATA
> syntax.This workaround will disappear in the near future. Fix your
> configuration.
>
> This script used to work on this machine. I don't know when it
> stopped. The actual cdrecord command was:
> cdrecord -v dev=2,0,0 speed=8 -dao driveropts=burnfree --padsize=128k InitialHDD.iso
>
> The messages from that command, up until the repeated messages, were:
> TOC Type: 1 = CD-ROM
> scsidev: '2,0,0'
> scsibus: 2 target: 0 lun: 0
> 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.
>
> Another mystery: what is wodim? That one is easy: wodim is a fork of
> cdrecord. So I was actually using wodim.

Fedora release notes covered that, IIRC.

> So: let's load the debuginfo package. Even though wodim's rpm is in
> updates, the -debuginfo package is missing. Another mystery.

How did you try to install it?
With "debuginfo-install"?

> This seems to suggest that dev=2,0,0 should be correct, but we already
> know it is not. Another mystery.
>
> The cdrecord command worked when I used dev=/dev/scd0.

That device naming changes is covered in the release notes, isn't it?

> I decided, like a good citizen, to report the wodim problems. It
> turns out that the bugzilla doesn't think that F7 has a "wodim"
> component, even though that is the name of the .rpm that it came in.
> Apparently cdrkit is the appropriate component name. Another
> surprise.c

It's been like that for years and is explained on the bugzilla pages.
The "component" is the src.rpm package name. Don't use the "Expert"
bugzilla mode if you need the instructions.

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
 
Old 01-19-2008, 01:52 AM
"Aldo Foot"
 
Default I just wanted to burn a CD from a .iso

On Jan 18, 2008 5:50 PM, D. Hugh Redelmeier <hugh@mimosa.com> wrote:

I'm knee deep in bugs/problems.

I just wanted to burn a .iso file to a CD. *(Why is another sad
story.) *On my desktop F7 x86_64 system.

I tried k3b, my normal tool. *Tools: Burn CD Image. *When I clicked

"Start", it hung, not even updating the window damage.

Why? *ps shows that it was hung awaiting a process doing lsof on /dev/sr0.

strace showed that the lsof was doing a stat on an NFS mount point. *I

have not idea why that would hang (but I could repeat it). *I have no
ideas why lsof cared about the mount point. *Two more mysteries.

I decided to burn the .iso using a script that I'd written a while

back. *A wrapper for cdrecord. *That failed too. *It put out an
endlessly repeating stream of warnings (with no newlines):

* *Unable to open this SCSI ID. Trying to map to old ATA syntax.This
* *workaround will disappear in the near future. Fix your

* *configuration.Unable to open this SCSI ID. Trying to map to old ATA
* *syntax.This workaround will disappear in the near future. Fix your
* *configuration.

This script used to work on this machine. *I don't know when it

stopped. *The actual cdrecord command was:
*cdrecord -v dev=2,0,0 speed=8 -dao driveropts=burnfree --padsize=128k InitialHDD.iso

The messages from that command, up until the repeated messages, were:
* *TOC Type: 1 = CD-ROM

* *scsidev: '2,0,0'
* *scsibus: 2 target: 0 lun: 0
* *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.

Another mystery: what is wodim? *That one is easy: wodim is a fork of
cdrecord. *So I was actually using wodim.



OK, what does "wodim --devices" say?
* * * *Segmentation fault

Another mystery. *I wonder what the segfault is about. *gdb says that
it is in strlen. *But the stack dump isn't very useful without the

debug info:
* *#0 *0x0000003602c77180 in strlen () from /lib64/libc.so.6
* *#1 *0x0000003602c460bb in vfprintf () from /lib64/libc.so.6
* *#2 *0x0000003602ce4228 in __vsnprintf_chk () from /lib64/libc.so.6

* *#3 *0x0000003602ce416b in __snprintf_chk () from /lib64/libc.so.6
* *#4 *0x0000000000437680 in list_devices ()
* *#5 *0x000000000040cef4 in main ()

So: let's load the debuginfo package. *Even though wodim's rpm is in

updates, the -debuginfo package is missing. *Another mystery.

There is another cdrecord command that can find drives:
* *# wodim -scanbus
* *scsibus2:
* * * * * *2,0,0 200) 'HP ' 'DVD Writer 740b ' 'HI24' Removable CD-ROM

* * * * * *2,1,0 201) 'TSSTcorp' 'DVD-ROM TS-H352C' 'HP01' Removable CD-ROM
* * * * * *2,2,0 * 202) *
* * * * * *2,3,0 * 203) *
* * * * * *2,4,0 * 204) *
* * * * * *2,5,0 * 205) *

* * * * * *2,6,0 * 206) *
* * * * * *2,7,0 * 207) *

This seems to suggest that dev=2,0,0 should be correct, but we already
know it is not. *Another mystery.

The cdrecord command worked when I used dev=/dev/scd0.


The script had another failure. *It ended with "eject /dev/cdwriter".
There is no /dev/cdwriter on my machine. *I'm sure that I've had that
pathname on my machines for years. *I wonder why it went away.

Another mystery.

I decided, like a good citizen, to report the wodim problems. *It
turns out that the bugzilla doesn't think that F7 has a "wodim"
component, even though that is the name of the .rpm that it came in.

Apparently cdrkit is the appropriate component name. *Another
surprise.c

https://bugzilla.redhat.com/show_bug.cgi?id=429385


https://bugzilla.redhat.com/show_bug.cgi?id=429386

--
fedora-list mailing list

fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list


--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
 
Old 01-19-2008, 01:58 AM
"Aldo Foot"
 
Default I just wanted to burn a CD from a .iso

On Jan 18, 2008 5:50 PM, D. Hugh Redelmeier <hugh@mimosa.com> wrote:

Another mystery: what is wodim? *That one is easy: wodim is a fork of
cdrecord. *So I was actually using wodim.


OK, what does "wodim --devices" say?
* * * *Segmentation fault
******

"man wodim" says this:
****** "because certain versions of Linux (kernel) limit
****** the set of SCSI commands allowed for non-root users.* Even* if* usage* without
****** root* identity* is possible in many cases, some device drivers still may fail,

****** show unexplainable problems and generally the problems become harder to debug.
****** The* risk* for* buffer-underruns is also increased"
could that be a hint?

could it be that the drive just went belly up?

I can't remember where and when I read that some drives break
when used in certain scenarios. I may be wrong.

~af


--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
 
Old 01-19-2008, 03:12 AM
"D. Hugh Redelmeier"
 
Default I just wanted to burn a CD from a .iso

| From: Robert L Cochran <cochranb@speakeasy.net>

| D. Hugh Redelmeier wrote:

| > I tried k3b, my normal tool. Tools: Burn CD Image. When I clicked
| > "Start", it hung, not even updating the window damage.
| >
| Are you sure the drive is working?

Yes, I'm sure. If you read to the end of my too-long story, you will
see:
The cdrecord command worked when I used dev=/dev/scd0.

The real k3b problem was something screwed up with NFS, I think. But
why lsof needed to do a stat on that mount point is not at all clear
to me. Nothing to do with the actual burner.

| Did you put a writable CD or DVD in the
| drive? And if you are writing to DVD, is the DVD the proper type, of +R or -R?

Through all this I had a blank CD-R in the drive. The final cdrecord
command burnt a CD that I could then boot on another computer (the
original point of the exercise).

| Have you run `mount` to see the optical drive device?

Mount does not know what to do with a blank CD.

| I don't often need to burn a CD or DVD -- today was my first time in a while
| that I've done it. I much prefer using flash drives to transport files.
| Capacities are generally larger, and flash drives seem less prone to damage
| than CD/DVD media.

I needed a bootable CD.

| If I must burn a DVD, I like to use growisofs.

I don't know if it knows how to do CDs. I do know that it won't do
--padsize=128k when burning a .iso.

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
 
Old 01-19-2008, 04:35 AM
"D. Hugh Redelmeier"
 
Default I just wanted to burn a CD from a .iso

| From: Michael Schwendt <mschwendt@gmail.com>

I appreciate your helpful reply (if not your tone).

| On 19/01/2008, D. Hugh Redelmeier <hugh@mimosa.com> wrote:

| > I tried k3b, my normal tool.
|
| There are alternative graphical burning programs, e.g. brasero. Just
| in case you didn't know.

Thanks. I don't mind cdrecord/wodim when it is wrapped in a script.
Apparently it was time to refresh my script.

| > Tools: Burn CD Image. When I clicked
| > "Start", it hung, not even updating the window damage.
| >
| > Why? ps shows that it was hung awaiting a process doing lsof on /dev/sr0.
| >
| > strace showed that the lsof was doing a stat on an NFS mount point. I
| > have not idea why that would hang (but I could repeat it). I have no
| > ideas why lsof cared about the mount point. Two more mysteries.
|
| Well, k3b includes quite a complex filesystem browser, which does much
| more than just displaying your home directory. If mounted fs are
| inaccessible, that can cause problems then.

I was just burning from a .iso so it didn't need to browse.

What hung was lsof. I'm guessing that it was just trying to see if
any other process was using the burner. Furthermore, I'm guessing
that lsof was trying to see if the device was mounted and was thus
sniffing around all the mounts.

The real mystery is why NFS is causing these hangs. I admit that the
server was rebooted while the client still had the mount (a day
before). But NFS should handle that gracefully. But I'm too lazy to
explore that right now.

| > So: let's load the debuginfo package. Even though wodim's rpm is in
| > updates, the -debuginfo package is missing. Another mystery.
|
| How did you try to install it?
| With "debuginfo-install"?

I didn't know (remember?) debuginfo-install. That worked. Thanks!

| > This seems to suggest that dev=2,0,0 should be correct, but we already
| > know it is not. Another mystery.
| >
| > The cdrecord command worked when I used dev=/dev/scd0.
|
| That device naming changes is covered in the release notes, isn't it?

Clearly wodim didn't read the release notes :-)

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
 
Old 01-19-2008, 12:11 PM
Alan Cox
 
Default I just wanted to burn a CD from a .iso

On Fri, 18 Jan 2008 18:58:57 -0800
"Aldo Foot" <lunixer@gmail.com> wrote:

> On Jan 18, 2008 5:50 PM, D. Hugh Redelmeier <hugh@mimosa.com> wrote:
>
> > Another mystery: what is wodim? That one is easy: wodim is a fork of
> > cdrecord. So I was actually using wodim.
> >
> >
> > OK, what does "wodim --devices" say?
> > Segmentation fault
> >
>
> "man wodim" says this:

Segmentation fault is a program crashing not a compatibility issue. It
broke, file a bug report.

Alan

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
 

Thread Tools




All times are GMT. The time now is 07:16 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org