Database Develop

Can't mount /system in twrp 2.8.3.0

I updated my twrp from 2.7.1 to 2.8.3.0. I haven't flashed a rom in a while, so I don't know for sure that it was working on the old one but I did install CM11 using 2.7.1. Now with 2.8.3 when I go into recovery and wipe is says it worked, but in red there is the error: "E: unable to mount /system".
I tried to repair it with twrp, using format /system as ext4, then wipe and it seems to work and mount correctly, but if I restart, into recovery the /system no longer mounts and gives the same error if I try to wipe it. When I select repair, it says the partition is 0mb. When I format as ext4 it then shows as the correct size (~1.8GB).
So bottom line is that when I try to flash a new rom, it gets stuck at the formating /system step. I think the problem is with twrp but I'm not sure. Any ideas what to do?
I have a T-mobile HTC one M7. It was CM11, but everything is wiped. TWRP 2.8.3. S-off unlocked bootloader.
Thanks!

modman21 said:
I updated my twrp from 2.7.1 to 2.8.3.0. I haven't flashed a rom in a while, so I don't know for sure that it was working on the old one but I did install CM11 using 2.7.1. Now with 2.8.3 when I go into recovery and wipe is says it worked, but in red there is the error: "E: unable to mount /system".
I tried to repair it with twrp, using format /system as ext4, then wipe and it seems to work and mount correctly, but if I restart, into recovery the /system no longer mounts and gives the same error if I try to wipe it. When I select repair, it says the partition is 0mb. When I format as ext4 it then shows as the correct size (~1.8GB).
So bottom line is that when I try to flash a new rom, it gets stuck at the formating /system step. I think the problem is with twrp but I'm not sure. Any ideas what to do?
I have a T-mobile HTC one M7. It was CM11, but everything is wiped. TWRP 2.8.3. S-off unlocked bootloader.
Thanks!
Click to expand...
Click to collapse
first of all the most reliable version of TWRP recovery is stil 2.6.3.3 or 2.6.3.4, most of the users on here would agree with me on that, newer is not always better.
Also, have you tried the format data option, select wipe then format data button, be warned though, this will wipe everything including your sdcard (internal) if this option works you will then have to sideload or push a rom to your device before you can flash.

Seanie280672 said:
first of all the most reliable version of TWRP recovery is stil 2.6.3.3 or 2.6.3.4, most of the users on here would agree with me on that
Click to expand...
Click to collapse
Agree 100% but CM11 require at least 2.7.0.8 to be flashed (block:by-name) and recommended version of twrp to flash CM11 is 2.7.1.2 http://wiki.cyanogenmod.org/w/Install_CM_for_m7
If not flashing a rom like CM11 still recommend using 2.6.3.3/.4 even if there are newer version.

They are talking about this in ARHD thread.
Seems a updater script problem.
Read here and below!
http://forum.xda-developers.com/showpost.php?p=57985309&postcount=84878
My 2 cents

Fain11 said:
They are talking about this in ARHD thread.
Seems a updater script problem.
Read here and below!
http://forum.xda-developers.com/showpost.php?p=57985309&postcount=84878
My 2 cents
Click to expand...
Click to collapse
Thanks for the link. I tried to find similar threads, but couldn't. They are having the same problem but with a different rom (I was trying to flash Sky Dragon android L). The solution on that thread was to use TWRP 2.6.3.3, but some people reported having no problems with 2.8.3. The install instructions for Sky Dragon say use the latest twrp but doesn't specify a version. I guess I could try TWRP 2.6.3.3 but I'm not sure if it will work since CM requires 2.7.1.
The other solution was to mount the partition manually before flashing using the terminal in recovery. This command was suggested:
Code:
run_program("/sbin/umount", "/system");
Haven't tried any of these solution myself. After 3 hours and wiping my entire data partition by accident, I USB-OTG copied my nandroid backup to my phone and did a complete recovery. Luckily the restore process didn't care about mounting /system. I may try this again with manual mounting, but likely I will wait for a twrp update. I'm not sure if twrp 2.6 supports usb-otg so it will be a pain in the ass if I wipe /data again by accident.
Random side note for anyone googling this, if you accidently wipe all the data from your sdcard and have to copy the nandroid backup for twrp, the the restore function won't recognize the files unless they are in exactly the right directory. The best way to get this is to copy the entire TWRP directory when saving your backup in the first place so you can just copy it back. If you didn't do that then just run a nandroid backup of the blank sdcard and it will recreate the folder structure for you. Then you copy the files into the correct folder.

alray said:
Agree 100% but CM11 require at least 2.7.0.8 to be flashed (block:by-name) and recommended version of twrp to flash CM11 is 2.7.1.2 http://wiki.cyanogenmod.org/w/Install_CM_for_m7
If not flashing a rom like CM11 still recommend using 2.6.3.3/.4 even if there are newer version.
Click to expand...
Click to collapse
Exactly this. I do not know the exact reason CM needs 2.7.1 so therefore I don't know if Sky Dragon needs it as well. The instructions just say use the latest twrp.
http://forum.xda-developers.com/showthread.php?t=2400161

Seanie280672 said:
first of all the most reliable version of TWRP recovery is stil 2.6.3.3 or 2.6.3.4, most of the users on here would agree with me on that, newer is not always better.
Also, have you tried the format data option, select wipe then format data button, be warned though, this will wipe everything including your sdcard (internal) if this option works you will then have to sideload or push a rom to your device before you can flash.
Click to expand...
Click to collapse
I did wipe my entire data partition (by accident), but I did not try to format it as ext4. I did format /system to ext4 (so now the partition was displaying correctly as ~1.8gb). The used the twrp repair, then wipe It seemed to work, but if I restarted right then, without even trying to flash the rom, the /system would not mount on reboot to recovery and would show as 0mb. I used all reasonable combinations and permutations of the wipe, repair and format functions on system, nothing worked.
I finally copied my nandroid backup via usb-otg and recovered back to cm11.

[Q] TWRP Backup failed - SD issues?

So I've searched quite a bit on this one and can't really seem to figure out what is going on.
I started on TWRP 2.7.1.0 and when backing up with adequate storage space I kept getting "backup failed". I tried 2.8.0.0, same thing, and finally 2.8.4.0 failed as well. I cleared a bunch of stuff off of it and was able to backup once. Two days later when I was going to try out a new rom, I decided to make a new backup and right back to where I am now - fails every time. I have 10gb free and the backup is less than 5gb. I was getting impatient wanting to update my rom, and figured since I already had one backup I may as well try to install a new rom - I tried to wipe data/cache/dalvik, and even that failed.
I attached two logs I saved from different backups. I've tried fix_permissions and nothing. I'm assuming this may be a error with the internal storage, perhaps my next step would be to format that partition (Is this just "format data" in TWRP wipe section?)
Thanks for the help!

E:Unable to stat - Internal storage corrupt - can't wipe or restore in TWRP

E:Unable to stat. Followed by file names when updating partition details.
Following a recent flash I started to notice I have files which are throwing an error and its meaning I can't cleanly wipe or restore meaning the phone in a bad way. Typical error at start of thread title.
Anyone any extra ideas? I'm ready to face losing /data/media if I can somehow get this to function.
I'm using a moto X 2014 on TWRP 2.8.7 but I think the issue is device agnostic. I am seeking out the stock images now. Presume if I flash complete stock images I can overwrite the corrupt partitions?
I can get it to flash an OS with a bit of media process crashing at first. If I can get back to a clean state I'm confident I have a nandroid ready to go (fingers crossed uncorrupted).
Thanks for any guidance!

I have the exact same problem, when I reflashed TWRP it seemed to fix it until I restored my data partition from a nandroid backup where the issue came back.

Twrp restore error

I am using TWRP 3.0.2-7 which was working fine until yesterday i got this "extracttarfork() error:255" while restoring a backup. I have restored that backup many times before too and didnt tamper with it in any way.
Now i have 5 huge backups on my sd card, none of which can be restored properly, i am saying properly because that error only shows up when the data partition almost finishes restoring. I can restore system and boot without any problem(basically any partition other than data)
According to the information i gathered from net, this error should occur when i am running low on storage which isnt the case. So totally confused
The log is in the zip
Any help will be appreciated, thanks

"extractTarFork() process ended with ERROR: 255" is occured on TWRP

I made backup of "/data" partiton of MIUI 11 xiaomi.eu rom.
and I tried to restore the backup after doing something, I got the error "extractTarFork() process ended with ERROR: 255"
I've tried more than dozens of times to restore the backup file from more than 3 kinds of recovery but the result was same.
I've got only 2 times of successful results of restore, but I don't know why the restore was success.
I've googled as much as I can to find the solution of this problem but I was not able to find any solution that works for me.
(I've tried formatting '/data' partition, mount-unmount, install the same version rom....)
Please let me know the solution.

hey did you solve it? i didn't know TWRP won't allow me restore my backup... (

Hi, i'm having the exact same issue. Maybe an issue with TWRP? I've heard it can also be an error that shows up when there is not enough available storage, but I had at least 32gb free.

same problem when trying to create a backup. Still worked a few days ago....
update: restored an old backup and now i am able to perform backups again. Still not sure what coused it though