I have Zorin Pro installed on 3 computers using the same usb for all installs Zorin has been running flawlessly on all computers for over 2 years. I am presently running Zorin 18.1 pro. My present problem is width a laptop Notebook NJx0AU, 13 gen I7 with 1 TB ssd and 16 gb memory . Everything was perfect until I was downloading a large file and got a io error . (sorry I do not remember the wording) and the download stopped. I shut down everything and powered off my computer normally, When I turned it on again it would not boot. I saw the following error message “Failed to start mmc service-Gnome display manager…...Dependency failed for mnt-usb\….Dependency failed for mnt -mmc” After trying to figure out what was going on I decided the fastest solution was a clean reinstall. The install went ok but seemed a little slow.. The boot after install worked but was very slow. Everything was extremely sluggish. I shut down the computer normally when I went to restart it would not boot and got the same error message as before the new install. I was able to get into the new install by booting from the usb. Again running extremely slow and sluggish. Here is a log file I found.:
10:15:48 AM kernel: i915 0000:00:02.0: [drm] ERROR Unclaimed access detected prior to suspending 10:07:35 AM gdm3: Gdm: on_display_removed: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed 10:07:25 AM systemd: Failed to start app-gnome-gnome\x2dkeyring\x2dssh-1978.scope - Application launched by gnome-session-binary. 10:07:25 AM systemd: Failed to start app-gnome-gnome\x2dkeyring\x2dssh-1978.scope - Application launched by gnome-session-binary. 10:07:25 AM systemd: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-1982.scope - Application launched by gnome-session-binary. 10:07:25 AM systemd: Failed to start app-gnome-gnome\x2dkeyring\x2dpkcs11-1984.scope - Application launched by gnome-session-binary. 10:07:24 AM gdm3: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed 10:07:23 AM gdm-session-wor: gkr-pam: unable to locate daemon control file 10:06:19 AM kernel: ACPI Error: Aborting method _SB.IETM._OSC due to previous error (AE_NOT_FOUND) (20250404/psparse-529) 10:06:16 AM bluetoothd: sap-server: Operation not permitted (1) 10:05:48 AM kernel: ACPI Error: Aborting method _SB.PC00.CNVW._DSM due to previous error (AE_NOT_FOUND) (20250404/psparse-529)
If anybody has an idea about this it would be much appreciated.
Check Your SSD Health
Boot from USB and run:
sudo smartctl -a /dev/nvme0n1
(or /dev/sda if it's a SATA SSD)
Look for:
- FAILING status
- High reallocated sector count
- CRC errors
- Any warnings
If SMART shows issues, your SSD is failing and needs replacement.
I noticed that in all that text there was a message about no AE found which I think refers to a kernel vulnerability which had to be blocked to prevent malware infection.
I did a quick search on the mmc mount failure, and Brave A.I. search result came back with:
" The error message "Dependency failed for /mnt" indicates that the systemd service manager could not successfully mount the file system specified for the /mnt directory during the boot process. This failure prevents the system from reaching the local-fs.target (Local File Systems), which can cause the boot sequence to hang or drop into emergency mode.
Common causes for this error include:
-
Incorrect UUID or Device Path : The
/etc/fstabfile contains a UUID or device identifier that does not match the actual partition, often resulting from disk migrations, re-partitioning, or hardware changes. -
Conflicting Mount Points : Another entry in
/etc/fstab(such as a cloud-init mount) may already be using the/mntdirectory, causing a conflict when the system attempts to mount a second drive there. -
Missing or Invalid Filesystem : The target drive may be disconnected, formatted with an unsupported filesystem, or have a corrupted superblock.
-
Configuration Errors : Syntax errors in
/etc/fstab, such as extra spaces or invalid options, or the presence of leftover systemd mount unit files (e.g.,/etc/systemd/system/mnt-*.mount) with incorrect UUIDs.
To resolve this, users typically boot from a live USB, access the system's /etc/fstab file, and either correct the UUID, remove the problematic mount entry, or add the nofail option to allow the system to boot even if the drive is unavailable.
AI-generated answer. Please verify critical facts."
As you are using Zorin Pro I would be tempted to contact Team Zorin for support directly. Please keep us posted.
yeah you are right it could be a fstab problem, slow boot it's a clue
Is the BIOS of the Notebook in UEFI or Legacy Mode? Are secure Boot and Fast Boot in BIOS disabled? Does the System run in Wayland or X11? You can check that with the Command echo $XDG_SESSION_TYPE via Terminal.
Yes that single large block of unformatted text is hard to read and comprehend. It could do with splitting up into paragraphs. One for @tmitch to consider for future posts (please) 
First I want to thank everyone who responded to my post. Much appreciated.
Second swarfendor437 asked to”keep us posted”. The good news is Zorin is up and running great again.
Third I want to apologize for the way my convoluted word salad was presented. I was pretty frustrated and should probably have gone for a cup of coffee and calmed down before posting.
I have no clue why downloading a file caused a io error that totally messed up my computer. I have no clue why a usb that successfully completed five successful Zorin installations (3 on my commuters and 2 on friends who I “rescued” from Windows) failed this time. My UEFI settings were all correct and I always let the installation software do its validation check.
I downloaded a new ISO and created a new bookable usb, did a successful Zorin installation and all is well again.