LVM disk appears to have grown since partition table was written?

[gr8_lkr]

Hello experts,

cu had a system board replaced recently,  needed EFI to boot up system and now concerned of these messages in syslog.

x: iexgbe0: INITIALIZING HP  PCIe 2-p 10GbE Built-in at hardware path 0/0/0/3/0/0/0
Oct 27 09:06:41 bspbldb1 vmunix: iexgbe1: INITIALIZING HP  PCIe 2-p 10GbE Built-in at hardware path 0/0/0/3/0/0/1
Oct 27 09:06:41 bspbldb1 vmunix: iexgbe2: INITIALIZING HP  PCIe 2-p 10GbE Built-in at hardware path 0/0/0/4/0/0/0
Oct 27 09:06:41 bspbldb1 vmunix: iexgbe3: INITIALIZING HP  PCIe 2-p 10GbE Built-in at hardware path 0/0/0/4/0/0/1
Oct 27 09:06:41 bspbldb1 vmunix: AF_INET socket/streams output daemon running, pid 53
Oct 27 09:06:41 bspbldb1 vmunix: afinet_prelink: module installed
Oct 27 09:06:41 bspbldb1 vmunix: Starting the STREAMS daemons-phase 1
Oct 27 09:06:41 bspbldb1 vmunix: ia64dsk: The disk for dev_t 1000003 appears to have grown since the partition table was written.
Oct 27 09:06:41 bspbldb1 vmunix: LVM : Failure in attaching PV (dev=0x1000005) to the root volume group.
Oct 27 09:06:41 bspbldb1 vmunix: The physical volume does not exist, or is not configured in the kernel
Oct 27 09:06:41 bspbldb1 vmunix: LVM : Activation of root volume group failed
Oct 27 09:06:41 bspbldb1 vmunix: ia64dsk: The disk for dev_t 1000003 appears to have grown since the partition table was written.
Oct 27 09:06:43 bspbldb1  above message repeats 2 times
Oct 27 09:06:41 bspbldb1 vmunix: Quorum not present, or some physical volume(s) are missing
Oct 27 09:06:41 bspbldb1 vmunix: LVM: Scanning for Root VG PVs (VGID 0x29326b7f 0x4dca4fcd)
Oct 27 09:06:41 bspbldb1 vmunix: ia64dsk: The disk for dev_t 1000003 appears to have grown since the partition table was written.
There appears to be several issues here but they are only concerned about the "disk grown" at this time

Any assistance much appreciated !

G

[Matti_Kurkela]

Perhaps the system disk has been cloned using dd or a similar tool, and the duplicate disk was not exactly the same size as the original, but slightly bigger?

Anyway, the "disk grown" message seems to be the least of the problems: it might just be an informative message.

A bigger problem is that one of the PVs of the root volume group seems to be completely missing. If the missing PV was a mirror of the existing one, booting the system with the -lq boot option might allow the system to start up normally. Then the missing mirror should be fixed.

You might want to use the idisk command to view the EFI partition table information, and diskinfo -v to see the actual size of the disk.