** Attachment removed: CurrentDmesg.txt
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1439445/+attachment/4363682/+files/CurrentDmesg.txt
** Attachment added: CurrentDmesg.txt
the RTC clock was kept in UTC. This gave a wrong time at boot, and
possibly shoke fsck about a superblock in the future.
Once I changed UTC to yes in /etc/default/rcS, I was able to remove the
fsck.mode=skip as they were no more 30s delay during boot.
FIXED !
** Changed in: systemd (Ubuntu)
Obviously, using fsck.mode=skip kernel parameter does not show the 30s
wait.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1439445
Title:
systemd-fsck laps 30s on boot
so I removed the bcache LUKS device thing from the equation:
I commented it out the relevant line for home in /etc/crypttab and /etc/fstab
to use a dummy empty folder for /home on the main root SSD partition
and rebooted
and this still happens, this time it is
$ systemd-analyze blame|head -5
** Attachment removed: CurrentDmesg.txt
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1439445/+attachment/4363619/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1439445/+attachment/4363682/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1439445/+attachment/4363655/+files/UdevDb.txt
** Description changed:
Using 15.04 beta 2 witht the following setup:
/dev/sda is a SSD (crucial mx100) in main SATA port of Inspiron 15 3521
/dev/sdb is
7 matches
Mail list logo