[Expired for e2fsprogs (Ubuntu) because there has been no activity for
60 days.]
** Changed in: e2fsprogs (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
http
is that issue still seen ?
** Changed in: e2fsprogs (Ubuntu)
Status: New => Incomplete
--
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/1438824
Title:
ALL FSCKs tr
** Attachment added: "grip contigu"|ux.ver" syslog>/tmp/bootups.txt"
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1438824/+attachment/4406821/+files/bootups.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e
perhaps the trigger is when the system boots up with a system time which
preceeds the prior bootup. this sort of thing happens because of
bug#1335522. and that would explain why it happened this time.
imho such time discrepancy should not trigger full lengthy filesystem
checks.
i think this sho
** Package changed: systemd (Ubuntu) => e2fsprogs (Ubuntu)
** Changed in: e2fsprogs (Ubuntu)
Status: Incomplete => New
--
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/bug
ok, waiting for it to happen again. when i was ready to shutdown both
my vivid boxes last night i just flipped off their powerstrip switches
without logout nor shutdown. this morning, no FSCKs. whatever triggers
them, that's not it.
maybe time discrepancy, if the last OS running had the wrong t
After a boot which does the fsck, can you please do "sudo journalctl -b
> /tmp/journal.txt" and attach /tmp/journal.txt here? Perhaps that says
why it got started. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to system
"several times in a row" is ambiguous, sorry, to be more clear, all
filesystems are checked once through per bootup. Or, sometimes, the
bootup is normal (ie does not check all filesystems). whatever triggers
it, checking all filesystems seems to happen several bootups in a row,
then i'll enjoy se
all spindles here are MBR. before systemd this was handled by mountall.
if not systemd, what package handles this now? you've labeled this
incomplete, what is needed?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd i
https://help.ubuntu.com/community/UEFI
--
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/1438824
Title:
ALL FSCKs triggered for no apparent reason
Status in systemd package
your issue seems related to gpt:
systemd-gpt-auto-generator[176]: Failed to determine partition table type of
/dev/sde: Input/output error
[ 21.72] systemd[174]:
/lib/systemd/system-generators/systemd-gpt-auto-generator failed with error
code 1.
so the non stop fsck.
Pay attention the b
Probably not a systemd bug
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
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/1438824
Title:
ALL FSCKs trigge
12 matches
Mail list logo
