[Touch-packages] [Bug 1843623] Re: LVM volumes not activated during boot after upgrade to 18.04 LTS

2019-09-12 Thread Marius Gedminas
So, uh, I tried another reboot so I could debug the problem some more, and ... well ... the machine booted. No problems. I've no idea what's going on, feel free to close this bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is

[Touch-packages] [Bug 1843623] Re: LVM volumes not activated during boot after upgrade to 18.04 LTS

2019-09-11 Thread Marius Gedminas
In case this might be relevant: - /var is a separate partition (/dev/md1) - /var/cache is a separate partition (an LVM volume) - /tmp is a separate partition (an LVM volume) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to

[Touch-packages] [Bug 1843623] Re: LVM volumes not activated during boot after upgrade to 18.04 LTS

2019-09-11 Thread Marius Gedminas
FWIW journalctl -b is showing a bunch of Sep 11 19:16:30 fridge lvmetad[457]: WARNING: Ignoring unsupported value for cmd. Sep 11 19:16:30 fridge lvmetad[457]: WARNING: Ignoring unsupported value for cmd. before systemd unit timeouts that are about those missing partitions failing to mount.

[Touch-packages] [Bug 1843623] Re: LVM volumes not activated during boot after upgrade to 18.04 LTS

2019-09-11 Thread Marius Gedminas
If I run pvscan --cache -aay in the systemd emergency console, all logical volumes get activated and the system then proceeds to boot normally. It seems like for some reason udev is not running pvscan for me? -- You received this bug notification because you are a member of Ubuntu Touch seeded