Hello!
Boot on my disk was totally gone. I can't to do nothing. No one menu showing. I was investigate partitions and there show no files everywhere. In live session it says to can't find EFI directory when I was try to do new grub installation.
Please work on the Thread Title and then describe what Your actual Problem is.
It's nothing to see if you copy the link?
No.
Simply write down Your Issue in Your initial Comment. I take what You have there currently and set it in the Thread Title.
Delete that thread if nobody will comment here...
You have now a Description. So, we will see if we can solve this.
- Is Windows still installed on Your System? If yes: Did You got any Updates before this happened?
- Is Fast Start-Up in Windows disabled?
- Are Secure Boot and Fast Boot in BIOS disabled?
- Did You tried it with starting Zorin from USB Stick in Live Mode and run there Boot Repair?
- Can You show from Live Boot a Picture of the Partitions in GParted?
- Do You have in BIOS in the Boot Order an ''ubuntu'' Entry?
- Is Your BIOS in UEFI or Legacy Mode?
- What Tool did You use the create the Bootstick?
2 Likes
Ziga88, please remember that no one on here has any knowledge or experience operating your computer. Only you have that.
You must relay what updates you recall or an installations you made or what you have tried so far.
Include your system specs.
We had this same trouble when you sent this request to me in a private message:
Without details, we do not even know where to begin on troubleshooting.
What you describe sounds like your partitions were just simply removed: Which aside from drive failure - cannot happen by itself.
What is most likely is that the partitions are not removed and you cannot boot the ones that are there.
What strikes me as most probable: Root /var filled up with logs - and now you cannot boot.
That's regular problem in Zorin. If you left system on trough the night, next day you don't know what will happen when you will reboot system. I was experienced that many times.
In times when was been Windows used wasn't been this problems.
Data is on disk. I see EFI partition(sda1) and sda2, also amount of partitions.
Yeah you all must me understand also, I don't have nerves to deal with that same thing every few months...
I was say already to I don't using windows anymore..
Secure boot is disabled all the time.
You are not alone in experiencing this.
A lot of the time, it is /var directory filled with logs - when the system then tries to write for system files, there is no space left.
This is the first thing I would check.
Why this is predominantly a Gnome Problem: Lite users do not experience this much at all. I never have. Gnome builds up a Lot of logs.
This is further compounded by extensions and additional snap or flatpaks that take up a lot of space.
Zorin OS Core is complex and heavy.
As you want to avoid Windows OS, what about a lighter distro?
1 Like
Is that so, interesting. Why cleaning of that isn't automated?
Perhaps, but I don't like to have OS which looks like Win 3.1 and is without animations.
We can help set it up to be automated.
But first, we need to determine if that is the cause - and get your system bootable.
If you are getting "No OS found", have you checked that the connector cable to the drive is not loose (Which may explain the problem repeating)?
Have you checked your BIOS settings to see if you are set to Legacy or to EFI?
(I know already that you said you did a S.M.A.R.T. test of the drive).
Ok. I using laptop. I'm, is set to UEFI. Yes, disk isn't very bad.
I have issues with BootLoader on sdb. Boot info says to there is unknown BootLoader and to there aren't no BootLoader installed in the MBR of /dev/sda.
Here is log.
boot-repair-4ppa2056-zorin1 [20260304_2043]
============================== Boot Info Summary ===============================
=> No boot loader is installed in the MBR of /dev/sda.
sda1: __________________________________________________________________________
File system: vfat
Boot sector type: FAT32
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /efi/BOOT/fbx64.efi /efi/BOOT/mmx64.efi
/efi/ubuntu/grubx64.efi /efi/ubuntu/mmx64.efi
/efi/ubuntu/shimx64.efi /efi/ubuntu/grub.cfg
sda2: __________________________________________________________________________
File system: ext4
Boot sector type: -
Boot sector info:
Operating System:
Boot files:
sdb: ___________________________________________________________________________
File system: iso9660
Boot sector type: Unknown
Boot sector info:
Mounting failed: mount: /mnt/BootInfo/FD/sdb: /dev/sdb already mounted or mount point busy.
================================ 0 OS detected =================================
================================ Host/Hardware =================================
CPU architecture: 64-bit
Video: Haswell-ULT Integrated Graphics Controller Jet PRO [Radeon R5 M230 / R7 M260DX / Radeon 520 Mobile] from Intel Corporation Advanced Micro Devices, Inc. [AMD/ATI]
Live-session OS is Zorin 64-bit (Zorin OS 17.3, jammy, x86_64)
===================================== UEFI =====================================
BIOS/UEFI firmware: 1.90(1.90) from INSYDE Corp.
The firmware is EFI-compatible, and is set in EFI-mode for this live-session.
SecureBoot disabled (confirmed by mokutil).
BootCurrent: 0003
Timeout: 0 seconds
BootOrder: 0000,2001,2003,2002
Boot0000* ubuntu HD(1,GPT,d9b63b9a-5807-4b6b-9e2d-aedb48791571,0x800,0x100000)/File(\EFI\ubuntu\shimx64.efi)RC
Boot0001* Realtek PXE PciRoot(0x0)/Pci(0x1c,0x3)/Pci(0x0,0x0)/MAC(2c600c0c14d4,0)/IPv6([::]:<->[::]:,0,0)RC
Boot0002* Realtek PXE PciRoot(0x0)/Pci(0x1c,0x3)/Pci(0x0,0x0)/MAC(2c600c0c14d4,0)/IPv4(0.0.0.00.0.0.0,0,0)RC
Boot0003* EFI USB Device (takeMS Colorline) PciRoot(0x0)/Pci(0x1d,0x0)/USB(0,0)/USB(0,0)/HD(1,MBR,0x749c9c64,0x240,0x2780)RC
Boot2001* EFI USB Device RC
Boot2002* EFI DVD/CDROM RC
Boot2003* EFI Network RC
1d43d986c265d8c455d020e4a1f28c52 sda1/BOOT/fbx64.efi
1d260ff1255f189ab621209796ee2fed sda1/BOOT/mmx64.efi
1535d97a530fe1aa6f0d87717547d309 sda1/ubuntu/grubx64.efi
1d260ff1255f189ab621209796ee2fed sda1/ubuntu/mmx64.efi
07e25dcaf57c776875f78fa36827c58e sda1/ubuntu/shimx64.efi
1535d97a530fe1aa6f0d87717547d309 sda1/BOOT/BOOTX64.efi
============================= Drive/Partition Info =============================
Disks info: ____________________________________________________________________
sda : is-GPT, no-BIOSboot, has---ESP, not-usb, not-mmc, no-os, no-wind, 2048 sectors * 512 bytes
Partitions info (1/3): _________________________________________________________
sda1 : no-os, 64, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, not-far
sda2 : no-os, 64, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, farbios
Partitions info (2/3): _________________________________________________________
sda1 : is---ESP, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot
sda2 : isnotESP, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot
Partitions info (3/3): _________________________________________________________
sda1 : not--sepboot, no---boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, no--grub.d, sda
sda2 : maybesepboot, no---boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, no--grub.d, sda
fdisk -l (filtered): ___________________________________________________________
Disk sda: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Disk identifier: 2111D8BC-769C-4D52-BE2C-F6D7FEBCF331
Start End Sectors Size Type
sda1 2048 1050623 1048576 512M EFI System
sda2 1050624 976771071 975720448 465.3G Linux filesystem
Disk sdb: 14.94 GiB, 16043212800 bytes, 31334400 sectors
Disk identifier: 0x749c9c64
Boot Start End Sectors Size Id Type
sdb1 * 0 7365599 7365600 3.5G 0 Empty
sdb2 576 10687 10112 4.9M ef EFI (FAT-12/16/32)
sdb3 7368704 31334399 23965696 11.4G 83 Linux
parted -lm (filtered): _________________________________________________________
sda:500GB:scsi:512:512:gpt:ATA TOSHIBA MQ01ABF0:;
1:1049kB:538MB:537MB:fat32:EFI System Partition:boot, esp;
2:538MB:500GB:500GB:ext4::;
sdb:16.0GB:scsi:512:512:msdos:takeMS Colorline:;
2:295kB:5472kB:5177kB:::esp;
3:3773MB:16.0GB:12.3GB:ext4::;
Free space >10MiB: ______________________________________________________________
sdb: 5.22MiB:3598MiB:3593MiB
blkid (filtered): ______________________________________________________________
NAME FSTYPE UUID PARTUUID LABEL PARTLABEL
sda
├─sda1 vfat E70C-C175 d9b63b9a-5807-4b6b-9e2d-aedb48791571 EFI System Partition
└─sda2 ext4 febb4a53-7158-4342-9221-0a39d23530ba 76a327c4-17b6-466f-ac62-7d134e97d6f6
sdb iso9660 2025-05-30-01-29-56-00 Zorin OS 17.3 Core 64bit
├─sdb1 iso9660 2025-05-30-01-29-56-00 749c9c64-01 Zorin OS 17.3 Core 64bit
├─sdb2 vfat A0A5-EC30 749c9c64-02
└─sdb3 ext4 95684013-bfe8-43cf-a4b9-e52f25da7a0c 749c9c64-03 writable
Mount points (filtered): _______________________________________________________
Avail Use% Mounted on
/dev/disk/by-label/writable[/install-logs-2026-03-04.1/crash] 10.5G 1% /var/crash
/dev/disk/by-label/writable[/install-logs-2026-03-04.1/log] 10.5G 1% /var/log
/dev/sda1 503.3M 1% /mnt/boot-sav/sda1
/dev/sda2 330.2G 23% /mnt/boot-sav/sda2
/dev/sdb1 0 100% /cdrom
efivarfs 914B 94% /sys/firmware/efi/efivars
Mount options (filtered): ______________________________________________________
===================== sda1/efi/ubuntu/grub.cfg (filtered) ======================
search.fs_uuid febb4a53-7158-4342-9221-0a39d23530ba root hd0,gpt2
set prefix=($root)'/boot/grub'
configfile $prefix/grub.cfg
======================== Unknown MBRs/Boot Sectors/etc =========================
Unknown BootLoader on sdb
Suggested repair: ______________________________________________________________
The default repair of the Boot-Repair utility would not act on the boot.
That's unbelieveable..
So, your bootloader is on sda1, and you are not using MBR, but are using EFI boot
So, that looks good.
If you can reach grub menu, have you tried Recovery - Recovery menu > fsck?
Nope, I can't do this that way.
All was gone to... When I input at grub "ls" show error: failure reading sector 0x0 from hd0 and to on device hd0 is no known filesystem detected, sector size 512B. No partitions showing also.
I find the Sentence at the Beginning interesting:
This means the system is using EFI, not MBR (Legacy).
From this; running fsck is definitely needed.
Ziga88, since you already said you cannot even reach the grub menu to run fsck, the only other way is the complex way: