The Zorin 17 boot process stops with errors

I have a iMac with
Intel Core 5i-426 CPU @ 1,40Gz * 4
RAM 7.7 GiB
and the disk capacity of 500 GB

I’m trying to replace a Zorin OS 16.3 with a Zorin 17 Pro.

It all starts well, but stops and this is how the screen

******** screen capture starts *****

Checking

•/pool/restricted/nvidia-utils-535_535,129.03-Bubuntub,22.04,1_amd64, deb..../pool/restricte

Checking . /pool/restricted/server-xorg-video-nvidia-535_535. 129.03-0ubuntu.22.04.1_amd64. deb... /pc

Checking . /README.diskdefines...../README.diskdefines: 0K

Check finished: errors found in 1 files! You might encounter errors.

BusyBox v1.30.1 (Ubuntu 1:1,30.1-7ubuntus) built-in shell (ash)

Enter 'help' for a list of built-in commands. (initramfs) -

cp: can't create '/root/var/10g/': Is a directory
cp: can't create '/root/etc/': Is a directory
mount: mounting /dev on /root/dev failed: No such file or directory
mount: mounting /dev on /root/dev failed: No such file or directory
mount: mounting /run on /root/run failed: No such file or directory
run-init: can't execute 'isbin/init': No such file or directory
Target filesystem doesn't have requested /sbin/init.
run-init: can't execute 'isbin/init': No such file or directory
run-init: can't execute '/etc/init'

: No such file or directory|
|run-init: can't execute|'/bin/init': No such file or directory|
||run-init: can't execute '/bin/sh': No such file or directory|
||run-init: can't execute ": No such file or directory|
||No init found. Try passing init= bootarg.

BusyBox v1.30.1 (Ubuntu 1:1,30.1-7ubuntus) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs) _

********* screen capture ends ******

Can anybody help me forward and what to do, please.

Matti

Is this a fresh installation of Zorin OS 17?

Have you run fsck with the drive unmounted?

Haven’t run the fsck yet. It is a fresh installation.

I would recommend trying fsck first.

Be sure to only run fsck with the drive unmounted. If the drive is mounted during fsck, it can be physically damaged in ways that cannot be fixed (Running the fsck command will also show a warning about this).

I checked. The answer was
Disk /dev/loop0: 55.68 MiB, 58363904 bytes, 113992 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

As a fresh install; I would just re-install Zorin OS 17.

If you did have any personal files on the drive, please be sure to back them up.

Firstly, did you validate the .iso you downloaded by checking the SHA256 checksum? Also what medium/burning iso software did you use on the USB to create installation media for the i-Mac?

I haven't done the checksum check. I'll do it first thing in the morning. I used the Unetbooting. Tried both balenaEtcher. Didn't function. Really appreciate your help.

Excuse me the delay. I did the following.

  1. tested the SHA256 - it was right
  2. Used balenaEtcher, linux terminal and Unetbootin - all failed
  3. Tried installing 16.3 to the USB stick - worked faultlesly
  4. Bougth a new USB stick - same problem
  5. Again tried to install 16.3 Lite, 17 Core and 17 Pro - 16.3 functions with Netbootin and balenaEtcher but nothing everything with 17 fails
  6. I've come into conclusion that there is something with version 17 and Mac iron, which makes a mess of it.

This is a logical conclusion.

One last thing, can you try Ventoy instead of an etcher? Ventoy works differently than the etchers do.

Recently, I had install Zorin 17 Core (dual boot) on a Macbook 2009 (Core Duo, 8GB RAM, 240GB HDD).

I followed this link... maybe it can help you.

type exit and hit ENTER (to see the partition with error)

fsck /dev/sda2 -y (replace /dev/sda2 with your partition name)

reboot (If the reboot command doesn't work, type exit and hit ENTER.)

For more details:

Thank you, I’ll definitely take your advice.

Thank you. I’ll have a look. I’ll be travelling this and next week but will try it again next weekend.

1 Like

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.