Its not everyday that I have the honor of talking to an actual developer for a GNU utility. I am extremely lucky, grateful and honored to have your input on my problem. Thank you so much for that.
The idea of using multi-session to add the file to the ISO image is genius by the way.
There is however one problem I am facing:
The super-block is getting corrupted somehow, and that too in a very weird way. I will explain later.
So first, this is the command that I ran:
xorriso -dev Fedora-Workstation-Live-x86_64-31-1.9.iso -boot_image any keep -map /home/sreyan/anaconda-ks.cfg /isolinux/anacondaks.cfg
It ran perfectly, but when I tried mounting the now modified ISO image by double clicking in GNOME File Manager which uses GNOME Disks to mount ISO files I get the error:
Error mounting /dev/loop0p1 at /run/media/sreyan/Fedora-WS-Live-31-1-9:
can't read superblock on /dev/loop0p1
can't read superblock on /dev/loop0p1
Screenshot here: https://imgur.com/a/wLktqsp
Now is where it gets weird.
I thought that the image was completely corrupted but I wanted to check if I could mount it via command line, so I did:
sudo mount -t iso9660
Fedora-Workstation-Live-x86_64-31-1.9.iso /mnt
Weirdly, no errors. I went to the /mnt directory and I could browse all my files and even verified that the file that I added in was actually added in.
I also ran isovfy on my modified image, again it reported no errors.
So I printed out some diagnostic information of the ISO using the command that you shared, I did not know any other way:
xorriso -indev
Fedora-Workstation-Live-x86_64-31-1.9.iso
-report_el_torito plain -report_system_area plain
I did this on both the original untouched ISO and the modified one.
The only relevant differences I could find where:
In Original:
El Torito catalog : 42 1
In Modified:
El Torito catalog : 942111 1
In Original:
Media summary: 1 session, 942080 data blocks, 1840m data, 20.3g free
In Modified:
Media summary: 1 session, 942113 data blocks, 1840m data, 20.3g free
To rectify this I tried certain variations of the command you shared:
xorriso -dev Fedora-Workstation-Live-x86_64-31-1.9.iso -boot_image any keep -rom_toc_scan "on:emul_wide" -map /home/sreyan/anaconda-ks.cfg /isolinux/anacondaks.cfg
xorriso -dev Fedora-Workstation-Live-x86_64-31-1.9.iso -boot_image any keep -md5 off -map /home/sreyan/anaconda-ks.cfg /isolinux/anacondaks.cfg
xorriso -dev Fedora-Workstation-Live-x86_64-31-1.9.iso -boot_image any keep -md5 off -rom_toc_scan on:emul_wide -map /home/sreyan/anaconda-ks.cfg /isolinux/anacondaks.cfg
But none of the above worked, I kept getting the same error.
Can you please help me ?
What am I doing wrong ?
Thanks again.
On Tue, Apr 7, 2020 at 11:10 PM Thomas Schmitt <scdbackup@xxxxxxx> wrote:
Hi,
i wrote:
> The resulting ISO will grow by the size of the whole ISO directory tree
> and the size of the data files which get added.
Clarification:
"size of the whole ISO directory tree" means the size of the meta-data,
not the size of the data files in the tree.
The meta-data in Fedora-Workstation-Live-x86_64-31-1.9.iso are very small,
because there are very few files in the tree.
Adding a text file of a few hundred bytes yielded a growth of 393216 bytes.
Have a nice day :)
Thomas
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Regards,
Sreyan Chakravarty
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx