Completely Locked Out of System After Update
- Login o registrati per inviare commenti
Hi All, I'm having a pretty serious issue and have run out of ideas.
I did a normal system update a couple days ago. This was pretty standard stuff, total download was about 55mb. No reboot required afterward.
However after I did reboot I am unable to gain access to the system. Here are the specifics:
1. The system boots to Grub with no issue, everything seems normal. I can use the keyboard to toggle between the normal boot option and advanced options (this is a Trisquel only system)
2. Under advanced options i am asked for my user name and password and am then kicked back to the Grub main screen. I cannot access a command line from Grub.
3. If I allow the system to boot normally it will go to the Trisquel login page, which seems a hair out of focus, and the whole page does not recognize inputs from either the mouse or keyboard...its like they are not plugged in. After a few minutes my energy settings kick in and the system goes to sleep with no way for me to wake it.
Has anyone seen a similar issue, and are there any ideas on how to fix it? I am inbetween backups and even though I wouldn't lose much, I'd prefer to lose nothing.
A bit of an update. i just tried to do a repair update using a livecd and I am getting "can't resolve" failed errors when trying to connect to the software sources, but i can confirm i have web access. Are there currently any issues with accessing updates?
Try changing your software sources. If you can't get to the GUI to do this,
edit /etc/apt/sources.list (as root) and replace all the references to the old
address with the new one. Give mirror.fsf.org a shot. I use it- it's a bit
slow, but reliable as hell. Never had any problems.
It is possible that the mirror you use to fetch packages is down.
As for the GRUB password, it is written in /etc/grub.d/01_PASSWORD, which you can read from any Live system. Not much of a security... and the GRUB developers agree that "requiring authentication at the boot loader level would only serve to make it difficult to recover broken systems" without adding any additional security in most cases: https://www.gnu.org/software/grub/manual/grub.html#Security
Assuming you can boot an older kernel from GRUB's "advanced options", you can then get rid of GRUB's password by commenting all lines of /etc/grub.d/01_PASSWORD (i.e., using with administrative privileges a text editor to have all lines begin with "#") and then executing 'sudo update-grub'.
Tell us whether an older kernel brings you a usable system. However, if you are certain that the kernel was not updated between the last non-problematic boot and the first problematic, then it must not be the problem. Maybe a hardware problem and you could test your RAM with memtest86+ and your partitions with SMART auto-tests.
- Login o registrati per inviare commenti