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:
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
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 Linuxthe 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
(02-01-2024, 03:17 PM)stevef link Wrote:Quote:so i can only get into the system with a recovery usbDoes 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.