After having "fixed" the grub/EFI/UUID problems, my boot times have slowed down.
Mind you, I can boot from the SSD, the "old" neon partition can be mounted separately, and everything works.
But, grub-install still gives warning on six partition table entries.
Like: GUID Partition Table Header signature is wrong: b14185eed2da66d8 != 5452415020494645
repeated six times with different text for the first entry but with the same for the second (5452415020494645).
It then says, Installation finished. No error reported.
Ok, everything works. But the boot is slow.
It goes reasonably fast, then hangs on "searching for Btrfs filesystems". 30 seconds, look:
Dmesg does not report the "searching for Btrfs filesystems" but it's what it says when it hangs there.
I really don't think I have any btrfs filesystems, BTW.
Then it goes fast again and:
One minute, 27 seconds! It used to boot the lot in less than that.
Here again, dmesg does not mention it, but it hangs on a long message, of the sort:
Start job is running for dev-disk-by\longhexstring.
Then after a minute and a half (!), it says, Timed out waiting for device dev-disk-by\longhexstring.
Now, they really look like disk-related problems.
Maybe like, six GUID partition table header signatures being wrong?
I've looked far and wide on how to "correct" that problem. All I could find looks like taking a flamethower to a bowl of petunias and hoping they will revive.
Any suggestions?
[BTW] none of the hex strings reported in the partition warnings seem to have any relation to the ones reported by blkid.
Mind you, I can boot from the SSD, the "old" neon partition can be mounted separately, and everything works.
But, grub-install still gives warning on six partition table entries.
Like: GUID Partition Table Header signature is wrong: b14185eed2da66d8 != 5452415020494645
repeated six times with different text for the first entry but with the same for the second (5452415020494645).
It then says, Installation finished. No error reported.
Ok, everything works. But the boot is slow.
It goes reasonably fast, then hangs on "searching for Btrfs filesystems". 30 seconds, look:
Code:
[Thu Jun 20 15:09:50 2019] Btrfs loaded, crc32c=crc32c-intel [Thu Jun 20 15:10:21 2019] random: crng init done
I really don't think I have any btrfs filesystems, BTW.
Then it goes fast again and:
Code:
[Thu Jun 20 15:10:27 2019] audit: type=1400 audit(1561036228.196:11): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libreoffice-xpdfimport" pid=947 comm="apparmor_parser" [Thu Jun 20 15:11:54 2019] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
Here again, dmesg does not mention it, but it hangs on a long message, of the sort:
Start job is running for dev-disk-by\longhexstring.
Then after a minute and a half (!), it says, Timed out waiting for device dev-disk-by\longhexstring.
Now, they really look like disk-related problems.
Maybe like, six GUID partition table header signatures being wrong?
I've looked far and wide on how to "correct" that problem. All I could find looks like taking a flamethower to a bowl of petunias and hoping they will revive.
Any suggestions?
[BTW] none of the hex strings reported in the partition warnings seem to have any relation to the ones reported by blkid.
Comment