I tried doing that command at the bash type screen before and got nothing so I probably need to finish the log in, then go into terminal and try the command,. Will try that.
Says reloading system manager configuration
Staring default target
Then after a while came back with the same stuff about emergency mode
Now typing isn’t being recognized
That should work at that screen... But a couple of things:
You may need to type
exit
at that screen first.
The second is: if at a Minimal Bash-like editing supported screen - it usually does not offer any means of proceeding to a normal boot.
I would recommend performing
fsck
at this point if you are feeling truly stuck.
fsck from util-Linux 2.39.3
e2fsck 1.47.0 (5-Feb-2023)
/dev/nvme0n1p5 is mounted
e2fsck: cannot continue, aborting
Sorry, I was not being clear. Running fsck cannot be done on a mounted drive.
I was awaiting your confirmation of willingness to take that step.
The process requires that you boot the LiveUSB (stick) of Zorin OS, then access that drive and perform fsck on it.
That Being Said: There is a safe fsck option yuo can run from the Grub Menu...
IF you can reach the Grub Menu (Where you choose Zorin or Advanced Options for Zorin)..
Select the Advanced Options...
Then Zorin on 6.8 (Recovery)
and in that recovery menu, arrow key down to fsck.
It is safe and practical to try that way first.
The LiveUSb stick method is more thorough - and good if a FS is very corrupted...
Tried the journalctl -xb and got a screenful of stuff that I can try to photograph. Except photo is apparently too big.
I cannot see anything obviously saying error.
Possibly relevant in the journalctl output
No NUMA configuration found
Faking a node at …
Unknown kernel command line parameters splash will be passed to user space
Warning ITS mitigation depends on retooling and rethink support
ACPI FADT declares system doesn’t support PCIe ASPM so disable it
A number of items could not be reserved
PCI 0000:00:14.0 can’t find IRQ for PCI INT a please try using pci=bios irq
DMAR no ATSR found
DNAR no SATC found
Several features said to be inconsistent
A few things about device descriptor errors and devices not responding to setup address
I think I need to leave this for tonight.
I can’t even get to grub at the moment
It is a scary thing... Daunting. Leaves a person feeling kind of helpless.
For those of us over here - we are peeking through fractured glass hoping for enough glimpses to clue us in on a vague and unusual issue.
I think you are making the right call. Step back and let the mind settle.
Approach later fresh.
Because however daunting it seems - It will get fixed.
Maybe by an ah-ha moment or maybe luck.
Appreciate your support as usual.
Need to get some sleep and go to church in the morning. Then I may try the live boot and fsck.
1 Like
You can in this File disabling Auto Login, too. Did You tried that?
Thanks @ponce-de-leon I did see that. I didn’t use it yet because the troubleshooting with @Aravisian seems to be taking me in a different direction. I’m going to take another look at the 4000 lines of journalctl this afternoon and try to see what happened right before it went wrong. There’s a lot of systemD in there.
I think where the process went wrong may have been:
System is tainted: local-hwclock
Subject: the system is configured in a way that might cause problems
Defined by: systemd
Support: Enterprise open source support | Ubuntu
Everything after that I think was me trying to fix it. Unsuccessfully.
Does that suggest anything?
I am now going to hard reboot because I don’t know how to get out of the journal list. Exit and ctl-x don’t work.
Then I’ll try to see if I can get into grub and do the fsck from the advanced options.
If I can’t then I’ll try booting to my ventoy stick which has Zorin 17.3 on it and do fsck from there.
If that doesn’t work, do you think I should try a reinstall? If so would I be best to try to download 18.1 using a different computer and install or alternatively install 17.3 that I already have then upgrade?
Either way I assume I’d do the something else option or would erase and install be best? I should probably unplug my usb data drive before doing anything, right?
I couldn’t find an fsck option under advanced options in grub so I tried the 6.8 kernel recovery option choice.
That ended with the line
153.343455 general protection fault, probably for non-canonical address
0xe49fd5cf942d9508: 000 [#2] preempt EMP nopti
Does that suggest anything?
Maybe I’ll try to take a look at my grub file next just in case I can see anything that has changed.
After that, I’ll wait until I hear comments back before considering a reinstall.
Ok, a little more progress. I rebooted again using the 6.8 choice and I am back to the original situation in Zorin but with no mouse, or at least no mouse pointer, and very slow response to keyboard when entering password for the default key ring.
I’m thinking I’d like to get into the settings menu and look around but is there even a way of doing that with no mouse pointer. Just FYI my mouse is wired and plugged into one of the rear usb ports. The reason I say no mouse pointer is that when I move it around, sometimes it seems to highlight an icon on the task bar as if I was hovering over it.
These are the things that stand out.
USB routing, USB enumeration and that the kernel is in protection mode.
What can usually cause this are File System corruption (That is the reason for trying fsck and Faulty RAM.
I would try fsck From the LiveUSB first, since kernel protection is blocking it using this shortcut.
And if no good, try MemTest on RAM.
If RAM tests as ok; then yes... trying a reinstall of the OS is a valid option. If it was me, I would download the .iso and not try to use the Upgrade Tool from 17. Upgrading from 17 adds complicating factors.
Yes, you can unplug the Data drive to be safe.
If erase and install is a valid option for you (You are not dual booting or have other sensitive customizations), then simpler is better.
Opened the custom.conf file in terminal and changed autologin to false and Wayland to true, and I uncommented that line.
Rebooted and selected non Xorg choice
Got logged in back on Wayland with mouse pointer and normal speed of response to keyboard.
Seems like I.m back to where I started by whatever happenstance so perhaps I’ll leave we’ll enough alone for now. I would still like to try Xorg if it will work for me but not just now.
1 Like
Interesting.
There is no possible means of Kernel Protection Mode from logging into Xorg. That is unexplainable at this time - So I must agree that for now, if it is not broken, let's not fix it until it is. There is some other factor at work, here.
1 Like
Again thanks. Considerable relief here! I may try again in a week or so if I’m feeling brave.
Running recovery mode on the kernel seemed to fix something because after rebooting from that at least I could get into Zorin, but still seemed to need Wayland for the mouse and keyboard to function properly, strange.
1 Like
You are braver than I am. I do not want to go anywhere near your computer.
I would open a terminal and type
sudo apt update
and it would print
Initiating thermonuclear warhead launch
I would hit ctl+c to cancel, it would print
Confirmation accepted
1 Like