On 8/31/19 3:26 PM, Étienne Mollier wrote:
Perhaps you can attempt a boot in "Recovery Mode", see the
"Advanced Boot Options" at the Grub menu stage of the boot.
It could have a positive effect if a faulty kernel module is
loaded and causes this loop in the boot sequence. Maybe a check
of the memory and SMART data, if those options are available
from your BIOS, could be welcome, especially SMART since some
messages were mentioning checking the disk.
Thanks for idea. However, there is no Grub here, only Lilo. I will check
BIOS for options.
If operations here over do not make any difference, then you
really should consider creating a Rescue drive on an USB thumb.
I have had a good experience with SystemRescueCD over the years:
http://www.system-rescue-cd.org/
But if you have a Debian installation media, you can also
achieve a thing or two by booting on the "Rescue Mode".
Will try some of those. I have Debian installation media for 6.0.1 only
and unsure whether it would work with strech.
If you absolutely positively do not want to build a rescue
media, last chance option would be to edit the Grub menu entry,
and in the linux line, edit (or append if non-existent) the
following "init=" option (hit 'e' to edit the menu entry and F10
to boot):
linux root=UUID=[...] ro init=/bin/bash
This is a last chance option, do not expect your system to
operate properly without a regular init process. Boot in this
mode only to proceed to your investigations as of why the
machine fails to spawn the login process. Quitting this shell
hangs the machine; you have to hard reset.
As said, no Grub here. Is there similar option for Lilo?
Thanks!
Misko
