kernel: device-mapper: table: 254:1: adding target device sda1 caused an alignment inconsistency
When booting, I get 12 error messages similar to the following (three groups of four, each group with a different “start” value and corresponding minor device)
> Jul 24 03:40:08 small kernel: device-mapper: table: 254:1: adding target device sda1 caused an alignment inconsistency: physical_block_size=4096, logical_block_size=512, alignment_offset=0, start=33553920
Can anyone tell me what it means and what I should do about it?
Thanks!
Rick
============================
Information that might be useful:
> rbthomas@small:~$ lsblk
> NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
> sda 8:0 0 931.5G 0 disk
> `-sda1 8:1 0 931.5G 0 part
> |-small-swap 254:0 0 10G 0 lvm [SWAP]
> |-small-root 254:1 0 30G 0 lvm /
> `-small-home 254:2 0 100G 0 lvm /home
> mmcblk2 179:0 0 3.7G 0 disk
> |-mmcblk2p1 179:1 0 512M 0 part /boot/efi
> `-mmcblk2p2 179:2 0 2G 0 part /boot
> rbthomas@small:~$ sudo gdisk -l /dev/sda
> GPT fdisk (gdisk) version 1.0.3
>
> Partition table scan:
> MBR: protective
> BSD: not present
> APM: not present
> GPT: present
>
> Found valid GPT with protective MBR; using GPT.
> Disk /dev/sda: 1953525168 sectors, 931.5 GiB
> Model: nal USB 3.0
> Sector size (logical/physical): 512/4096 bytes
> Disk identifier (GUID): F040A793-41E6-46E6-9147-FED15A526294
> Partition table holds up to 128 entries
> Main partition table begins at sector 2 and ends at sector 33
> First usable sector is 34, last usable sector is 1953525134
> Partitions will be aligned on 2048-sector boundaries
> Total free space is 2014 sectors (1007.0 KiB)
>
> Number Start (sector) End (sector) Size Code Name
> 1 2048 1953525134 931.5 GiB 8E00 Linux LVM
> rbthomas@small:~$
> rbthomas@small:~$ sudo lvdisplay
> --- Logical volume ---
> LV Path /dev/small/root
> LV Name root
> VG Name small
> LV UUID brZiAH-bjpQ-ThUf-cx20-qTNc-uHuL-dcNrA6
> LV Write Access read/write
> LV Creation host, time grml, 2018-07-23 02:10:20 -0700
> LV Status available
> # open 1
> LV Size 30.00 GiB
> Current LE 7680
> Segments 1
> Allocation inherit
> Read ahead sectors auto
> - currently set to 256
> Block device 254:1
>
> --- Logical volume ---
> LV Path /dev/small/swap
> LV Name swap
> VG Name small
> LV UUID UyLz6P-ooDS-hixd-D40U-EHEn-j2ss-xSEHay
> LV Write Access read/write
> LV Creation host, time grml, 2018-07-23 02:10:52 -0700
> LV Status available
> # open 2
> LV Size 10.00 GiB
> Current LE 2560
> Segments 1
> Allocation inherit
> Read ahead sectors auto
> - currently set to 256
> Block device 254:0
>
> --- Logical volume ---
> LV Path /dev/small/home
> LV Name home
> VG Name small
> LV UUID qMdtCI-DOBG-G1tK-ur04-mLHX-nccd-vPWPEH
> LV Write Access read/write
> LV Creation host, time grml, 2018-07-23 02:11:12 -0700
> LV Status available
> # open 1
> LV Size 100.00 GiB
> Current LE 25600
> Segments 1
> Allocation inherit
> Read ahead sectors auto
> - currently set to 256
> Block device 254:2
>
> rbthomas@small:~$
> rbthomas@small:~$ sudo pvdisplay -v
> Wiping internal VG cache
> Wiping cache of LVM-capable devices
> --- Physical volume ---
> PV Name /dev/sda1
> VG Name small
> PV Size 931.51 GiB / not usable 32.69 MiB
> Allocatable yes
> PE Size 4.00 MiB
> Total PE 238459
> Free PE 202619
> Allocated PE 35840
> PV UUID 4PuUWe-01xm-mtQE-nEtt-HSXZ-ZRyd-uZypdH
> rbthomas@small:~$ sudo vgdisplay
> --- Volume group ---
> VG Name small
> System ID
> Format lvm2
> Metadata Areas 1
> Metadata Sequence No 5
> VG Access read/write
> VG Status resizable
> MAX LV 0
> Cur LV 3
> Open LV 3
> Max PV 0
> Cur PV 1
> Act PV 1
> VG Size 931.48 GiB
> PE Size 4.00 MiB
> Total PE 238459
> Alloc PE / Size 35840 / 140.00 GiB
> Free PE / Size 202619 / 791.48 GiB
> VG UUID SFb0ZB-EeSj-jYmd-F6FJ-7Jdh-imsH-v688ZZ
>
>
Reply to: