@Smokey just an observation from your BIOS Security tab screenshot. Secure Boot Mode says "Standard" not "Disabled". What are the options for that setting?
To me the word "Standard" could imply Secure Boot is the normal default setting for a Windows PC i.e. set Enabled, not Disabled. But I do not know this BIOS, so can you check your Secure Boot Mode options.
Yes, that could be the reason that you otherwise have no access to this settings.
Could You go here in the Secure Boot Options to see Help Text at the right Side?
Thanks Zabadabadoo.
When I enable Secure Boot I can then access the settings below the heading as well as passwords for the disks. The Standard heading then changes to Custom which is what it is now with Secure boot disabled on the following page.
What I have not done which might make a difference is select Erase all Secure Boot Settings. The same for TPM as there are settings there that remain after disabling.
I guess I can't break it more than it is already broken.
I have also thought about forwarding the Grub Repair result files to the email address provided with the the error warnings, but first I will try the Erase all setting and see what happens. Any thoughts?
Can you post screenshot of that, showing also the right hand side of screen as Ponce-De-Leon has also asked.
If Secure Boot and TMP are indeed disabled. You should not need to erase settings that are not being used.
The Boot Repair Disk output shows the dreaded "NVram is locked" Error.
There should be advice here on the forum to help with that.
EDIT: e.g. old thread here: NVram Locked (Zorin not found in efibootmgr)
My old acer laptop also had this problem, and the way I solved it was this:
First step:
In the BIOS, go to the "Boot" tab and set Secure Boot to "Enabled"
Second step (optional but recommended):
In the "Security" tab, select "Restore Secure Boot to Factory Default". I say this is optional because usually it's not necessary, but the other day the usual steps stopped working on my old laptop until I did that first, so better do it now to prevent problems later.
Third step:
In the "Exit" tab, save and exit.
Fourth step:
Go back to the BIOS, "Security" tab, "Select an UEFI file as trusted for executing".
There, navigate through a file structure that should be something like this:
hdd -> ubuntu -> grubx64.efi (could be a bit different if you have a ssd instead of a hdd; this is how I remember it looking like in my laptop)
Then name it however you want, it doesn't matter (naming it "zorin" would make it more easily to identify though)
Fifth step:
On the "Boot" tab, set "Secure Boot" to "Disabled". Then go to Exit and select save and exit.
Now the laptop should be able to boot into zorin fine.
Here is the photo showing the Standard heading changed to Custom, as requested.
Sorro's post seems to indicate otherwise, unless a successful solution depends on something else that is currently "unknown".
Perhaps I missed something here but the solution seems to be to install Pop! OS. I will search further in the questions of the "NVram is locked" Error.
Your input is much valued. Thank you.
A Serendipidous Success of Sorts
I now have Zorin installed and working on the HDD. The next challenge for me will be to get the OS booting from the SSD.
I say senendipititdous as success happened with an accidental change in Sorro's suggested process. I saved the changes to the Security settings while still in Secure Boot mode.
That brought up a boot menu with photos of what happened after. I don't remember when I turned off Secure mode:
There was never an option to access the SDD in the installation process. I have tested access to the SSD by saving a Writer file on the SSD after creating a new folder on it. It also opens from the Recent list in Writer.
Whilst you have marked your last post as Solution with ZorinOS on your HDD, you have not achieved your objective of installing ZorinOS on your SSD. Are you still wanting to do that?
I was in the process of editing the last post to add that I now have access to the already installed Zorin on the SSD. It had been installed on both the HDD and the SSD, despite what was being shown by the USB installer's tools. They showed the HDD as being completely empty.
I am now presented with a menu of options.
Edit takes me to a file showing two different versions of linux, 6.8.0-60 generic for the HDD and 6.8.0-57 generic for the SSD. Any implications in that?
So it is the second "Zorin OS 17.3 (17) (on dev/sdb2)" that refers to your SSD install.
Although not top of the list, so not default boot item, if selected does that boot up OK?
Yes, and I have just moved from writing to you from a Windows 11 desktop to now writing this reply from Zorin on the SSD.
I guess you are now wanting to tidy up. i.e. Remove Zorin from HDD and just leave it on SDD for that to be your default boot. Or at least swap the two grub listings over so the SSD is default boot.
Correct. Zorin on the HDD behaves differently. It is much slower to load and locks during the process of rebooting or shutting down, requiring an extended power key press to turn off completely.
How would you suggest as the best way to removed Zorin from the HDD?
As you now have a working system from SSD, I will let someone with more knowledge help you with your "tidy up" removal of ZorinOS from HDD whilst leaving ZorinOS on SSD as primary boot source.
It would help if you posted a Gparted screenshot of your HDD partitions.
It may just be a case of deleting the Zorin partitions from HDD and then doing a Boot Repair (grub repair), but I do not want to break your working system. Maybe @Aravisian (or someone used to manipulating multi-drive installations and partitions) can help when next available.
SDA is the HDD with an undesired installation of Zorin. SDB is the SSD with the working instance of Zorin which is to remain.
Okay, on sdb is the EFI Partition the ext4 formatted / Mounting Point. that looks good and right to me.
On sda I don't see any Mounting Point, only formatted to ext4. So, there shouldn't be installed something. Are there any Files on this? If not this should be ready.
Do You see the exact same when You go to ''Other Locations'' and there choose Your Machine?
It seems so. The only difference is the Swap file on the SSD - the current boot.
I installed Audacity on the SSD and made a short recording after not being able to get my headset recognised on the HDD install. Now the same files are in both Music directories.
