Related
I am running cyanogen's rom with a fat32 partition and ext3 partition. When i run fdisk on the device /dev/sdb, i get this as a result and it looks ok:
Code:
# fdisk /dev/sdb
Command (m for help): p
Disk /dev/sdb: 8067 MB, 8067743744 bytes
249 heads, 62 sectors/track, 1020 cylinders
Units = cylinders of 15438 * 512 = 7904256 bytes
Disk identifier: 0x000eadb7
Device Boot Start End Blocks Id System
/dev/sdb1 1 941 7263548 c W95 FAT32 (LBA)
/dev/sdb2 942 1005 487398 83 Linux
Partition 2 does not end on cylinder boundary.
however, I cant mount my partitions reliably. Sometimes when I plug it in, I get the fat32 partition as /dev/android, and sometimes I get the ext3 partition. but under both circumstances, i NEVER see /dev/sdb1 or /dev/sdb2.
Code:
# ls /dev | grep sd
lrwxrwxrwx 1 root root 4 2009-07-20 15:55 root -> sda3
brw-rw---- 1 root disk 8, 0 2009-07-20 15:55 sda
brw-rw---- 1 root disk 8, 1 2009-07-20 15:55 sda1
brw-rw---- 1 root disk 8, 2 2009-07-20 15:55 sda2
brw-rw---- 1 root disk 8, 3 2009-07-20 15:55 sda3
brw-rw---- 1 root disk 8, 16 2009-07-21 20:43 sdb
however, my dmesg reports this:
Code:
78640.618666] sd 30:0:0:0: [sdb] 15757312 512-byte hardware sectors: (8.06 GB/7.51 GiB)
[78640.620661] sd 30:0:0:0: [sdb] Write Protect is off
[78640.620664] sd 30:0:0:0: [sdb] Mode Sense: 03 00 00 00
[78640.620667] sd 30:0:0:0: [sdb] Assuming drive cache: write through
[78640.624658] sd 30:0:0:0: [sdb] 15757312 512-byte hardware sectors: (8.06 GB/7.51 GiB)
[78640.626659] sd 30:0:0:0: [sdb] Write Protect is off
[78640.626662] sd 30:0:0:0: [sdb] Mode Sense: 03 00 00 00
[78640.626665] sd 30:0:0:0: [sdb] Assuming drive cache: write through
[78640.626669] sdb: sdb1 sdb2
[78640.633034] usb 1-2:1.0: uevent
[78640.633122] usb 1-2: uevent
[78640.899187] usb 1-2:1.0: uevent
[78640.899276] usb 1-2: uevent
[78641.054596] VFS: Can't find ext3 filesystem on dev sdb1.
it takes a bunch of tries of unplugging the usb and plugging it back in until it finally somehow mounts my fat32 partition under /media/disk. Is this some configuration issue? Before I partitioned my sdcard, it was fine mounting just a fat32 partition as the entire card, no problems.
check you hald
/etc/init.d/hald restart
do you have support for udev in you kernel ?
Check this steps and tell us it worked
yes HAL is running and has been running the entire time:
Code:
# rc-update show
alsasound | boot
bootmisc | boot
checkfs | boot
checkroot | boot
clock | boot
consolefont | boot
cupsd | default
dbus | default
hald | default
hostname | boot
keymaps | boot
lm_sensors | default
local | default nonetwork
localmount | boot
modules | boot
net.eth0 | default
net.lo | boot
numlock | default
rdate | default
rmnologin | boot
sshd | default
syslog-ng | default
urandom | boot
xdm | default
Code:
$ ps aux | grep hal
103 3544 0.0 0.0 26956 4032 ? Ss Jul24 0:01 /usr/sbin/hald --use-syslog --verbose=no
root 3545 0.0 0.0 15624 1176 ? S Jul24 0:00 hald-runner
root 3548 0.0 0.0 17748 1124 ? S Jul24 0:00 hald-addon-input: Listening on /dev/input/event1 /dev/input/event0 /dev/input/event3
103 3553 0.0 0.0 16608 968 ? S Jul24 0:00 hald-addon-acpi: listening on acpi kernel interface /proc/acpi/event
root 3558 0.0 0.0 17748 1128 ? S Jul24 0:08 hald-addon-storage: polling /dev/sr0 (every 2 sec)
john5788 4596 0.0 0.0 130688 3120 ? Sl Jul24 0:00 /usr/libexec/gvfs-hal-volume-monitor
root 11452 0.0 0.0 17748 1124 ? S Jul24 0:01 hald-addon-storage: polling /dev/sdb (every 2 sec)
john5788 13851 0.0 0.0 84792 864 pts/1 R+ 10:10 0:00 grep --colour=auto hal
restarting does not help anything.
udevd --version ??
since version 140 those stupids rules messed up with removable devices.
Since I'm lazy I built my kernel with genkernel and it took care of everything about udev.
Code:
# udevd --version
141
so its a rule in udev that is screwin this up?
i'm not using genkernel, I rolled my own kernel out, have been doing it this way for years.
Code:
# uname -a
Linux john5788 2.6.29-gentoo-r5 #1 SMP Fri May 29 16:56:58 PDT 2009 x86_64 Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz GenuineIntel GNU/Linux
John5788 said:
Code:
# udevd --version
141
so its a rule in udev that is screwin this up?
i'm not using genkernel, I rolled my own kernel out, have been doing it this way for years.
Code:
# uname -a
Linux john5788 2.6.29-gentoo-r5 #1 SMP Fri May 29 16:56:58 PDT 2009 x86_64 Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz GenuineIntel GNU/Linux
Click to expand...
Click to collapse
Yeah i think ...
what's the output of dmesg |grep EXT3-fs ?
the output has a bunch of instances last night when i was plugging and unplugging the device. like i said, sometimes it recognized my fat32 partition, sometimes ext3.
Code:
# dmesg | grep EXT3-fs
[ 9016.479321] EXT3-fs warning: mounting unchecked fs, running e2fsck is recommended
[ 9016.481783] EXT3-fs: mounted filesystem with ordered data mode.
[ 9111.770944] EXT3-fs error (device sdb2): ext3_put_super: Couldn't clean up the journal
[ 9134.532699] EXT3-fs warning: mounting unchecked fs, running e2fsck is recommended
[ 9134.534632] EXT3-fs: recovery complete.
[ 9134.536841] EXT3-fs: mounted filesystem with ordered data mode.
[ 9166.843481] EXT3-fs warning: mounting unchecked fs, running e2fsck is recommended
[ 9166.849252] EXT3-fs: mounted filesystem with ordered data mode.
[ 9184.778649] EXT3-fs error (device sdb2): ext3_put_super: Couldn't clean up the journal
[ 9243.636550] EXT3-fs warning: mounting unchecked fs, running e2fsck is recommended
[ 9243.638973] EXT3-fs: recovery complete.
[ 9243.638976] EXT3-fs: mounted filesystem with ordered data mode.
[ 9305.343298] EXT3-fs warning: mounting unchecked fs, running e2fsck is recommended
[ 9305.345249] EXT3-fs: mounted filesystem with ordered data mode.
[ 9328.776678] EXT3-fs error (device sdb2): ext3_put_super: Couldn't clean up the journal
[15048.450805] EXT3-fs: recovery complete.
[15048.452800] EXT3-fs: mounted filesystem with ordered data mode.
[15055.778655] EXT3-fs error (device sdb2): ext3_put_super: Couldn't clean up the journal
ok it seems one of partitions is broken i've looked around the web
try to :
e2fsck -p your /home partitions and
fsck.vfat -p /dev/sdb1 and e2fsck -p /dev/sdb2
I don't use any kind of automation, not even hal, but I have the same issue, without corruption though.
However, I have found that using cfdisk on /dev/sdb makes /dev/sdb{1,2} appear magically, and I can mount them correctly.
That's not really elegant, but it works for me.
I use adb push most of the time anyways, that way I don't have to unmount the SD from the phone and everything is smooth.
Zappletoo said:
I don't use any kind of automation, not even hal, but I have the same issue, without corruption though.
However, I have found that using cfdisk on /dev/sdb makes /dev/sdb{1,2} appear magically, and I can mount them correctly.
That's not really elegant, but it works for me.
I use adb push most of the time anyways, that way I don't have to unmount the SD from the phone and everything is smooth.
Click to expand...
Click to collapse
tht's strange cfdisk should not help mounting the devices but if it work it's worthing give it a try.
it has to be something with hal and rules :
emerge -pv hal dbus
etc-update
should get rid of that problem
PS : Zappletoo what linux distribution are you using ??
Gentoo.
But I don't use HAL, I don't see any good reason to. I'll try to activate it to see if it makes a difference, but I doubt it.
I'm not sure why cfdisk helps, maybe it simply updates the partition table somewhere.
Update : starting hald makes it work. Using partprobe works as well.. So I guess I was right about the partition table part.
what do you mean use cfdisk on it?
did you just select mount from the phone, then run cfdisk /dev/sdb, then immediately quit?
no no run cfdisk on your computer
Edit: yes I misread. That's what he did.
If things goes well your 2 partitions should appear
John5788 said:
what do you mean use cfdisk on it?
did you just select mount from the phone, then run cfdisk /dev/sdb, then immediately quit?
Click to expand...
Click to collapse
Yes, on the computer.
Apparently it does the same as partprobe, which is available in the sys-apps/parted package.
Hald does everything automatically though, but it's bloated.
Never had a problem with gentoo. No Hal...udev 1.41...custom kernel. Somewhere else on this forum however someone pointed out the phone doesn't show up properly in linux without first probing it. i.e. 'fdisk -l /dev/sda'. This has worked for me whenever I choose to mount it (which is almost never cuz i love adb).
Hi,it all started after i flashed TWRP in my HTC sensation xe(i had 4EXT recovery),then i wanted to flash a new rom but something happened and my htc freezed and then i pulled out the battery and inserted it,i turned it On but then it couldn't mount the system,cache,data.One of my friends managed to flash again the 4EXT recovery and told me that my partitions are corrupted.I tried some metjods with adb but nothing happened,
</tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext ra_isize -m 0 /dev/block/mmcblk0p37> but it says <no such file or directory>
and also tried this <parted /dev/block/mmcblk0 mkfs ext2> but it says <can't have overlapping partitions>
noutsos said:
Hi,it all started after i flashed TWRP in my HTC sensation xe(i had 4EXT recovery),then i wanted to flash a new rom but something happened and my htc freezed and then i pulled out the battery and inserted it,i turned it On but then it couldn't mount the system,cache,data.One of my friends managed to flash again the 4EXT recovery and told me that my partitions are corrupted.I tried some metjods with adb but nothing happened,
</tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext ra_isize -m 0 /dev/block/mmcblk0p37> but it says <no such file or directory>
and also tried this <parted /dev/block/mmcblk0 mkfs ext2> but it says <can't have overlapping partitions>
Click to expand...
Click to collapse
do you have access to the bootloader/recovery?
noutsos said:
Hi,it all started after i flashed TWRP in my HTC sensation xe(i had 4EXT recovery),then i wanted to flash a new rom but something happened and my htc freezed and then i pulled out the battery and inserted it,i turned it On but then it couldn't mount the system,cache,data.One of my friends managed to flash again the 4EXT recovery and told me that my partitions are corrupted.I tried some metjods with adb but nothing happened,
</tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext ra_isize -m 0 /dev/block/mmcblk0p37> but it says <no such file or directory>
and also tried this <parted /dev/block/mmcblk0 mkfs ext2> but it says <can't have overlapping partitions>
Click to expand...
Click to collapse
I have the same problem with you,,,I have not fix it at all,,,maybe we can ask @shantur for help,,,
which rom and the TWRP version do you use???
[email protected] said:
I have the same problem with you,,,I have not fix it at all,,,maybe we can ask @shantur for help,,,
which rom and the TWRP version do you use???
Click to expand...
Click to collapse
i can access my 4est recovery but i dont have a rom,after flashing one my phone stucks in the logo
noutsos said:
i can access my 4est recovery but i dont have a rom,after flashing one my phone stucks in the logo
Click to expand...
Click to collapse
are you on S-ON?
post your bootloader details
rzr86 said:
are you on S-ON?
post your bootloader details
Click to expand...
Click to collapse
i am S OFF
firmware 3.33
hboot 1.27.1100
radio 11.24A.3504.31_M
noutsos said:
i am S OFF
firmware 3.33
hboot 1.27.1100
radio 11.24A.3504.31_M
Click to expand...
Click to collapse
ok probably you need to update 4ext version to the latest
also redownload the rom
by the way which rom did you try to flash?
rzr86 said:
ok probably you need to update 4ext version to the latest
also redownload the rom
by the way which rom did you try to flash?
Click to expand...
Click to collapse
i tried to flash viperS 5.1.0
i tried to flash the stock,when i do factory reset it says "E:formate_volume: make_extf4fs failed on /dev/block/mmcblk0p24"
and then i reboot and stucks in htc logo
noutsos said:
i tried to flash viperS 5.1.0
i tried to flash the stock,when i do factory reset it says "E:formate_volume: make_extf4fs failed on /dev/block/mmcblk0p24"
and then i reboot and stucks in htc logo
Click to expand...
Click to collapse
use the option format all partitions except sdcard from 4ext
then reflash the rom
which version of 4ext do you have?
rzr86 said:
use the option format all partitions except sdcard from 4ext
then reflash the rom
which version of 4ext do you have?
Click to expand...
Click to collapse
version 1.0.0.5 RC5
but the same thing occurs,in system is blk0p22,in data number23,in cache number24
when i try to flash custo rom it says installation aborted
noutsos said:
version 1.0.0.5 RC5
but the same thing occurs,in system is blk0p22,in data number23,in cache number24
when i try to flash custo rom it says installation aborted
Click to expand...
Click to collapse
here is the latest version of 4ext
http://www.4shared.com/zip/WnSyLWMaba/4EXT_Recovery_Touch_v1006_RC3_.html
extract the recovery.img and flash it via fastboot command
but probably your emmc is corrupted unfortunately
by the way did you try a ruu.exe?
rzr86 said:
here is the latest version of 4ext
http://www.4shared.com/zip/WnSyLWMaba/4EXT_Recovery_Touch_v1006_RC3_.html
extract the recovery.img and flash it via fastboot command
but probably your emmc is corrupted unfortunately
by the way did you try a ruu.exe?
Click to expand...
Click to collapse
tried ruu exe but nth happened,cant find the device,and cant fastboot
How does fastboot not work? Does usb not connect at all?
Hey guys, any news about fixing bug in TWRP which caused corrupting partitions and bricking phones?
Hi guys,
I have the same issue as OP, however only the /data won't get mounted. My phone got stuck while doing wipe of the data partition in TWRP 2.6.3.0 (it didn't freeze, but it was taking over 40 minutes already), so I had to take the battery out and put it back in.
First, I tried using TWRP 2.6.3.0 to perform the wipe again, but I got
Code:
E:Unable to mount '/data'
I got the same error when I tried to install any ROM, so the installation got aborted.
Then I flashed 4EXT Recovery Touch v1.0.0.6 RC3 through fastboot and did Format all partitions (except sdcard). The format went fine with no errors, however when I tried to flash any ROM (I tried CyanogenMod 11 with 3.0.16 kernel by sultanxda and Slimkat specifically), I get:
Code:
Installing update...
set_metadata_recursive: some changes failed
E:Error in /sdcard/Slim-pyramid-4.4.4.build.7.8-WEEKLY-6262.zip (Status 7)
Installation aborted.
Same happens with the CM11 ROM. I also tried performing the full format with 4EXT recovery, then flashing the ROMs with TWRP. Same problem as before, Unable to mount '/data'.
Here is my bootloader info:
S-OFF
Firmware 3.33
HBOOT 1.27.1100
Radio 11.24A.3504.31_M
I am pretty much desperate at this point. Is there any way or chance of fixing my partitions? I haven't tried fixing it using parted, because I was unable to find a good howto for Sensation. I would be happy for any advice.
MatesCZ said:
Then I flashed 4EXT Recovery Touch v1.0.0.6 RC3 through fastboot and did Format all partitions (except sdcard). The format went fine with no errors, however when I tried to flash any ROM (I tried CyanogenMod 11 with 3.0.16 kernel by sultanxda and Slimkat specifically), I get:
Code:
Installing update...
set_metadata_recursive: some changes failed
E:Error in /sdcard/Slim-pyramid-4.4.4.build.7.8-WEEKLY-6262.zip (Status 7)
Installation aborted.
Same happens with the CM11 ROM. I also tried performing the full format with 4EXT recovery, then flashing the ROMs with TWRP. Same problem as before, Unable to mount '/data'..
Click to expand...
Click to collapse
i think something is wrong with the rom zip or with sdcard
try to redownload the rom and flash it again with 4ext recovery
or try to flash a different rom
rzr86 said:
i think something is wrong with the rom zip or with sdcard
try to redownload the rom and flash it again with 4ext recovery
or try to flash a different rom
Click to expand...
Click to collapse
Here is what I did:
- Formatted the SD card
- Put CM11, Slimkat and ViperS/C2 5.2.1 on it
- Checked MD5/SHA1 sums for each of them
- Went to 4EXT, performed full format
- Tried to flash Slimkat first, same result as before:
Code:
Installing update...
set_metadata_recursive: some changes failed
E:Error in /sdcard/Slim-pyramid-4.4.4.build.7.8-WEEKLY-6262.zip (Status 7)
Installation aborted.
- Tried to flash ViperS, the installer went through fine, no errors, however, after exiting the installer, 4EXT recovery window was showing:
Code:
Starting AROMA Installer version 2.70RC2
(c) 2013 by amarullz xda-developers
E:Error in /sdcard/ViperSC2_5.2.1.zip
(Status 0)
Installation aborted.
Tried to reboot anyway, but phone is stuck on the Sensation logo
MatesCZ said:
Here is what I did:
- Formatted the SD card
- Put CM11, Slimkat and ViperS/C2 5.2.1 on it
- Checked MD5/SHA1 sums for each of them
- Went to 4EXT, performed full format
- Tried to flash Slimkat first, same result as before:
Code:
Installing update...
set_metadata_recursive: some changes failed
E:Error in /sdcard/Slim-pyramid-4.4.4.build.7.8-WEEKLY-6262.zip (Status 7)
Installation aborted.
- Tried to flash ViperS, the installer went through fine, no errors, however, after exiting the installer, 4EXT recovery window was showing:
Code:
Starting AROMA Installer version 2.70RC2
(c) 2013 by amarullz xda-developers
E:Error in /sdcard/ViperSC2_5.2.1.zip
(Status 0)
Installation aborted.
Tried to reboot anyway, but phone is stuck on the Sensation logo
Click to expand...
Click to collapse
in both cases the issue is the sdcard as i see
i suggest to format your sdcard
backup first whatever you need
or if you have a different sdcard try to flash the rom with that one
rzr86 said:
in both cases the issue is the sdcard as i see
i suggest to format your sdcard
backup first whatever you need
or if you have a different sdcard try to flash the rom with that one
Click to expand...
Click to collapse
As I mentioned, I did format the SD card before trying.
Also today I tried with different, definitely working SD card (also formatted before trying) - same results as mentioned before. Doesn't seem to be SD card-related.
I also tried flashing stock ROM from RUU by extracting the rom.zip and renaming it to P58IMG.zip - the process gets stuck at
Code:
[6] USERDATA -Updating
forever. This consequently locked my bootloader, but I was able to unlock it again using fastboot.
I managed to retrieve log from 4EXT, and this is what it says during format of everything:
Code:
About to format everything..
..except your fat32 partition
Format BOOT SYSTEM DATA CACHE SD-EXT..?
Formatting /boot...
I:Formatting unknown device.
Formatting /system...
mke2fs 1.42.9 (28-Dec-2013)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=64 blocks, Stripe width=64 blocks
51296 inodes, 204799 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
7 block groups
32768 blocks per group, 32768 fragments per group
7328 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840
Allocating group tables: 0/7 done
Writing inode tables: 0/7 done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: 0/7 done
-- Wiping data...
Formatting /data...
mke2fs 1.42.9 (28-Dec-2013)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=64 blocks, Stripe width=64 blocks
76480 inodes, 305852 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
10 block groups
32768 blocks per group, 32768 fragments per group
7648 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912
Allocating group tables: 0/10 done
Writing inode tables: 0/10 done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: 0/10 done
Formatting /cache...
mke2fs 1.42.9 (28-Dec-2013)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=64 blocks, Stripe width=64 blocks
30720 inodes, 30709 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
1 block group
32768 blocks per group, 32768 fragments per group
30720 inodes per group
Allocating group tables: 0/1 done
Warning: could not read block 0: Attempt to read block from filesystem resulted in short read
Writing inode tables: 0/1 done
Creating journal (1024 blocks): done
Writing superblocks and filesystem accounting information: 0/1 done
W:failed to mount /dev/block/mmcblk0p24 (Invalid argument)
W:failed to mount /dev/block/mmcblk0p24 (Invalid argument)
Formatting /sdcard/.android_secure...
I:Formatting unknown device.
Data wipe complete.
All internal partitions have been formatted.
This includes dalvik-cache and batt stats
since they are just files / directories.
Your sdcard(s) weren't touched
no worries.
These lines in particular are most likely related to the problem
Warning: could not read block 0: Attempt to read block from filesystem resulted in short read
...
W:failed to mount /dev/block/mmcblk0p24 (Invalid argument)
W:failed to mount /dev/block/mmcblk0p24 (Invalid argument)
Click to expand...
Click to collapse
MatesCZ said:
As I mentioned, I did format the SD card before trying.
Also today I tried with different, definitely working SD card (also formatted before trying) - same results as mentioned before. Doesn't seem to be SD card-related.
I also tried flashing stock ROM from RUU by extracting the rom.zip and renaming it to P58IMG.zip - the process gets stuck at
Code:
[6] USERDATA -Updating
forever. This consequently locked my bootloader, but I was able to unlock it again using fastboot.
I managed to retrieve log from 4EXT, and this is what it says during format of everything:
Code:
About to format everything..
..except your fat32 partition
Format BOOT SYSTEM DATA CACHE SD-EXT..?
Formatting /boot...
I:Formatting unknown device.
Formatting /system...
mke2fs 1.42.9 (28-Dec-2013)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=64 blocks, Stripe width=64 blocks
51296 inodes, 204799 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
7 block groups
32768 blocks per group, 32768 fragments per group
7328 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840
Allocating group tables: 0/7 done
Writing inode tables: 0/7 done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: 0/7 done
-- Wiping data...
Formatting /data...
mke2fs 1.42.9 (28-Dec-2013)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=64 blocks, Stripe width=64 blocks
76480 inodes, 305852 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
10 block groups
32768 blocks per group, 32768 fragments per group
7648 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912
Allocating group tables: 0/10 done
Writing inode tables: 0/10 done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: 0/10 done
Formatting /cache...
mke2fs 1.42.9 (28-Dec-2013)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=64 blocks, Stripe width=64 blocks
30720 inodes, 30709 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
1 block group
32768 blocks per group, 32768 fragments per group
30720 inodes per group
Allocating group tables: 0/1 done
Warning: could not read block 0: Attempt to read block from filesystem resulted in short read
Writing inode tables: 0/1 done
Creating journal (1024 blocks): done
Writing superblocks and filesystem accounting information: 0/1 done
W:failed to mount /dev/block/mmcblk0p24 (Invalid argument)
W:failed to mount /dev/block/mmcblk0p24 (Invalid argument)
Formatting /sdcard/.android_secure...
I:Formatting unknown device.
Data wipe complete.
All internal partitions have been formatted.
This includes dalvik-cache and batt stats
since they are just files / directories.
Your sdcard(s) weren't touched
no worries.
These lines in particular are most likely related to the problem
Click to expand...
Click to collapse
yeah you are right
some partitions are broken probably from TWRP because a lot of users faced issues similar with yours
someone posted a solution few days ago how to boot a rom from sdcard
he had also broken partitions in internal memory caused from TWRP and he managed to boot a rom from sdcard
he created two partitions
one to be recognized as /data and one to be recognized as /system and mounted them successfully(if i remember well)
but i can't find that post
if i find it i will come with edit
Phone: Galaxy S3 VZW 32GB
Recovery: TWRP 2.7.1.0
Mod: CM11 m8
Kernel, governer, etc all CM11 stock.
Problem:
Twice today the phone rebooted itself while performing large file copy operations. last_kmsg from both reboots basically look the same:
Code:
[40996.107363] Buffer I/O error on device mmcblk0p15, logical block 6751031
[40996.114291] Buffer I/O error on device mmcblk0p15, logical block 6751032
[40996.120761] Buffer I/O error on device mmcblk0p15, logical block 6751033
[40996.127476] Buffer I/O error on device mmcblk0p15, logical block 6751034
[40996.134160] Buffer I/O error on device mmcblk0p15, logical block 6751035
[40996.140813] Buffer I/O error on device mmcblk0p15, logical block 6751036
[40996.147528] Buffer I/O error on device mmcblk0p15, logical block 6751037
[40996.154181] Buffer I/O error on device mmcblk0p15, logical block 6751038
[40996.160926] Buffer I/O error on device mmcblk0p15, logical block 6751039
[41056.701656] ACDB=> get_hw_delay: Path = 0 samplerate = 48000 usec = 0 status 0
[41056.708065] afe_callback: cmd = 0x100dc returned error = 0x3
[41056.713681] afe_send_hw_delay: config cmd failed
[41065.991721] kgsl kgsl-3d0: |kgsl_late_resume_driver| late resume start
[41066.310781] cypress_touchkey 16-0020: not real interrupt (1).
[41117.725034] EXT4-fs error (device mmcblk0p15): ext4_mb_generate_buddy:741: group 113, 644 clusters in bitmap, 530 in gd
[41117.744476] Aborting journal on device mmcblk0p15-8.
[41117.764161] Kernel panic - not syncing: EXT4-fs (device mmcblk0p15): panic forced after error
[41117.764161]
[41117.773257] [<c0013ee8>] (unwind_backtrace+0x0/0xe0) from [<c0778f40>] (panic+0x88/0x1f8)
[41117.781344] [<c0778f40>] (panic+0x88/0x1f8) from [<c01a7134>] (ext4_handle_error+0x8c/0x98)
[41117.789738] [<c01a7134>] (ext4_handle_error+0x8c/0x98) from [<c01a7ca0>] (__ext4_grp_locked_error+0xe8/0x1c4)
[41117.799626] [<c01a7ca0>] (__ext4_grp_locked_error+0xe8/0x1c4) from [<c01b6618>] (ext4_mb_generate_buddy+0x25c/0x2e8)
[41117.810125] [<c01b6618>] (ext4_mb_generate_buddy+0x25c/0x2e8) from [<c01b8620>] (ext4_mb_init_cache+0x358/0x5f0)
[41117.820288] [<c01b8620>] (ext4_mb_init_cache+0x358/0x5f0) from [<c01b8db8>] (ext4_mb_load_buddy+0x278/0x2b4)
[41117.830085] [<c01b8db8>] (ext4_mb_load_buddy+0x278/0x2b4) from [<c01ba0fc>] (ext4_mb_find_by_goal+0x3c/0x23c)
[41117.840005] [<c01ba0fc>] (ext4_mb_find_by_goal+0x3c/0x23c) from [<c01ba9e0>] (ext4_mb_regular_allocator+0x4c/0x388)
[41117.850351] [<c01ba9e0>] (ext4_mb_regular_allocator+0x4c/0x388) from [<c01bc120>] (ext4_mb_new_blocks+0x1fc/0x5c0)
[41117.860728] [<c01bc120>] (ext4_mb_new_blocks+0x1fc/0x5c0) from [<c01b31d8>] (ext4_ext_map_blocks+0xfcc/0x15ac)
[41117.870739] [<c01b31d8>] (ext4_ext_map_blocks+0xfcc/0x15ac) from [<c018cf7c>] (ext4_map_blocks+0xf8/0x2e4)
[41117.880353] [<c018cf7c>] (ext4_map_blocks+0xf8/0x2e4) from [<c0190d4c>] (mpage_da_map_and_submit+0x114/0x57c)
[41117.890241] [<c0190d4c>] (mpage_da_map_and_submit+0x114/0x57c) from [<c0191908>] (ext4_da_writepages+0x340/0x5b8)
[41117.900496] [<c0191908>] (ext4_da_writepages+0x340/0x5b8) from [<c00ff3e0>] (do_writepages+0x24/0x38)
[41117.909713] [<c00ff3e0>] (do_writepages+0x24/0x38) from [<c00f6d14>] (__filemap_fdatawrite_range+0x60/0x6c)
[41117.919419] [<c00f6d14>] (__filemap_fdatawrite_range+0x60/0x6c) from [<c00f6de8>] (filemap_write_and_wait_range+0x34/0x68)
[41117.930436] [<c00f6de8>] (filemap_write_and_wait_range+0x34/0x68) from [<c0188ab0>] (ext4_sync_file+0xb4/0x414)
[41117.940447] [<c0188ab0>] (ext4_sync_file+0xb4/0x414) from [<c0158338>] (vfs_fsync_range+0x34/0x44)
[41117.949451] [<c0158338>] (vfs_fsync_range+0x34/0x44) from [<c0158368>] (vfs_fsync+0x20/0x28)
[41117.957874] [<c0158368>] (vfs_fsync+0x20/0x28) from [<c01586a0>] (sys_fdatasync+0x18/0x34)
[41117.966115] [<c01586a0>] (sys_fdatasync+0x18/0x34) from [<c000e000>] (ret_fast_syscall+0x0/0x30)
[41117.974874] CPU1: stopping
[41117.977529] [<c0013ee8>] (unwind_backtrace+0x0/0xe0) from [<c0012f6c>] (handle_IPI+0x100/0x1cc)
[41117.986258] [<c0012f6c>] (handle_IPI+0x100/0x1cc) from [<c0008670>] (gic_handle_irq+0xa8/0xb4)
[41117.994804] [<c0008670>] (gic_handle_irq+0xa8/0xb4) from [<c000ddbc>] (__irq_usr+0x3c/0x60)
[41118.003166] Exception stack(0xcb443fb0 to 0xcb443ff8)
[41118.008141] 3fa0: 75254dc0 752a4547 000001a4 00000564
[41118.016321] 3fc0: 00002000 00000010 00000612 75252000 bea932dc 75254f00 bea932ed 7522b6e8
[41118.024531] 3fe0: 40224e24 bea93268 40211be7 4021ab9c 80010030 ffffffff
[41118.131322] Rebooting in 5 seconds..
[41123.135045] Going down for restart now
[41123.138005] msm_restart : clear reset flag
Connected via ADB and ran e2fsck, but all appears ok.
Code:
e2fsck -pcfv /dev/block/mmcblk0p15
sh: badblocks: not found
/dev/block/mmcblk0p15: Updating bad block inode.
19845 inodes used (1.13%)
1139 non-contiguous files (5.7%)
19 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 19521/116/1
6040224 blocks used (86.35%)
0 bad blocks
1 large file
17771 regular files
1861 directories
0 character device files
0 block device files
5 fifos
0 links
191 symbolic links (185 fast symbolic links)
8 sockets
--------
19836 files
~ # ?[6ne2fsck -pcfv /dev/block/mmcblk0p17
e2fsck -pcfv /dev/block/mmcblk0p17
sh: badblocks: not found
/dev/block/mmcblk0p17: Updating bad block inode.
161 inodes used (0.30%)
19 non-contiguous files (11.8%)
0 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 153
34685 blocks used (16.13%)
0 bad blocks
0 large files
147 regular files
5 directories
0 character device files
0 block device files
0 fifos
0 links
0 symbolic links (0 fast symbolic links)
0 sockets
--------
152 files
1) Did the file system already correct the previous errors, which is why none are detected now?
2) Any other commands/tests that can be run to determine really what is/was wrong?
any other thoughts on why this issue would occur?
Got another crash last night, again copying a lot of new music onto the phone from computer. Crash call stack is different this time though.
Code:
[ 7523.190689] Buffer I/O error on device mmcblk0p15, logical block 6850041
[ 7523.197373] Buffer I/O error on device mmcblk0p15, logical block 6850042
[ 7523.204241] Buffer I/O error on device mmcblk0p15, logical block 6850043
[ 7523.210711] Buffer I/O error on device mmcblk0p15, logical block 6850044
[ 7523.217395] Buffer I/O error on device mmcblk0p15, logical block 6850045
[ 7523.224140] Buffer I/O error on device mmcblk0p15, logical block 6850046
[ 7523.230732] Buffer I/O error on device mmcblk0p15, logical block 6850047
[ 7523.237721] Aborting journal on device mmcblk0p15-8.
[ 7523.288385] kgsl kgsl-3d0: |kgsl_late_resume_driver| late resume start
[ 7523.633754] cypress_touchkey 16-0020: not real interrupt (1).
[ 7524.010986] EXT4-fs error (device mmcblk0p15): ext4_journal_start_sb:328: Detected aborted journal
[ 7524.018982] EXT4-fs (mmcblk0p15): Remounting filesystem read-only
[ 7524.061985] Kernel panic - not syncing: EXT4-fs panic from previous error
[ 7524.062016]
[ 7524.069340] [<c00138c8>] (unwind_backtrace+0x0/0xe0) from [<c07b5180>] (panic+0x88/0x1f8)
[ 7524.077459] [<c07b5180>] (panic+0x88/0x1f8) from [<c01a0714>] (__ext4_abort+0xc0/0xe0)
[ 7524.085394] [<c01a0714>] (__ext4_abort+0xc0/0xe0) from [<c01a0b34>] (ext4_journal_start_sb+0x154/0x1b8)
[ 7524.094794] [<c01a0b34>] (ext4_journal_start_sb+0x154/0x1b8) from [<c018b140>] (ext4_dirty_inode+0x14/0x40)
[ 7524.104530] [<c018b140>] (ext4_dirty_inode+0x14/0x40) from [<c014e37c>] (__mark_inode_dirty+0x2c/0x1c4)
[ 7524.113839] [<c014e37c>] (__mark_inode_dirty+0x2c/0x1c4) from [<c0141c9c>] (file_update_time+0x100/0x120)
[ 7524.123392] [<c0141c9c>] (file_update_time+0x100/0x120) from [<c00f15a4>] (__generic_file_aio_write+0x2cc/0x428)
[ 7524.133586] [<c00f15a4>] (__generic_file_aio_write+0x2cc/0x428) from [<c00f1760>] (generic_file_aio_write+0x60/0xc8)
[ 7524.144085] [<c00f1760>] (generic_file_aio_write+0x60/0xc8) from [<c01819e4>] (ext4_file_write+0x258/0x2bc)
[ 7524.153821] [<c01819e4>] (ext4_file_write+0x258/0x2bc) from [<c012b108>] (do_sync_write+0x9c/0xd8)
[ 7524.162763] [<c012b108>] (do_sync_write+0x9c/0xd8) from [<c012b1ec>] (vfs_write+0xa8/0x130)
[ 7524.171095] [<c012b1ec>] (vfs_write+0xa8/0x130) from [<c012b414>] (sys_pwrite64+0x50/0x80)
[ 7524.179275] [<c012b414>] (sys_pwrite64+0x50/0x80) from [<c000de80>] (ret_fast_syscall+0x0/0x30)
[ 7524.188004] CPU1: stopping
[ 7524.190659] [<c00138c8>] (unwind_backtrace+0x0/0xe0) from [<c001294c>] (handle_IPI+0x100/0x1cc)
[ 7524.199357] [<c001294c>] (handle_IPI+0x100/0x1cc) from [<c0008670>] (gic_handle_irq+0xa8/0xb4)
[ 7524.207964] [<c0008670>] (gic_handle_irq+0xa8/0xb4) from [<c000dc3c>] (__irq_usr+0x3c/0x60)
[ 7524.216296] Exception stack(0xc6637fb0 to 0xc6637ff8)
[ 7524.221271] 7fa0: b65f8b76 b6ed66d7 b65f8b77 00000037
[ 7524.229481] 7fc0: 00000000 b6ed66da b65faba4 b65f8b54 b65f8b74 b796f610 b6ed5398 00000000
[ 7524.237630] 7fe0: 50704001 b65f8b3c b6ecb283 b6ebf55c 60030030 ffffffff
[ 7524.344360] Rebooting in 5 seconds..
[ 7529.347686] Going down for restart now
[ 7529.350708] msm_restart : clear reset flag
Wrong forum or the content too technical for people?
BSOD2600 said:
Phone: Galaxy S3 VZW 32GB
Recovery: TWRP 2.7.1.0
Mod: CM11 m8
Kernel, governer, etc all CM11 stock.
Problem:
Twice today the phone rebooted itself while performing large file copy operations. last_kmsg from both reboots basically look the same:
Code:
[40996.107363] Buffer I/O error on device mmcblk0p15, logical block 6751031
[40996.114291] Buffer I/O error on device mmcblk0p15, logical block 6751032
[40996.120761] Buffer I/O error on device mmcblk0p15, logical block 6751033
[40996.127476] Buffer I/O error on device mmcblk0p15, logical block 6751034
[40996.134160] Buffer I/O error on device mmcblk0p15, logical block 6751035
[40996.140813] Buffer I/O error on device mmcblk0p15, logical block 6751036
[40996.147528] Buffer I/O error on device mmcblk0p15, logical block 6751037
[40996.154181] Buffer I/O error on device mmcblk0p15, logical block 6751038
[40996.160926] Buffer I/O error on device mmcblk0p15, logical block 6751039
[41056.701656] ACDB=> get_hw_delay: Path = 0 samplerate = 48000 usec = 0 status 0
[41056.708065] afe_callback: cmd = 0x100dc returned error = 0x3
[41056.713681] afe_send_hw_delay: config cmd failed
[41065.991721] kgsl kgsl-3d0: |kgsl_late_resume_driver| late resume start
[41066.310781] cypress_touchkey 16-0020: not real interrupt (1).
[41117.725034] EXT4-fs error (device mmcblk0p15): ext4_mb_generate_buddy:741: group 113, 644 clusters in bitmap, 530 in gd
[41117.744476] Aborting journal on device mmcblk0p15-8.
[41117.764161] Kernel panic - not syncing: EXT4-fs (device mmcblk0p15): panic forced after error
[41117.764161]
[41117.773257] [<c0013ee8>] (unwind_backtrace+0x0/0xe0) from [<c0778f40>] (panic+0x88/0x1f8)
[41117.781344] [<c0778f40>] (panic+0x88/0x1f8) from [<c01a7134>] (ext4_handle_error+0x8c/0x98)
[41117.789738] [<c01a7134>] (ext4_handle_error+0x8c/0x98) from [<c01a7ca0>] (__ext4_grp_locked_error+0xe8/0x1c4)
[41117.799626] [<c01a7ca0>] (__ext4_grp_locked_error+0xe8/0x1c4) from [<c01b6618>] (ext4_mb_generate_buddy+0x25c/0x2e8)
[41117.810125] [<c01b6618>] (ext4_mb_generate_buddy+0x25c/0x2e8) from [<c01b8620>] (ext4_mb_init_cache+0x358/0x5f0)
[41117.820288] [<c01b8620>] (ext4_mb_init_cache+0x358/0x5f0) from [<c01b8db8>] (ext4_mb_load_buddy+0x278/0x2b4)
[41117.830085] [<c01b8db8>] (ext4_mb_load_buddy+0x278/0x2b4) from [<c01ba0fc>] (ext4_mb_find_by_goal+0x3c/0x23c)
[41117.840005] [<c01ba0fc>] (ext4_mb_find_by_goal+0x3c/0x23c) from [<c01ba9e0>] (ext4_mb_regular_allocator+0x4c/0x388)
[41117.850351] [<c01ba9e0>] (ext4_mb_regular_allocator+0x4c/0x388) from [<c01bc120>] (ext4_mb_new_blocks+0x1fc/0x5c0)
[41117.860728] [<c01bc120>] (ext4_mb_new_blocks+0x1fc/0x5c0) from [<c01b31d8>] (ext4_ext_map_blocks+0xfcc/0x15ac)
[41117.870739] [<c01b31d8>] (ext4_ext_map_blocks+0xfcc/0x15ac) from [<c018cf7c>] (ext4_map_blocks+0xf8/0x2e4)
[41117.880353] [<c018cf7c>] (ext4_map_blocks+0xf8/0x2e4) from [<c0190d4c>] (mpage_da_map_and_submit+0x114/0x57c)
[41117.890241] [<c0190d4c>] (mpage_da_map_and_submit+0x114/0x57c) from [<c0191908>] (ext4_da_writepages+0x340/0x5b8)
[41117.900496] [<c0191908>] (ext4_da_writepages+0x340/0x5b8) from [<c00ff3e0>] (do_writepages+0x24/0x38)
[41117.909713] [<c00ff3e0>] (do_writepages+0x24/0x38) from [<c00f6d14>] (__filemap_fdatawrite_range+0x60/0x6c)
[41117.919419] [<c00f6d14>] (__filemap_fdatawrite_range+0x60/0x6c) from [<c00f6de8>] (filemap_write_and_wait_range+0x34/0x68)
[41117.930436] [<c00f6de8>] (filemap_write_and_wait_range+0x34/0x68) from [<c0188ab0>] (ext4_sync_file+0xb4/0x414)
[41117.940447] [<c0188ab0>] (ext4_sync_file+0xb4/0x414) from [<c0158338>] (vfs_fsync_range+0x34/0x44)
[41117.949451] [<c0158338>] (vfs_fsync_range+0x34/0x44) from [<c0158368>] (vfs_fsync+0x20/0x28)
[41117.957874] [<c0158368>] (vfs_fsync+0x20/0x28) from [<c01586a0>] (sys_fdatasync+0x18/0x34)
[41117.966115] [<c01586a0>] (sys_fdatasync+0x18/0x34) from [<c000e000>] (ret_fast_syscall+0x0/0x30)
[41117.974874] CPU1: stopping
[41117.977529] [<c0013ee8>] (unwind_backtrace+0x0/0xe0) from [<c0012f6c>] (handle_IPI+0x100/0x1cc)
[41117.986258] [<c0012f6c>] (handle_IPI+0x100/0x1cc) from [<c0008670>] (gic_handle_irq+0xa8/0xb4)
[41117.994804] [<c0008670>] (gic_handle_irq+0xa8/0xb4) from [<c000ddbc>] (__irq_usr+0x3c/0x60)
[41118.003166] Exception stack(0xcb443fb0 to 0xcb443ff8)
[41118.008141] 3fa0: 75254dc0 752a4547 000001a4 00000564
[41118.016321] 3fc0: 00002000 00000010 00000612 75252000 bea932dc 75254f00 bea932ed 7522b6e8
[41118.024531] 3fe0: 40224e24 bea93268 40211be7 4021ab9c 80010030 ffffffff
[41118.131322] Rebooting in 5 seconds..
[41123.135045] Going down for restart now
[41123.138005] msm_restart : clear reset flag
Connected via ADB and ran e2fsck, but all appears ok.
Code:
e2fsck -pcfv /dev/block/mmcblk0p15
sh: badblocks: not found
/dev/block/mmcblk0p15: Updating bad block inode.
19845 inodes used (1.13%)
1139 non-contiguous files (5.7%)
19 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 19521/116/1
6040224 blocks used (86.35%)
0 bad blocks
1 large file
17771 regular files
1861 directories
0 character device files
0 block device files
5 fifos
0 links
191 symbolic links (185 fast symbolic links)
8 sockets
--------
19836 files
~ # ?[6ne2fsck -pcfv /dev/block/mmcblk0p17
e2fsck -pcfv /dev/block/mmcblk0p17
sh: badblocks: not found
/dev/block/mmcblk0p17: Updating bad block inode.
161 inodes used (0.30%)
19 non-contiguous files (11.8%)
0 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 153
34685 blocks used (16.13%)
0 bad blocks
0 large files
147 regular files
5 directories
0 character device files
0 block device files
0 fifos
0 links
0 symbolic links (0 fast symbolic links)
0 sockets
--------
152 files
1) Did the file system already correct the previous errors, which is why none are detected now?
2) Any other commands/tests that can be run to determine really what is/was wrong?
Click to expand...
Click to collapse
Did you ever figure this out?
Was it transferring from SD to External SD? Or just to Internal?
Sent from my SCH-I535 using XDA Free mobile app
Nope, never figured this out and yes it's occurred more than once.
Seem to recall was transferring large file content from PC to Internal. Don't think it's happened with CM11m10 -- yet... but on the other hand I dont do large file transfers daily.
Still an issue with CM11m11 (or more likely the hardware). system reboot when deleting a ~300 MB file from within MX Player.
Code:
[52140.774902] Buffer I/O error on device mmcblk0p15, logical block 4134812
[52140.781556] end_request: I/O error, dev mmcblk0, sector 43663360
[52140.787874] Buffer I/O error on device mmcblk0p15, logical block 5046272
[52140.794405] end_request: I/O error, dev mmcblk0, sector 44711936
[52140.800387] Buffer I/O error on device mmcblk0p15, logical block 5177344
[52140.807254] Buffer I/O error on device mmcblk0p15, logical block 5242880
[52140.813846] Buffer I/O error on device mmcblk0p15, logical block 5275648
[57664.812106] EXT4-fs error (device mmcblk0p15): ext4_mb_generate_buddy:741: group 158, 2379 clusters in bitmap, 1936 in gd
[57664.822300] Aborting journal on device mmcblk0p15-8.
[57664.833928] Kernel panic - not syncing: EXT4-fs (device mmcblk0p15): panic forced after error
[57664.833928]
[57664.842962] [<c0013928>] (unwind_backtrace+0x0/0xe0) from [<c07abc78>] (panic+0x88/0x1f8)
[57664.851172] [<c07abc78>] (panic+0x88/0x1f8) from [<c01a257c>] (ext4_handle_error+0x8c/0x98)
[57664.859504] [<c01a257c>] (ext4_handle_error+0x8c/0x98) from [<c01a30e8>] (__ext4_grp_locked_error+0xe8/0x1c4)
[57664.869393] [<c01a30e8>] (__ext4_grp_locked_error+0xe8/0x1c4) from [<c01b1a60>] (ext4_mb_generate_buddy+0x25c/0x2e8)
[57664.879892] [<c01b1a60>] (ext4_mb_generate_buddy+0x25c/0x2e8) from [<c01b3a68>] (ext4_mb_init_cache+0x358/0x5f0)
[57664.890055] [<c01b3a68>] (ext4_mb_init_cache+0x358/0x5f0) from [<c01b4200>] (ext4_mb_load_buddy+0x278/0x2b4)
[57664.899852] [<c01b4200>] (ext4_mb_load_buddy+0x278/0x2b4) from [<c01b7ea4>] (ext4_free_blocks+0x578/0x9f0)
[57664.909436] [<c01b7ea4>] (ext4_free_blocks+0x578/0x9f0) from [<c01ac74c>] (ext4_ext_remove_space+0x6ec/0xe94)
[57664.919385] [<c01ac74c>] (ext4_ext_remove_space+0x6ec/0xe94) from [<c01aed00>] (ext4_ext_truncate+0x100/0x1d0)
[57664.929365] [<c01aed00>] (ext4_ext_truncate+0x100/0x1d0) from [<c0188a24>] (ext4_truncate+0xb4/0x174)
[57664.938582] [<c0188a24>] (ext4_truncate+0xb4/0x174) from [<c018d2c0>] (ext4_evict_inode+0x328/0x490)
[57664.947678] [<c018d2c0>] (ext4_evict_inode+0x328/0x490) from [<c0142c84>] (evict+0x94/0x158)
[57664.956101] [<c0142c84>] (evict+0x94/0x158) from [<c0139f50>] (do_unlinkat+0xe8/0x130)
[57664.963975] [<c0139f50>] (do_unlinkat+0xe8/0x130) from [<c000dec0>] (ret_fast_syscall+0x0/0x30)
[57665.072964] Rebooting in 5 seconds..
[57670.076779] Going down for restart now
[57670.079800] msm_restart : clear reset flag
Official TWRP for Huawei P8 Lite 2017
Working
Code:
[CENTER]* Touchscreen
* Adb
* Backup
* Wipe
* File manager
* MTP
[/CENTER]
Not Working
Code:
[CENTER]You tell me
[/CENTER]
Installation
Code:
[CENTER]* put you phone in fastboot mode and type
"fastboot flash recovery_ramdisk <grab_here_the_img>"
* reboot
[/CENTER]
Download
TWRP official page
Android 11 Unofficial TWRP
DarkJoker360 Sourceforge
Please support my work, it's very important! Thanks
DONATIONS
Regards !
Reserved
Using it on Honor 6X, working fine.
One issue, it doesn't recognise the device while flashing stock rom using hurupdater.
Adoptable storage is not working, show sdcard but empty. (I wouldn't recommend putting something to SD card because it will on 99% overwrite existing stuff).
I am doing with my p8 lite and the result is all the time same error: partition lenght
i have tried fastboot flash recovery file.img and fastboot flash recovery_ramdisk file.img this last says ok, but then when i reboot appear all the same
Is there any solution ????
Thanks.
New TWRP Update !
* Fixed Adb
* Re-enabled OTG Usb wipes
Also I submitted for Official mantainership.
NOTE: P10 Lite won't receive supports since I broke it, just use P8 Lite 2017 stuff.
Hello from now the recovery is official !
Grab latest builds from official website and enjoy
DarkJoker360 said:
Hello from now the recovery is official !
Grab latest builds from official website and enjoy
Click to expand...
Click to collapse
Nice job dude! Keep rocking
(Anyway this twrp won't recongnize my adoptable storage so....)
DunoCZ said:
Nice job dude! Keep rocking
(Anyway this twrp won't recongnize my adoptable storage so....)
Click to expand...
Click to collapse
DMESG output
Code:
[ 395.228881s][pid:249,cpu0,mmcqd/1]mmcqd/1 rw time:7228125 ms,write time:0 ms,read time:7228125 ms
[ 395.228912s][pid:249,cpu0,mmcqd/1]mmcqd/1 workload < 1%, duty 7228125, period 335947444373, req_cnt=4
[ 395.228912s][pid:249,cpu0,mmcqd/1]mmcqd/1 Read Throughput=21650 kB/s, size: 151552 bytes, time:7 ms
[ 395.243530s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): bogus number of reserved sectors
[ 395.243530s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): Can't find a valid FAT filesystem
[ 395.244201s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): bogus number of reserved sectors
[ 395.244201s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): Can't find a valid FAT filesystem
[ 395.244384s][pid:325,cpu7,recovery]hisi_vibrator_enable,value=80
[ 395.324401s][pid:325,cpu7,in irq]hisi_vibrator_timer_func called
[ 395.703674s][pid:325,cpu5,recovery]FAT-fs (mmcblk1p1): bogus number of reserved sectors
[ 395.703674s][pid:325,cpu5,recovery]FAT-fs (mmcblk1p1): Can't find a valid FAT filesystem
[ 395.704345s][pid:325,cpu5,recovery]FAT-fs (mmcblk1p1): bogus number of reserved sectors
[ 395.704345s][pid:325,cpu5,recovery]FAT-fs (mmcblk1p1): Can't find a valid FAT filesystem
[ 395.704528s][pid:325,cpu5,recovery]hisi_vibrator_enable,value=80
[ 395.784545s][2020:08:10 14:22:16][pid:0,cpu5,in irq]hisi_vibrator_timer_func called
[ 395.925598s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): bogus number of reserved sectors
[ 395.925628s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): Can't find a valid FAT filesystem
[ 395.926300s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): bogus number of reserved sectors
[ 395.926300s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): Can't find a valid FAT filesystem
[ 395.926483s][pid:325,cpu7,recovery]hisi_vibrator_enable,value=80
[ 396.006622s][pid:325,cpu7,in irq]hisi_vibrator_timer_func called
[ 396.088073s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): bogus number of reserved sectors
[ 396.088104s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): Can't find a valid FAT filesystem
[ 396.088745s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): bogus number of reserved sectors
[ 396.088745s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): Can't find a valid FAT filesystem
[ 396.088928s][pid:325,cpu7,recovery]hisi_vibrator_enable,value=80
Mount output when it's working
Code:
/dev/block/dm-0 on /external_sd type f2fs (rw,seclabel,noatime,background_gc=on,user_xattr,inline_xattr,acl,inline_data,inline_dentry,extent_cache,mode=adaptive,verify_encrypt,active_logs=6)
/dev/block/dm-0 on /sdcard type f2fs (rw,seclabel,noatime,background_gc=on,user_xattr,inline_xattr,acl,inline_data,inline_dentry,extent_cache,mode=adaptive,verify_encrypt,active_logs=6)
DunoCZ said:
DMESG output
Code:
[ 395.228881s][pid:249,cpu0,mmcqd/1]mmcqd/1 rw time:7228125 ms,write time:0 ms,read time:7228125 ms
[ 395.228912s][pid:249,cpu0,mmcqd/1]mmcqd/1 workload < 1%, duty 7228125, period 335947444373, req_cnt=4
[ 395.228912s][pid:249,cpu0,mmcqd/1]mmcqd/1 Read Throughput=21650 kB/s, size: 151552 bytes, time:7 ms
[ 395.243530s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): bogus number of reserved sectors
[ 395.243530s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): Can't find a valid FAT filesystem
[ 395.244201s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): bogus number of reserved sectors
[ 395.244201s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): Can't find a valid FAT filesystem
[ 395.244384s][pid:325,cpu7,recovery]hisi_vibrator_enable,value=80
[ 395.324401s][pid:325,cpu7,in irq]hisi_vibrator_timer_func called
[ 395.703674s][pid:325,cpu5,recovery]FAT-fs (mmcblk1p1): bogus number of reserved sectors
[ 395.703674s][pid:325,cpu5,recovery]FAT-fs (mmcblk1p1): Can't find a valid FAT filesystem
[ 395.704345s][pid:325,cpu5,recovery]FAT-fs (mmcblk1p1): bogus number of reserved sectors
[ 395.704345s][pid:325,cpu5,recovery]FAT-fs (mmcblk1p1): Can't find a valid FAT filesystem
[ 395.704528s][pid:325,cpu5,recovery]hisi_vibrator_enable,value=80
[ 395.784545s][2020:08:10 14:22:16][pid:0,cpu5,in irq]hisi_vibrator_timer_func called
[ 395.925598s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): bogus number of reserved sectors
[ 395.925628s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): Can't find a valid FAT filesystem
[ 395.926300s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): bogus number of reserved sectors
[ 395.926300s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): Can't find a valid FAT filesystem
[ 395.926483s][pid:325,cpu7,recovery]hisi_vibrator_enable,value=80
[ 396.006622s][pid:325,cpu7,in irq]hisi_vibrator_timer_func called
[ 396.088073s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): bogus number of reserved sectors
[ 396.088104s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): Can't find a valid FAT filesystem
[ 396.088745s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): bogus number of reserved sectors
[ 396.088745s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): Can't find a valid FAT filesystem
[ 396.088928s][pid:325,cpu7,recovery]hisi_vibrator_enable,value=80
Mount output when it's working
Code:
/dev/block/dm-0 on /external_sd type f2fs (rw,seclabel,noatime,background_gc=on,user_xattr,inline_xattr,acl,inline_data,inline_dentry,extent_cache,mode=adaptive,verify_encrypt,active_logs=6)
/dev/block/dm-0 on /sdcard type f2fs (rw,seclabel,noatime,background_gc=on,user_xattr,inline_xattr,acl,inline_data,inline_dentry,extent_cache,mode=adaptive,verify_encrypt,active_logs=6)
Click to expand...
Click to collapse
ofc, wrong file system, should be VFAT not F2FS
haky 86 said:
ofc, wrong file system, should be VFAT not F2FS
Click to expand...
Click to collapse
F2FS it's because Adoptable storage, for example discontinued SHRP can mount it and read it without any problem.
Anyone can help me unlock the bootloader first, i dont have the unlock code from huawei because they closed it.
DunoCZ said:
F2FS it's because Adoptable storage, for example discontinued SHRP can mount it and read it without any problem.
Click to expand...
Click to collapse
well I see this : FAT-fs (mmcblk1p1): Can't find a valid FAT filesystem
it's mean wrong file system lol
haky 86 said:
well I see this : FAT-fs (mmcblk1p1): Can't find a valid FAT filesystem
it's mean wrong file system lol
Click to expand...
Click to collapse
You never used adopted storage right?
Here is output of fdisk.
Code:
:/ $ su
:/ # fdisk -l /dev/block/mmcblk1
Found valid GPT with protective MBR; using GPT
Disk /dev/block/mmcblk1: 60456960 sectors, 848M
Logical sector size: 512
Disk identifier (GUID): d8cd974c-9971-4801-aa06-39559b5fa3c1Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 60456926
Number Start (sector) End (sector) Size Name
1 2048 34815 16.0M android_meta
2 34816 60456926 28.8G android_expand
:/ #
And even shrp have in fstab vfat for /external_sd, so it's not sdcard related problem, it's TWRP's partition support problem. And also SHRP mounts /dev/block/dm-0 not /dev/block/mmcblk1p1.
DunoCZ said:
You never used adopted storage right?
Here is output of fdisk.
Code:
:/ $ su
:/ # fdisk -l /dev/block/mmcblk1
Found valid GPT with protective MBR; using GPT
Disk /dev/block/mmcblk1: 60456960 sectors, 848M
Logical sector size: 512
Disk identifier (GUID): d8cd974c-9971-4801-aa06-39559b5fa3c1Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 60456926
Number Start (sector) End (sector) Size Name
1 2048 34815 16.0M android_meta
2 34816 60456926 28.8G android_expand
:/ #
And even shrp have in fstab vfat for /external_sd, so it's not sdcard related problem, it's TWRP's partition support problem...
Click to expand...
Click to collapse
exactly it has been disabled even on official berkeley twrp.
haky 86 said:
exactly it has been disabled even on official berkeley twrp.
Click to expand...
Click to collapse
Still doesn't mean it's useless on 16GB device....
DunoCZ said:
Still doesn't mean it's useless on 16GB device....
Click to expand...
Click to collapse
I never use twrp for such of things only for testing roms/gapps, knowing that it's broken at least. but meh it's good to see something official for such platform
haky 86 said:
I never use twrp for such of things only for testing roms/gapps, knowing that it's broken at least. but meh it's good to see something official for such platform
Click to expand...
Click to collapse
Yep that's true, hope someone will brought adoptable back to 3.4.0-0.
papoy1019 said:
Anyone can help me unlock the bootloader first, i dont have the unlock code from huawei because they closed it.
Click to expand...
Click to collapse
Use DC unlocker, you can buy credits via Google Pay... First Downgrade to Android 7 ... Then unlock bootloader
I got a FAILED remote: partition lenght get error, when flashing
Do you know why?
I've made this mistake before, and it drives me nuts. I changed phones and put my old phones sd card in my new phone (Nokia 8.3). I was just going to see if it could read it. It couldn't and asked me if I wanted to format. I selected no, and removed the card. I put the card in my linux computer and I can't mount it. I did get a replacement for my old phone through warranty (teracube) and tried putting it in that, and it wouldn't read it either. I've had this problem before. I think even having the sdcard in a phone does something to it even if you don't format it. I think I formatted the card initially as ext2 but I could be mistaken.
Any help would be appreciated. I really want to recover the data.
mount:
Code:
[3630 21-01-23 7:06][email protected]/home/larry%sudo mount /dev/sda2 /mnt/tmp
NTFS signature is missing.
Failed to mount '/dev/sda2': Invalid argument
The device '/dev/sda2' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
[3630 21-01-23 7:06][email protected]/home/larry%sudo mount -tvfat /dev/sda2 /mnt/tmp
mount: /mnt/tmp: wrong fs type, bad option, bad superblock on /dev/sda2, missing codepage or helper program, or other error.
fdisk:
Code:
[3630 21-01-23 7:06][email protected]/home/larry%sudo fdisk /dev/sda
Command (m for help): p
Disk /dev/sda: 119.1 GiB, 127865454592 bytes, 249737216 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C8FBA780-1A1F-4B71-8D9D-D623A671C61D
Device Start End Sectors Size Type
/dev/sda1 2048 34815 32768 16M unknown
/dev/sda2 34816 249737182 249702367 119.1G unknown
An SD-card ( from Android's point of view it's a portable USB-device ) usually is FAT32 formatted, AFAIK, but I may err as always ...