Στις 11/12/20 8:51 π.μ., ο/η Chris Murphy έγραψε:
On Thu, Dec 10, 2020 at 1:59 PM Kostas Sfakiotakis
<kostassf@xxxxxxxxxxxxxxx> 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 .
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
