Can't boot into EOS. Freezes at grub loading screen

General system Kernel, boot, graphics & hardware
1

I have noticed in the last couple of months that I would run into an issue that seems to be repeating itself about once a week. I boot up EOS and when it gets to the grub menu, it just freezes where it says that message along the lines of “loading ramdisk”. Normally I was able to fix this using the EOS ISO booted into a live session. I would then use gparted to check the drive and when I would reboot it would work again as normal. Then a week or so later it would occur again. Rinse and repeat.

This time the issue is not repairable. Reason why is I changed the ISO I had on ventoy to the new Galileo release and this ISO does not boot like the last one. It gets to the black screen that has two lines that say “downloading” as seen in the image below and won’t move further.

image
image1920×1440 212 KB

2

This is concerning. Is your disk failing or are you dual-booting without “fast startup” in Windows being disabled?

Try it without ventoy.

3

Yea, it certainly doesn’t seem normal to have to keep fixing whatever it is that keeps causing it to not boot. The problem was occurring first on systemd boot, and I thought changing to grub would fix it permanently, but it’s not the case at all.

I don’t use windows, only Linux. I’m typing this from my Debian machine.

I’ll try right now without Ventoy and report back.

4

Unless you are regularly shutting down improperly such as letting a laptop battery die, pulling the plug or holding the power button to force the machine off, you should really check and see if that disk is failing.

It isn’t normal that your filesystem would be regularly getting corrupted.

5

I have to use ventoy. My system only recognizes USB ISO’s using the GPT partition table. Using MS-DOS partition table does not recognize the USB.

What did the EOS ISO change for it to not work on ventoy? I try both normal and grub boot in ventoy and both freeze.

Is there anywhere I can download the previous ISO? This would temporarily give me access back to my system.

6

We didn’t make any changes to the ISO building process. It does, however, use a newer kernel.

Have you tried updating ventoy?

7

I’m not sure why, but when I try to run the ventoy executable, nothing happens. I opened terminal in the files directory and ran ./VentoyGUI.x86_64 and it still won’t run. A log file was generated in the ventoy folder.

[2023/10/26 12:18:00]
[2023/10/26 12:18:00] =========================================================
[2023/10/26 12:18:00] =========================================================
[2023/10/26 12:18:00] =============== VentoyGui x86_64 ===============
[2023/10/26 12:18:00] =========================================================
[2023/10/26 12:18:00] =========================================================
[2023/10/26 12:18:00] log file is <log.txt>
[2023/10/26 12:18:00] pid:35477 ppid:35471 uid:1000 euid:1000
[2023/10/26 12:18:00] adjust dir:1 current path:/home/nomad/Downloads/ventoy-1.0.96
[2023/10/26 12:18:00] =========RAW ARGS BEGIN===========
[2023/10/26 12:18:00] argv[0]=<./VentoyGUI.x86_64>
[2023/10/26 12:18:00] =========RAW ARGS END===========
[2023/10/26 12:18:00] uname -m <x86_64> 64bit
[2023/10/26 12:18:00] Build bit is 64 (x86_64)
[2023/10/26 12:18:00] Now detect the GUI type …
[2023/10/26 12:18:00] 1417 libs found in cache format 1
[2023/10/26 12:18:00] LIB:<libgtk-4.so.1>
[2023/10/26 12:18:00] LIB:<libgtk-3.so.0>
[2023/10/26 12:18:00] LIB:<libgtk-x11-2.0.so.0>
[2023/10/26 12:18:00] LIB:<libQt5X11Extras.so.5>
[2023/10/26 12:18:00] ldconfig lib flags 0x17
[2023/10/26 12:18:00] lib flags GLADE2:[NO] GTK2:[YES] GTK3:[YES] GTK4:[YES] QT4:[NO] QT5:[YES] QT6:[NO]
[2023/10/26 12:18:00] distro_check_gui_env …
[2023/10/26 12:18:00] Key arch is not found in json data.
[2023/10/26 12:18:00] check <DESKTOP_SESSION>
[2023/10/26 12:18:00] Key arch is not found in json data.
[2023/10/26 12:18:00] check <DESKTOP_SESSION>
[2023/10/26 12:18:00] Key arch is not found in json data.
[2023/10/26 12:18:00] check <DESKTOP_SESSION>
[2023/10/26 12:18:00] Can not distinguish GTK and QT, default use GTK.
[2023/10/26 12:18:00] This is gtk3 X environment.
[2023/10/26 12:18:00] exe = /home/nomad/Downloads/ventoy-1.0.96/tool/x86_64/Ventoy2Disk.gtk3
[2023/10/26 12:18:00] execute permission check success.
[2023/10/26 12:18:00] EUID check failed.
[2023/10/26 12:18:00] try restart self by pkexec …
[2023/10/26 12:18:00] pkexec not found
[2023/10/26 12:18:00] ### Please run with root privileges. ###

image

8

It looks like pkexec isn’t being found on whatever distro you are running.

Try running it with sudo.

9

sudo ventoy -u /dev/sdX will update the ventoy installed on device /dev/sdX.

10

we need to find out what’s happening, why can’t you boot, you need to change the grub command line options:
remove quiet and increase the loglevel, idk maybe 5 or 6 (max 7) in GRUB_CMDLINE_LINUX_DEFAULT

you can do this before boot by pressing E in grub

11

There is no quiet in the linux line of grub. As soon as I set the loglevel from 3 to 6 it goes to the same grub boot and freezes. I have to do a hard reset each time.

12

I am running Debian Stable. Sudo is giving me a command error.

sudo: /VentoyGUI.x86_64: command not found

13

What is Ventoy LiveCD.ISO? Can I just write this with popsicle and use it the same way?

Edit: NVM, it writes it as MS-DOS partition table, so I can’t even launch into it.

14

Which boot mode did you use in Ventoy’s boot menu?
Normal mode or Grub mode?
Grub mode should work. Well, it has for me so far.

15

Grub mode is what I have always had to use, and then followed by ‘nomodeset’. Previous ISO it worked, new ISO freezes.

16

I should note, other distros I have on Ventoy boot just fine on grub mode. Debian and Arch boot fine. Even live session of FreeBSD boots.

17

Did you check the integrity of your downloaded EnOS’ ISO?

18

I deleted it and redownloaded it again from a different mirror link. Same result.

19

I missed this msg. Yeah, I ran that and ventoy was already up-to-date

nomad@debian:~/Downloads/ventoy-1.0.96$ sudo sh Ventoy2Disk.sh -u /dev/sda
[sudo] password for nomad:

  Ventoy: 1.0.96  x86_64
  longpanda admin@ventoy.net
  https://www.ventoy.net

Upgrade operation is safe, all the data in the 1st partition (iso files and other) will be unchanged!

Update Ventoy 1.0.96 ===> 1.0.96 Continue? (y/n) y
esp partition processing …

Update Ventoy on /dev/sda successfully finished.

nomad@debian:~/Downloads/ventoy-1.0.96$

1 Like
20

I found the previous EOS ISO torrent link and downloaded it to my ventoy. I tried to boot from that as well, and it brought me to an error this time surprisingly: HDMI/DP requires binding with gfx driver

So this time I tried to live boot fedora instead, and it booted into the live environment. I ran "KDE Partition Manager’ and ran check on my OS drive to fix errors, and now I am back into my system thankfully.

This still doesn’t explain why this keeps happening and why it seems to be getting worse.

sudo smartctl -a /dev/nvme0n1
[sudo] password for nomad:
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.6.2-arch1-1] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number: Samsung SSD 970 EVO Plus 2TB
Serial Number:
Firmware Version: 4B2QEXM7
PCI Vendor/Subsystem ID: 0x144d
IEEE OUI Identifier: 0x002538
Total NVM Capacity: 2,000,398,934,016 [2.00 TB]
Unallocated NVM Capacity: 0
Controller ID: 6
NVMe Version: 1.3
Number of Namespaces: 1
Namespace 1 Size/Capacity: 2,000,398,934,016 [2.00 TB]
Namespace 1 Utilization: 177,052,237,824 [177 GB]
Namespace 1 Formatted LBA Size: 512
Namespace 1 IEEE EUI-64: 002538 54214091a9
Local Time is: Sun Nov 26 15:41:30 2023 PST
Firmware Updates (0x16): 3 Slots, no Reset required
Optional Admin Commands (0x0017): Security Format Frmw_DL Self_Test
Optional NVM Commands (0x0057): Comp Wr_Unc DS_Mngmt Sav/Sel_Feat Timestmp
Log Page Attributes (0x0f): S/H_per_NS Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg
Maximum Data Transfer Size: 128 Pages
Warning Comp. Temp. Threshold: 82 Celsius
Critical Comp. Temp. Threshold: 85 Celsius

Supported Power States
St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat
0 + 7.59W - - 0 0 0 0 0 0
1 + 7.59W - - 1 1 1 1 0 200
2 + 7.59W - - 2 2 2 2 0 1000
3 - 0.0500W - - 3 3 3 3 2000 1200
4 - 0.0050W - - 4 4 4 4 500 9500

Supported LBA Sizes (NSID 0x1)
Id Fmt Data Metadt Rel_Perf
0 + 512 0 0

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART/Health Information (NVMe Log 0x02)
Critical Warning: 0x00
Temperature: 46 Celsius
Available Spare: 100%
Available Spare Threshold: 10%
Percentage Used: 1%
Data Units Read: 83,704,677 [42.8 TB]
Data Units Written: 68,005,708 [34.8 TB]
Host Read Commands: 370,141,304
Host Write Commands: 172,131,520
Controller Busy Time: 1,554
Power Cycles: 228
Power On Hours: 1,268
Unsafe Shutdowns: 35
Media and Data Integrity Errors: 0
Error Information Log Entries: 0
Warning Comp. Temperature Time: 0
Critical Comp. Temperature Time: 0
Temperature Sensor 1: 46 Celsius
Temperature Sensor 2: 45 Celsius

Error Information (NVMe Log 0x01, 16 of 64 entries)
No Errors Logged

Read Self-test Log failed: Invalid Field in Command (0x002)