I see "dm_parse_tocblock(): Cannot find TOCBLOCK, database may be corrupt" at boot. Why?

Ask Fedora
1

Context

At boot, with Plymouth configured to render dmesg output (once booted, acquired with | grep tocblock), I see the undermentioned appear upon resolution change:

dm_parse_tocblock(): Cannot find TOCBLOCK, database may be corrupt.

This always occurs twice: [1]

[    4.002547] ldm_parse_tocblock(): Cannot find TOCBLOCK, database may be corrupt.
[    4.002556] ldm_parse_tocblock(): Cannot find TOCBLOCK, database may be corrupt.

Diagnosis

From online research, I’ve ascertained that: [2]

  1. dm_parse_tocblock() refers to the Logical Disk Manager, which is utilised by “Windows Dynamic Disks” (panned, striped, mirrored, or RAID volumes) being unable to parse the “Table of Contents block” in the LDM database, which stores metadata about dynamic volumes. [3]

  2. “Cannot find TOCBLOCK, database may be corrupt” refers to the LDM being unable to locate a valid TOC.

However, I have not manually configured panned, stripped or mirrored storage, and I do not utilise RAID. [4] That means that I have no reason to believe that I utilise Windows Dynamic Disks. Consequently, why does this appear?

Of note is that kde-partitionmanager-25.04.1 returns the undermentioned in its log:

2025-06-03 22:08:42: Using backend plugin: pmsfdiskbackendplugin (1)
2025-06-03 22:09:20: Device found: ST1000LM014-1EJ164
2025-06-03 22:09:21: Partition ‘/dev/sdb1’ is not properly aligned (first sector: 63, modulo: 63).
2025-06-03 22:09:21: Partition ‘/dev/sdb1’ is not properly aligned (last sector: 976,768,064, modulo: 1,089).
2025-06-03 22:09:21: Partition ‘/dev/sdb2’ is not properly aligned (first sector: 976,768,065, modulo: 1,089).
2025-06-03 22:09:21: Partition ‘/dev/sdb2’ is not properly aligned (last sector: 1,465,144,064, modulo: 769).
2025-06-03 22:09:21: Partition ‘/dev/sdb3’ is not properly aligned (first sector: 1,465,144,065, modulo: 769).
2025-06-03 22:09:21: Partition ‘/dev/sdb3’ is not properly aligned (last sector: 1,953,523,119, modulo: 1,456).

Configuration

lsblk -o NAME,FSTYPE,FSVER,FSAVAIL,FSUSE%,MOUNTPOINTS returns:

NAME        FSTYPE FSVER FSAVAIL FSUSE% MOUNTPOINTS
sda                                     
└─sda1      exfat  1.0                  
sdb                                     
├─sdb1      ntfs                        
├─sdb2      ntfs                        
└─sdb3                                  
sdc                                     
zram0       swap   1                    [SWAP]
nvme1n1                                 
├─nvme1n1p1 vfat   FAT32  579.5M     3% /boot/efi
├─nvme1n1p2 ext4   1.0    480.9M    44% /boot
├─nvme1n1p3 ext4   1.0                  
└─nvme1n1p4 btrfs           1.2T    31% /home
                                        /
nvme2n1                                 
└─nvme2n1p1 btrfs                       
nvme0n1                                 
└─nvme0n1p1 ntfs                        
nvme3n1                                 
├─nvme3n1p1 btrfs                       
├─nvme3n1p2 ntfs                        
└─nvme3n1p3 ntfs

  1. linuxquestions.org/questions/linux-software-2/ldm-problem-cannot-find-tocblock-599472/#post2958365 ↩︎

  2. chatgpt.com/share/683f6582-5878-8006-bd68-1f4d927d1c2c ↩︎

  3. forum.proxmox.com/threads/ldm_parse_tocblock-cannot-find-tocblock-database-may-be-corrupt.35366/#post-173379 ↩︎

  4. unix.stackexchange.com/revisions/718886/1 ↩︎