Installed zoran on an old laptop and ran into a problem now I all I get is the grub command line when I start up the computer. If I try to get into BIOS to change the boot to go back to the USB stick still it goes to the grub command line if I click on diagnostics it goes to the grub command line no matter what I do in that boot menu I end up at the grub command line how the heck do I get this machine working again? I have a video showing all this but I don't know how to post those here.
Just figured it out (how to share a video, not the fix for the machine).
Hi, You can't post videos here but if you have an account with a video provider such as vimeo.com you can upload to there and then provide a 'share' link to your post, or whatever video channel you subscribe to.
Could you provide us with some more details about your notebook? Make and model?
You probably need to run fsck File System Check.
This can be done using LiveUSb - or if you have a grub Menu, from Advanced Options for Zorin, then Zorin on [kernel version] (Recovery)
One area you did not show in the video is BIOS setup (F10). On my experience of HP desktops, pressing F10 at boot time should take you to BIOS setup. I would also try your USB stick in a different port.
Regarding your issue,
" Minimal BASH-like line editing is supported at the GRUB prompt typically indicates a corrupted or misconfigured bootloader. This issue often occurs after installation, especially on UEFI systems, and can be resolved with the following steps:
Boot from a live USB and open a terminal.
Identify your EFI and root partitions using sudo fdisk -l (look for a small FAT32 partition labeled "EFI" and your root partition, usually ext4).
Mount your root partition (e.g., sudo mount /dev/nvme0n1p2 /mnt ).
Mount the EFI partition (e.g., sudo mount /dev/nvme0n1p1 /mnt/boot/efi ).
If the issue persists, check the GRUB configuration file (/mnt/boot/efi/EFI/ubuntu/grub.cfg ) for incorrect partition references (e.g., pointing to a wrong disk or partition) and correct them manually using nano or vim .
Note : This error is commonly caused by incorrect GRUB installation during partitioning or a firmware setting that reverts the boot entry to shimx64.efi . Ensure Secure Boot is disabled in firmware and the correct boot entry (e.g., grubx64.efi ) is set via efibootmgr .