I recently installed Zorin OS 16 on a Dell Latitude 5510 with Windows 10 already installed.
Zorin OS worked just fine until I had to boot back into Windows once, after which it refuses to start.
More precisely, after the GRUB shows up and I select Zorin OS as a boot option, I see the Zorin name and logo appear for a while under the Dell logo, then the former disappears and the computer is left stuck on the Dell startup logo.
Is there a way to salvage the install ?
does not work (as in, command not found) on both the GRUB command prompt as well as the root command prompt when I try to boot into recovery mode.
While in recovery mode, I tried updating the GRUB and fixing broken packages.
I also took a picture of the partition layout, if that can be of help.
When I proceed with boot, I just get stuck on a black screen until I press the Power butto, at which point a few lines of text appear and the computer shuts down.
You might try running boot repair from the live medium. Open the live session and search boot repair. You'll have to look at the options carefully since the cause of the problem is unknown.
Thanks
I assume boot-repair isn't installed by default since I the root command prompt did not find it ?
I've quickly looked at the docs for boot-repair, is it risky to just run it with default options, at least as a first try ?
I'm still not very knowledgeable about handling boot and partitions.
I ran boot-repair from the live version as suggested here
And it apparently found the culprit : Safe Boot enabled, NVRam locked.
I do remember reading that Zorin was Safe Boot compatible, but if I just have to disable it that's not too much of a problem.
I wonder if it will cause problems with booting on Windows ?
You've got it.
No, Safe boot is not compatible - Zorin OS can mostly run with Secure Boot; but it is still recommended to turn Secure Boot Off on Linux machines as it still can interfere with independent apps.
I tried turning it off, Windows boots just fine, but Zorin still won't.
I ran boot-repair from the live version again, and I still get the Locked-NVram message.
From what I can see online people describe it as an hardware issue, encountered during setup, that is fixed by physically resetting something on the motherboard or flashing the BIOS.
But it's still puzzling that Zorin ran just fine for days, and only had issues after I had to reboot in Windows.
I looked into it, seems like Intel refers to it as VT-d.
I checked that my processor is compatible with it, and nothing in the BIOS has that exact name, but there's something called "VT for Direct I/O" and I believe that's what they use for IOMMU. It is enabled.
I checked a few more options : while I disabled Safe Boot, there's something called UEFI Boot Path Security, should it be disabled as well ?
I also disabled Fast Boot within Windows itself, but there's also a Fastboot setting in my BIOS, could that interfere with boot ?
And lastly, just to check, the boot option for Zorin in my BIOS is
at the top of my boot order. It failed to boot and skipped to the "ubuntu" option where my GRUB is located.
I tried disabling "Fastboot" in the BIOS as well, but nothing changed.
As much as I would like to be, this is a work computer, so I'm going to try to keep the explosions at a minimum
IT was kind enough to let me install whatever I want on that computer, but I don't think they would appreciate me accidentally bricking the entire machine.
Interesting... Well, I guess revert that back. But now, I am confused... Do you have Ubuntu installed as well?
That might explain the above...
Are you able to boot into Zorin at all?
Fortunately, there is not a lot you can do that can brick it... But refrain from ever using the rm -rf commandat all. That is an unusual IT dept. that allowed you to install Zorin.
I don't, it was automatically added to my boot order as I installed Zorin, and labelled as "ubuntu".
I can't, my problem is still as I described im my original post.
Their answer was along the line of "Do whatever you want, we'll just reinstall Windows when it inevitably crashes". Well, I'm one OS down so far, hoping the second doesn't follow
I might have to, I has spent quite some time configuring Zorin and I was hoping to salvage it somehow.
But I believe simply reinstalling might not solve the root of the problem, and next time I'll boot into Windows it will stop working again.
It's kind of a shame, I just needed to export some data from Windows to bring everything back to Zorin, I might not have noticed the issue for months otherwise, as I don't really use any Windows-specific software for now.