cant get back to grub. stuck at grub rescue because of 32bit uefi

[supa1234]

hi i have a asus t100taf, it has a baytrail cpu.

i did a sudo apt-get dist-upgrade and it ended up messing up grub. so i can only get into the system with a recovery usb.  Because if i try to boot regularly i will end up at grub resucue.

this is the code i get when i try to run sudo apt-get grub-efi:

Code:

apt-get install --reinstall grub-efi
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
  grub-efi-amd64
The following packages will be REMOVED:
  grub-gfxpayload-lists grub-pc
The following NEW packages will be installed:
  grub-efi grub-efi-amd64
0 upgraded, 2 newly installed, 2 to remove and 4 not upgraded.
Need to get 49.4 kB of archives.
After this operation, 419 kB disk space will be freed.
Do you want to continue? [Y/n] y
Ign:1 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 grub-efi-amd64 amd64 2.06-2ubuntu14.4
Ign:2 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 grub-efi amd64 2.06-2ubuntu7.2
Ign:1 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 grub-efi-amd64 amd64 2.06-2ubuntu14.4
Ign:2 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 grub-efi amd64 2.06-2ubuntu7.2
Ign:1 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 grub-efi-amd64 amd64 2.06-2ubuntu14.4
Ign:2 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 grub-efi amd64 2.06-2ubuntu7.2
Ign:1 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 grub-efi-amd64 amd64 2.06-2ubuntu14.4
Err:2 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 grub-efi amd64 2.06-2ubuntu7.2
  Temporary failure resolving 'archive.ubuntu.com'
Err:1 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 grub-efi-amd64 amd64 2.06-2ubuntu14.4
  Temporary failure resolving 'archive.ubuntu.com'
E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/g/grub2-unsigned/grub-efi-amd64_2.06-2ubuntu14.4_amd64.deb  Temporary failure resolving 'archive.ubuntu.com'
E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/g/grub2/grub-efi_2.06-2ubuntu7.2_amd64.deb  Temporary failure resolving 'archive.ubuntu.com'
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

[WytWun]

hi i have a asus t100taf, it has a baytrail cpu.

i did a sudo apt-get dist-upgrade and it ended up messing up grub.

When you attempt to boot normally, do you get a

Code:

grub>

prompt?  If so, the first part of this post may be helpful, particularly the grub recovery link.  Ignore the "Observations:" section of that posting as that is unrelated to the grub issue.

I'm sorry I can't help you with the apparently broken state of your apt configuration as I've never gotten into that situation.

[stevef]

so i can only get into the system with a recovery usb

Does this mean you boot from a recovery usb and then somehow boot the system that is installed on the hard disk ?

It seems you have experience of installing a 64bit OS on a 32bit UEFI.
If you are confident that running the 'apt-get install --reinstall grub-efi' command will fix the issue then we can look at the mechanics of the problem.

The system seems to be unable to find the required files - it reports not being able to resolve the name 'archive.ubuntu.com'

To check the name resolution and connectivity, open a terminal with Ctrl Alt and T
Execute this command at the prompt.

Code:

ping -c 5 archive.ubuntu.com

The expected good response is that the system will convert the server name to an address and then send 5 test packets which should elicit 5 responses from the server and report this with some statistics.  If ok the number of packets transmitted will equal the number of packets received.  If not ok, there is something wrong, so report back with the response.

If the response is ok, the next step would be to try pasting this link into a browser.
http://archive.ubuntu.com/ubuntu/pool/ma...-unsigned/

This should show you a file list - if not let us know what happens instead.

If you can see a file list check that 'grub-efi-amd64_2.06-2ubuntu14.4_amd64.deb' is listed.  If it is listed then we need to dig a bit deeper.


If you are NOT confident that running the 'apt-get install --reinstall grub-efi' command will fix your issue then we need to look at how to fix the grub rescue in another way.

[supa1234]

I don't get grub>

i get grub rescue> when i try to boot without a usb rescue stick. the exact error is: "error: 'grub_is_lockdown' not found. entering rescue mode...

[quote author=supa1234 link=topic=9497.msg61620#msg61620 date=1706777681]
hi i have a asus t100taf, it has a baytrail cpu.

i did a sudo apt-get dist-upgrade and it ended up messing up grub.

When you attempt to boot normally, do you get a

Code:

grub>

prompt?  If so, the first part of this post may be helpful, particularly the grub recovery link.  Ignore the "Observations:" section of that posting as that is unrelated to the grub issue.

I'm sorry I can't help you with the apparently broken state of your apt configuration as I've never gotten into that situation.
[/quote]

[supa1234]

yeah i used super grub2 disk (i guess its similar to boot repair) but what it does is it, searches for all the boot methods on the machine and then i can click on one of the options with the kernel for linux lite and then it will boot like normal. but once i get inside the OS, i can't fix grub to be able to boot without the super grub2 disk.

also the ping worked and sent me back 5 packets and also the link worked in the browser and i was able to see the grub-efi-amd64_2.06-2ubuntu14.4_amd64.deb it is listed.

this is my fdisk -l result:

Code:

Disk /dev/mmcblk2: 29.12 GiB, 31268536320 bytes, 61071360 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: D949E4DF-28F3-4AED-AB32-9AAB0FDC7179

Device           Start      End  Sectors  Size Type
/dev/mmcblk2p1    2048  1050623  1048576  512M EFI System
/dev/mmcblk2p2 1050624 61069311 60018688 28.6G Linux filesystem


Disk /dev/mmcblk1: 59.48 GiB, 63864569856 bytes, 124735488 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xde2a0d45

Device         Boot     Start       End   Sectors  Size Id Type
/dev/mmcblk1p1 *         2048 120477695 120475648 57.4G 83 Linux
/dev/mmcblk1p2      120477696 124671999   4194304    2G 83 Linux

the 32bit uefi is on the dev/mmcblk2p1 and thats why i think the method is to use mount and chroot option to have grub installed to there. but you can let me know your thoughts on how i can solve it.

also wanted to know your thoughts about this as a means to solve the issue: https://unix.stackexchange.com/questions...ub-install

so i can only get into the system with a recovery usb

Does this mean you boot from a recovery usb and then somehow boot the system that is installed on the hard disk ?

It seems you have experience of installing a 64bit OS on a 32bit UEFI.
If you are confident that running the 'apt-get install --reinstall grub-efi' command will fix the issue then we can look at the mechanics of the problem.

The system seems to be unable to find the required files - it reports not being able to resolve the name 'archive.ubuntu.com'

To check the name resolution and connectivity, open a terminal with Ctrl Alt and T
Execute this command at the prompt.

Code:

ping -c 5 archive.ubuntu.com

The expected good response is that the system will convert the server name to an address and then send 5 test packets which should elicit 5 responses from the server and report this with some statistics.  If ok the number of packets transmitted will equal the number of packets received.  If not ok, there is something wrong, so report back with the response.

If the response is ok, the next step would be to try pasting this link into a browser.
http://archive.ubuntu.com/ubuntu/pool/ma...-unsigned/

This should show you a file list - if not let us know what happens instead.

If you can see a file list check that 'grub-efi-amd64_2.06-2ubuntu14.4_amd64.deb' is listed.  If it is listed then we need to dig a bit deeper.


If you are NOT confident that running the 'apt-get install --reinstall grub-efi' command will fix your issue then we need to look at how to fix the grub rescue in another way.

[supa1234]

[member=9039]stevef[/member]

I got in, finally after so many days of trying. it was this command that got me back in.

Code:

grub-install --efi-directory=[efi dir]
grub-mkconfig -o /boot/grub/grub.cfg

efi dir = /boot/efi the reason is because like in that last link i posted of the unix & linux website, it asked me to run:

Code:

mount | grep /boot/efi

which showed that /boot/efi was linked to /dev/mmcblk2p1.

thanks for all the help. now i want to try and see if i can get back into my other OS that is micro sd card (in micro sd card slot of this device) in this same asus t100taf. so i will have to create a partition off the main hard drive and then try to mount and bind the grub boot files for that OS.

yeah i used super grub2 disk (i guess its similar to boot repair) but what it does is it, searches for all the boot methods on the machine and then i can click on one of the options with the kernel for linux lite and then it will boot like normal. but once i get inside the OS, i can't fix grub to be able to boot without the super grub2 disk.

also the ping worked and sent me back 5 packets and also the link worked in the browser and i was able to see the grub-efi-amd64_2.06-2ubuntu14.4_amd64.deb it is listed.

this is my fdisk -l result:

Code:

Disk /dev/mmcblk2: 29.12 GiB, 31268536320 bytes, 61071360 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: D949E4DF-28F3-4AED-AB32-9AAB0FDC7179

Device           Start      End  Sectors  Size Type
/dev/mmcblk2p1    2048  1050623  1048576  512M EFI System
/dev/mmcblk2p2 1050624 61069311 60018688 28.6G Linux filesystem


Disk /dev/mmcblk1: 59.48 GiB, 63864569856 bytes, 124735488 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xde2a0d45

Device         Boot     Start       End   Sectors  Size Id Type
/dev/mmcblk1p1 *         2048 120477695 120475648 57.4G 83 Linux
/dev/mmcblk1p2      120477696 124671999   4194304    2G 83 Linux

the 32bit uefi is on the dev/mmcblk2p1 and thats why i think the method is to use mount and chroot option to have grub installed to there. but you can let me know your thoughts on how i can solve it.

also wanted to know your thoughts about this as a means to solve the issue: https://unix.stackexchange.com/questions...ub-install

[quote author=stevef link=topic=9497.msg61622#msg61622 date=1706800659]

so i can only get into the system with a recovery usb

Does this mean you boot from a recovery usb and then somehow boot the system that is installed on the hard disk ?

It seems you have experience of installing a 64bit OS on a 32bit UEFI.
If you are confident that running the 'apt-get install --reinstall grub-efi' command will fix the issue then we can look at the mechanics of the problem.

The system seems to be unable to find the required files - it reports not being able to resolve the name 'archive.ubuntu.com'

To check the name resolution and connectivity, open a terminal with Ctrl Alt and T
Execute this command at the prompt.

Code:

ping -c 5 archive.ubuntu.com

The expected good response is that the system will convert the server name to an address and then send 5 test packets which should elicit 5 responses from the server and report this with some statistics.  If ok the number of packets transmitted will equal the number of packets received.  If not ok, there is something wrong, so report back with the response.

If the response is ok, the next step would be to try pasting this link into a browser.
http://archive.ubuntu.com/ubuntu/pool/ma...-unsigned/

This should show you a file list - if not let us know what happens instead.

If you can see a file list check that 'grub-efi-amd64_2.06-2ubuntu14.4_amd64.deb' is listed.  If it is listed then we need to dig a bit deeper.


If you are NOT confident that running the 'apt-get install --reinstall grub-efi' command will fix your issue then we need to look at how to fix the grub rescue in another way.

[/quote]

[trinidad]

Not sure here, but when you get a message that a known repository is not currently available it can be because of time sync or lags in time sync caused by opening too big of a file initially during some application time sync operation.

https://ubuntu.com/server/docs/use-timed...-timesyncd
It may be worth checking status etc. I'm not sure if logging could be a bottleneck but I think something is on your system. You can also change time servers if any faster/closer ones are available.
Sorry. Post needs to be moved.

TC 

[supa1234]

I had ran those commands you mentioned before i ran the command to fix my grub problem.

Not sure here, but when you get a message that a known repository is not currently available it can be because of time sync or lags in time sync caused by opening too big of a file initially during some application time sync operation.

https://ubuntu.com/server/docs/use-timed...-timesyncd
It may be worth checking status etc. I'm not sure if logging could be a bottleneck but I think something is on your system. You can also change time servers if any faster/closer ones are available.
Sorry. Post needs to be moved.

TC