Bug 2156004

+++ This bug was initially created as a clone of Bug #2035641 +++

Please check the attached screenshot.

dracut-initqueue: mount: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error.
dracut: FATAL: failed to find a root filesystem on /run/initramfs/squashed.img.
dracutRefusing to continue.

--- Additional comment from Artem S. Tashkinov on 2021-12-26 11:09:06 UTC ---

The Cinnamon spin also doesn't work with the option. Let's try "vanilla".

--- Additional comment from Artem S. Tashkinov on 2021-12-26 11:20:18 UTC ---

The default workstation image (Fedora-Workstation-Live-x86_64-35-1.2.iso) doesn't boot with the same errors.

--- Additional comment from Artem S. Tashkinov on 2021-12-26 11:21:26 UTC ---

I've given the VM 8GB of RAM which should be plenty.

--- Additional comment from Artem S. Tashkinov on 2022-03-31 13:51:52 UTC ---

Does this package have maintainers? Anyone? Does anyone care? Is this a bug tracker or just a useless website no one attends to?

--- Additional comment from Pavel Valena on 2022-04-05 19:32:47 UTC ---

Fedora is a community project anyone can contribute to. Feel free to send a PR, if you think it's a packaging issue:
https://docs.fedoraproject.org/en-US/ci/pull-requests/

Also, there's a project upstream, in which you can help fix or file an issue:
https://github.com/dracutdevs/dracut/

Lastly, your bug report is missing a dracut version (nvr), proper steps to reproduce (apart from the subject - but come on, is it that hard to write it clearly, in case there's a new maintainer who tries to find his way? Not everyone is and expert.), and a sosreport would be helpful as well:
https://fedoraproject.org/wiki/How_to_debug_Dracut_problems

On the matter, my first guess would be that some executable might be missing for it to work - like the decompression algorithm. Feel free to experiment, add it, regenerate dracut and let us know!
Example:
https://github.com/dracutdevs/dracut/pull/1545/

--- Additional comment from  on 2022-04-09 06:33:05 UTC ---



--- Additional comment from  on 2022-04-09 06:34:39 UTC ---



--- Additional comment from  on 2022-04-09 06:36:10 UTC ---

Error appears to have been introduced between Fedora 32 and Fedora 33, and continues through Fedora 35.

dmsquash-live-root attempts to mount /run/initramfs/squashed.img and fails to mount because /run/initramfs/squashed.img created by rd.live.ram is corrupted in Fedora 33 (and 35). Manual attempts to mount from emergency mode with dmsquash-live-root generate the same errors.

Analysis of rd.live.ram created squashed.img files from Fedora 32, 33, and 35 Live Workstation disks show that Fedora 32 unpacks as expected with unsquashfs, but both Fedora 33 and Fedora 35 generate this error when analyzing the files offline:

# unsquashfs squashed.img 
Read on filesystem failed because EOF
FATAL ERROR: File system corruption detected

Fedora 35 is running dracut 055-5.fc35

I migrated ahead to dracut 56 (on Fedora 35) and it still has this issue. rdsosreports from Fedora 32 (expected behavior) and Fedora 35 (failure behavior) attached.

--- Additional comment from  on 2022-04-11 05:13:23 UTC ---

Disregard attachments - I discovered the underlying problem - those squashed.img files are truncated because ram disk space is full.

Fedora 32 only required *4 GB* for rd.live.ram (dracut 50).

Subsequent Fedora Workstation spins (33-36 Beta) require *10 GB* RAM.

What needs to be done to reduce memory usage on initial boot?

--- Additional comment from  on 2022-04-11 15:17:10 UTC ---

I ran livecd-creator to generate a 4 GB spin that previously required 8 GB RAM. Now it requires 20 GB RAM.

Compared with the above numbers, there's a 2.5x increase in RAM requirements, and supports Pavel's comment above, except it appears *compression* is missing. I looked but couldn't find where this occurs - any pointers will be appreciated to help resolve this.

--- Additional comment from Ben Cotton on 2022-11-29 17:33:07 UTC ---

This message is a reminder that Fedora Linux 35 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13.
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
'version' of '35'.

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

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 35 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 Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

--- Additional comment from Ben Cotton on 2022-12-13 16:11:23 UTC ---

Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13.

Fedora Linux 35 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 Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

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