Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1659758 - livecd-iso-to-disk cannot create non-fat overlay
Summary: livecd-iso-to-disk cannot create non-fat overlay
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: livecd-tools
Version: 33
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Neal Gompa
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-12-16 07:07 UTC by Karel Volný
Modified: 2021-05-29 19:14 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-27 20:29:20 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Karel Volný 2018-12-16 07:07:38 UTC
Description of problem:
Trying to create bootable USB stick with KDE live and some additional tools, I have run into filesystem limit of 4 GB. However, I am unable to force different filesystem.

Reading --help, there is:

    --msdos
        Forces format to use the msdos (vfat) filesystem instead of ext4.

but in reality, it defaults to vfat and any option to force ext4 (or anything else) is missing ...


Version-Release number of selected component (if applicable):
livecd-iso-to-mediums-26.1-1.fc29.x86_64

How reproducible:
always

Steps to Reproduce:
1. livecd-iso-to-disk --format --reset-mbr --efi --overlayfs ./Fedora-KDE-Live-x86_64-29-1.2.iso /dev/sdb
2. livecd-iso-to-disk --format --reset-mbr --efi --overlay-size-mb 8192 ./Fedora-KDE-Live-x86_64-29-1.2.iso /dev/sdb

Actual results:
1.
        ALERT:
        If the target filesystem is formatted as vfat or msdos, you must
        specify an --overlay-size-mb <size> value for an embedded overlayfs.

        Exiting...

2.
        ALERT:
        An overlay size greater than 4095 MiB
        is not allowed on VFAT formatted filesystems.


Expected results:
no such errors, operation continues

Additional info:

Comment 1 Frederick Grose 2018-12-25 06:57:39 UTC
What --help fails to mention is that in this script --efi specifies a GUID partition table with a fat filesystem.  This script currently only formats a single partition on the target device, and /EFI/BOOT/ must be on a fat filesystem.

If UEFI booting is required on a system, and you want an overlay larger than the fat limit of 4095 MiB, the USB stick could be manually partitioned with a small EFI System Partition for /EFI/BOOT/ components and a second ext4 formatted partition for the other LiveOS components (/images, /LiveOS, /syslinux, ...).  The grub.cfg would need to reference the UUID's of the second partition and the overlay directory/file name would need to bear the second partition's name and UUID.

If legacy MBR booting is available, the following script should work to give you a USB stick with an OverlayFS overlay the size of the ext4 formatted disk.

 livecd-iso-to-disk --format --reset-mbr --overlayfs ./Fedora-KDE-Live-x86_64-29-1.2.iso /dev/sdb

Comment 2 Ben Cotton 2019-10-31 20:15:48 UTC
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '29'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 29 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Ben Cotton 2019-11-27 20:29:20 UTC
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 4 Radka Gustavsson 2020-04-29 20:39:33 UTC
I believe that this is very valid issue that would make this tool a magical wand on modern systems. EFI is a must have, while VFAT is a must get rid of. Using the --efi option with overlay or home systems above 4g should be a standard. Either >4g or efi is very silly restriction.

In the ideal world it would default to creating efi with separate partitions for data and boot, as necessary.

Comment 5 Frederick Grose 2020-04-30 03:02:14 UTC
I'm working on this now and will soon submit a pull request to https://github.com/livecd-tools/livecd-tools for testing & evaluation. The MacIntel boot path is probably broken and could use the help of some experienced developers.

Comment 6 Ben Cotton 2020-08-11 13:05:42 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 33 development cycle.
Changing version to 33.

Comment 7 Mikel Pérez 2021-05-29 16:33:28 UTC
(In reply to Frederick Grose from comment #5)
> I'm working on this now and will soon submit a pull request to
> https://github.com/livecd-tools/livecd-tools for testing & evaluation. The
> MacIntel boot path is probably broken and could use the help of some
> experienced developers.

how'd that go? hope you get it merged because definitely there's an audience for it
this bug is still valid as of Fedora 34

Comment 8 Frederick Grose 2021-05-29 19:14:23 UTC
See https://github.com/livecd-tools/livecd-tools/pull/176  Testing, comments would be appreciated.


Note You need to log in before you can comment on or make changes to this bug.