sdauth
l33t
Joined: 19 Sep 2018
Posts: 638
Location: Ásgarðr
|
 Posted: Thu Oct 17, 2024 3:19 am Post subject: kernel 6.11.3 device-mapper alignment inconsistency |
 |
|
Hello,
I upgraded my kernel from 6.6.52 to 6.11.3, all good but this shows up in dmesg :
| Code: | [ 71.761899] device-mapper: table: 253:1: adding target device sde1 caused an alignment inconsistency: physical_block_size=4096, logical_block_size=512, alignment_offset=0, start=16777216
[ 71.761914] device-mapper: table: 253:1: adding target device sde1 caused an alignment inconsistency: physical_block_size=4096, logical_block_size=512, alignment_offset=0, start=16777216
[ 71.762139] device-mapper: table: 253:1: adding target device sde1 caused an alignment inconsistency: physical_block_size=4096, logical_block_size=512, alignment_offset=0, start=16777216
[ 71.762145] device-mapper: table: 253:1: adding target device sde1 caused an alignment inconsistency: physical_block_size=4096, logical_block_size=512, alignment_offset=0, start=16777216
[ 106.904936] device-mapper: table: 253:2: adding target device sdb1 caused an alignment inconsistency: physical_block_size=4096, logical_block_size=512, alignment_offset=0, start=16777216
[ 106.904951] device-mapper: table: 253:2: adding target device sdb1 caused an alignment inconsistency: physical_block_size=4096, logical_block_size=512, alignment_offset=0, start=16777216
[ 106.905203] device-mapper: table: 253:2: adding target device sdb1 caused an alignment inconsistency: physical_block_size=4096, logical_block_size=512, alignment_offset=0, start=16777216
[ 106.905208] device-mapper: table: 253:2: adding target device sdb1 caused an alignment inconsistency: physical_block_size=4096, logical_block_size=512, alignment_offset=0, start=16777216
[ 131.785762] device-mapper: table: 253:3: adding target device sdc1 caused an alignment inconsistency: physical_block_size=4096, logical_block_size=512, alignment_offset=0, start=16777216
[ 131.785777] device-mapper: table: 253:3: adding target device sdc1 caused an alignment inconsistency: physical_block_size=4096, logical_block_size=512, alignment_offset=0, start=16777216
[ 131.786028] device-mapper: table: 253:3: adding target device sdc1 caused an alignment inconsistency: physical_block_size=4096, logical_block_size=512, alignment_offset=0, start=16777216
[ 131.786034] device-mapper: table: 253:3: adding target device sdc1 caused an alignment inconsistency: physical_block_size=4096, logical_block_size=512, alignment_offset=0, start=16777216
[ 165.961267] device-mapper: table: 253:4: adding target device sdd1 caused an alignment inconsistency: physical_block_size=4096, logical_block_size=512, alignment_offset=0, start=16777216
[ 165.961281] device-mapper: table: 253:4: adding target device sdd1 caused an alignment inconsistency: physical_block_size=4096, logical_block_size=512, alignment_offset=0, start=16777216
[ 165.961549] device-mapper: table: 253:4: adding target device sdd1 caused an alignment inconsistency: physical_block_size=4096, logical_block_size=512, alignment_offset=0, start=16777216
[ 165.961555] device-mapper: table: 253:4: adding target device sdd1 caused an alignment inconsistency: physical_block_size=4096, logical_block_size=512, alignment_offset=0, start=16777216 |
disks are mounted correctly (btrfs on all disks) but there was no such warning with kernel 6.6.
| Code: | NAME ALIGNMENT MIN-IO OPT-IO PHY-SEC LOG-SEC ROTA SCHED RQ-SIZE RA WSAME
sdb 0 4096 16776704 4096 512 1 bfq 256 32764 0B
└─sdb1 0 4096 16776704 4096 512 1 bfq 256 32764 0B
└─hdd2 -1 4096 0 4096 512 1 32764 0B
sdc 0 4096 16776704 4096 512 1 bfq 256 32764 0B
└─sdc1 0 4096 16776704 4096 512 1 bfq 256 32764 0B
└─hdd3 -1 4096 0 4096 512 1 32764 0B
sdd 0 4096 16776704 4096 512 1 bfq 256 32764 0B
└─sdd1 0 4096 16776704 4096 512 1 bfq 256 32764 0B
└─hdd4 -1 4096 0 4096 512 1 32764 0B
sde 0 4096 16776704 4096 512 1 bfq 256 32764 0B
└─sde1 0 4096 16776704 4096 512 1 bfq 256 32764 0B
└─hdd -1 4096 0 4096 512 1 32764 0B |
The verify option of gdisk says :
| Code: | Warning: There is a gap between the main partition table (ending sector 33)
and the first usable sector (2048). This is helpful in some exotic configurations,
but is unusual. The util-linux fdisk program often creates disks like this.
Using 'j' on the experts' menu can adjust this gap.
Caution: Partition 1 doesn't end on a 2048-sector boundary. This may
result in problems with some disk encryption tools. |
In order to fix that, I would have to format them... isn't ?
Or maybe I can just ignore it ?
Thanks |
|
Kernel & Hardware
