Hey all, so I was making some new bootanimations and was about to try them out when I noticed that even after remounting /system rw and performing an operation, I was getting filesystem errors which caused it to remount ro (standard linux procedure to avoid data corruption.)
Here's the output while using adb shell while TWRP is running:
So I rebooted back in to TWRP (it was semi-hung after the fs error) and ran `e2fsck /dev/block/sde13` and it found and fixed a few errors. My question is, has anyone else experienced this ? Is it fairly common or should I be considering a warranty return ?
I know with traditional HDDs and even SDDs, this can be an indication of a failing drive, or also from a power failure during a write operation on /system (I'm sure I've had a few.)
After my e2fsck, I was able to copy the bootanimation.zip in to place and it works fine (I'll post after I polish a bit). Hopefully I won't see it again, but I did want to reach out in case others were seeing this or had more experience about it's implications with this storage medium. Thanks!
Here's the output while using adb shell while TWRP is running:
Code:
<2>[01-05 19:55:34.389] [0][51: bdi_writeback_w]EXT4-fs error (device sde13): ext4_mb_generate_buddy:757: group 27, block bitmap and bg descriptor inconsistent: 1 vs 65364 free clusters
<3>[01-05 19:55:34.389] [0][51: bdi_writeback_w]Aborting journal on device sde13-8.
<2>[01-05 19:55:34.389] [0][51: bdi_writeback_w]EXT4-fs (sde13): Remounting filesystem read-only
<2>[01-05 19:55:34.389] [0][51: bdi_writeback_w]EXT4-fs error (device sde13): ext4_mb_generate_buddy:757: group 28, block bitmap and bg descriptor inconsistent: 1 vs 43594 free clusters
<2>[01-05 19:55:34.389] [0][51: bdi_writeback_w]EXT4-fs error (device sde13): ext4_mb_generate_buddy:757: group 29, block bitmap and bg descriptor inconsistent: 16190 vs 49475 free clusters
<2>[01-05 19:55:34.389] [0][51: bdi_writeback_w]EXT4-fs error (device sde13): ext4_mb_generate_buddy:757: group 30, block bitmap and bg descriptor inconsistent: 32258 vs 20790 free clusters I know with traditional HDDs and even SDDs, this can be an indication of a failing drive, or also from a power failure during a write operation on /system (I'm sure I've had a few.)
After my e2fsck, I was able to copy the bootanimation.zip in to place and it works fine (I'll post after I polish a bit). Hopefully I won't see it again, but I did want to reach out in case others were seeing this or had more experience about it's implications with this storage medium. Thanks!
from xda-developers http://ift.tt/2dhQpo1
via IFTTT
Aucun commentaire:
Enregistrer un commentaire