How to stop systemd or whatever does, to always tries to check and fix disk errors

[Keith]

On 6/19/23 5:44 PM, Mario Marietto wrote:
> Hello.
> 
> I would like to upgrade the kernel and I want to enable KVM on my old 
> but still functional "Samsung Chromebook ARM model XE303C12 SNOW" 
> because later I want to virtualize FreeBSD with qemu and kvm. I've 
> started following this tutorial :
> 
> 
> *http://www.virtualopensystems.com/en/solutions/guides/kvm-on-chromebook/* <http://www.virtualopensystems.com/en/solutions/guides/kvm-on-chromebook/>
> 
> 
> As you can see,they used Ubuntu 13.04 as userland. No,I don't want to 
> run such an old ubuntu version ! Actually my problem is that only 2 
> times over 10 tries my chromebook is able to boot correctly with the 
> same setup. I've also completely erased the sd card with sudo dd 
> if=/dev/zero of=/dev/mmcblk1 status=progress bs=2M but very rarely it 
> wants to boot. I don't understand where the error is. When I insert the 
> sd card into the slot it beeps and it prepares itself to boot chrome OS 
> from the internal memory,not Linux from the sd card.
> 
> The problem could be systemd or whatever does that,to check and fix disk 
> errors because it does not support natively chrome os disk partitions 
> flags. So it may break those flags after the first boot. So,I want to 
> ask if there is a method that stops systemd or whatever to check and fix 
> disk errors. Thanks.
> 
> -- 
> Mario.
> 

use "fsck.mode=skip" as a kernel parameter to bypass all filesystem 
checks at boot time.

systemd-fsck-root.service (8)

-- 
Keith