I updated my ZOS16.3 (Dell 13-9343) via the normal Software Update method backed into the OS. Afterwards, when I tried to boot into ZOS using dual-boot, the system would just be stuck in the Dell&ZOS logo screen. I tried recovery mode, and these showed up:
I tried Bootloader fixing using the LiveCD too, but it doesn't work and now my Win10 is missing from the menu too. I have to press F12 to get into the other menu to bootup Win10.
There are 2 lines of your screenshot I find worrying:
first is: "...segfault....error 6..."
the second is: "kernel panic - not syncing:attempting to kill init!....."
I have done a bit of websearching and hardware failure is often mentioned in reply to these messages.
Can you boot any of the kernels listed in grub menu?
Can you boot Zorin live USB? (I think you said you can do this)
I hope others with more knowledge will be able to help more than I can.
EDIT: A thought. As your problem occured after a normal software update, I wonder if there was a download file corruption or incomplete update from the Software Updater.
I did a full system diagnostic via the BIOS and it showed no errors.
I'm able to boot into Win10 when it was still in the OS select menu. I think it's GRUB2. Even though it's missing from the menu now, I can still boot into Win10 after smashing F12 to get into, I think, the UEFI, menu. I forgot what everything is again after a few years of focusing on everything else.
I'm also able to boot into multiple different LiveCD, including ZOS16.3 and 17.1. But, the LiveCD boot repair app doesn't fix my booting into my ZOS16.3, and now it's caused Win10 to disappear from the dual-boot selection menu.
I also tried Rescatex, but, still no joy.
I think the Software Update messed up with the kernels. I can't even boot into any of the other older ones, including recoveries. Never had such headache before.
Yes. That is what I would call the BIOS boot device selection menu.
In summary. You are dual-booting Z16.3 and Win10. I assume both on the same physical drive.
Are you able to post a screen from Gparted, showing your drive partitions, so we can see if anything there looks wrong.
In the past, Boot Repair Disk or maybe known as Grub Repair) has fixed the problem of an Operating System missing from Grub menu. But that is usually after a human error during installation, not the result of a straightforward OS update.
Whilst running from Live USB, I would back-up all your personal files etc as soon as possible. I hope you do not have to do a re-installation of ZorinOS but it could come to that.
@Aravisian This is a strange one and beyond me. If you can think of anything to help, I am sure it would be appreciated. I assume Kev is in HK timezone.
Although, I'm still a GNU/Linux noob, this is my first time seeing this issue too. If all else fails or if a solution can't be found, I guess I'll have to delete the partition and maybe just install ZOS17.1 as the new dual-boot. I only have one drive.
It's Win10 is missing from the Zorin Grub now too.
I don't really have much, as mostly sync my important files to my NAS. It's the setting things up again that's a hassle. I live in a different city north of the border now, and didn't bring most of my computer things from home.
Good thing I can still boot into Win10, as sadly I still depend on it for my current "new" studies and probably future work. My close to 10 year old baby is my only main laptop still.
I agree that this sounds like a read/write error occurred during the update/upgrade process.
This is a rare occurrence that can be caused by a brief (or persistent...) hardware fault or by packet loss.
If booting to a LiveCD image and then running Grub Repair is not working, my first suspect would be EFI partition corruption.
This could be resolved by a dual process of first removing, then recreating the EFI partition, then running the Grub install on the newly created partition; then performing the same procedure for the Windows OS install of reinstalling the bootloader (since even though the Windows OS boot is currently working, it won't be if the EFI partition and its bootloaders are removed.)
The other option is to back up any files using LiveCD to access the drive, then reinstall Zorin OS.
The second option is the one I would go for in this position. Reinstalling always looms as the most intimidating enemy... yet in reality, often resolves more problems than you realized that you had, gives a fresh clean start and is easier and swifter than a person expects. It does more good than our fears will allow us to consider.
I guess... like a dentist.
The university I'm at outsourced the network infrastructure to three mobile companies. It's not as stable as regular fiber-based ones and latency is often horrendous, especially being behind the Great Firewall. Everything is wireless or mobile, even when plugged into wall Ethernet ports.
I think I'll start fresh with ZOS 17.1. It'll be much easier at this point. Hopefully it'll give me better benefits than 16.3 on my antique laptop.
