search

neilbrown / gnubee-tools

Tools for building gnubee firmware - and maybe more.
Other
31 stars 14 forks source link

LVM issues on kernel 5.10.1 #30

Closed leocrawford closed 3 years ago

leocrawford commented 3 years ago

Hi,

I upgraded to your most recent kernel (gnubee-5.10.1-gbpc1.bin) and on subsequent boots my LVM partitions didn't come up. 

sda                          8:0    0  1.8T  0 disk  
└─sda1                       8:1    0  1.8T  0 part  
  └─md127                    9:127  0  1.8T  0 raid1 
    └─NasLVMGroup1-storage 252:0    0  1.8T  0 lvm   /tmp/c
sdb                          8:16   0  1.8T  0 disk  
└─sdb1                       8:17   0  1.8T  0 part  
  └─md127                    9:127  0  1.8T  0 raid1 
    └─NasLVMGroup1-storage 252:0    0  1.8T  0 lvm   /tmp/c
sdc                          8:32   0 59.6G  0 disk  
├─sdc1                       8:33   0   10G  0 part  /

These were set to come up using systemd, and I found that mounting them manually (e.g. mount /dev/mapper/NasLVMGroup1-storage /tmp/c as shown) worked, whereas a corresponding systemd-mount didn't.

Further blikd lists the LVM partition but it doesn't appear on ls /dev/disk/by-uuid and parted -l shows

Model: Linux device-mapper (linear) (dm)
Disk /dev/mapper/NasLVMGroup1-storage: 1979GB
Sector size (logical/physical): 512B/4096B
Partition Table: loop
Disk Flags: 

Number  Start  End     Size    File system  Flags
 1      0.00B  1979GB  1979GB  ext4

As the only change I made was a kernel upgrade, and I see some LVM modifications last June (I'm not sure what kernel I was running previously) I wondered if it was possibly the kernel? Most online docs suggest rebuilding initramfs, but I'm not sure if that is possible/needed when upgrading kernel versions on this?

leocrawford commented 3 years ago

OK, I don't understand the cause and why an upgrade to a new kernel triggered it, but the problem seems to match (and is resolved by):

https://github.com/systemd/systemd/issues/11255