i haven't missed anything, you're inventing a scenario based on fragments of knowledge and assumptions. > is there a mysterious set of commands they came up wi

i haven't missed anything, you're inventing a scenario based on fragments of knowledge and assumptions. > is there a mysterious set of commands they came up with to skip an fsck the final sentence of the opening post. > I am fully aware that the OP wants to cancel the fsck(8) in progress well then why are you offering a priori fixes? > Instead, to prevent additional filesystem checks, there are tools to make this possible of course there are, but this is entirely irrelevant to the discussion at hand. > The concept of "going back in time" during an active check, to change a kernel parameter, so it doesn't start to begin with is a strange one. no strange, impossible. this is my point. ok, imagine, someone had been in a car accident, and fractured their skull on the window because they weren't wearing their seatbelt. this discussion is akin to a doctor telling the patient (or whoever) that they could wear a seatbelt, and then this wouldn't have happened. just wear a seatbelt in future and you wont fracture your skull. just change the fsck counter/add a kernel boot parameter and fscks wont happen.