Hi,
As the title says, I can’t boot using the latest update, I can do it using the March 8th deployment. The journalctl command doesn’t show any alert or error.
During the boot process there are 4 timed out jobs:
(1 of 4) Job dev-diskby\x2duuid-51…5.device/start running (45s / 45s)
(2 of 4) Job dev-zram0.device/start running (45s / 45s)
(3 of 4) Job dev-diskby\x2duuid-64…0.device/start running (45s / 45s)
(4 of 4) Job dev-diskby\x2duuid-a5…1.device/start running (45s / 45s)
These devices exist and don’t generate alerts while booting from the previous deployments. The fstab file is exactly the same on both deployments.
Do you have any idea about what could be the cause? Is there something I could do for fixing it?
Thank you very much in advance.