Skip to main content ↑ ↓
Topic: Bootloop failure due to fsck... (Read 130 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Bootloop failure due to fsck...

Hi again. There is a really big problem when using OpenRC in current configuration. I often lose power due to shitty electrical installation at my building, it just cuts off. The thing is - Whenever there's powerloss, ext4.fsck is triggered automatically on boot, most of the time it is just trivial journal stuff, but sometimes fsck can't correct it and then OpenRC aborts booting altogether. I had to boot off USB drive and check it manually myself. I've disabled fsck from boot as a temporary solution, but this isn't ideal. ;/

This is really bad and shouldn't be a default way of handling things, we should think of a way to stop execution and tell the user to either boot anyway or forcibly check the drive... Or something else, I don't know, but bootlooping is not the way to do it.
Log:
Spoiler (click to show/hide)
 

Re: Bootloop failure due to fsck...

Reply #1 –
In /etc/conf.d/fsck you could set fsck_abort_on_errors="NO"
Then the boot should continue regardless of any errors. If it's the rootfs with the errors though YMMV.
I wouldn't want to do this myself. I'd prefer to boot into a Live iso or another Linux sytem on another partition and fix it there.

If you are regularly getting little 'blips' of no power rather than it going  off for long periods then maybe a ups powerstrip would be a good idea?