Ubuntu wont boot

kons

New Member
Joined
Aug 29, 2022
Messages
4
Reaction score
0
Credits
36
My laptop wont start Ubuntu anymore. When I turn it on, it shows me the Lenovo logo (Im on a thinkpad) and then black screen. When I use a USB with Ubuntu on it, it starts extremely slowly, but I'm eventually able to use the live try out mode. Another thing is that when I use the USB, I get to the grub menu, but without it, I can only get to the lenovo bios somehow. But no matter how long I wait, or how often I select my Ubuntu system in the bios system, it just wont start.
Does anyone have an idea what this could be, and how I can fix this? Any help would be greatly appreciated. Thanks!
 


Give us some more info on your machine which thinkpad? If you can boot to a terminal install inxi
Code:
sudo apt install inxi
And then run this command and post the output here.
Code:
inxi -Fxxxzr

It sounds like the boot sector may have been damaged. But can know for sure without more info.
 
Give us some more info on your machine which thinkpad? If you can boot to a terminal install inxi
Code:
sudo apt install inxi
And then run this command and post the output here.
Code:
inxi -Fxxxzr

It sounds like the boot sector may have been damaged. But can know for sure without more info.
Im not able to boot into terminal without the installation usb, at least to my abilities. However I did it from the try out mode of the ubuntu usb, i how that this works also.
Code:
System:
  Kernel: 5.15.0-43-generic arch: x86_64 bits: 64 compiler: gcc v: 11.2.0
    Desktop: GNOME v: 42.2 tk: GTK v: 3.24.33 wm: gnome-shell dm: GDM3 v: 42.0
    Distro: Ubuntu 22.04.1 LTS (Jammy Jellyfish)
Machine:
  Type: Laptop System: LENOVO product: 20YDS00G00 v: ThinkPad E14 Gen 3
    serial: <superuser required> Chassis: type: 10 serial: <superuser required>
  Mobo: LENOVO model: 20YDS00G00 serial: <superuser required> UEFI: LENOVO
    v: R1OET26W (1.05 ) date: 04/28/2021
Battery:
  ID-1: BAT0 charge: 29.2 Wh (56.5%) condition: 51.7/57.0 Wh (90.7%)
    volts: 11.6 min: 11.5 model: SMP 5B11C732 type: Li-poly serial: <filter>
    status: discharging cycles: 253
CPU:
  Info: 6-core model: AMD Ryzen 5 5500U with Radeon Graphics bits: 64
    type: MT MCP smt: enabled arch: Zen 2 level: v3 rev: 1 cache: L1: 384 KiB
    L2: 3 MiB L3: 8 MiB
  Speed (MHz): avg: 1334 high: 2070 min/max: 400/4056 boost: enabled cores:
    1: 1097 2: 1097 3: 1097 4: 1098 5: 1097 6: 1098 7: 1035 8: 1022 9: 1617
    10: 1616 11: 2070 12: 2070 bogomips: 50301
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: AMD Lucienne vendor: Lenovo driver: amdgpu v: kernel
    arch: GCN-5.1 pcie: speed: 8 GT/s lanes: 16 ports: active: eDP-1
    empty: DP-1,HDMI-A-1 bus-ID: 04:00.0 chip-ID: 1002:164c class-ID: 0300
  Device-2: IMC Networks Integrated Camera type: USB driver: uvcvideo
    bus-ID: 1-3:2 chip-ID: 13d3:56fb class-ID: fe01 serial: <filter>
  Display: x11 server: X.Org v: 1.21.1.3 with: Xwayland v: 22.1.1
    compositor: gnome-shell driver: X: loaded: amdgpu
    unloaded: fbdev,modesetting,radeon,vesa gpu: amdgpu display-ID: :0
    screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
    s-diag: 582mm (22.93")
  Monitor-1: eDP-1 mapped: eDP model: ChiMei InnoLux 0x140a res: 1920x1080
    hz: 60 dpi: 158 size: 309x173mm (12.17x6.81") diag: 354mm (13.9") modes:
    max: 1920x1080 min: 640x480
  Message: Unable to show GL data. Required tool glxinfo missing.
Audio:
  Device-1: AMD Renoir Radeon High Definition Audio vendor: Lenovo
    driver: snd_hda_intel v: kernel pcie: speed: 8 GT/s lanes: 16
    bus-ID: 04:00.1 chip-ID: 1002:1637 class-ID: 0403
  Device-2: AMD Raven/Raven2/FireFlight/Renoir Audio Processor
    vendor: Lenovo driver: N/A pcie: speed: 8 GT/s lanes: 16 bus-ID: 04:00.5
    chip-ID: 1022:15e2 class-ID: 0480
  Device-3: AMD Family 17h HD Audio vendor: Lenovo driver: snd_hda_intel
    v: kernel pcie: speed: 8 GT/s lanes: 16 bus-ID: 04:00.6 chip-ID: 1022:15e3
    class-ID: 0403
  Sound Server-1: ALSA v: k5.15.0-43-generic running: yes
  Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: Lenovo driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1
    port: 3000 bus-ID: 02:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: enp2s0 state: down mac: <filter>
  Device-2: Realtek RTL8822CE 802.11ac PCIe Wireless Network Adapter
    vendor: Lenovo driver: rtw_8822ce v: N/A pcie: speed: 2.5 GT/s lanes: 1
    port: 2000 bus-ID: 03:00.0 chip-ID: 10ec:c822 class-ID: 0280
  IF: wlp3s0 state: up mac: <filter>
Bluetooth:
  Device-1: Realtek Bluetooth Radio type: USB driver: btusb v: 0.8
    bus-ID: 3-4:3 chip-ID: 0bda:c123 class-ID: e001 serial: <filter>
  Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter>
    bt-v: 3.0 lmp-v: 5.1 sub-v: 6d7d hci-v: 5.1 rev: 19b7
Drives:
  Local Storage: total: 3.74 GiB used: 5.3 MiB (0.1%)
  ID-1: /dev/sda type: USB vendor: Generic model: Flash Disk size: 3.74 GiB
    type: SSD serial: <filter> rev: 8.07 scheme: GPT
Partition:
  ID-1: / size: 11.16 GiB used: 172.4 MiB (1.5%) fs: overlay source: ERR-102
  ID-2: /var/log size: 147.8 MiB used: 5.3 MiB (3.6%) fs: ext4
    dev: /dev/sda4
Swap:
  Alert: No swap data was found.
Sensors:
  Missing: Required tool sensors not installed. Check --recommends
Repos:
  Packages: 1852 pm: dpkg pkgs: 1843 pm: snap pkgs: 9
  Active apt repos in: /etc/apt/sources.list
    1: deb cdrom:[Ubuntu 22.04.1 LTS _Jammy Jellyfish_ - Release amd64 (20220809.1)]/ jammy main restricted
    2: deb http://archive.ubuntu.com/ubuntu/ jammy main restricted
    3: deb http://security.ubuntu.com/ubuntu/ jammy-security main restricted
    4: deb http://archive.ubuntu.com/ubuntu/ jammy-updates main restricted
Info:
  Processes: 327 Uptime: 8m wakeups: 1 Memory: 22.32 GiB used: 2.26 GiB
  (10.1%) Init: systemd v: 249 target: graphical (5) default: graphical
  Compilers: gcc: N/A Shell: Bash v: 5.1.16 running-in: gnome-terminal
  inxi: 3.3.21
 
Try running startx at the prompt. :)

If that fails you may need boot repair.

Are you getting any error messages?
 
Try running startx at the prompt. :)

If that fails you may need boot repair.

Are you getting any error messages?
Can I do that from the live Ubuntu usb? Without that I can get to any terminal or promt, only black screen.

Also, if I try to do boot repair from the try out mode, I only get the option to create summary , but not do recommended repairs. Here is the summary:
Code:
boot-repair-4ppa200                                              [20220830_1206]

============================== Boot Info Summary ===============================


sda: ___________________________________________________________________________

    File system:       iso9660
    Boot sector type:  Grub2 (v1.99-2.00)
    Boot sector info:  Grub2 (v1.99-2.00) is installed in the boot sector of
                       sda and looks at sector 0 of the same hard drive for
                       core.img, but core.img can not be found at this
                       location.
    Mounting failed:   mount: /mnt/BootInfo/FD/sda: /dev/sda ist bereits eingehängt oder wird gerade benutzt.


================================ 0 OS detected =================================


================================ Host/Hardware =================================

CPU architecture: 64-bit
Video: Lucienne from Advanced Micro Devices, Inc. [AMD/ATI]
Live-session OS is Ubuntu 64-bit (Ubuntu 22.04.1 LTS, jammy, x86_64)

===================================== UEFI =====================================

BIOS/UEFI firmware: R1OET26W (1.05 )(1.5) from LENOVO
The firmware is EFI-compatible, and is set in EFI-mode for this live-session.
SecureBoot disabled - SecureBoot disabled - Bitte melden Sie diese Nachricht an [email protected].
BootCurrent: 001B
Timeout: 0 seconds
BootOrder: 0000,0016,0017,0018,0019,001A,001B,001C
Boot0000* ubuntu    HD(1,GPT,c62d7773-1843-4ebc-b99b-38706fd63fa9,0x800,0x100000)/File(\EFI\ubuntu\shimx64.efi)
Boot0010  Setup    FvFile(721c8b66-426c-4e86-8e99-3457c46ab0b9)
Boot0011  Boot Menu    FvFile(126a762d-5758-4fca-8531-201a7f57f850)
Boot0012  Diagnostic Splash Screen    FvFile(a7d8d9a6-6ab0-4aeb-ad9d-163e59a7a380)
Boot0013  Lenovo Diagnostics    FvFile(3f7e615b-0d45-4f80-88dc-26b234958560)
Boot0014  Startup Interrupt Menu    FvFile(f46ee6f4-4785-43a3-923d-7f786c3c8479)
Boot0015  Rescue and Recovery    FvFile(665d3f60-ad3e-4cad-8e26-db46eee9f1b5)
Boot0016* USB CD    VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,86701296aa5a7848b66cd49dd3ba6a55)
Boot0017* USB FDD    VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,6ff015a28830b543a8b8641009461e49)
Boot0018* NVMe0    VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,001c199932d94c4eae9aa0b6e98eb8a400)
Boot0019* NVMe1    VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,001c199932d94c4eae9aa0b6e98eb8a401)
Boot001A* ATA HDD0    VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f600)
Boot001B* USB HDD    VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,33e821aaaf33bc4789bd419f88c50803)
Boot001C* PXE BOOT    VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,78a84aaf2b2afc4ea79cf5cc8f3d3803)
Boot001D  Regulatory Information    FvFile(478c92a0-2622-42b7-a65d-5894169e4d24)


============================= Drive/Partition Info =============================

Disks info: ____________________________________________________________________


Partitions info (1/3): _________________________________________________________


Partitions info (2/3): _________________________________________________________


Partitions info (3/3): _________________________________________________________


fdisk -l (filtered): ___________________________________________________________

Disk sda: 3.74 GiB, 4010803200 bytes, 7833600 sectors
Disk identifier: 9240A165-D190-4AB6-8A10-46DC207B42EE
        Start     End Sectors  Size Type
sda1       64 7465119 7465056  3.6G Microsoft basic data
sda2  7465120 7473615    8496  4.1M EFI System
sda3  7473616 7474215     600  300K Microsoft basic data
sda4  7475200 7833536  358337  175M Linux filesystem

parted -lm (filtered): _________________________________________________________

sda:4011MB:scsi:512:512:gpt:Generic Flash Disk:;
1:32.8kB:3822MB:3822MB::ISO9660:hidden, msftdata;
2:3822MB:3826MB:4350kB::Appended2:boot, esp;
3:3826MB:3827MB:307kB::Gap1:hidden, msftdata;
4:3827MB:4011MB:183MB:ext4::;

blkid (filtered): ______________________________________________________________

NAME   FSTYPE   UUID                                 PARTUUID                             LABEL                    PARTLABEL
sda    iso9660  2022-08-10-16-21-45-00                                                    Ubuntu 22.04.1 LTS amd64
├─sda1 iso9660  2022-08-10-16-21-45-00               9240a165-d190-4ab6-8a11-46dc207b42ee Ubuntu 22.04.1 LTS amd64 ISO9660
├─sda2 vfat     8D6C-A9F8                            9240a165-d190-4ab6-8a12-46dc207b42ee ESP                      Appended2
├─sda3                                               9240a165-d190-4ab6-8a13-46dc207b42ee                          Gap1
└─sda4 ext4     512ecb01-9321-4821-bfdd-b887816c8cd0 222617eb-35cf-7641-af78-d2bb5eb9cf3d writable                 

Mount points (filtered): _______________________________________________________

                                                               Avail Use% Mounted on
/dev/disk/by-label/writable[/install-logs-2022-08-30.0/crash] 129.4M   4% /var/crash
/dev/disk/by-label/writable[/install-logs-2022-08-30.0/log]   129.4M   4% /var/log
/dev/sda1                                                          0 100% /cdrom

Mount options (filtered): ______________________________________________________

/dev/disk/by-label/writable[/install-logs-2022-08-30.0/crash] ext4            rw,relatime
/dev/disk/by-label/writable[/install-logs-2022-08-30.0/log]   ext4            rw,relatime
/dev/sda1                                                     iso9660         ro,noatime,nojoliet,check=s,map=n,blocksize=2048,iocharset=utf8



Suggested repair: ______________________________________________________________

The default repair of the Boot-Repair utility would not act on the boot.
 
Last edited:
If it won't boot from the HD. I would say something is corrupt in the Install itself and I would try to backup any important files using the live session and do a complete reinstall of the system. Paying attention to how the boot loader is installed If this is a Linux only machine - turn off secure boot and fast boot if it has it. and use legacy bios if available. good luck
 
Last edited:
If if won't boot from the HD. I would say something is corrupt in the Install itself and I would try to back any important files using the live session and do a complete reinstall of the system. Paying attention to how the boot loader is install If this is a Linux only machine - turn off secure boot and fast boot if it has it. and use legacy bios if available. good luck
Agreed-
If the distribution won't boot something is corrupt.
In fact, the mounting failed in the output posted in post #5.

Looking more at the additional output:
Code:
The default repair of the Boot-Repair utility would not act on the boot.

***Looks like the boot image is corrupt.***

Secure boot is already disabled:-
 
kons wrote:
when I use the USB, I get to the grub menu, but without it, I can only get to the lenovo bios somehow.
In that case you might consider re-installing grub as outlined here:

Hopefully, grub will pick up the OS and boot it. If, after successful installation of grub, but continued failure to boot, at least you'll know it's not a problem with grub, but something else.
 
kons wrote:

In that case you might consider re-installing grub as outlined here:

Hopefully, grub will pick up the OS and boot it. If, after successful installation of grub, but continued failure to boot, at least you'll know it's not a problem with grub, but something else.
So maybe this is a stupid question, but to do that I need to know the name of the disk (like sdX), right? I tried figuring out which it is, and what the USB is, but when I run lsblk for example, this is what i get:
Code:
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
loop0    7:0    0   2.1G  1 loop /rofs
loop1    7:1    0    62M  1 loop /snap/core20/1587
loop2    7:2    0 163.3M  1 loop /snap/firefox/1635
loop3    7:3    0     4K  1 loop /snap/bare/5
loop4    7:4    0 400.8M  1 loop /snap/gnome-3-38-2004/112
loop5    7:5    0  91.7M  1 loop /snap/gtk-common-themes/1535
loop6    7:6    0  45.9M  1 loop /snap/snap-store/582
loop7    7:7    0    47M  1 loop /snap/snapd/16292
loop8    7:8    0   284K  1 loop /snap/snapd-desktop-integration/14
sda      8:0    1   3.7G  0 disk
├─sda1   8:1    1   3.6G  0 part /cdrom
├─sda2   8:2    1   4.1M  0 part
├─sda3   8:3    1   300K  0 part
└─sda4   8:4    1   175M  0 part /var/crash
                                 /var/log

So if I understand this correctly, sda is the usb, but where is my original ubuntu then?


Also, this is the output of fdsik -l:
Code:
Disk /dev/loop0: 2.13 GiB, 2288189440 bytes, 4469120 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


Disk /dev/loop1: 61.96 MiB, 64970752 bytes, 126896 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


Disk /dev/loop2: 163.29 MiB, 171225088 bytes, 334424 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


Disk /dev/loop3: 4 KiB, 4096 bytes, 8 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


Disk /dev/loop4: 400.8 MiB, 420265984 bytes, 820832 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


Disk /dev/loop5: 91.69 MiB, 96141312 bytes, 187776 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


Disk /dev/loop6: 45.86 MiB, 48091136 bytes, 93928 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


Disk /dev/loop7: 46.96 MiB, 49242112 bytes, 96176 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


Disk /dev/sda: 3.74 GiB, 4010803200 bytes, 7833600 sectors
Disk model: Flash Disk     
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 9240A165-D190-4AB6-8A10-46DC207B42EE

Device       Start     End Sectors  Size Type
/dev/sda1       64 7465119 7465056  3.6G Microsoft basic data
/dev/sda2  7465120 7473615    8496  4.1M EFI System
/dev/sda3  7473616 7474215     600  300K Microsoft basic data
/dev/sda4  7475200 7833536  358337  175M Linux filesystem


Disk /dev/loop8: 284 KiB, 290816 bytes, 568 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
 
kons wrote:
I need to know the name of the disk (like sdX)
According to the inxi output on your machine, it doesn't look like a hard drive was detected.
Drives:
Local Storage: total: 3.74 GiB used: 5.3 MiB (0.1%)
ID-1: /dev/sda type: USB vendor: Generic model: Flash Disk size: 3.74 GiB
type: SSD serial: <filter> rev: 8.07 scheme: GPT
Normally hard drive output, which is not a USB looks something like:
Drives:
Local Storage: total: 1.82 TiB used: 37.39 GiB (2.0%)
ID-1: /dev/sda vendor: Western Digital model: WD10EZEX-00WN4A0
size: 931.51 GiB
Boot repair output shows that what looks like block devices are seen, the two "nvme" lines.

I wonder if you can get the boot menu to come up when turning on the machine. My Lenovo Thinkpad uses the F12 key to bring that up, and then I can choose to boot from hard drive or usb.

If the ubuntu live usb isn't able to detect the hard drive, I would try a specialised rescue usb like systemrescuecd and see what it sees.
 
Last edited:
I think the problem is not software but hardware. That H.D. may have gone bad. It won't even show up on the inxi readout.
 
Last edited:
For times like this...I always have two things...a spare Drive and an Image of my OS.
happy0034.gif
 

Members online


Top