Code: Select all

lvmetad is not active yet; using direct activation during sysinit...

neon-devedition-gitunstable-current.iso 08-02-17

On my desktop pc install this message causes a delay of +/-2 seconds on the boot time.

On my Sony Vaio laptop install this message causes a delay of +/-15 seconds on the boot time.

I read this is something to do with LVM??

Any advice on this would be welcome.
Can I eliminate this from the boot?

Loving KDE Neon

Any ideas at all community?

neilhoughton wrote:Any ideas at all community?

You ask as if you're not running LVM, but I'm guessing you are? Without LVM you shouldn't have this message. With LVM a couple seconds is not usual.

Not sure why your Lenovo is taking 13 seconds longer to initialize LVM...but I'm not that well versed in LVM issues. I'm sure someone else will chime in...

I did not select lvm on either install.
I don't remember an option for lvm at install.
I simply chose 'erase disk and install...'

Code: Select all

mrneilypops@neon:~$ sudo fdisk /dev/sdb -l
Disk /dev/sdb: 223.6 GiB, 240057409536 bytes, 468862128 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x2bd269a5

Device     Boot     Start       End   Sectors   Size Id Type
/dev/sdb1            2049 450402086 450400038 214.8G 83 Linux
/dev/sdb2       450402087 468857024  18454938   8.8G 82 Linux swap / Solaris


https://scrotlabs.org/images/2017/02/22 ... 124117.png

neilhoughton wrote:[code]mrneilypops@neon:~$ sudo fdisk /dev/sdb -l
Device Boot Start End Sectors Size Id Type
/dev/sdb1 2049 450402086 450400038 214.8G 83 Linux

That might be the problem with the delay...your sector start is 2049 which should be 2048. Funny that the partition starts at 2049. Did you delete the partition or just format the old partition?

Perhaps wipe the partitions and recreate them letting the partition editor in the installation do it automatically. It will align the partition properly at 2048 for the start and may speed things up.

@compatico
Thanks for the feedback.
On both installs I just formatted the old partition with the installer.
Perhaps I should have wiped the drive first??

I will maybe do a reinstall soon on a totally wiped drive and update the thread...

Update:

Sony Vaio laptop
Reformat drive to FAT32 using gparted live
Reinstall KDE Neon [neon-devedition-gitunstable-current.iso 23-02-17] - same issue
Reformat drive to ext4 using gparted live
Reinstall KDE Neon [neon-devedition-gitunstable-current.iso 23-02-17] - same issue
Manjaro KDE test install [Manjaro KDE Edition (16.10.3)] - standard partitioning.
No errors on boot regarding lvmetad...

T.B.C...

neilhoughton wrote:Update:

Sony Vaio laptop
Reformat drive to FAT32 using gparted live
Reinstall KDE Neon [neon-devedition-gitunstable-current.iso 23-02-17] - same issue
Reformat drive to ext4 using gparted live
Reinstall KDE Neon [neon-devedition-gitunstable-current.iso 23-02-17] - same issue
Manjaro KDE test install [Manjaro KDE Edition (16.10.3)] - standard partitioning.
No errors on boot regarding lvmetad...

T.B.C...

You said you formatted the drive for Neon reinstall, but you didn't delete the partitions?
That might be the reason Neon issues an error, since you partitioned with Manjaro and no issues.

What does Fdisk show now for partition byte start sector?

Manjaro KDE partition byte sector start = 2049 but no lvmetad messages...?

Progress!

Sony Vaio install
neon-useredition-current.iso 23/02/17
partition byte sector start = 2048
no lvmetad boot message or boot delay!

I might install the Neon user edition on my desktop PC and update the thread...

So, it would appear that this is an issue with the developer edition installs...

I'm going to mark this post solved in so much as a return to KDE Neon user edition on my laptop.
I will keep the unstable version on my desktop pc for the moment as the lvmetad issue only adds a 2 second delay to the boot process...
I will stay tuned....