[Touch-packages] [Bug 1797282] Re: fsck not running at all on reboot

2019-07-09 Thread Ewan Mellor
In my case, Ubuntu 18.04 running on AWS, the problem was as follows: 1. /etc/fstab had 0 in the 6th (passno) field. I presume this is the default that AWS places there, or maybe this is determined by the Ubuntu template on AWS. 2. According to a comment that I found on Stack Overflow, this is

[Touch-packages] [Bug 1797282] Re: fsck not running at all on reboot

2019-07-09 Thread Ewan Mellor
** Changed in: systemd (Ubuntu) Status: Expired => Confirmed -- 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/1797282 Title: fsck not running at all on reboot

[Touch-packages] [Bug 1797282] Re: fsck not running at all on reboot

2019-02-12 Thread Launchpad Bug Tracker
[Expired for systemd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: systemd (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu.

[Touch-packages] [Bug 1797282] Re: fsck not running at all on reboot

2018-12-14 Thread Phil Pemberton
I'm seeing this on an Ubuntu 16.04.5 LTS system running on top of LVM. In my case, I get: *** /dev/mapper/wolf-root will be checked for errors at next reboot *** Having to dig out a 16.04 LTS Server USB stick every time I need to run FSCK is extremely inconvenient. It turns an unattended

[Touch-packages] [Bug 1797282] Re: fsck not running at all on reboot

2018-10-17 Thread Brian Murray
I've been unable to recreate this on an Ubuntu installation of Ubuntu 16.04.5 which I then upgraded to Ubuntu 18.04. If I set 'tune2fs -c1' for my root partition it is checked for errors on every boot. I'll have someone test with an AWS EC2 instance. @dman777 while you say you set -c1 the output

[Touch-packages] [Bug 1797282] Re: fsck not running at all on reboot

2018-10-16 Thread tomtom
Changed package based on comment made by Theodore Ts'o ** Package changed: e2fsprogs (Ubuntu) => systemd (Ubuntu) -- 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/1797282

[Touch-packages] [Bug 1797282] Re: fsck not running at all on reboot

2018-10-15 Thread Theodore Ts'o
This is probably not assigned to the right package. It's not an issue with e2fsprogs, but whatever component is running fsck. This might be systemd, or upstart, or whatever the heck Ubuntu is using these days. I lost track a while ago. :-) I can tell, you as the Debian maintainer of

[Touch-packages] [Bug 1797282] Re: fsck not running at all on reboot

2018-10-15 Thread dman777
Can this be bumped up to a high importance? This is a major issue as not checking the file system leads to a broken system. ** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.

[Touch-packages] [Bug 1797282] Re: fsck not running at all on reboot

2018-10-11 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: e2fsprogs (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.

[Touch-packages] [Bug 1797282] Re: fsck not running at all on reboot

2018-10-11 Thread Paul White
** Package changed: ubuntu => e2fsprogs (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1797282 Title: fsck not running at all on reboot Status in e2fsprogs