My Grub bootloader is causing issues in Booting

Ask Fedora
, ,
1

Everything was file, a few days ago I even updated Fedora 40 to the latest version available from the Gnome store. After that I downloaded few Applications from the Gnome store in Flatpak. And it was still fine, no errors on Restarting as such. But, yesterday when I was switching on my system I encountered a few error message after booting into Fedora from Grub. A side note if relevant: The night before this happened I got a small pakage update, I don’t remember the name of it though, and after downloading the update I had shut down my laptop.

Like this :point_down:t2:

IMG_20240810_154926
IMG_20240810_1549261920×1390 101 KB

And when I click Enter (or any key) and go back to the Grub OS selection screen and again select Fedora to boot, then I get a little different error

Like this :point_down:t2:

IMG_20240810_154942
IMG_20240810_1549421920×983 75 KB

However, after 3-4 times of force shutting down the system and starting it again, gets me to boot into Fedora just fine.

I tried searching for this issue but all I found was a solution to reinstall Grub, which I would have done but I sensed it’s better to be sure before doing it as I also have a dual boot system which might have a share in the issue.

For additional information:
I installed Fedora 40 on my HP laptop with an i3 7th gen processor (integrated GPU) in a Dual Boot system with Windows 11. The /Root and /Home are 118 Gib in a shared Btrfs filesystem, and the /Boot is 900 Mib.

2

Hi there.

Given that after several trials you manage to start up the system, it means that the issue is not persistent. Could be disk related (disk health or space issues).

Could you provide the outputs of the following terminal commands (after a successful login):

  • information about your disk(s), by running: sudo fdisk -l, lsblk and df -h (different commands)
  • your boot entry for the default kernel, by running sudo grubby --info=DEFAULT
  • details about your system, by running inxi -Fzxx.

Please post all of the outputs as preformatted text, by using the </> button (or by applying Ctrl+E upon the selected text).

1 Like
3

Hello Mike,

Before providing you with the output of the terminal commands you asked, I would like to inform you about the mishap I faced yesterday with my system. So yesterday I again got some updates to a few apps along with a “GNOME App Service 46” update (I can’t recall the exact name but I guess you will get it anyhow).

After this I had shut down my laptop and then I went on to boot into my Windows 11 system. And then I got an error message from windows and it was informing me to boot into windows from a live USB and then fix it.

IMG_20240812_005057
IMG_20240812_0050571920×1328 226 KB

And after that now whenever I switch on my laptop, it directly gets into windows without showing Grub Selector and then windows throws an error on me and then I’m stuck on blue screen.

However I went on to my Manufacturer’s boot menu by pressing F9 after switching on the laptop and then I selected Fedora from there and then Grub came. However it was not booting just like that Fedora still shows me the error message for which I raised the Issue here. Nevertheless, going over to my boot menu and selecting fedora and repeating it 4-5 times got me into Fedora.

Please guide me to fix both of my systems without clean install…

Now, the Outputs of the Commands you asked:-

sudo fdisk -l

Disk /dev/sda: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: HGST HTS541010B7
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 0E55ACF8-1340-43F9-B0D1-034E1A6E78C5

Device          Start        End    Sectors   Size Type
/dev/sda1        2048  692869119  692867072 330.4G Microsoft basic data
/dev/sda2   692871168 1953259519 1260388352   601G Microsoft basic data
/dev/sda3  1953262991 1953525134     262144   128M Microsoft reserved

Partition 3 does not start on physical sector boundary.


Disk /dev/sdb: 238.47 GiB, 256060514304 bytes, 500118192 sectors
Disk model: SSD 256GB       
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: CC54AB0C-6EAE-41F1-B02D-C3E317640355

Device         Start       End   Sectors  Size Type
/dev/sdb1       2048   1128447   1126400  550M EFI System
/dev/sdb2    1128448   1161215     32768   16M Microsoft reserved
/dev/sdb3    1161216 248625151 247463936  118G Microsoft basic data
/dev/sdb4  498020352 500117503   2097152    1G Windows recovery environment
/dev/sdb5  248625152 250554367   1929216  942M Linux extended boot
/dev/sdb6  250554368 498020351 247465984  118G Linux filesystem

Partition table entries are not in disk order.


Disk /dev/zram0: 8 GiB, 8589934592 bytes, 2097152 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

lsblk

NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda      8:0    0 931.5G  0 disk 
├─sda1   8:1    0 330.4G  0 part /mnt/inbox
├─sda2   8:2    0   601G  0 part 
└─sda3   8:3    0   128M  0 part 
sdb      8:16   0 238.5G  0 disk 
├─sdb1   8:17   0   550M  0 part /boot/efi
├─sdb2   8:18   0    16M  0 part 
├─sdb3   8:19   0   118G  0 part 
├─sdb4   8:20   0     1G  0 part 
├─sdb5   8:21   0   942M  0 part /boot
└─sdb6   8:22   0   118G  0 part /home
                                 /
sr0     11:0    1  1024M  0 rom  
zram0  252:0    0     8G  0 disk [SWAP]

df -h

Filesystem      Size  Used Avail Use% Mounted on
/dev/sdb6       119G   20G   99G  17% /
devtmpfs        4.0M     0  4.0M   0% /dev
tmpfs           5.8G     0  5.8G   0% /dev/shm
efivarfs        128K   66K   58K  54% /sys/firmware/efi/efivars
tmpfs           2.4G  2.0M  2.4G   1% /run
tmpfs           5.8G   16K  5.8G   1% /tmp
/dev/sda1       331G  597M  330G   1% /mnt/inbox
/dev/sdb6       119G   20G   99G  17% /home
/dev/sdb5       909M  295M  552M  35% /boot
/dev/sdb1       546M   46M  501M   9% /boot/efi
tmpfs           1.2G  200K  1.2G   1% /run/user/1000

sudo grubby --info=DEFAULT

index=0
kernel="/boot/vmlinuz-6.9.12-200.fc40.x86_64"
args="ro rootflags=subvol=@ rhgb quiet"
root="UUID=e76e695e-46b4-482e-a65f-85faea706c82"
initrd="/boot/initramfs-6.9.12-200.fc40.x86_64.img"
title="Fedora Linux (6.9.12-200.fc40.x86_64) 40 (Workstation Edition)"
id="30208ce0cda142e2b726ee9e3bfc7a69-6.9.12-200.fc40.x86_64"

inxi -Fzxx

inxi -Fzxx
bash: inxi: command not found...
Install package 'inxi' to provide command 'inxi'? [N/y]
4

There are at least two red flags in your outputs. Neither seems to be critical, they can lead to the source of your issues though:

  • The first one is related to disk sda.

It is documented that this can cause performance issues, and it is usually fixed by moving the partition to a start position multiple of 8, but preferably multiple of the sector size ( 512 bytes logical or 4096 physical).

  • The second one is related to disk sdb.

Again, not a big issue, but it shows that some changes in partitions have taken place. If it wasn’t you, it might have been Windows.

Some questions:

  • Windows is installed on sdb, sda or both? If on both disks, which one is causing issues?

  • Do you know what /dev/sda3 is there for (recovery partition?), and if it went through any changes recently? See misalignment issue mentioned above.

  • Do you know what /dev/sdb4 is there for (again, recovery partition?), and if it went through any changes or it was created recently? It appears to have been created by Windows, but not at install time (assuming Windows was installed first), but rather later, given that it resides at the end of the disk (see start and end sectors, and also the message regarding partition table entries not being in disk order).

  • What is the output from blkid?

  • You’ll have to install inxi in order to provide the output from inxi -Fzxx.

5

You could have followed the prompt and installed inxi then provided the output as asked for.

I assume the grub menu appears when it is failing to boot properly.
If so then please try booting from one of the older kernels that may be installed to see if the issue is only the current (newest) kernel or if it is with booting in general.

If the menu does not display then it may be forced by pressing the ‘shift’ key as soon as the bios splash screen disappears and holding it down until the menu does appear.

This appears it may be a disk health issue and we need to narrow down the cause.
if not already installed, please install the smartmontools package then provide the output of sudo smartctl -a /dev/sda and sudo smartctl -a /dev/sdb so we may see the health of both drives.

6

A windows default installation always installs the recovery partition at the very end of the drive. It usually is partition 4 on the drive. When reducing the windows file system to allow space to install linux in dual boot the new partitions are numbered consecutively but not in order of the way positioned on the drive since partition 4 was created and numbered by the windows installation. This is totally normal when dual booting with windows.

sdb4 is not an issue.

1 Like
7

This appears not standard for a fedora installation.
Mine on a newly installed F40 VM shows this. Notice the difference in the args= line.

$ sudo grubby --info=DEFAULT
[sudo] password for jvian: 
index=0
kernel="/boot/vmlinuz-6.10.3-200.fc40.x86_64"
args="ro rootflags=subvol=root rhgb quiet"
root="UUID=cc9cee3b-fcdc-490f-8017-da9d3d5c3a60"
initrd="/boot/initramfs-6.10.3-200.fc40.x86_64.img"
title="Fedora Linux (6.10.3-200.fc40.x86_64) 40 (Workstation Edition)"
id="64e54e6600e74931889187e00be0393c-6.10.3-200.fc40.x86_64"

Have you changed the naming on the sub-volumes on your btrfs file system?
Are you booting with grub or using systemd-boot?

Please post the result of cat /proc/cmdline and cat /etc/kernel/cmdline, as well as cat /etc/default/grub

Booting problems often occur when certain changes (such as btrfs subvolume names, among others) are made and the change is not propagated into the initramfs image by using dracut before rebooting.

8

Can you please provide some more details on how to do it, because it is a system partition which cannot be moved by conventional Disk managers.

Both Windows and Fedora are installed in sdb, so sdb is the issue here.

Yes, It was automatically created by Windows.

Nothing, It is not giving any output.

System:
  Kernel: 6.10.3-200.fc40.x86_64 arch: x86_64 bits: 64 compiler: gcc
    v: 2.41-37.fc40
  Desktop: GNOME v: 46.4 tk: GTK v: 3.24.43 wm: gnome-shell dm: GDM
    Distro: Fedora Linux 40 (Workstation Edition)
Machine:
  Type: Laptop System: HP product: HP Laptop 15q-bu0xx v: Type1ProductConfigId
    serial: <superuser required> Chassis: type: 10 serial: <superuser required>
  Mobo: HP model: 832A v: 23.77 serial: <superuser required>
    part-nu: 4TS72PA#ACJ UEFI: Insyde v: F.68 date: 07/22/2021
Battery:
  ID-1: BAT1 charge: 27.5 Wh (85.7%) condition: 32.1/32.1 Wh (100.0%)
    volts: 15.8 min: 14.6 model: Hewlett-Packard PABAS0241231 serial: <filter>
    status: discharging
CPU:
  Info: dual core model: Intel Core i3-7100U bits: 64 type: MT MCP
    arch: Amber/Kaby Lake note: check rev: 9 cache: L1: 128 KiB L2: 512 KiB
    L3: 3 MiB
  Speed (MHz): avg: 551 high: 705 min/max: 400/2400 cores: 1: 700 2: 705
    3: 400 4: 400 bogomips: 19200
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
Graphics:
  Device-1: Intel HD Graphics 620 vendor: Hewlett-Packard driver: i915
    v: kernel arch: Gen-9.5 ports: active: eDP-1 empty: DP-1,HDMI-A-1,HDMI-A-2
    bus-ID: 00:02.0 chip-ID: 8086:5916
  Device-2: Chicony HP TrueVision HD Camera driver: uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 1-5:3 chip-ID: 04f2:b5d5
  Display: wayland server: X.org v: 1.20.14 with: Xwayland v: 24.1.2
    compositor: gnome-shell driver: gpu: i915 display-ID: 0
  Monitor-1: eDP-1 model: BOE Display 0x0687 res: 1920x1080 dpi: 142
    diag: 394mm (15.5")
  API: OpenGL v: 4.6 vendor: intel mesa v: 24.1.5 glx-v: 1.4 es-v: 3.2
    direct-render: yes renderer: Mesa Intel HD Graphics 620 (KBL GT2)
    device-ID: 8086:5916 display-ID: :0.0
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
Audio:
  Device-1: Intel Sunrise Point-LP HD Audio vendor: Hewlett-Packard
    driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:9d71
  API: ALSA v: k6.10.3-200.fc40.x86_64 status: kernel-api
  Server-1: JACK v: 1.9.22 status: off
  Server-2: PipeWire v: 1.0.7 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
Network:
  Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: Hewlett-Packard driver: r8169 v: kernel pcie: speed: 2.5 GT/s
    lanes: 1 port: 4000 bus-ID: 01:00.0 chip-ID: 10ec:8168
  IF: eno1 state: down mac: <filter>
  Device-2: Realtek RTL8723DE 802.11b/g/n PCIe Adapter
    vendor: Hewlett-Packard driver: rtw_8723de v: N/A pcie: speed: 2.5 GT/s
    lanes: 1 port: 3000 bus-ID: 02:00.0 chip-ID: 10ec:d723
  IF: wlo1 state: up mac: <filter>
Bluetooth:
  Device-1: Realtek Bluetooth 4.2 Adapter driver: btusb v: 0.8 type: USB
    rev: 1.1 speed: 12 Mb/s lanes: 1 bus-ID: 1-4:2 chip-ID: 0bda:b009
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 4.2
    lmp-v: 8
Drives:
  Local Storage: total: 1.14 TiB used: 21.11 GiB (1.8%)
  ID-1: /dev/sda vendor: HGST (Hitachi) model: HTS541010B7E610
    size: 931.51 GiB speed: 6.0 Gb/s serial: <filter>
  ID-2: /dev/sdb model: SSD 256GB size: 238.47 GiB speed: 1.5 Gb/s
    serial: <filter>
Partition:
  ID-1: / size: 118 GiB used: 20.14 GiB (17.1%) fs: btrfs dev: /dev/sdb6
  ID-2: /boot size: 908.9 MiB used: 354.5 MiB (39.0%) fs: ext4
    dev: /dev/sdb5
  ID-3: /boot/efi size: 546 MiB used: 45.8 MiB (8.4%) fs: vfat
    dev: /dev/sdb1
  ID-4: /home size: 118 GiB used: 20.14 GiB (17.1%) fs: btrfs dev: /dev/sdb6
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 54.0 C pch: 39.5 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 12 GiB available: 11.59 GiB used: 2.34 GiB (20.2%)
  Processes: 261 Power: uptime: 33m wakeups: 0 Init: systemd v: 255
    target: graphical (5) default: graphical
  Packages: pm: flatpak pkgs: 40 Compilers: N/A Shell: Bash v: 5.2.26
    running-in: gnome-terminal inxi: 3.3.34
9

Yes, extremely sorry for that. I have just posted the output of inxi -Fzxx in the reply before this one. Please check it out.

Yes, It’s with booting in general because Windows is also affected.

Yes, I had to do it for using Timeshift. I followed this article in terms of naming during installation to attain a Timeshift compatible system.
If it’s wrong, can you please provide a guide on to revert it without a reinstalling Fedora?

The outputs you asked:

sudo smartctl -a /dev/sda

smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.10.3-200.fc40.x86_64] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     HGST Travelstar Z5K1000
Device Model:     HGST HTS541010B7E610
Serial Number:    WXQ1A482VZ8E
LU WWN Device Id: 5 0014ee 65dfd4aac
Firmware Version: 03.01A03
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Form Factor:      2.5 inches
TRIM Command:     Available, deterministic
Device is:        In smartctl database 7.3/5528
ATA Version is:   ACS-3 T13/2161-D revision 5
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Mon Aug 12 08:27:59 2024 IST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

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

General SMART Values:
Offline data collection status:  (0x00)	Offline data collection activity
					was never started.
					Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0)	The previous self-test routine completed
					without error or no self-test has ever 
					been run.
Total time to complete Offline 
data collection: 		( 3600) seconds.
Offline data collection
capabilities: 			 (0x51) SMART execute Offline immediate.
					No Auto Offline data collection support.
					Suspend Offline collection upon new
					command.
					No Offline surface scan supported.
					Self-test supported.
					No Conveyance Self-test supported.
					Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
					power-saving mode.
					Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
					General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 ( 117) minutes.
SCT capabilities: 	       (0x303d)	SCT Status supported.
					SCT Error Recovery Control supported.
					SCT Feature Control supported.
					SCT Data Table supported.

SMART Attributes Data Structure revision number: 32
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   100   100   050    Pre-fail  Always       -       3
  3 Spin_Up_Time            0x0027   057   054   021    Pre-fail  Always       -       1258
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       36713
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002f   100   100   030    Pre-fail  Always       -       24520
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       6361
 10 Spin_Retry_Count        0x0033   100   100   050    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       3161
183 Runtime_Bad_Block       0x0032   100   100   000    Old_age   Always       -       0
184 End-to-End_Error        0x003b   100   100   097    Pre-fail  Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       1
188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -       2
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
191 G-Sense_Error_Rate      0x0032   001   001   000    Old_age   Always       -       24972
192 Power-Off_Retract_Count 0x0032   098   098   000    Old_age   Always       -       2349347111459
193 Load_Cycle_Count        0x0032   022   022   000    Old_age   Always       -       156506
194 Temperature_Celsius     0x0022   035   053   000    Old_age   Always       -       35 (Min/Max 31/35)
197 Current_Pending_Sector  0x0032   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   100   100   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   200   200   000    Old_age   Offline      -       0
240 Head_Flying_Hours       0x0032   100   100   000    Old_age   Always       -       660666
243 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       8889482

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%      3019         -
# 2  Short offline       Completed without error       00%       811         -
# 3  Short offline       Completed without error       00%       811         -
# 4  Short offline       Completed without error       00%       811         -
# 5  Short offline       Completed without error       00%       810         -
# 6  Extended offline    Completed without error       00%       805         -
# 7  Short offline       Completed without error       00%       803         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

The above only provides legacy SMART information - try 'smartctl -x' for more

sudo smartctl -a /dev/sdb

smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.10.3-200.fc40.x86_64] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:     SSD 256GB
Serial Number:    AA20231101256G535655
LU WWN Device Id: 0 000000 000000000
Firmware Version: HPS2227P
User Capacity:    256,060,514,304 bytes [256 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Form Factor:      2.5 inches
TRIM Command:     Available
Device is:        Not in smartctl database 7.3/5528
ATA Version is:   ACS-2 T13/2015-D revision 3
SATA Version is:  SATA 3.2, 6.0 Gb/s (current: 1.5 Gb/s)
Local Time is:    Mon Aug 12 08:30:49 2024 IST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

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

General SMART Values:
Offline data collection status:  (0x00)	Offline data collection activity
					was never started.
					Auto Offline Data Collection: Disabled.
Total time to complete Offline 
data collection: 		(    0) seconds.
Offline data collection
capabilities: 			 (0x00) 	Offline data collection not supported.
SMART capabilities:            (0x0000)	Automatic saving of SMART data		is not implemented.
Error logging capability:        (0x00)	Error logging supported.
					General Purpose Logging supported.

SMART Attributes Data Structure revision number: 1
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x0032   100   100   050    Old_age   Always       -       0
  5 Reallocated_Sector_Ct   0x0032   100   100   050    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   100   100   050    Old_age   Always       -       210
 12 Power_Cycle_Count       0x0032   100   100   050    Old_age   Always       -       440
160 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       0
161 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       100
163 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       12
164 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       9
165 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       24
166 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       4
167 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       11
168 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       0
169 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       100
175 Program_Fail_Count_Chip 0x0032   100   100   050    Old_age   Always       -       16777216
176 Erase_Fail_Count_Chip   0x0032   100   100   050    Old_age   Always       -       3532
177 Wear_Leveling_Count     0x0032   100   100   050    Old_age   Always       -       33812736
178 Used_Rsvd_Blk_Cnt_Chip  0x0032   100   100   050    Old_age   Always       -       131074
181 Program_Fail_Cnt_Total  0x0032   100   100   050    Old_age   Always       -       0
182 Erase_Fail_Count_Total  0x0032   100   100   050    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0032   100   100   050    Old_age   Always       -       163
194 Temperature_Celsius     0x0032   100   100   050    Old_age   Always       -       41
195 Hardware_ECC_Recovered  0x0032   100   100   050    Old_age   Always       -       1445
196 Reallocated_Event_Count 0x0032   100   100   050    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   100   100   050    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0032   100   100   050    Old_age   Always       -       0
199 UDMA_CRC_Error_Count    0x0032   100   100   050    Old_age   Always       -       0
232 Available_Reservd_Space 0x0032   100   100   050    Old_age   Always       -       100
241 Total_LBAs_Written      0x0032   100   100   050    Old_age   Always       -       24807
242 Total_LBAs_Read         0x0032   100   100   050    Old_age   Always       -       29988

SMART Error Log Version: 1
ATA Error Count: 1445 (device log contains only the most recent five errors)
	CR = Command Register [HEX]
	FR = Features Register [HEX]
	SC = Sector Count Register [HEX]
	SN = Sector Number Register [HEX]
	CL = Cylinder Low Register [HEX]
	CH = Cylinder High Register [HEX]
	DH = Device/Head Register [HEX]
	DC = Device Command Register [HEX]
	ER = Error register [HEX]
	ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 1445 occurred at disk power-on lifetime: 209 hours (8 days + 17 hours)
  When the command that caused the error occurred, the device was in an unknown state.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 40 30 c0 61 27 00   at LBA = 0x002761c0 = 2580928

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 20 30 c0 61 27 40 08      00:43:53.920  WRITE FPDMA QUEUED
  61 20 28 40 61 27 40 08      00:43:53.920  WRITE FPDMA QUEUED
  61 20 20 c0 61 07 40 08      00:43:53.920  WRITE FPDMA QUEUED
  61 20 18 40 61 07 40 08      00:43:53.920  WRITE FPDMA QUEUED
  60 00 48 80 44 aa 40 08      00:43:53.920  READ FPDMA QUEUED

Error 1444 occurred at disk power-on lifetime: 209 hours (8 days + 17 hours)
  When the command that caused the error occurred, the device was in an unknown state.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 40 88 c8 aa 87 00   at LBA = 0x0087aac8 = 8891080

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 08 88 c8 aa 87 40 08      00:43:53.850  WRITE FPDMA QUEUED
  60 00 80 80 3a aa 40 08      00:43:53.850  READ FPDMA QUEUED
  ef 10 02 00 00 00 a0 08      00:43:53.840  SET FEATURES [Enable SATA feature]
  ec 00 00 00 00 00 a0 08      00:43:53.840  IDENTIFY DEVICE
  ef 03 42 00 00 00 a0 08      00:43:53.840  SET FEATURES [Set transfer mode]

Error 1443 occurred at disk power-on lifetime: 209 hours (8 days + 17 hours)
  When the command that caused the error occurred, the device was in an unknown state.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 40 68 80 32 aa 00   at LBA = 0x00aa3280 = 11154048

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 68 80 32 aa 40 08      00:43:53.680  READ FPDMA QUEUED
  60 00 60 80 2e aa 40 08      00:43:53.680  READ FPDMA QUEUED
  60 00 58 80 2d aa 40 08      00:43:53.680  READ FPDMA QUEUED
  60 40 50 40 2d aa 40 08      00:43:53.680  READ FPDMA QUEUED
  60 20 48 f0 eb c5 40 08      00:43:53.670  READ FPDMA QUEUED

Error 1442 occurred at disk power-on lifetime: 209 hours (8 days + 17 hours)
  When the command that caused the error occurred, the device was in an unknown state.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 40 68 68 9c cf 00   at LBA = 0x00cf9c68 = 13605992

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 20 68 68 9c cf 40 08      00:43:53.030  READ FPDMA QUEUED
  60 08 60 d0 34 c2 40 08      00:43:53.030  READ FPDMA QUEUED
  60 18 58 d8 48 c7 40 08      00:43:53.030  READ FPDMA QUEUED
  60 08 50 18 27 c2 40 08      00:43:53.030  READ FPDMA QUEUED
  60 20 48 58 08 cc 40 08      00:43:53.030  READ FPDMA QUEUED

Error 1441 occurred at disk power-on lifetime: 209 hours (8 days + 17 hours)
  When the command that caused the error occurred, the device was in an unknown state.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 40 60 68 61 c8 00   at LBA = 0x00c86168 = 13132136

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 18 60 68 61 c8 40 08      00:43:52.080  READ FPDMA QUEUED
  60 20 58 00 7d 05 40 08      00:43:52.080  READ FPDMA QUEUED
  60 18 50 08 e6 c4 40 08      00:43:52.070  READ FPDMA QUEUED
  60 18 48 b0 d8 c2 40 08      00:43:52.070  READ FPDMA QUEUED
  60 18 40 90 90 cf 40 08      00:43:52.070  READ FPDMA QUEUED

SMART Self-test log structure revision number 0
Warning: ATA Specification requires self-test log structure revision number = 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]

Selective Self-tests/Logging not supported

The above only provides legacy SMART information - try 'smartctl -x' for more

cat /proc/cmdline

BOOT_IMAGE=(hd1,gpt5)/vmlinuz-6.10.3-200.fc40.x86_64 root=UUID=e76e695e-46b4-482e-a65f-85faea706c82 ro rootflags=subvol=@ rhgb quiet

cat /etc/kernel/cmdline

root=UUID=e76e695e-46b4-482e-a65f-85faea706c82 ro rootflags=subvol=@ rhgb quiet

cat /etc/default/grub

GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"
GRUB_DEFAULT=saved
GRUB_DISABLE_SUBMENU=true
GRUB_TERMINAL_OUTPUT="console"
GRUB_CMDLINE_LINUX="rhgb quiet"
GRUB_DISABLE_RECOVERY="true"
GRUB_ENABLE_BLSCFG=true
10

Don’t bother. If WIndows is happy about a misaligned partition, it will be fine. The Linux system won’t be slowed down by a partition it is never going to access.

1 Like
11

I wonder if there is a mismatch between how the various subsystems identify the disks. The GRUB error posted in the OP says that 'hd0, gpt5' (first disk), which is identified by Fedora as /dev/sdb5 (second disk). There is also a backquote-apostrophe (mis)use for hd0.

Maybe all this is normal?

12

btrfs-assistant is usually a better option for Fedora, which doesn’t require such an advanced installation setup as required by the guide you provided, nor renaming the subvolumes.

13

That’s sad to hear now, how can I revert?

14

I would focus now on solving the current issue. @computersavvy or the others might advise you to remove the rootflags=subvol=@ argument from the boot line, and some other changes, which might make timeshift useless anyhow.

Once the issue is solved, then you could discuss the possibilities of migrating to btrfs-assistant. Best if done in a different topic.

However, there is a risk that your drive is failing, so better prepare for some backup solutions.

1 Like
15

In grub you would (should) always use the “search” command to find the correct disk and partition based on the file system UUID. Sometimes the “hd0” is whichever disk unit was selected to be the disk you boot from, or maybe not. The back-quote was at some time, maybe 20 years ago, used as opening quote character and the regular quote as a closing quote. Like `abc’.

As you only have one disk with a partition 5 (do we count from 1 or from 0?), there can only be one disk unit which matches.

1 Like
16

The subvol must be set to whatever the name given to the root subvolume is. If the root subvolume is renamed to “@”, then that is what you need to specify.

17

There are moments that Fedora boots. So configuration is fine. The “@” subvolume is no problem at all as long as it is used consistently. Grub fails sometimes. Windows fails sometimes. The only conclusion I can draw is hardware. I would start with (let) checking whether the drive is seated firmly and the contacts are OK. There are two things in the disk1 smart:

191 G-Sense_Error_Rate      0x0032   001   001   000    Old_age   Always       -       24972

The “value” is driven down to 001, so either the value is invalid or the disk suffered many g-forces.
The next one, Power-off retract count raw is too high to believe but value is still 098.

From Acronis support

Description

G-sense error rate S.M.A.R.T. parameter indicates the number of errors caused by externally-induced shock or vibration.

Recommendations

This parameter is considered informational by the most hardware vendors. Although degradation of this parameter can be an indicator of drive aging and/or potential electromechanical problems, it does not directly indicate imminent drive failure. Regular backup is recommended. Pay closer attention to other parameters and overall drive health.

18

Okay but what’s the solution? Do I have to change my ssd?

19

It’s unclear for mee. The hdd is seen as sda, the sdd as sdb, but grub looks for (hd0,gpt5). Can you interrupt grub, go to the grub shell and type “ls” to see what grub’s interpretation is of drive order? The HDD is the oldest one and has many G-sense related problems, but the SDD is also not without errors logged.
I also do not understand why grub wants (hd0,gpt5) while UUID’s are used for referencing the partitions. And your /proc/cmdline refers to (hd1,gpt5).
In any case, I would check wether the HDD and SDD are thight in their connectors.

20

Within bios (which is what grub appears to use) I think the drives are counted from 0
but the partitions on the drive are counted from 1 the way every utility I use shows it.

The comment about the drive failing may be correct, or a bad cable.

The same drive is smart capable and shows numerous errors – either due to drive failure or cable/controller problems which shows with the reduced SATA connection rate. Interesting enough is that all the errors shown occurred at the same time – 209 power on hours which to me might indicate a cable/connection issue rather than drive issue.

My suggestion would be to first replace the drive data cable with a new 6 Gb/s cable then monitor to see if there is a difference. After booting you can see in dmesg the data connection speed for the drive as it is configured.
Something like this should appear.

# dmesg | grep  -E "ata1|ata2|ata3"
[    0.659234] ata1: SATA max UDMA/133 abar m131072@0xfc780000 port 0xfc780100 irq 37 lpm-pol 3
[    0.659237] ata2: SATA max UDMA/133 abar m131072@0xfc780000 port 0xfc780180 irq 37 lpm-pol 3
[    0.659239] ata3: SATA max UDMA/133 abar m131072@0xfc780000 port 0xfc780200 irq 37 lpm-pol 3
[    0.964401] ata1: SATA link down (SStatus 0 SControl 300)
[    1.430528] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[    1.433764] ata2.00: ATAPI: HL-DT-ST BD-RE  WH14NS40, 1.03, max UDMA/100
[    1.439100] ata2.00: configured for UDMA/100
[    1.974258] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[    2.069800] ata3.00: ATA-10: ST4000VN008-2DR166, SC60, max UDMA/133
[    2.070195] ata3.00: 7814037168 sectors, multi 16: LBA48 NCQ (depth 32), AA
[    2.070199] ata3.00: Features: NCQ-sndrcv
[    2.071618] ata3.00: configured for UDMA/133

To explain that
SATA port 1 is not connected
Port 2 is connected to a DVD drive which is only capable of the lower speed. (1.5 Gp/s)
Port 3 is an active drive and is connected at full speed. (6 Gp/s)

Your drive shows capable of the higher speed but only configures at the lower speed. A bad cable / connection could both force the lower speed and cause signal interference with data loss.

The fact that the SSD drive only shows 210 power on hours with the errors at 209 hours really leads me toward the cable/connection issue.

1 Like