I'm getting a error flashing Nightlies (same one in my previous thread, where I tried all options and couldnt figure it out). Here's the error output from CWM recovery, hoping someone could read it and explain why the flash of a Nightly over a previous one is not working for me.
Code:
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
W:failed to mount /dev/block/mmcblk0p25 (Invalid argument)
-- Wiping cache...
Formatting /cache...
I:Formatting unknown device.
I:Formatting ext3 device.
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
52624 inodes, 209715 blocks
10485 blocks (5%) reserved for the super user
First data block=1
Maximum filesystem blocks=262144
26 block groups
8192 blocks per group, 8192 fragments per group
2024 inodes per group
Superblock backups stored on blocks:
8193, 24577, 40961, 57345, 73729, 204801
tune2fs 1.41.6 (30-May-2009)
Setting current mount count to 1
Creating journal inode: done
This filesystem will be automatically checked every 34 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
e2fsck 1.41.6 (30-May-2009)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p27: 11/52624 files (0.0% non-contiguous), 10771/209715 blocks
Cache wipe complete.
E:unknown volume for path [/sd-ext]
rm: can't remove '/cache/dalvik-cache': No such file or directory
rm: can't remove '/sd-ext/dalvik-cache': No such file or directory
Dalvik Cache wiped.
-- Installing: /sdcard/cm_vision_full-145.zip
Finding update package...
I:Update location: /sdcard/cm_vision_full-145.zip
Opening update package...
Installing update...
about to run program [/tmp/backuptool.sh] with 2 args
Creating filesystem with parameters:
Size: 435943936
Block size: 4096
Blocks per group: 32768
Inodes per group: 6652
Inode size: 256
Journal blocks: 1663
Label:
Blocks: 106431
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/26608 inodes and 3437/106431 blocks
error: file_write: write: I/O error
E:Error in /sdcard/cm_vision_full-145.zip
(Status 1)
Installation aborted.
I have a strange problem with my 8GB Nexus 7 and I hope, its not a hardware fault.
I buyed the Tablet in 08/2012 at googles playstore and installed CWM Recovery.
After Updating to Android 4.2 at 11/2012, the Tablet works 2 days without any Problems.
After a restart (battery was empty), the Tablet boots and stops at a screen for unlocking encrypted storage. It asks for a password.
Because i never entered a password, and never encrypt the Tablet, i try a wipe at CWM. It ends with an error message:
-- wiping data
Formatting /data
Error mounting /data
...
So i checked dmesg at ADB (cutted, full LOG is attached):
Code:
<6>[ 0.000000] Initializing cgroup subsys cpu
<5>[ 0.000000] Linux version 3.1.10-g52027f9 ([email protected]) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #1 SMP PREEMPT Thu Jun 28 16:19:26 PDT 2012
<6>[ 7.684297] mmc1: new high speed SDIO card at address 0001
<6>[ 7.691530] [mmc]:mmc_rescan_try_freq:1892 mmc1: sdio completed
<6>[ 9.020863] EXT4-fs (mmcblk0p4): recovery complete
<6>[ 9.021726] EXT4-fs (mmcblk0p4): mounted filesystem with ordered data mode. Opts:
<6>[ 9.070219] cable_detection_work_handler(): vbus_active = 0 and is_active = 1
<6>[ 9.070227] The USB cable is connected
<3>[ 9.088156] mmcblk0: error -110 transferring data, sector 1391352, nr 64, cmd response 0x900, card status 0x4000d00
<3>[ 9.088301] end_request: I/O error, dev mmcblk0, sector 1391352
<3>[ 9.088379] end_request: I/O error, dev mmcblk0, sector 1391360
<3>[ 9.088515] end_request: I/O error, dev mmcblk0, sector 1391368
<3>[ 9.088590] end_request: I/O error, dev mmcblk0, sector 1391376
<3>[ 9.088725] end_request: I/O error, dev mmcblk0, sector 1391384
<3>[ 9.088800] end_request: I/O error, dev mmcblk0, sector 1391392
<3>[ 9.088935] end_request: I/O error, dev mmcblk0, sector 1391400
<3>[ 9.089011] end_request: I/O error, dev mmcblk0, sector 1391408
<3>[ 9.089177] Aborting journal on device mmcblk0p4-8.
<0>[ 9.090018] journal commit I/O error
<4>[ 28.937444] adbd (125): /proc/125/oom_adj is deprecated, please use /proc/125/oom_score_adj instead.
i tried to mount /dev/block/mmcblk0p9 with the following error:
Code:
<3>[ 1252.621408] EXT3-fs (mmcblk0p9): error: couldn't mount because of unsupported optional features (40)
<3>[ 1252.670984] EXT2-fs (mmcblk0p9): error: couldn't mount because of unsupported optional features (44)
<3>[ 1255.510979] mmcblk0: error -110 transferring data, sector 5997888, nr 40, cmd response 0x900, card status 0x4000d00
<3>[ 1255.511068] end_request: I/O error, dev mmcblk0, sector 5997888
<4>[ 1255.511204] quiet_error: 2283 callbacks suppressed
<3>[ 1255.511279] Buffer I/O error on device mmcblk0p9, logical block 458792
<4>[ 1255.511412] lost page write due to I/O error on mmcblk0p9
<3>[ 1255.511489] end_request: I/O error, dev mmcblk0, sector 5997896
<3>[ 1255.511624] Buffer I/O error on device mmcblk0p9, logical block 458793
<4>[ 1255.511755] lost page write due to I/O error on mmcblk0p9
<3>[ 1255.511828] end_request: I/O error, dev mmcblk0, sector 5997904
<3>[ 1255.511962] Buffer I/O error on device mmcblk0p9, logical block 458794
<4>[ 1255.512036] lost page write due to I/O error on mmcblk0p9
<3>[ 1255.512172] end_request: I/O error, dev mmcblk0, sector 5997912
<3>[ 1255.512247] Buffer I/O error on device mmcblk0p9, logical block 458795
<4>[ 1255.512379] lost page write due to I/O error on mmcblk0p9
<3>[ 1255.512454] end_request: I/O error, dev mmcblk0, sector 5997920
<3>[ 1255.512588] Buffer I/O error on device mmcblk0p9, logical block 458796
<4>[ 1255.512661] lost page write due to I/O error on mmcblk0p9
<3>[ 1255.543050] mmcblk0: error -110 transferring data, sector 6526376, nr 40, cmd response 0x900, card status 0x4000d00
<3>[ 1255.543191] end_request: I/O error, dev mmcblk0, sector 6526376
<3>[ 1255.543268] Buffer I/O error on device mmcblk0p9, logical block 524853
<4>[ 1255.543400] lost page write due to I/O error on mmcblk0p9
<3>[ 1255.543476] end_request: I/O error, dev mmcblk0, sector 6526384
<3>[ 1255.543607] Buffer I/O error on device mmcblk0p9, logical block 524854
<4>[ 1255.543679] lost page write due to I/O error on mmcblk0p9
<3>[ 1255.543811] end_request: I/O error, dev mmcblk0, sector 6526392
<3>[ 1255.543885] Buffer I/O error on device mmcblk0p9, logical block 524855
<4>[ 1255.544015] lost page write due to I/O error on mmcblk0p9
<3>[ 1255.544089] end_request: I/O error, dev mmcblk0, sector 6526400
<3>[ 1255.544221] Buffer I/O error on device mmcblk0p9, logical block 524856
<4>[ 1255.544351] lost page write due to I/O error on mmcblk0p9
<3>[ 1255.544426] end_request: I/O error, dev mmcblk0, sector 6526408
<3>[ 1255.544571] Buffer I/O error on device mmcblk0p9, logical block 524857
<4>[ 1255.544644] lost page write due to I/O error on mmcblk0p9
<3>[ 1255.573641] mmcblk0: error -110 transferring data, sector 13861888, nr 40, cmd response 0x900, card status 0x4000d00
<3>[ 1255.573780] end_request: I/O error, dev mmcblk0, sector 13861888
<3>[ 1255.573870] end_request: I/O error, dev mmcblk0, sector 13861896
<3>[ 1255.574004] end_request: I/O error, dev mmcblk0, sector 13861904
<3>[ 1255.574080] end_request: I/O error, dev mmcblk0, sector 13861912
<3>[ 1255.574215] end_request: I/O error, dev mmcblk0, sector 13861920
<3>[ 1255.583454] mmcblk0: error -110 transferring data, sector 13862120, nr 40, cmd response 0x900, card status 0x4000d00
<3>[ 1255.583593] end_request: I/O error, dev mmcblk0, sector 13862120
<3>[ 1255.583732] end_request: I/O error, dev mmcblk0, sector 13862128
<3>[ 1255.583808] end_request: I/O error, dev mmcblk0, sector 13862136
<3>[ 1255.583944] end_request: I/O error, dev mmcblk0, sector 13862144
<3>[ 1255.584019] end_request: I/O error, dev mmcblk0, sector 13862152
<4>[ 1255.597238] JBD: recovery failed
<3>[ 1255.597322] EXT4-fs (mmcblk0p9): error loading journal
I tried to erase the Memory with "dd if=/dev/zero of=/dev/block/mmcblk0p9". Dmesg was flooding with:
Code:
<3>[ 150.817559] end_request: I/O error, dev mmcblk0, sector 2503504
<3>[ 150.817665] end_request: I/O error, dev mmcblk0, sector 2503512
<3>[ 150.817842] end_request: I/O error, dev mmcblk0, sector 2503520
Also fastboot flash recovery/system etc. wont work.
It looks like the eMMC Chip died and got Read-Only.
I backed up the data by mounting with "-o loop,ro,noexec,noload" and ADB Pull. The chip dont write any changes back.
Any suggestions to fix the eMMC Chip?
Thanks
I know you mentioned fastboot flash partition, what about
fastboot erase system
fastboot erase userdata
Sent from my Nexus 7 using Tapatalk HD
Fastboot runs without error, but no change after booting. System and Userdata are not erased. Android stop at: unlock decrypted storage.
Code:
[email protected]:~# fastboot erase system
erasing 'system'... OKAY
[email protected]:~# fastboot erase userdata
erasing 'userdata'... OKAY
XMChrizzz said:
Fastboot runs without error, but no change after booting. System and Userdata are not erased. Android stop at: unlock decrypted storage.
Code:
[email protected]:~# fastboot erase system
erasing 'system'... OKAY
[email protected]:~# fastboot erase userdata
erasing 'userdata'... OKAY
Click to expand...
Click to collapse
So if you do those commands up top and nothing else it still boots into Android? If that's the case if contact Google to see what to do. If you got it from the Play Store it should be covered under warranty
Sent from my Nexus 7 using Tapatalk HD
OP's problem seems like a hardware issue.
Sent from my Nexus 7 using Tapatalk HD
Okay thank you, i will contact google.
So my tablet has been out of commission for a few months.. The battery drained fully one day and after charging it back up, it wouldn't boot (stuck on cyanogen boot screen) or go into recovery so I tried to re-flash the rom and then it got stuck in APX... so long story short, and a lot of experimentation later, I was able to reflash a working recovery and upgrade to the v8 bootloader, but I think my emmc is shot. --> When I try to flash a rom now it tells me that it can't mount certain partitions and what not, so! since some partitions apparently work, is it possible to flash a custom kernel or boot or something that looks at the sd card for the actual rom?
Read through another thread earlier today about figuring out if your emmc is hosed and ran dmesg | grep mmc in fastboot >>
Code:
<5>[ 0.000000] Kernel command line: tegraid=20.1.4.0.0 [email protected] androidbo
ot.serialno=[omitted] video=tegrafb console=none debug_uartport=hsport us
bcore.old_scheme_first=1 [email protected] [email protected]
brand=acer target_product=a500_ww_gen1 tegraboot=sdmmc gpt gpt_sector=15628287 a
ndroidboot.carrier=wifi-only bootloader_ver=0.03.14-MUL
<4>[ 3.323447] mmc0: Invalid maximum block size, assuming 512 bytes
<7>[ 3.323892] Registered led device: mmc0::
<6>[ 3.324098] mmc0: SDHCI controller on tegra [sdhci-tegra.3] using ADMA
<4>[ 3.324377] mmc1: Invalid maximum block size, assuming 512 bytes
<6>[ 3.324540] mmc1: no vmmc regulator found
<7>[ 3.324684] Registered led device: mmc1::
<6>[ 3.324846] mmc1: SDHCI controller on tegra [sdhci-tegra.2] using ADMA
<4>[ 3.325308] mmc2: Invalid maximum block size, assuming 512 bytes
<6>[ 3.325401] mmc2: no vmmc regulator found
<7>[ 3.325613] Registered led device: mmc2::
<6>[ 3.325772] mmc2: SDHCI controller on tegra [sdhci-tegra.0] using ADMA
<6>[ 3.417646] mmc0: new high speed MMC card at address 0001
<6>[ 3.418071] mmcblk0: mmc0:0001 M8G2FA 7.45 GiB
<6>[ 3.420953] mmcblk0: p1 p2 p3 p4 p5 p6 p7
<6>[ 3.654402] mmc1: new high speed SDHC card at address aaaa
<6>[ 3.654751] mmcblk1: mmc1:aaaa SU32G 29.7 GiB
<6>[ 3.657460] mmcblk1: p1
<3>[ 4.159931] EXT4-fs (mmcblk0p4): VFS: Can't find ext4 filesystem
<3>[ 5.586322] EXT4-fs (mmcblk0p4): VFS: Can't find ext4 filesystem
<3>[ 5.963153] EXT4-fs (mmcblk0p4): VFS: Can't find ext4 filesystem
<3>[ 6.356707] EXT4-fs (mmcblk0p4): VFS: Can't find ext4 filesystem
<3>[ 145.099265] EXT4-fs (mmcblk0p4): VFS: Can't find ext4 filesystem
<3>[ 145.541972] EXT4-fs (mmcblk0p4): VFS: Can't find ext4 filesystem
<3>[ 145.968406] EXT4-fs (mmcblk0p4): VFS: Can't find ext4 filesystem
Following the howto here. I flashed twrp-2.8.6.0-mako.img and then hilighted "Reboot" with the volume keys and selected "Recovery". TWRP booted, and there was a small text field that flashed by with some red text in it about "/cache" or something and then the phone rebooted. It's stuck now in a TWRP boot loop. I was able to get into the device shell over ADB while TWRP was busy looping around and found this in dmesg. Um, where do I go from here? I have a hunch I can probably mkfs.ext4 /dev/mmcblk0p23 and then TWRP will boot but it's just a gues; is there an official fix for this? Is mmcblk0p23 really hosed from flashing TWRP or is this a TWRP bug? I've installed TWRP on a few different devices and never had this happen before. Thanks!
Code:
<6>[ 2.949000] android_work: android_work: sent uevent USB_STATE=CONFIGURED
<3>[ 3.009308] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<6>[ 3.040012] unplug_usbcheck_work: usb_vin : 4607444, max_voltage_mv=4360
<3>[ 3.089516] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 3.194109] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 3.270044] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 3.375156] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 3.459606] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<6>[ 3.562276] EXT4-fs (mmcblk0p22): mounted filesystem with ordered data mode. Opts:
<7>[ 3.562643] SELinux: initialized (dev mmcblk0p22, type ext4), uses xattr
<6>[ 3.594140] EXT4-fs (mmcblk0p21): mounted filesystem with ordered data mode. Opts:
<7>[ 3.594353] SELinux: initialized (dev mmcblk0p21, type ext4), uses xattr
<3>[ 3.704318] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 3.789684] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 3.884846] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 3.999938] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 4.103647] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 4.199725] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 4.304318] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 4.399664] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 4.998077] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 5.069708] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 5.667968] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 5.739722] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 6.346558] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 6.439554] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 7.028109] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 7.099710] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<6>[ 7.129040] msm_ta_detect_work: USB exit ta detection - frindex
<3>[ 7.707828] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 7.799694] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<6>[ 8.598992] mipi_lgit_lcd_off started
<6>[ 8.729040] mipi_lgit_lcd_off finished
<6>[ 8.729253] mipi_dsi_panel_power: mipi lcd function started status = 0
<6>[ 9.403784] mipi_dsi_panel_power: mipi lcd function started status = 1
<6>[ 9.405493] mipi_dsi_panel_power : reset start.
<6>[ 9.426644] mipi_lgit_lcd_on started
<6>[ 9.489211] mipi_lgit_lcd_on finished
<3>[ 9.796978] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 9.879536] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 9.961513] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 10.059697] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 10.155226] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 10.239707] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<6>[ 10.329375] EXT4-fs (mmcblk0p21): mounted filesystem with ordered data mode. Opts:
<7>[ 10.329620] SELinux: initialized (dev mmcblk0p21, type ext4), uses xattr
<3>[ 10.444407] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 10.519670] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 10.624752] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 10.699679] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 10.812604] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 10.889760] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 10.984465] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 11.069647] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 11.667907] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 11.739752] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 12.338074] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 12.429360] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 13.037906] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 13.139600] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 13.744819] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 13.819655] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 14.438242] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 14.529681] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<6>[ 15.298977] mipi_lgit_lcd_off started
<6>[ 15.429055] mipi_lgit_lcd_off finished
<6>[ 15.429238] mipi_dsi_panel_power: mipi lcd function started status = 0
<6>[ 16.103982] mipi_dsi_panel_power: mipi lcd function started status = 1
<6>[ 16.105692] mipi_dsi_panel_power : reset start.
<6>[ 16.126842] mipi_lgit_lcd_on started
<6>[ 16.199114] mipi_lgit_lcd_on finished
<4>[ 16.457347] adbd (162): /proc/162/oom_adj is deprecated, please use /proc/162/oom_score_adj instead.
Hi,
- have you updated your android-sdk (adb, etc) to the newest version?
- bootloader unlocked?
- boot your device into the bootloader and reflash twrp. (In case you did not try again)
If something is not clear to you, just ask.
cheers
greg17477 said:
Hi,
- have you updated your android-sdk (adb, etc) to the newest version?
- bootloader unlocked?
- boot your device into the bootloader and reflash twrp. (In case you did not try again)
cheers
Click to expand...
Click to collapse
Just updated android SDK tools to v24.1.2 and SDK platform tools to v22 (latest) and re-flashed twrp. Still no go. /data is still messed up. I've flashed a Nexus 4 before (a year ago maybe? ) without having this problem and wondering if something changed in the newer models?
eris170 said:
<3>[ 14.529681] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
[/CODE]
Click to expand...
Click to collapse
Seems to be fixed now. I ran ADB shell while TWRP was "looping" and got back into the device. I formatted /dev/block/mmcblk0p23 with mke2fs which creates an EXT2 filesystem. There is no utility to create an EXT4 FS on the device... although now that I think about it, maybe I should have checked the /system directory which wasn't mount... ? Dunno... anyway android won't use the EXT2 filesystem as is so I used tune2fs utility to create the neccesary journals and "features" to make it match /dev/block/mmcblk022 (/system partition). After rebooting, the phone sat at the "flying dots" boot logo for about 5 mins. I figured it was likely still hosed so powered it off and got some sleep. This morning, I decided to let it boot for 10 mins before I would try something else. Surprisingly, it booted up within a couple mins to the Android 5.0 setup screen! Rebooting into TWRP Recovery now works too. Here is what I did in case it helps someone else:
Code:
# view kernel logs
~ # dmesg
<3>[ 30.179703] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
# figure out where "/data" is
~ # cat /etc/fstab
/dev/block/mmcblk0p21 /system ext4 rw
/dev/block/mmcblk0p23 /data ext4 rw
/dev/block/mmcblk0p22 /cache ext4 rw
# list features of "good" partition
~ # tune2fs -l /dev/block/mmcblk0p22 << good partition
Filesystem features: has_journal ext_attr resize_inode filetype needs_recovery extent sparse_super large_file uninit_bg
# format ext2 FS onto p23
~ # mke2fs /dev/block/mmcblk0p23
mke2fs 1.42.9 (28-Dec-2013)
Discarding device blocks: done
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
863264 inodes, 3449600 blocks
172480 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=3535798272
106 block groups
32768 blocks per group, 32768 fragments per group
8144 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208
Allocating group tables: done
Writing inode tables: done
Writing superblocks and filesystem accounting information: done
# just have an ext2 FS on p23 now
~ # dmesg
<4>[ 591.519548] SELinux: (dev mmcblk0p23, type ext2) has no security xattr handler
<4>[ 591.547810] SELinux: (dev mmcblk0p23, type ext2) has no security xattr handler
<4>[ 592.099709] SELinux: (dev mmcblk0p23, type ext2) has no security xattr handler
<4>[ 592.127758] SELinux: (dev mmcblk0p23, type ext2) has no security xattr handler
# Add FS features to p23.. I had to keep removing features here until it would succeed.
~ # tune2fs -O has_journal,ext_attr,resize_inode,filetype,needs_recovery,extent,sparse_super,large_file,uninit_bg /dev/block/mmcblk0p23
tune2fs 1.42.9 (28-Dec-2013)
Setting filesystem feature 'ext_attr' not supported.
~ # tune2fs -O has_journal,filetype,extent,sparse_super,large_file,uninit_bg /dev/block/mmcblk0p23
tune2fs 1.42.9 (28-Dec-2013)
Creating journal inode: done
# reboot and wait for a while to see what happens. After 10 mins, maybe try a reboot again??
~ # reboot
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:
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
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!
EDIT: nevermind, misread issue