Hi all,

At boot, i've got this error mesage. But computer work perfectly. 
[bruno@ zeus ~]$ cat /run/66/log/0/current | grep fsck
2020-08-31 17:15:59.469170780  66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: system-fsck
2020-08-31 17:15:59.469172884  66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: system-fsck
2020-08-31 17:16:08.184346526  s6-rc: info: processing service system-fsck: starting
2020-08-31 17:16:08.189554077  [system-fsck] starts...
2020-08-31 17:16:08.197017880  e2fsck: Cannot continue, aborting.
2020-08-31 17:16:08.198993888  fsck reports errors -- at least system should be rebooted
2020-08-31 17:16:08.206379645  s6-rc: info: service system-fsck started successfully
2020-08-31 17:16:08.430082319  66-dbctl(src/lib66/ssexec_dbctl.c: check_status: 159): tracing: Write state file of: system-fsck
2020-08-31 17:16:08.430088030  66-dbctl(src/lib66/ssexec_dbctl.c: check_status: 165): info: Started successfully: system-fsck
My / is on a crypted partition with luks (no lvm).Formatted with ext4. No swap. first partition is the FAT EFI partition.
Using EFI bootloader with: 
cryptdevice=UUID=uuid-of-my-nvme0n1p2:cryptroot root=/dev/mapper/cryptroot ...
I think (i may be wrong) that the fsck service ask for a real device like /dev/nvme0n1p2 and not /dev/mapper/cryptroot.

The error "sck reports errors -- at least system should be rebooted" appear just before the /etc/issue file.
Was your system powered off normally or was there a powerfailure before this?

I would switch /etc/66/inic.conf into verb..=4 and reboot
If you execute # mount -a do you get any warnings/errors? Swap, is it working? # free
No crash, no power failure. Computer always poweroff after shutdown correctly.
mount -a report nothing. I do not use swap.
/run/66/log/0/current with verbose=4

fstab: 
# /dev/mapper/cryptroot
UUID=cd9c9a85-d563-4d0f-859b-7dd66a213d7a       /               ext4            rw,relatime     0 1

# /dev/nvme0n1p1
UUID=40B5-6E43          /boot           vfat            rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro       0 2

# /dev/sda1
UUID=70a2634d-e7ac-4356-b3f8-7a8c1cacf50a       /mnt/backup     ext4    noauto,rw,users,relatime        0       0

# /dev/sdc1 LABEL=Blender
LABEL=Blender           /home/bruno/blender     ext4    noauto,rw,users,relatime        0       3
I've booted my obarun install key and opened the crypt part with cryptsetup. Launched fsck on the ext4 uncrypted partition. No problem.
The partition may be mounted before fsck?
FYI, the first boot was problematic as the installer has not created the tree. I've created them manually. Maybe something wrong here...

EDIT: after third lecture of /run/66/log/0/current, something appeared to my eyes: 
/dev/mapper/cryptroot is mounted.
2020-08-31 21:03:03.424519225  e2fsck: Cannot continue, aborting.
My partition is mounted BEFORE fsck which IS the problem.
Do not mount your encrypted partition at kernel command line and edit your /etc/66/conf with CRYPTTAB=!yes. Obviously the /etc/crypttab file must and correctly set.
???
The crypted partition is my root /. I was thinking (may be wrong) that crypttab was only for secondary partition but not for /.
Will try tomorrow. I'm going to bed now, my brain need some sleep ;)
Solved! :)
Tried to remove the root=/dev/mapper/cryptroot from the boot command line. Computer need manual intervention. cryptsetup + fsck + mount /.
But if i remove the / entry from fstab, fsck is made with the initramfs and computer boot without error.
That makes sense because / is defined by the bootloader and where the kernel image is ...
Thank you fungal_net and eric.

Powered by Obarun