Thank you for taking the time to report this issue and helping to make
Ubuntu better.
This failure looks like it was caused by a hardware failure, eg. look in
the logs and you'll see messages like these :-
Jul 9 11:55:24 ubuntu kernel: [ 2886.362427] EXT4-fs (dm-1): Remounting
filesystem read-only
Jul 9 11:55:24 ubuntu kernel: [ 2886.362436] EXT4-fs error (device dm-1) in
ext4_free_blocks:4943: IO failure
Jul 9 11:55:24 ubuntu kernel: [ 2886.425259] EXT4-fs error (device dm-1) in
ext4_do_update_inode:5317: Journal has aborted
Jul 9 11:55:24 ubuntu kernel: [ 2886.467449] EXT4-fs error (device dm-1) in
ext4_ext_remove_space:3061: IO failure
Jul 9 11:55:24 ubuntu kernel: [ 2886.511863] EXT4-fs error (device dm-1) in
ext4_do_update_inode:5317: Journal has aborted
Jul 9 11:55:24 ubuntu kernel: [ 2886.556344] EXT4-fs error (device dm-1) in
ext4_truncate:4528: IO failure
Jul 9 11:55:24 ubuntu kernel: [ 2886.611874] EXT4-fs error (device dm-1):
ext4_evict_inode:293: comm dpkg: couldn't truncate inode 11800738 (err -30)
Examining the information you have given us, this does not appear to be
a useful bug report so I am closing it, as it appears to be a faulty
device (or bad write-to-device). If you believe I'm in error, please
leave a comment explaining why and change the status back to 'new'. I
suggest you check your hardware (using `smartctl` etc), and use the
'check disc for defects' option to validate your media before install to
ensure a good download & write.
** Changed in: ubiquity (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835903
Title:
fsck problem occurs again and again
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1835903/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
