Not boot not disks


I am test 5 boot & not boot.

I am usb fedora 34, & it is disks. I am 2 tb disks is live & restore disks.

Do i is run fsck is mounted? Do it command is uuid?

1 Like

That is the grub boot menu.
Fedora 35 currently has the 5.17.5 kernel if you were to update.

You do not say exactly what the issue is. That menu does not show any errors.

Can you boot with one of the older kernels (5.16.18 or 5.16.19)? Some had trouble with the 5.16.20 kernel and it was quickly replaced with the 5.17.4 kernel update.

1 Like

Not boot.

One select - not boot
Two select. - not boot
,…

You write that none of the kernels you select boots. What does happen? We need some details.

(I am hospital … Sorry)

I am usb rescue, & disks & term.



It not boot?

1 Like

[liveuser@localhost-live ~]$ sudo fsck -V UUID=E7A7-ECAE

We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:

#1) Respect the privacy of others.
#2) Think before you type.
#3) With great power comes great responsibility.

fsck from util-linux 2.37.2
[/usr/sbin/fsck.vfat (1) – /dev/sda1] fsck.vfat /dev/sda1
fsck.fat 4.2 (2021-01-31)
/dev/sda1: 28 files, 3548/153290 clusters
[liveuser@localhost-live ~]$ sudo fsck -V UUID=4fabdff7-b16e-41c8-a105-84738b433500
fsck from util-linux 2.37.2
[/usr/sbin/fsck.ext4 (1) – /dev/sda2] fsck.ext4 /dev/sda2
e2fsck 1.46.3 (27-Jul-2021)
/dev/sda2: clean, 107/65536 files, 86196/262144 blocks
[liveuser@localhost-live ~]$ sudo fsck -V UUID=6fec64c0-a806-464e-9e7e-a72a403ba06e
fsck from util-linux 2.37.2
[/usr/sbin/fsck.btrfs (1) – /dev/sda3] fsck.btrfs /dev/sda3
If you wish to check the consistency of a BTRFS filesystem or
repair a damaged filesystem, see btrfs(8) subcommand ‘check’.
[liveuser@localhost-live ~]$ sudo btrfs check /dev/sda3
Opening filesystem to check…
ERROR: /dev/sda3 is currently mounted, use --force if you really intend to check the filesystem
[liveuser@localhost-live ~]$ sudo btrfs check /dev/sda3
Opening filesystem to check…
Checking filesystem on /dev/sda3
UUID: 6fec64c0-a806-464e-9e7e-a72a403ba06e
[1/7] checking root items
[2/7] checking extents
[3/7] checking free space cache
[4/7] checking fs roots
[5/7] checking only csums items (without verifying data)
[6/7] checking root refs
[7/7] checking quota groups skipped (not enabled on this FS)
found 312101376000 bytes used, no error found
total csum bytes: 279277308
total tree bytes: 14480097280
total fs tree bytes: 13515227136
total extent tree bytes: 582893568
btree space waste bytes: 2573984149
file data blocks allocated: 808210481152
referenced 661343227904
[liveuser@localhost-live ~]$

sudo btrfs check --repair /dev/sda3
enabling repair mode
WARNING:

Do not use --repair unless you are advised to do so by a developer
or an experienced user, and then only after having accepted that no
fsck can successfully repair all types of filesystem corruption. Eg.
some software or hardware bugs can fatally damage a volume.
The operation will start in 10 seconds.
Use Ctrl-C to stop it.

10 9 8 7 6 5 4 3 2 1
Starting repair.
Opening filesystem to check…
Checking filesystem on /dev/sda3
UUID: 6fec64c0-a806-464e-9e7e-a72a403ba06e
[1/7] checking root items
Fixed 0 roots.
[2/7] checking extents
No device size related problem found
[3/7] checking free space cache
cache and super generation don’t match, space cache will be invalidated
[4/7] checking fs roots
[5/7] checking only csums items (without verifying data)
[6/7] checking root refs
[7/7] checking quota groups skipped (not enabled on this FS)
found 312101376000 bytes used, no error found
total csum bytes: 279277308
total tree bytes: 14480097280
total fs tree bytes: 13515227136
total extent tree bytes: 582893568
btree space waste bytes: 2573984149
file data blocks allocated: 808210481152
referenced 661343227904
[liveuser@localhost-live ~]$

not boot!!

[liveuser@localhost-live ~]$ sudo btrfs check --clear-space-cache v1 /dev/sda3
Opening filesystem to check…
Checking filesystem on /dev/sda3
UUID: 6fec64c0-a806-464e-9e7e-a72a403ba06e
Free space cache cleared
[liveuser@localhost-live ~]$

[liveuser@localhost-live ~]$ sudo fsck -V UUID=6fec64c0-a806-464e-9e7e-a72a403ba06e
fsck from util-linux 2.37.2
[/usr/sbin/fsck.btrfs (1) – /dev/sda3] fsck.btrfs /dev/sda3
If you wish to check the consistency of a BTRFS filesystem or
repair a damaged filesystem, see btrfs(8) subcommand ‘check’.
[liveuser@localhost-live ~]$

strong textnot boot!!****

[liveuser@localhost-live ~]$ sudo btrfs check --repair /dev/sda3
enabling repair mode
WARNING:

Do not use --repair unless you are advised to do so by a developer
or an experienced user, and then only after having accepted that no
fsck can successfully repair all types of filesystem corruption. Eg.
some software or hardware bugs can fatally damage a volume.
The operation will start in 10 seconds.
Use Ctrl-C to stop it.

10 9 8 7 6 5 4 3 2 1
Starting repair.
Opening filesystem to check…
Checking filesystem on /dev/sda3
UUID: 6fec64c0-a806-464e-9e7e-a72a403ba06e
[1/7] checking root items
Fixed 0 roots.
[2/7] checking extents
No device size related problem found
[3/7] checking free space cache
[4/7] checking fs roots
[5/7] checking only csums items (without verifying data)
[6/7] checking root refs
[7/7] checking quota groups skipped (not enabled on this FS)
found 312096395264 bytes used, no error found
total csum bytes: 279277308
total tree bytes: 14480097280
total fs tree bytes: 13515227136
total extent tree bytes: 582893568
btree space waste bytes: 2573991882
file data blocks allocated: 808205500416
referenced 661338247168
[liveuser@localhost-live ~]$

liveuser@localhost-live ~]$ sudo fsck -V UUID=6fec64c0-a806-464e-9e7e-a72a403ba06e
fsck from util-linux 2.37.2
[/usr/sbin/fsck.btrfs (1) – /dev/sda3] fsck.btrfs /dev/sda3
If you wish to check the consistency of a BTRFS filesystem or
repair a damaged filesystem, see btrfs(8) subcommand ‘check’.

Help!! Help!! Help!!

Not boot!!

Do i is man btrfs is look btrfs-rescue?

Sudo btrfs-rescue is not path!!

We cannot tell you whether BTRFS is the origin of the problem if we do not know the very problem.

Before suggesting any means, we have to find out what the problem is. The information you provided so far does not help much. Currently, I do not see a reason to assume that BTRFS is the origin of the problem. If I got you right, your problem is that none of the kernels you can choose in GRUB is able to boot: therefore, I suggest that you …

  1. start your computer up to the GRUB menu (so, start it up to the point of the first picture you posted above, where you can choose the three kernels)
  2. start the 5.16.20-200 kernel and then make a picture of what happens next! → Is there an error screen? Does the screen freeze at some point? Does the computer simply restart? This is information we need.
  3. start the 5.16.19-200 kernel and then do the same as in 2). This is to compare if there is a difference between the two kernels.
  4. provide us with the pictures and answers to the questions in 2), so that we can analyze the problem.

This will enable us to determine the origin. If we know the origin, we can determine what to do next and how to fix it.

Also, I think the language barrier is a problem here in communication. Maybe you can use a translator like www.deepl.com? Maybe it supports your native language, and can facilitate the exchange of information.

1 Like

i have aphasia because stroke. i am live in virginia. i is old computer science, undergrad is computer science, and graduate is computer science.

GRUB menu:
5.16.20-200 & 5.16.19-200 & 5.16.19-200 is circle boot. no error screen.

i am reboot GRUB menu, and photos.

1 Like

I’m sorry. I was not aware of that.

Do you mean that if you boot any kernel, it reboots at some point and you just end up again in grub?

If we don’t have an error screen or so, it might be good to have the recent log files. You can start a live system and then go to a terminal. Mount your root partition at any mountpoint on the live system (I will assume that you mount it on /mnt/root). If you have a separated /var/ partition, you have to mount it on /mnt/root/var. Within the terminal, then do sudo chroot /mnt/root, and then get the log files of the recent boots:
sudo journalctl --boot=0
sudo journalctl --boot=-1
sudo journalctl --boot=-2

These three commands will output the recent three boots. Maybe the output of these commands can help us to identify the issue.

“Circle” boot - i am “no boot”

While booting, hit the ESC button so we can at least see what service fails to start or where the system hangs. Then take a new picture and upload it.


i am

sudo journalctl --boot=0 > /home/liveuser/journalctl.0

why? what? website is not text