Zorin OS 17 Core - Cannot Boot - System Message

[WillingToLearn777]

Greetings Folks!
Hope you having a great year so far.
Please provide a solution for the attached "System Message". I cannot boot into Zorin OS as I normally do.

Thank you.

 

[dos2unix]

Before typing exit to resume the normal boot peocess.
Try this.

systemctl set-default multi-user.target

Then type exit to resume the boot up.
You Xwindows won't be running, but at least you can login and see what's going on.

dmesg | grep -Ei 'warn|error|unsupported|connect|fail'

Maybe that will give a clue.

 

[WillingToLearn777]

Before typing exit to resume the normal boot peocess.
Try this.

systemctl set-default multi-user.target

Then type exit to resume the boot up.
You Xwindows won't be running, but at least you can login and see what's going on.

dmesg | grep -Ei 'warn|error|unsupported|connect|fail'

Maybe that will give a clue.

Thanks for your prompt response. I will give this a bash. Will let you know what happens.

 

[WillingToLearn777]

The same red message appears after I entered code 1 above and entered exit.

Please advise further.

 

[osprey]

The same red message appears after I entered code 1 above and entered exit.

Please advise further.

Since the message has repeated on text login (as I understand may have been done if the suggestion in post #2 by @dos2unix was followed), then it would be wise to run a fsck. It's easy to run from a live disk where the installation partitions are not mounted.

One can run a live disk, identify the root and any other partitions from the command: lsblk, and run: fsck <device-name>

 

[WillingToLearn777]

Since the message has repeated on text login (as I understand may have been done if the suggestion in post #2 by @dos2unix was followed), then it would be wise to run a fsck. It's easy to run from a live disk where the installation partitions are not mounted.

One can run a live disk, identify the root and any other partitions from the command: lsblk, and run: fsck <device-name>

Thanks for your response. Please bare with me I am Linux Newbie not at all experienced with the run codes.
At the command line "press Control D to continue" do I continue and then enter lsblk and run fsck device name?

Please advise further.

 

[WillingToLearn777]

Thanks for your response. Please bare with me I am Linux Newbie not at all experienced with the run codes.
At the command line "press Control D to continue" do I continue and then enter lsblk and run fsck device name?

Please advise further.

A. Background that may assist. Before I had this "boot system error message''
1. My Notebook has two disc drives 1) SSD - Windows 11 installed 2) Spindle - Linux Zorin installed
2. Dual boot was activated. Start the Notebook it provides me a screen to enter a Windows Boot Locker password.
3. Press enter and a screen appears to select Windows 11 or Linux Zorin.
4. Select the OS manually and enter takes me to the live system. (Automatically goes to Zorin OS)
This process has been operating perfectly for over a year.
B. Current situation. With the ''boot system error message''
1. Start the Notebook it takes me to the Windows Boot Locker screen to enter a password.
2. Enter the password and then press F12 it takes me to the boot selection screen to select Windows or Ubuntu.
3. Select Windows and enter it takes me to the live OS and it is operating correctly.
4. Select Ubuntu and enter it takes me to point A3 above.
5. The system runs automatically to select Zorin as set in the Boot Manger sequence.
6. Select Zorin manually and enter I get the ''boot system error message'' (B5 gives this error message as well)
7. Select Windows manually and enter it takes me to the live OS and it is operating correctly.

Hope this helps!

 

[dos2unix]

In the first picture I see press cntrl-d to continue, or press [Enter] to go into maintenance mode.
You should be running the systemctl command, and the fsck commands in maintenance mode.

Before you do the cntrl-D to continue, or exit the maintenance mode.

 

[WillingToLearn777]

In the first picture I see press cntrl-d to continue, or press [Enter] to go into maintenance mode.
You should be running the systemctl command, and the fsck commands in maintenance mode.

Before you do the cntrl-D to continue, or exit the maintenance mode.

Thanks for your response. I will give it a try and respond.

 

[WillingToLearn777]

Thanks for your response. I will give it a try and respond.

Entered the lsblk and fsck command codes.
Received the attached message.

 

[KGIII]

You don't use the literal <device name. You input the name of your device, which appears to be sda in this case, though I can't remember if you have to specify the partition. If so, it's sda1 and sda2, If the latter is true, run the command once each for both of those device names.

 

[dos2unix]

I see a ton of snap devices on here. It could be one of those.
In the meantime try

fsck -y /dev/sda1
and
fsck -y /dev/sda2

 

[WillingToLearn777]

You don't use the literal <device name. You input the name of your device, which appears to be sda in this case, though I can't remember if you have to specify the partition. If so, it's sda1 and sda2, If the latter is true, run the command once each for both of those device names.

Thank you for your response. I will give it a bash and respond.

You don't use the literal <device name. You input the name of your device, which appears to be sda in this case, though I can't remember if you have to specify the partition. If so, it's sda1 and sda2, If the latter is true, run the command once each for both of those device names.

Entered the device names.
Attached is the system screenshot.

 

[WillingToLearn777]

I see a ton of snap devices on here. It could be one of those.
In the meantime try

fsck -y /dev/sda1
and
fsck -y /dev/sda2

Thanks for your response. I will try and respond.

 

[WillingToLearn777]

Thanks for your response. I will try and respond.

Entered the command codes.
Attached is the screenshot.

 

[CaffeineAddict]

Entered the command codes.
Attached is the screenshot.

fsck needs to be run from live boot, bootable USB needs to be made with live ISO.

 

[GatorsFan]

In order to run fcsk the drive has to be unmounted - hence the error - you have a couple of options - boot into a Live USB and run the command from there or A more easy way is to tell Zorin to check the filesystem on next boot. You can do this by touching /forcefsck

sudo touch /forcefsck

Another way is to pres ESC on boot while Grub is loading. You will get the Grub-boot-menu Now you can choose to boot the recovery console. In the recovery console you can ask Zorin to fsck all disks.

 

[dos2unix]

It looks like it worked for /dev/sda1, but not /dev/sda2
You can exit and see if that fixed it, otherwise @GatorsFan and @CaffeineAddict are right, you will need a live USB to boot from.

 

[WillingToLearn777]

fsck needs to be run from live boot, bootable USB needs to be made with live ISO.

Thank you for your response.

 

[WillingToLearn777]

In order to run fcsk the drive has to be unmounted - hence the error - you have a couple of options - boot into a Live USB and run the command from there or A more easy way is to tell Zorin to check the filesystem on next boot. You can do this by touching /forcefsck

Another way is to pres ESC on boot while Grub is loading. You will get the Grub-boot-menu Now you can choose to boot the recovery console. In the recovery console you can ask Zorin to fsck all disks.

Thank you for your response. You said "A more easy way is to tell Zorin to check the filesystem on next boot. You can do this by touching /forcefsck - enter command ''sudo touch /forcefsck''.
Is the next boot at the selection for Maintenance command line?

Please advise further.