Software - Support > UEFI Secure Boot
cant get back to grub. stuck at grub rescue because of 32bit uefi
supa1234:
I had ran those commands you mentioned before i ran the command to fix my grub problem.
--- Quote from: trinidad on February 02, 2024, 10:23:53 AM ---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-timedatectl-and-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
--- End 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-timedatectl-and-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:
@stevef
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
--- End code ---
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
--- End code ---
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.
--- Quote from: supa1234 on February 01, 2024, 03:25:43 PM ---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
--- End code ---
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/405472/cannot-find-efi-directory-issue-with-grub-install
--- Quote from: stevef on February 01, 2024, 10:17:39 AM ---
--- Quote ---so i can only get into the system with a recovery usb
--- End quote ---
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
--- End code ---
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/main/g/grub2-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.
--- End quote ---
--- End 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
--- End code ---
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/405472/cannot-find-efi-directory-issue-with-grub-install
--- Quote from: stevef on February 01, 2024, 10:17:39 AM ---
--- Quote ---so i can only get into the system with a recovery usb
--- End quote ---
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
--- End code ---
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/main/g/grub2-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.
--- End quote ---
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 from: WytWun on February 01, 2024, 05:38:24 AM ---
--- Quote from: supa1234 on February 01, 2024, 03:54:41 AM ---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.
--- End quote ---
When you attempt to boot normally, do you get a
--- Code: ---grub>
--- End code ---
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.
--- End quote ---
Navigation
[0] Message Index
[#] Next page
Go to full version