Startup Errors - Need Help

Ask Fedora
1

Hey there, In the past couple of days I have been having a consistently inconstant booting into F40. I have Fedora Installed automatically in 2 drives (split) as I did post about it here if you wanna have more info.

During the system startup I select the 6.10.10-200.fc44 kernal boot option, sometimes It does boot successfully and sometimes it doesn’t, and when It doesn’t I try to see the ‘logs’ (pressing ESC) and I get lots of problems one of them is the same as this. But the solution in the Post didn’t help since

❯ cat /proc/cmdline
BOOT_IMAGE=(hd0,gpt2)/vmlinuz-6.10.10-200.fc40.x86_64
root=UUID=c8f974fd-0c0f-444c-98a7-60ef99f51177 ro rootflags=subvol=root
rd.driver.blacklist=nouveau modprobe.blacklist=nouveau rhgb quiet
rd.driver.blacklist=nouveau modprobe.blacklist=nouveau

so there is no resume=UUID=xxxx.

I would like to send the entire boot startup log or whatever you call it but I don’t know how to get it, Is there a place where those logs get saved or do I have to take a picture of it.

Auditional Info that may help:

❯ cat /etc/fstab

#
# /etc/fstab
# Created by anaconda on Thu Aug 29 15:47:52 2024
#
# Accessible filesystems, by reference, are maintained under '/dev/disk/'.
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info.
#
# After editing this file, run 'systemctl daemon-reload' to update systemd
# units generated from this file.
#
UUID=c8f974fd-0c0f-444c-98a7-60ef99f51177 /                       btrfs   subvol=root,compress=zstd:1 0 0
UUID=016aee7f-c3a8-4d6f-b905-3351a60a94a7 /boot                   ext4    defaults        1 2
UUID=F86B-B069          /boot/efi               vfat    umask=0077,shortname=winnt 0 2
UUID=c8f974fd-0c0f-444c-98a7-60ef99f51177 /home                   btrfs   subvol=home,compress=zstd:1 0 0

❯ lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
loop0         7:0    0     4K  1 loop /var/lib/snapd/snap/bare/5
loop1         7:1    0 119.1M  1 loop /var/lib/snapd/snap/bombsquad/23
loop2         7:2    0 120.3M  1 loop /var/lib/snapd/snap/bombsquad/28
loop3         7:3    0  55.4M  1 loop /var/lib/snapd/snap/core18/2846
loop4         7:4    0  55.7M  1 loop /var/lib/snapd/snap/core18/2829
loop5         7:5    0  74.3M  1 loop /var/lib/snapd/snap/core22/1612
loop6         7:6    0  74.2M  1 loop /var/lib/snapd/snap/core22/1621
loop7         7:7    0 150.3M  1 loop /var/lib/snapd/snap/figma-linux/197
loop8         7:8    0 164.8M  1 loop /var/lib/snapd/snap/gnome-3-28-1804/198
loop9         7:9    0  91.7M  1 loop /var/lib/snapd/snap/gtk-common-themes/1535
loop10        7:10   0  38.8M  1 loop /var/lib/snapd/snap/snapd/21759
sda           8:0    0 111.8G  0 disk 
└─sda1        8:1    0 111.8G  0 part 
zram0       252:0    0     8G  0 disk [SWAP]
nvme0n1     259:0    0 119.2G  0 disk 
├─nvme0n1p1 259:1    0   600M  0 part /boot/efi
├─nvme0n1p2 259:2    0     1G  0 part /boot
└─nvme0n1p3 259:3    0 117.7G  0 part /home
                                      /
2

Please don’t post the entire startup log, as it will contain lots of irrelevant detail. It is best to post concise text that relates to your issue. This can be found with web searches by others with the same issue.

The messages (as text, so suitable for forum posts) should be available using sudo dmesg for the current boot, or using journalctl – compare sudo dmesg -T |head with journalctl --no-hostname -b. Either method produces a lot of detail that is usually not relevant to a particular issue. journalctl has many options to filter output so you only see the relevant details. I would start by using the “priority” option with journalctl (see man journalctl for details). Note that journalctl output can produce very long lines, and that we don’t need to see your hostname. You can use journalctl --no-hostname <filter options>|cat to wrap long lines so text is suitable for posting.

3

I don’t know what Info I should send, there are a lot of thing colored in red (when using sudo dmesg, here they are:

[    0.126743] DMAR: [Firmware Bug]: No firmware reserved region can cover this RMRR [0x000000003b800000-0x000000003fffffff], contact BIOS vendor for fixes
[    0.126745] DMAR: [Firmware Bug]: Your BIOS is broken; bad RMRR [0x000000003b800000-0x000000003fffffff]
               BIOS vendor: American Megatrends Inc.; Ver: E16H8IWS.114; Product Version: REV:1.0

[    0.132230] x86/cpu: SGX disabled by BIOS.
[    0.934757] tpm tpm0: A TPM error (714) occurred attempting to create NULL primary
[    0.934761] tpm tpm0: TPM: security failed (NULL seed derivation): 714
[   32.145636] Bluetooth: hci0: Failed to send firmware data (-38)
[   34.339937] Bluetooth: hci0: command 0xfca6 tx timeout
[   34.339952] Bluetooth: hci0: Reading supported features failed (-110)
[   41.122608] Bluetooth: hci0: Malformed MSFT vendor event: 0x02
[   41.130678] Bluetooth: hci0: Reading supported features failed (-16)

repeating messages like this are everywhere replaced some info with ‘*’:

[16036.114204] ata4.00: exception Emask 0x10 SAct 0xffffffff SErr 0x440100 action 0x6 frozen
[16036.114209] ata4.00: irq_stat 0x08000000, interface fatal error
[16036.114211] ata4: SError: { UnrecovData CommWake Handshk }
[16036.114213] ata4.00: failed command: WRITE FPDMA QUEUED
[16036.114215] ata4.00: cmd 61/40:00:**:**:**/00:00:00:00:00/40 tag 0 ncq dma 32768 out
                        res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x10 (ATA bus error)
[16036.114220] ata4.00: status: { DRDY }
5

Please post logs as “pre-formatted” text using the </> button from the top line of the text entry panel. Your dmesg output has truncated lines.

Looks like you have multiple hardware problems. Check with your system vendor for BIOS updates. Some drive vendors provide bootable drive test tools.

If you boot the Fedora Workstation Live USB there is support for S.M.A.R.T in Gnome Disks. KDE Plasma Disks also has S.M.A.R.T support, but I have not used it.

You can install the command-line smartmon-tools in a “Live USB” session, but it isn’t persistent.

6

well the drive seems to be working fine sometimes and sometimes not LMAO. I will try the tools and I will update you guys.

7

I updated the bios not so long ago and there aren’t any new updates