F33 , System wide failure

[Kostas Sfakiotakis]

Greetings ,

Well i have just managed to recover from a system wide failure ( aka the 
system wasn't booting , it was basically asking me to run journalctl -xb 
, whatever that is ) .


It would seem that F33 was failing to boot due to a damaged  var 
partition ( /dev/mapper/F31-F31Var ) and it was asking me to run e2fsck 
manually .


The question is can really a damaged var partition prevent the system 
from booting  ( any explanation on that would be greatly appreciated ) .

Although the system booted "normally" i got a message that the "Linux 
Kernel Module Init Script" failed to start .

Can someone explain to me in English what that thing is ( Am not sure i 
know the guy ) ???



Kind Regards,

Kostas

[Chris Murphy]

On Thu, Dec 10, 2020 at 1:59 PM Kostas Sfakiotakis
<kostassf(a)cha.forthnet.gr&gt; wrote:

>  It would seem that F33 was failing to boot due to a damaged  var
>  partition ( /dev/mapper/F31-F31Var ) and it was asking me to run e2fsck
>  manually .
>
>
>  The question is can really a damaged var partition prevent the system
>  from booting  ( any explanation on that would be greatly appreciated ) . 
If it can't mount, it does seem like systemd will indefinitely wait
for it to appear, unless that mountpoint has 'nofail' option in fstab.
The problem with that is, it's pretty much a required directory. Same
for /etc.


>  Although the system booted "normally" i got a message that
> the "Linux
>  Kernel Module Init Script" failed to start .
>
>  Can someone explain to me in English what that thing is ( Am not sure i
>  know the guy ) ??? 
Not sure. You got this message where/when?

-- 
Chris Murphy

[Kostas Sfakiotakis]

Στις 11/12/20 8:51 π.μ., ο/η Chris Murphy έγραψε:
>  On Thu, Dec 10, 2020 at 1:59 PM Kostas Sfakiotakis
>  <kostassf(a)cha.forthnet.gr&gt; wrote:
>
> > It would seem that F33 was failing to boot due to a damaged  var
> > partition ( /dev/mapper/F31-F31Var ) and it was asking me to run e2fsck
> > manually .
> >
> >
> > The question is can really a damaged var partition prevent the system
> > from booting  ( any explanation on that would be greatly appreciated ) .
>  If it can't mount, it does seem like systemd will indefinitely wait
>  for it to appear, unless that mountpoint has 'nofail' option in fstab.
>  The problem with that is, it's pretty much a required directory. Same
>  for /etc. 
Well it does seem that , such was the case . From the journal
it would seem that it was indeed trying to mount the partition ( /var
resides in a seperate LVM partition /dev/mapper/F31-F31Var ) but
it was failing and it was asking me to run e2fsck manually . OOOppsss
well that last part ( of /var being a mandatory directory . possibly for 
/var/log ?? )
was what i was afraid off .

> > Although the system booted "normally" i got a message
> that the "Linux
> > Kernel Module Init Script" failed to start .
> >
> > Can someone explain to me in English what that thing is ( Am not sure i
> > know the guy ) ???
>  Not sure. You got this message where/when? 
I might have a screenshot for it . It popped up during the boot process 
towards the
end .