Marking as won't fix. No reaction since >1 year. Feel free to reopen the 
bugreport if you explore the bug again.

thanks && regards,
-mika-

* eModul <bts@bts.grml.org> [20071220 12:16]:

> By installing grml on a harddisk with an already existing vfat partition grml2hd
> realised the existence of the partition and installed the system after
> formatting it as ext3. But it didn't change the partition table, so there was no
> way to boot from the freshly installed grml system. I would expect grml2hd to
> change the partition id accordingly instead of leaving it as a fat partition in
> the partition table.
> Furthermore the bootable flag hasn't been set to the partition, so the installed
> grub in the partition could not be found during the booting process (lilo would
> have been found either).

Good catch, thx. Though I do not really like touching the disk and
setting the partition type "manually" - especially as grml2hd itself
does not provide any partitioning procedure. So I think this will
become a warning/error message instead. :)

What I don't understand right now is why the check:

 fdisk -l 2>/dev/null | grep $PARTITION | grep -qe 'Linux$' -qe 'Linux LVM$' -qe 'Linux raid autodetect$' && RC=0

seems to fail on your system. Can you please provide the output of
'fdisk -l' on your system?

regards,
-mika-.

By installing grml on a harddisk with an already existing vfat partition grml2hd
realised the existence of the partition and installed the system after
formatting it as ext3. But it didn't change the partition table, so there was no
way to boot from the freshly installed grml system. I would expect grml2hd to
change the partition id accordingly instead of leaving it as a fat partition in
the partition table.
Furthermore the bootable flag hasn't been set to the partition, so the installed
grub in the partition could not be found during the booting process (lilo would
have been found either).

Digging through the code of grml2hd in hg.grml.org I could not find any
functions assigned to these tasks.