0

Apparently, ubuntu 18.04 has decided to make system changes without asking.

One of these was a change from Grub2 64 bit which was fine, to shim which has now locked up my computer and made it unusable. Login does not work. Boot gives error message "failed to set moklistrt"

Since I can not login, how can I use live boot cd to repair this?

karel
  • 114,770
CPUDave
  • 1
  • Forgot to include running on AMD 8300 8 cores, 240 GB SSD, 16 GB ram, /home on 3 TB hd. – CPUDave Jun 10 '21 at 18:40
  • I didn't get this change on my 18.04 UEFI system. There was a grub-efi-amd64* update on 6/4, but it did not cause any problems. – Organic Marble Jun 10 '21 at 20:19
  • Thanks, not sure what is wrong here but even a full grub-install did not fix it. When booting, I do not get a boot menu screen, it just goes straight to the error, then boots ubuntu and the login screen comes up but I can not login, it just reloads the login screen again.. – CPUDave Jun 11 '21 at 17:31
  • Did a complete reinstall, the same problem. I did leave out an important bit of information. The /home directory is reassigned to a partition on another drive in fstab 18.04 new install boots with /home on the new drive but the problem appears again when /home in fstab is pointed to the old /home partition. – CPUDave Jun 13 '21 at 02:03
  • Please edit your question and include the full output of sudo blkid and the full contents of /etc/fstab/. – Organic Marble Jun 13 '21 at 02:41
  • Sounds like a problem in your "hidden" files (those beginning with a dot). See https://askubuntu.com/questions/916991/login-loop-on-admin-account-guest-works-fine/916999#916999 – ubfan1 Jun 13 '21 at 04:10
  • Thanks Organic Marble: As soon as I can get it uploaded. Do not have network access from shell nor will flash drives work. – CPUDave Jun 16 '21 at 23:56
  • Was not able to provide requested info due to that computer not having internet connection. – CPUDave Jun 29 '21 at 17:47
  • Resolved problem by complete new install, including overwriting /home and all files. The cause in this case was in copying files from another computer, the ownership, group, etc. were corrected but it still would not boot. Apparently, something in the xconfig was not right although the Xauthority etc, was fixed. – CPUDave Jun 29 '21 at 17:50

0 Answers0