You are not logged in.
Hi all,
Last week-end I moved to systemd: everything run smooth.
I use to update my system every 1 or 2 days.
Yesterday I got new updates, some few files and a new linux-3.XXX version (sorry, I don't remember the serial).
I also run the lilo command to update the boot files as well (I am 99,99% sure about that).
This morning I realized my laptop is not booting: the small lillo window appears, I tries to boot, but then restarts the boot and the lilo window appears again.
So I don't know if:
1) I forgot or mistyped the lilo command yesterday (just 1% of probabilities)
2) Something is broken after so many changes with systemd and so on: must add that after runing into systemd I already did one "pacman -Syu" without any problem, a couple of days ago...
Frankly, I don't knw where to start checking...
Thanks,
Last edited by jmvidalvia (2012-10-18 05:43:06)
Offline
What you could do is chroot into your existing install.
Then take a look at your log files and try to find out what went wrong
You could aslo take a look at this page tuo edit LILO at boottime,
which you could also do when you're chrooted.
Offline
I'm not very familiar with lilo, but I'm not sure why you'd have to reconfigure it for a normal update.
It sounds like something is wrong in your lilo configuration and it isn't properly pointing to the kernel and/or boot partition.
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
Hi,
I chrooted and run lilo again, and the problem was solved.
Nevertheless, I cheked the bash history of my root user and confirmed that I indeed executed lilo after updating the system, so something wrong happened then to cause that problem.
Thanks,
Offline