Re: CD images, ISO

From: Keith Krehbiel (redsilo_at_pldi.net)
Date: 10/26/04


Date: Tue, 26 Oct 2004 08:40:52 -0500

Rod Smith wrote:
> In article <10nauqnmnkt6g35@corp.supernews.com>,
> Keith Krehbiel <redsilo@pldi.net> writes:
>
>>Rod Smith wrote:
>>
>>>In article <10n8qd231kbkg46@corp.supernews.com>,
>>> Keith Krehbiel <redsilo@pldi.net> writes:
>>>
>>>
>>>>I have scratched the first CD in my set to the point where it is mostly
>>>>unuseable for installation. I downloaded an image that I am reasonable
>>>>certain would be a replacement for the one I ruined. When I try to
>>>>extract the image to copy the files and burn a new CD
>>>
>>>Don't try it that way. Download the image file and burn it straight to
>>>CD-R *AS AN IMAGE FILE* (that is, do *NOT* burn a CD with a single big
>>>file). You can do this directly with cdrecord, or most GUI CD-R tools have
>>>an option to burn a CD-R from an image file. If you need more help on
>>>this, post with information on the CD-R software you're using.
>>>
>>
>>Actually burning a single big file was about the only option I had not
>>tried. The file I have downloaded has a garbage title and a generic
>>icon but Disk Copy will open it and create an image. The problem is
>>that all the files and folders in the image are named to ISO standards
>>rather than something that Linux would understand.
>
>
> The CD-R image file is a complete ISO-9660 filesystem in a single file.
> The Disk Copy tool just accesses that filesystem the way a Mac normally
> does, except from the file rather than from an actual CD-ROM. The
> filesystem image is almost certainly ISO-9660 with Rock Ridge extensions,
> which means that it *DOES* have long filenames, but they're encoded via
> Rock Ridge, which pre-X versions of MacOS can't understand. (Mac disc
> images will be either HFS or ISO-9660 plus HFS, so Macs will see HFS long
> filenames.) All of this is irrelevant once the CD-R is created correctly,
> because what you should do is find a way to burn the image to disc
> without adding it in a wrapper filesystem. That is, the usual way to
> create a CD-R is to take files from a disk directory, wrap them in an
> ISO-9660 filesystem (often plus other options), and write that created
> filesystem to the CD-R. What you want to do is to write the file to disc
> *WITHOUT* first wrapping it in an ISO-9660 filesystem, because the image
> file *IS* an ISO-9660 filesystem.
>
>
>>I tried just now to create an
>>image from the file with my burner software (Discribe) and it wouldn't
>>read the file. Thanks for your suggestion though.
>
>
> I'm afraid I'm not familiar with Discribe, so I can't tell you precisely
> how to do what's needed with it, or even if it's possible -- it's
> conceivable that Discribe is crippled and lacks the necessary option. Look
> for something called "burn from image file," "create CD-R from ISO image,"
> or something similar. You don't want to *CREATE* an image file -- you've
> already got one. You want to COPY that existing image file to disc.
>
> If Discribe is so crippled that it won't do what you need, you might look
> into other software. I'm not familiar with MacOS options, so I can't point
> you to specific products, but there's got to be something that'll do the
> job. If you've already installed Linux and can access the file from Linux,
> just use cdrecord to burn the image file to CD-R from Linux.
>
>
>>The real filenames
>>are saved in each directory in a file called TABLE, something or
>>another.
>
>
> This is a common practice when using certain Unix/Linux CD-R creation
> tools. Placing the long filenames in a special files enables users of OSs
> that can't read them to figure out what's what. You can and should ignore
> this detail, along with everything you see when accessing the file with
> Disk Copy, because using Disk Copy as any part of this process is the
> wrong approach -- or at the very least, it's the way-too-hard approach.
>
>
>>Seems like there should be some way to reconstruct it.
>
>
> In theory, yes. Reconstruction is the wrong approach, though; it's like
> trying to pick all the toppings off of a pizza to make a sandwich from
> them, when a sandwich just like the one you want to make is sitting right
> next to the pizza. Only multiply that by a thousandfold. ;-)
>

Thanks for your reply. I finally applied some repair goop to my
original disk and was able to get a decent install. From the error
messages I was able to determine that at least part of the corruption
happens in the /x directory in /pool.
I have, so far, not found a way to access disks other than the system
disk from inside linux. I am not sure if I have something wrong with
the system or if it is an operator malfunction. At least this time I
have emacs and am learning to use it. Several of my attempts to install
omitted emacs and that was one of the reasons to reinstall: to get a
tool to examine a few things.
One of the things I have done is to start using a rewriteable disk so I
don't burn a coaster every time.
Don't try it that way. Download the image file and burn it straight to

>>>CD-R *AS AN IMAGE FILE* (that is, do *NOT* burn a CD with a single big
>>>file). You can do this directly with cdrecord, or most GUI CD-R
tools have
>>>an option to burn a CD-R from an image file.

Discribe has an option to copy CD/DVD. I will try that next. It sounds
like what you were describing. I am able to copy the image into the
buffer in almost any format I have tried but I don't remember if I have
burnt a disc that way. I am sure I have not tried the copy CD/DVD
function yet.
Any suggestions on reading 'foreign' devices from within linux?
Thanks again for your help. It was most informative.
Keith



Relevant Pages

  • Re: Erasing a DVD-/+RW DISC
    ... >to create a 'MASTER' disk and then do a disk copy once I know ... >So you are saying that when I do a disc copy to my DVD+R disc, ... Of cause a profi would do (in Linux) ... You could do excellent data hiding in those not used sectors too. ...
    (sci.crypt)
  • trying to rescue disk
    ... The contents could be saved and were put on another disk. ... I also could not boot from it anymore, tried that and the screen was filled with an endless string of "GRUB GRUB GRUB..." ... My guess is that the addressing on the Seagate is somehow different than on the Maxtor, which makes it less straightforward to transfer a whole disc image between the two. ... See if you can use a Knoppix disk or another Linux live CD to look at that partition. ...
    (Debian-User)
  • Re: mirroring
    ... *Migrating an Existing Linux to RAID1* ... this copies your data from the existing disk to the new disk then overwrites your existing disk* ... Change the partition type on the existing non-raid disk to type 'fd' ... Create the degraded RAID array on the empty disk, but leave out the existing system disk for now. ...
    (RedHat)
  • Re: mirroring
    ... *Migrating an Existing Linux to RAID1* ... Change the partition type on the existing non-raid disk to type 'fd' ... Changed system type of partition 1 to fd (Linux raid autodetect) ...
    (RedHat)
  • Re: Panasonic HD Recorders - What disk format?
    ... The earlier part of this is more about what may be Linux partitioning, ... might be possible to present the recorder with a larger disk already ... Most DOS/Windows utilities such as FDisk, Ghost, and Partition Magic Pro ... prompts to format it. ...
    (alt.os.linux)