Fwd: Problem with mkiso - Solved
Greg Morgan
drkludge at cox.net
Fri Oct 15 05:12:17 UTC 2004
Edgar,
Anytime you see a 'Violación de segmento' or 'segmentation fault' that
is the point where you have to begin your trouble shooting. If you
would have tried FC1 you may have experienced the same error. It may be
helpful for you to print out the documentation located here
http://rau.homedns.org/twiki/bin/view/Anaconda/AnacondaDocumentationProject
or here http://www.linuxworks.com.au/redhat-installer-howto.html or
paste the steps in a file. As you perform the steps place a check mark
by each step or sub-step. This will help you remember where you are if
you are interrupted in the process or help you remember the next thing
to do. If a step fails you must resolve it before proceeding. This is
exactly what I did with the 'Input/output error' messages. When I
looked at my copy target directory, it did not have the isolinux
directory for example. So if your start using this type of technique,
you will be more successful. You will also enjoy what you can do with
the open source tools.
Greg
Edgar Chillón 'Chillux' wrote:
> Men, it works !!! Really truly thanks !!!!!
>
> The error was that I forgot this step:
>
> ind /home/fdrive/fc2iso -name TRANS.TBL -exec rm -f
> {} \;
>
> Thanks !
> --- Greg Morgan escribió:
>
>>Edgar,
>>
>>I was bored tonight so I thought I would fool around
>>with your issue. If
>>you are planning to make changes to the CD set, then
>>you will want to go
>>through and perform all the steps as described in
>>the documentation.
>>The following steps bypass much of the
>>documentation.
>>
>>I tried the steps on a real FC2 cd that I installed
>>from. I received
>>the following errors. They appear to be fatal to
>>me:
>>cp: reading `/mnt/cdrom/Fedora/base/comps.rpm':
>>Input/output error
>>cp: reading `/mnt/cdrom/Fedora/base/hdlist':
>>Input/output error
>>cp: reading `/mnt/cdrom/Fedora/base/hdlist2':
>>Input/output error
>>Moreover, not all of the directories were copied
>>from the cd into my
>>working directory.
>>
>>Since I still had the ISO file that I used to create
>>the CD with I tried
>>these steps. They are a little different from the
>>two sites listed
>>below but have the same intent. You will have to
>>adapt the file paths
>>to your system. (The pathing is for a samba/NFS
>>server.)
>># Switch to root
>>su - root
>># Go to the ISO directory location.
>>cd /home/ddrive/fedoracore2
>># Mount the ISO file.
>>mount -t iso9660 -o loop FC2-i386-disc1.iso
>>/mnt/cdrom
>>#Make a set of working directories
>>mkdir -p /home/fdrive/fc2iso
>>mkdir -p /home/fdrive/fc2iso/i386
>># Copy the files from the CD/ISO.
>>cp -a /mnt/cdrom/* /home/fdrive/fc2iso/i386
>>cp /mnt/cdrom/.discinfo /home/fdrive/fc2iso/i386
>># Clean up the original cd TRANS.TBL files.
>>find /home/fdrive/fc2iso -name TRANS.TBL -exec rm -f
>>{} \;
>># Go to the location of disc 1 files.
>>cd /home/fdrive/fc2iso/i386
>># Make sure the /home/fdrive/fc2iso/i386 directory
>>has
>># the same files as the /mnt/cdrom directory .
>>ls -l
>># Make sure that I create the iso file in the
>>directory
>># above the directory containing the files in the
>>iso.
>>cd /home/fdrive/fc2iso
>># Create the iso. Note the \ has to be the last
>>character
>># on the line. I did this for readability on my
>>part.
>>mkisofs -b isolinux/isolinux.bin \
>>-c isolinux/boot.cat -J -p "chillux at mycompany.com" \
>>-V "Fedora Core 2 with updates disc1" \
>>-r -T -v -A "Fedora Core Linux/i386 2" \
>>-o fedoracore2-disc1.iso -no-emul-boot \
>>-boot-load-size 4 -boot-info-table -l i386
>>
>>The final output showed:
>>...
>> 99.18% done, estimate finish Wed Oct 13 21:52:39
>>2004
>>Total translation table size: 131221
>>Total rockridge attributes bytes: 54553
>>Total directory bytes: 96256
>>Path table size(bytes): 94
>>Done with: The File(s) Block(s)
>>332482
>>Writing: Ending Padblock Start Block
>>332589
>>Done with: Ending Padblock Block(s) 150
>>Max brk space used 8e000
>>332739 extents written (649 MB)
>>
>># I am done with the mounted ISO file so unmount the
>>file.
>>umount /mnt/cdrom
>>
>>My version of mkisofs is 2.01a27.
>>
>>I hope this helps,
>>Greg
>>
>>Edgar Chillón 'Chillux' wrote:
>>
>>>Sooo ? what do I have to do ? I copyed the disc 1
>>>again and I have the same problem !!!!
>>>
>>>Any ideas ? or I will have to go back to fedora
>>
>>core 1
>>
>>>?
>>>
>>>Regards.
>>>
>>> --- Edgar Chillón 'Chillux'
>>
>><e_chillon at yahoo.com.mx>
>>
>>>escribió:
>>>
>>>
>>>>I did it as the manual said:
>>>>
>>>>cp -R /mnt/cdrom/* /mnt/fedora-custom
>>>>cp /mnt/cdrom/.discinfo /mnt/fedora-custom
>>>>
>>>>Then I tryed to create the iso but it send me that
>>>>error. I thoungh it was a disk problem, I tryed in
>>>>other disk and the problem is the same ... I don't
>>>>know how to do, I've tryed to find some of this in
>>>>google but I didnt find anything ...
>>>>
>>>>Please, some body help ..
>>>>
>>>>
>>>>--- Greg Morgan escribió:
>>>>
>>>>
>>>>>Edgar Chillón 'Chillux' wrote:
>>>>>
>>>>>
>>>>>>Can some body explain me what do I have this
>>>>>
>>>>>problem:
>>>>>
>>>>>Edgar
>>>>>
>>>>>The clue may be in this statement
>>>>>
>>>>>>I am occuping the Fedora Core 2, I didnt
>>
>>change
>>
>>>>>>anything, I just simple copy the first disk
>>
>>and
>>
>>>>>try to
>>>>>
>>>>>>make it iso but I didnt work ...
>>>>>
>>>>>How did you "copy" the first disk? When
>>
>>following
>>
>>>>>these instructions
>>>>>
>>>>
> http://rau.homedns.org/twiki/bin/view/Anaconda/PreparingTheBuildEnvironment,
>
>>>>>did you perform steps 1, 2, 3--just for CD ONE,
>>>>
>>>>and
>>>>
>>>>
>>>>>7? I point this out
>>>>>because of the segmentation fault during the
>>>>>directory tree writing
>>>>>step, "> Writing: Directory tree"
>>>>>
>>>>>
>>>>>
>>>>>>[root at chillux fedora-custom]# mkisofs -b
>>>>>>isolinux/isolinux.bin -c isolinux/boot.cat -J -p
>>>>>>"chillux at mycompany.com" -V "Fedora Core 2 with
>>>>>>updates disc1" -r -T -v -A "Fedora Core
>>>>
>>>>Linux/i386
>>>>
>>>>
>>>>>2"
>>>>>
>>>>>
>>>>>>-o fedoracore2-disc1.iso -no-emul-boot
>>>>>
>>>>>-boot-load-size
>>>>>
>>>>>
>>>>>>4 -boot-info-table -l i386
>>>>>
>>>>>Your mkisofs options look good based on
>>>>>
>>>>
> http://www.linuxworks.com.au/redhat-installer-howto.html#s8
>
>>>>>and
>>>>>
>>>>
> http://rau.homedns.org/twiki/bin/view/Anaconda/CustomizingFedoraCore.
>
>>>>>>INFO: UTF-8 character encoding detected by
>>>>>
>>>>>locale
>>>>>
>>>>>
>>>>>>settings.
>>>>>> Assuming UTF-8 encoded filenames on
>>>>
>>>>source
>>>>
>>>>
>>>>>>filesystem,
>>>>>> use -input-charset to override.
>>>>>>mkisofs 2.01 (i686-pc-linux-gnu)
>>>>>>Scanning i386
>>>>>>Scanning i386/Fedora
>>>>>>Scanning i386/Fedora/base
>>>>>>Scanning i386/Fedora/rpms
>>>>>>Scanning i386/images
>>>>>>Scanning i386/images/pxeboot
>>>>>>Scanning i386/isolinux
>>>>>>Excluded by match: i386/isolinux/boot.cat
>>>>>>Using SYSTEM_CONFIG_SECURITYLEVEL000.;1 for
>>>>>>
>>>>>
> i386/Fedora/rpms/system-config-securitylevel-tui-1.3.12-1.i386.rpm
>
>>>>>>(system-config-securitylevel-1.3.12-1.i386.rpm)
>>>>>>Writing: Initial Padblock
>>>>
>>>>
>>>>
>>>>>>Start Block 0
>>>>>>Done with: Initial Padblock
>>>>
>>>>
>>>>
>>>>>>Block(s) 16
>>>>>>Writing: Primary Volume Descriptor
>>>>
>>>>
>>>>
>>>>>>Start Block 16
>>>>>>Done with: Primary Volume Descriptor
>>>>
>>>>
>>>>
>>>>>>Block(s) 1
>>>>>>Writing: Eltorito Volume Descriptor
>>>>
>>>>
>>>>
>>>>>>Start Block 17
>>>>>>Size of boot image is 4 sectors -> No emulation
>>>>>>Done with: Eltorito Volume Descriptor
>>>>
>>>>
>>>>
>>>>>>Block(s) 1
>>>>>>Writing: Joliet Volume Descriptor
>>>>
>>>>
>>>>
>>>>>>Start Block 18
>>>>>>Done with: Joliet Volume Descriptor
>>>>
>>>>
>>>>
>>>>>>Block(s) 1
>>>>>>Writing: End Volume Descriptor
>>>>
>>>>
>>>>
>>>>>>Start Block 19
>>>>>>Done with: End Volume Descriptor
>>>>
>>>>
>>>>
>>>>>>Block(s) 1
>>>>>>Writing: Version block
>>>>
>>>>
>>>>
>>>>>>Start Block 20
>>>>>>Done with: Version block
>>>>
>>>>
>>>>
>>>>>>Block(s) 1
>>>>>>Writing: Path table
>>>>
>>>>
>>>>
>>>>>>Start Block 21
>>>>>>Done with: Path table
>>>>
>>>>
>>>>
>>>>>>Block(s) 4
>>>>>>Writing: Joliet path table
>>>>
>>>>
>>>>
>>>>>>Start Block 25
>>>>>>Done with: Joliet path table
>>>>
>>>>
>>>>
>>>>>>Block(s) 4
>>>>>>Writing: Directory tree
>>>>
>>>>
>>>>
>>>>>>Start Block 29
>>>>>>Violación de segmento
>>>>>
>>>>>Why the fault here?
>>>>>
>>>>>
>>>>>
>>>>>>I tried the same with this:
>>>>>>mkisofs -J -p "user at mycompany.com" -P "Red Hat"
>>>>
>>>>-r
>>>>
>>>>
>>>>>-T
>>>>>
>>>>>
>>>>>>-V "Fedora Core 1 with updates disc2" -v -A
>>>>>
>>>>>"Fedora
>>>>>
>>>>>
>>>>>>Core Linux/i386 1" -o fedoracore1-disc2.iso i386
>>>>>>but I need the first image bootable !!!
>>>>>>
>>>>>>I am occuping the Fedora Core 2, I didnt change
>>>>>>anything, I just simple copy the first disk and
>>>>>
>>>>>try to
>>>>>
>>>>>
>>>>>>make it iso but I didnt work ...
>>>>>>
>>>>>>Any idea ?
>>>>>
More information about the Kickstart-list
mailing list