Hi Thomas, Thanks for your email. My responses are inline to your mail below prefixed with VPK>>
Thanks,
VIjay
On Thu, Aug 1, 2024 at 3:47 PM Thomas Schmitt <scdbac...@gmx.net> wrote:
> Hi,
>
> if you reply to this mail, then please also o bug-grub@gnu.org, not only
> to me in private. (A private Cc to me is unnecessary but would be ok.)
>
>
> Vijay Kirpalani wrote:
> > I built a bootable ISO and have appended an ext2 disk partition in it.
>
> How exactly did you do it ?
>
VPK>> Here are the commands i used in the 2 step process:
*Step1:*
grub-mkrescue --modules="part_msdos part_gpt gzio ext2 iso9660" -o
final1.iso -d img0
I use the output of this command in step2 which i copy to my working folder
out-combine
which i use in below command.
*Step2:*
xorriso -as mkisofs \
-o final.iso \
-c boot.catalog \
-volid "MY_CUSTOM_LINUX" \
-b boot/grub/i386-pc/eltorito.img \
-no-emul-boot \
-boot-load-size 4 \
-boot-info-table \
-append_partition 2 \
0x83 disk.img \
-partition_cyl_align all=1 \
out-combine
> (Really the strange step1-step2 way which you show in your previous mail ?
> That would make an ISO which would boot only via Legacy BIOS and only
> from CD-ROM. Your disk.img would be in the ISO image as partition 2.)
>
> What do the following commands report ?
>
> path_to_iso=...path.to.your.ISO.image...
>
> xorriso -indev "$path_to_iso" -report_el_torito plain
> -report_system_area plain
>
VPK>> See the attached text file command_output.
>
> (Please send the output as text - not as screenshot - to this list:
> bug-grub@gnu.org )
>
>
> > I booted the ISO in Virtual Box.
>
> As what kind of device did you submit the ISO image to Virtual Box ?
> CD-ROM ? Hard disk ?
>
VPK>> when I created the VM, i provided the ISO file as input, and i also
had
virtual box create a virtual disk. which is what shows up hd0
in the grub
prompt when i do a "ls".
VPK>> The boot order is optical drive first and then harddisk.
>
>
> > During boot, i see grub is detecting the ext2 partition as part of cd
> drive
> > and as type Iso9660. To elaborate. on the grub command line when i do an
> ls
> > i get
> > (hd0), (cd), (cd,msdos2), (cd,msdos1).
> > when i do an ls on (cd,msdos1) it is showing as Iso9660 filesystem type.
>
> I am quite sure that GRUB would not mistake an ext2 for an ISO 9660
> filesystem.
> With the answers to above questions it should be possible to find out
> whether partition 1 is indeed the ISO 9660 filesystem or an ext2.
> (Or to propose runs of "dd | file" which then tells what is in the
> partitions.)
>
>
> > also, i was expecting my ext2 partition to be detected as part of hd0.
>
> Are you sure that (hd0) has anything to do with the ISO image ?
> Did you inquire its filesystem type and look at the files in it ?
>
> VPK>> When I do an "ls" on hd0 in the grub prompt it is gives a message No
known filesystem type detected,
as I indicated in the earlier part of the mail, that hd0 was
created by virtual box
VPK>> for a debian ISO that i downloaded, i see that there is an appended
partition that is
appended to hd0 --> (hd0,msdos1) an "ls" on (hd0,msdos1)
reveals it is a ext* partition.
i guess this is where it stores the root file system. I wanted
to emulate the same and have
my root filesystem in (hd0, msdos1).
VPK>> i am trying to build an ISO for my application environment that uses
a much older version of Debian
and it has dependency on Ruby, mysql....etc dependent libraries
that i need to include along with the OS.
>
> Have a nice day :)
>
> Thomas
>
>
command_output
Description: Binary data
