Dev1 Galaxy Forum / [SOLVED] persist initramfs fsck.log / persist the following output on disc fail

Re: [SOLVED] persist initramfs fsck.log / persist the following output on disc fail

dummy@example.com (fsmithred) — Fri, 06 Mar 2026 11:54:49 +0000

@onedevone,
Stop spreading FUD about refractasnapshot. It's not even relevant FUD. The OP's problem has nothing at all to do with refractasnapshot or the live isos.

Re: [SOLVED] persist initramfs fsck.log / persist the following output on disc fail

dummy@example.com (onedevone) — Fri, 06 Mar 2026 08:21:41 +0000

This is what permananently broke Refractasnapshot. If you create ISO with Refractasnapshot of your painstakingly configured system, then your ISO will not boot. Unfixable.

Re: [SOLVED] persist initramfs fsck.log / persist the following output on disc fail

dummy@example.com (grebulos) — Sun, 08 Feb 2026 22:28:21 +0000

Thank you!

Re: [SOLVED] persist initramfs fsck.log / persist the following output on disc fail

dummy@example.com (ralph.ronnquist) — Sun, 08 Feb 2026 21:33:00 +0000

Nothng to worry about.

TL;DR; The initial boot sequence includes a filesystem check of the root filesystem, and that results in a log file which at that time resides in RAM. Then the scripting for some reason gets confused when trying to store the log on disk. I'm guessing the script writer failed to consider the range of possible boot-up scenrios so ended up making the script lodging a spurious notice instead.

[SOLVED] persist initramfs fsck.log / persist the following output on disc fail

dummy@example.com (grebulos) — Sun, 08 Feb 2026 19:40:39 +0000

Immediately after installation from devuan_excalibur_6.1.0_amd64_netinstall.iso, the following two failures are shown in the boot process:

Sun Feb 08: 15:18:10 2026: Cannot persist initramfs fsck.log ... failed!
...
Sun Feb 08: 15:18:10 2026: Checking file systems...Cannot persist the following output on disc ... failed!

I have searched the web, but anything I found was in conjunction with an additional error/failure (like this here: https://dev1galaxy.org/viewtopic.php?id=7586) and these two were not addressed.

Is this something to worry about? And if so, what can be done to fix it?

Thanks for any suggestions.

Current disk layout:

nvme0n1
├─nvme0n1p1 vfat   FAT32       9D48-C8DC                             965.3M     1% /boot/efi
├─nvme0n1p2 ext4   1.0         2a1c42c6-75e1-43b3-b040-a5804f476b56      9G     9% /
├─nvme0n1p3 ext4   1.0         3fccc3db-8aac-40c9-aeef-f60ed632416b    3.6G     7% /var
├─nvme0n1p4 swap   1           dcdcc142-cb52-44dc-a485-7f587b4a354d                [SWAP]
└─nvme0n1p5 ext4   1.0         c5ab0730-631b-4dfb-a186-d3c0fd74ef03   95.1G     0% /srv