Re: 6.6.x kernels do not boot successfully

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> >         Starting systemd-fsck-root.service - File System Check on /dev/disk/by-uuid/8ff57a6b-2a55-4e9d-870d-855d-855d68d35bee...
> > [ OK ] Starting systemd-fsck-root.service - File System Check on /dev/disk/by-uuid/8ff57a6b-2a55-4e9d-870d-855d-855d68d35bee.
> >
> > I have to reboot and select older kernel 6.5.12-*fc39.x86_64
> >
> > Best Regards & Thank you for trying to help
> >
> > Antonio
> > --
>
> My guess (and that's all it is) is that something in /etc/fstab can't be
> mounted after the root filesystem. I'd try adding "noauto" to everything
> there except for "/," "/home," etc. Just mount the stuff you must have
> to get the system up. Also, maybe (???) set the last arg on the fstab
> lines to 0 rather than 1 or 2. Everyone on the list -- please comment on
> the last idea. I tried it on a cloud server and it didn't cause a
> problem, but better to have the experts here weigh in.
>
> * make a copy of fstab
>
> * make the edits to fstab
>

Systemd fstab needs nofail to not go to emergency shell (It is systemd
why would they honor the meaning of an option 30+ years old when they
can just make up a new option) .   nofail on all but critical
filesystems and "0 0" at the end should stop the fsck.  And I would
think the option should not have been nofail but either fail or
allowfail as nofail seems to be the opposite of what you really want.

Based on it failing/not fsck'ing I would think one of the filesystems
underlying device driver is broken in some manner.

The standard I use is "0 0" and nofail  (and implemented on 20k+
systems where I work) for all not required to boot up fs'es.  Job #1
is to get the machine up and on the network.  Having the machine
without network at emergency prompt only slows down the process of
fixing it (the ilo remote consoles suck, no cut-n-paste and random key
repeats, and only one person can work at a time).
--
_______________________________________________
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
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux