The officially official Devuan Forum!

grebulos

Member

Registered: 2026-02-07

Posts: 7  

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

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

ralph.ronnquist

Administrator

From: Battery Point, Tasmania, AUS

Registered: 2016-11-30

Posts: 1,686  

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

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.

grebulos

Member

Registered: 2026-02-07

Posts: 7  

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

Thank you!

onedevone

Member

Registered: 2026-01-01

Posts: 13  

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

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

fsmithred

Administrator

Registered: 2016-11-25

Posts: 2,917  

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

@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.

Deiwah8y

Member

Registered: 2026-05-17

Posts: 1  

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

You have this problem, if your /var is a mount point.
It's not mounted yet during initscripts execution.
I use these patches to fix:

--- /etc/init.d/checkroot.sh
+++ /etc/init.d/checkroot.sh
@@ -175,7 +175,9 @@
 	then
 		rootcheck=no
 		# logsave_best_effort but do not display again
-		if [ -x /sbin/logsave ] && [ -e "${FSCK_LOGFILE}" ]; then
+		if [ -w "${FSCK_LOGFILE}" ]; then
+			cp /run/initramfs/fsck.log "${FSCK_LOGFILE}"
+		elif [ -x /sbin/logsave ]; then
 			logsave -s "${FSCK_LOGFILE}" >/dev/null \
 			    cat /run/initramfs/fsck.log
 		else

--- /usr/lib/init/mount-functions.sh
+++ /usr/lib/init/mount-functions.sh
@@ -727,7 +727,9 @@
 # This function does not actually belong here; it is duct-tape solution
 # for #901289.
 logsave_best_effort() {
-	if [ -x /sbin/logsave ] && [ -e "${FSCK_LOGFILE}" ]; then
+	if [ -w "${FSCK_LOGFILE}" ]; then
+		"$@" | tee "${FSCK_LOGFILE}"
+	elif [ -x /sbin/logsave ]; then
 		logsave -s "${FSCK_LOGFILE}" "$@"
 	else
 		log_failure_msg "Cannot persist the following output on disc"

greenjeans

Member

Registered: 2017-04-07

Posts: 1,657  

Website

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

@onedevone, funny I used Refracta-Snapshot just a couple days ago for like the oh, 1000th time or better, and it worked perfectly (as always) and have multiple users right now using that iso live for testing purposes.

I'm guessing user error is the issue, perhaps if you explain the process you used (in another thread, let's not get too off-topic in this one), then someone may be able to help you?

---

https://sourceforge.net/projects/vuu-do/ Vuu-do GNU/Linux, Devuan-based Openbox systems.
Devuan 6 mate-mini iso, pure Devuan, 100% no-vuu-do, mostly
Please donate to support Devuan and init freedom! https://devuan.org/os/donate
https://devuanusers.com/