fsck: recovering journal every reboot [Solved]

[Blaze]

Seems this issue with aufs https://aufs.sourceforge.net/

[rych]

porteux, could you release PorteuX 0.5 with new /sbin/init, kernel 6.2.11, and Nvidia driver 535.85.25 -- which promises to be the best working combination for now?

[beny]

hi porteux current in text mode work as usual with the 6.3.9 kernel, clean reboot and clean shutdown,i have only upgraded the gcc to the current version in devel package.

[porteux]

@rych, it would be a bit frustrating to release PorteuX 0.5 with 2 main packages older than PorteuX 0.4, but yes, maybe we can do that. Or for now I can share with you guys just the fixed initrd, kernel and Nvidia driver. What you think?

Speaking of Nvidia driver, it's interesting that you mentioned this specific version (I couldn't find it here: https://download.nvidia.com/XFree86/Linux-x86_64/). On my machine 525.85.05 is the newest version that doesn't show artifacts, so I'm stuck on it. These new 535.xx.xx are the worse: https://v.redd.it/link/1450z8m/asset/cn ... SH_720.mp4

@beny, PorteuX 0.4 is not unmounting /union properly and this issue only appears if you have PorteuX in an EXT partition and use 'fsck' cheatcode. Also, regardless if you're running the upcoming PorteuX 0.5 or Porteus 5, kernel 6.3.x seems to have a bug where the system fails to unmount /union -- well, on my machine it fails only if I use Nvidia drivers (using nouveau it works).

[porteux]

Here we go (just initrd, kernel and nvidia driver):

https://www.mediafire.com/file/itrm9ga4 ... 0.5rc1.zip

[rych]

porteux, well if you recompiled /sbin/init fixing the issue of this thread -- I guess I could replace just that file? Also I'll take this:

1- I fixed the union unmount step that was missing in PorteuX -- to be released in 0.5 version. This fixes the 'clearing orphaned inode' messages, but unfortunately it doesn't fix the 'recovering journal' ones.

As for the kernels and Nvidia, "interesting that you mentioned this specific version" -- I was quoting from the other thread you linked:
Porteus Kernel Builder (Post by fulalas #94602) :

I noticed that since 6.3.x systems with Nvidia card don't shutdown/reboot properly (i.e. union is mounted as read-only because it fails to unmount).
The issue doesn't seem to be in the .config file or the Nvidia driver. That's what I did using the same .config file in all builds:
kernel 6.2.11 -> it shuts down/reboots properly with Nvidia driver 535.85.25 and 535.43.02
...

From which I deduced a working combination would be the rebuilt /sbin/init + kernel 6.2.11 + Nvidia driver 535.85.25. Right? Or just give me something that works best at the moment and I'll continue testing

[rych]

Here we go (just initrd, kernel and nvidia driver):

Oh thanks, will try that tomorrow (if the link actually works)

[rych]

this specific version (I couldn't find it here

must be a typo then, not 535.85.25 but 525.85.05 ?

[porteux]

this specific version (I couldn't find it here

must be a typo then, not 535.85.25 but 525.85.05 ?

Yes, a typo.

The link works, but it looks odd with '...' in the middle.

[rych]

Here we go (just initrd, kernel and nvidia driver):

With the new files, the problem remains exactly the same: "recovering journal" and "clearing orphaned inode" on the next reboot.

All I did was to boot PorteuX 5.0rc1 and shutdown with whatever changed saved on EXIT in an ext4 /changes folder. A second longer delay at shutdown but still not clean. Rebooting with fsck (into the Porteus 5.0) found orphaned inodes and recovered journal on the porteux partition only.

Booting with

Code: Select all

	set porteus_parms="changes=EXIT:/porteux login=root fsck load=1920x1080 vga_detect"
	linux   /boot/syslinux/vmlinuzX $porteus_parms
	initrd /boot/syslinux/initrd.zst

Have to rename vmlinuz-> vmlinuzX because these share the EFI partition with the Porteus5.0, but the new initrd.zst and vmlinuzX are different now and are taken from 05rc1:

Code: Select all

root@porteus:/mnt/sda1/boot/syslinux# ls -la initrd* vmlinuz*
  922616 Dec 15  2022 initrd.xz*
1031992 Jun 24 21:36 initrd.zst*
1034951 May 19 10:05 initrdOLD.zst*
6131200 Dec 24  2022 vmlinuz*
9513696 Jun 26 23:26 vmlinuzX*
9354624 May 22 17:37 vmlinuzXOLD*

Kernel module also:

Code: Select all

root@porteus:/mnt/sda2/porteux/base# ls -la
110092288 Jun 26 23:43 000-kernel-6.2.16.xzm*
146223104 May 20 13:21 001-core-stable-20230520.xzm*
126283776 May 20 13:36 002-xorg-stable-20230520.xzm*
 23130112 May 20 13:50 002-xtra-stable-20230520.xzm*
 10371072 May 22 23:51 003-lxde-0.10.1-stable-20230520.xzm*

Please tell me what looks wrong and what next to try. I'm pleased it solved it for you but unfortunately not for me. Or am I missing something?

[porteux]

@rych, you're not missing anything. I made a stupid mistake and completely forgot to include the magic ingredient: static /sbin/init

https://www.mediafire.com/file/ts0jwco6 ... 6_64-1.xzm

It should work now!

[rych]

porteux, thank you it works now: a clean shutdown, fsck finds no problems on reboot. [Solved]