[SOLVED] System stalls as it tries to enter grub

[ineuw]

Using a dual boot desktop with an upgraded LM Cinnamon 20.2 from 20.1. As of yesterday, I am having difficulties starting Grub when powering on. Sometimes, it hangs as it tries to load, or displays the grub option but is frozen. I set the motherboard to beep when entering grub and that is not happening. Grub finally loaded on the the fourth try. Uploaded the boot repair to https://paste.ubuntu.com/p/TB883RpYVk/. All disks are r/w.

In Windows 10, I would execute the online disk repair, or at least a system file check. But in Linux, I don't know where to start.

After grub, and before the login window, the Linux disk utility flashes but doesn't stay on. I will check my previous posts because this is a recurring issue and I resolved it before.

Code: Select all

$ inxi -Fxz
System:    Kernel: 5.4.0-80-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 
           Desktop: Cinnamon 5.0.5 Distro: Linux Mint 20.2 Uma base: Ubuntu 20.04 focal 
Machine:   Type: Desktop Mobo: ASRock model: B360 Pro4 serial: <filter> 
           UEFI: American Megatrends v: P4.30 date: 12/06/2019 
CPU:       Topology: Dual Core model: Intel Pentium Gold G5600 bits: 64 type: MT MCP 
           arch: Kaby Lake rev: B L2 cache: 4096 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31199 
           Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 
           4: 800 
Graphics:  Device-1: Intel 8th Gen Core Processor Gaussian Mixture Model vendor: ASRock 
           driver: i915 v: kernel bus ID: 00:02.0 
           Display: x11 server: X.Org 1.20.9 driver: modesetting unloaded: fbdev,vesa 
           resolution: 1536x864_59.00~59Hz 
           OpenGL: renderer: Mesa Intel UHD Graphics 630 (CFL GT2) v: 4.6 Mesa 20.2.6 
           direct render: Yes 
Audio:     Device-1: Intel Cannon Lake PCH cAVS vendor: ASRock driver: snd_hda_intel 
           v: kernel bus ID: 00:1f.3 
           Sound Server: ALSA v: k5.4.0-80-generic 
Network:   Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 3.2.6-k 
           port: efa0 bus ID: 00:1f.6 
           IF: eno1 state: up speed: 100 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 2.90 TiB used: 273.31 GiB (9.2%) 
           ID-1: /dev/sda vendor: SanDisk model: SDSSDHII120G size: 111.79 GiB 
           ID-2: /dev/sdb vendor: Seagate model: ST1000DM003-1SB10C size: 931.51 GiB 
           ID-3: /dev/sdc vendor: Seagate model: ST2000DM008-2FR102 size: 1.82 TiB 
           ID-4: /dev/sdd model: SATA3 64GB SSD size: 59.63 GiB 
Partition: ID-1: / size: 54.26 GiB used: 15.97 GiB (29.4%) fs: ext4 dev: /dev/sdd3 
           ID-2: swap-1 size: 3.75 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sdd2 
Sensors:   System Temperatures: cpu: 35.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Info:      Processes: 224 Uptime: 1h 54m Memory: 15.31 GiB used: 2.64 GiB (17.2%) 
           Init: systemd runlevel: 5 Compilers: gcc: 9.3.0 Shell: bash v: 5.0.17 
           inxi: 3.0.38 

[mikeflan]

I''m really not sure about this, but you can try this is you think it is best:
https://howtoubuntu.org/how-to-repair-r ... tu-live-cd

[ineuw]

I''m really not sure about this, but you can try this is you think it is best:
https://howtoubuntu.org/how-to-repair-r ... tu-live-cd

Much thanks. There is no reason why I shouldn't try.

[ineuw]

As Julius Caesar said, I tried it, it failed, ended up using boot-repair.

The process described works up to a point and then the author made an error in the instructions. What he instructed, plus what I tried to guess what he meant failed with the message that "cannot find the EFI folder". Tried it twice just to be certain. . . . .

Should have read this:

https://unix.stackexchange.com/question ... all#405525

[mikeflan]

If you want to report where the first procedure fails, this would be a good place to record that.

[ineuw]

If you want to report where the first procedure fails, this would be a good place to record that.

The https://unix.stackexchange.com/question ... all#405525 describes it precisely. Unfortunately, I haven't kept notes, or taken a photo, which I sometimes do. My problems rarely happen more than once as one can see from my posts.

[mikeflan]

The correct link is above, and here:
https://unix.stackexchange.com/question ... all#405525

[ineuw]

Thanks again for the reply. While this issue was resolved, the mounting problems with this upgraded installation from 20.1 to 20.2, I am installing a fresh copy.