*** This bug is a duplicate of bug 1573095 ***
https://bugs.launchpad.net/bugs/1573095
Although this is closed as dup, I thought would be good to clarify why
Debian Buster doesn't reproduce (at first). What happens is that Debian
includes the fsck on initrd by default, and in Ubuntu that doesn't
happen - the reason behind it is that rootfs is marked as always-verify
in the 6th field of fstab (fs_passno) in the Debian cloud image I got,
whereas Ubuntu cloud image use the default value, 0.
Once I changed Debian to not include fsck on initrd, it reproduced the
issue. And once I set Ubuntu rootfs to have value 1 on fstab's 6th
field, it stopped to reproduce. When fsck is on initrd, we don't
log_warn "fsck not present, so skipping $NAME file system", so we don't
fail in _checkfs_once(), hence there's no infinite loop on checkfs().
Cheers,
Guilherme
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879987
Title:
machine get stuck at boot if specified 'console=ttyS* ' doesn't exist.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1879987/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
