kernel 4.19.6-300.fc29.x86_64 does not boot

[François Patte]

Bonjour,

The last kernel 4.19.6-300.fc29.x86_64 on my f29 does not boot: after a
long stop at "reached target basic system", the boot stops with this
message (repeated many times):

dracut-initqueue timeout starting timeout scripts

then an emergency shell is opened

then what can I do?

Thank you.

-- 
François Patte
UFR de mathématiques et informatique
Laboratoire CNRS MAP5, UMR 8145
Université Paris Descartes
45, rue des Saints Pères
F-75270 Paris Cedex 06
Tél. [phone]
http://www.math-info.univ-paris5.fr/~patte

[Samuel Sieb]

On 12/10/18 3:24 AM, François Patte wrote:
>  The last kernel 4.19.6-300.fc29.x86_64 on my f29 does not boot: after
> a
>  long stop at "reached target basic system", the boot stops with this
>  message (repeated many times):
>  
>  dracut-initqueue timeout starting timeout scripts
>  
>  then an emergency shell is opened 
That often means that dracut can't find the root filesystem.  Are there 
any differences between the kernel lines in the grub config file other 
than just the version?

[François Patte]

Le 10/12/2018 à 17:17, Samuel Sieb a écrit :
>  On 12/10/18 3:24 AM, François Patte wrote:
> > The last kernel 4.19.6-300.fc29.x86_64 on my f29 does not boot: after a
> > long stop at "reached target basic system", the boot stops with this
> > message (repeated many times):
> >
> > dracut-initqueue timeout starting timeout scripts
> >
> > then an emergency shell is opened
>  
>  That often means that dracut can't find the root filesystem.  Are there
>  any differences between the kernel lines in the grub config file other
>  than just the version? 
One more time your clue is the good one! For an unknown reason the
installation of the new kernel wrote a wrong grub.cfg pointing as the
root partition an unused partition on my system.... Strangely when I run
grub2-mkconfig this was corrected. I cannot understand why the
installation script of the kernel has made this mistake.

Thank you.

-- 
François Patte
UFR de mathématiques et informatique
Laboratoire CNRS MAP5, UMR 8145
Université Paris Descartes
45, rue des Saints Pères
F-75270 Paris Cedex 06
Tél. [phone]
http://www.math-info.univ-paris5.fr/~patte

[Tim]

Allegedly, on or about 11 December 2018, François Patte sent:
>  For an unknown reason the installation of the new kernel wrote a
>  wrong grub.cfg pointing as the root partition an unused partition on
>  my system.... Strangely when I run grub2-mkconfig this was corrected.
>  I cannot understand why the installation script of the kernel has
>  made this mistake. 
On some motherboards, when you boot from removable media, all the other
drives get a different drive number than when you don't boot from it.

-- 
[tim@localhost ~]$ uname -rsvp
Linux 4.16.11-100.fc26.x86_64 #1 SMP Tue May 22 20:02:12 UTC 2018 x86_64

Boilerplate:  All mail to my mailbox is automatically deleted.
There is no point trying to privately email me, I only get to see
the messages posted to the mailing list.

This email tagline has been Australianised.  Bloody oath...

[François Patte]

Le 11/12/2018 à 08:12, Tim via users a écrit :
>  Allegedly, on or about 11 December 2018, François Patte sent:
> > For an unknown reason the installation of the new kernel wrote a
> > wrong grub.cfg pointing as the root partition an unused partition on
> > my system.... Strangely when I run grub2-mkconfig this was corrected.
> > I cannot understand why the installation script of the kernel has
> > made this mistake.
>  
>  On some motherboards, when you boot from removable media, all the other
>  drives get a different drive number than when you don't boot from it. 
I don't understand your remark: I didn't boot on a removable media, I
just updated my system using dnf....

-- 
François Patte
UFR de mathématiques et informatique
Laboratoire CNRS MAP5, UMR 8145
Université Paris Descartes
45, rue des Saints Pères
F-75270 Paris Cedex 06
Tél. [phone]
http://www.math-info.univ-paris5.fr/~patte