16 Gb of memory instead of 32

[jufofu]

I've updated to .253 with all the wipes last week and today I discovered I only have 16 Gb of internal memory now.
Has anybody encountered the same issue? What can cause such a problem? And how can I solve it?

 

[MattyCurrann]

I've been getting this issue but some reason, I'm not limited to 16, I'm limited to 22? I'm not sure.

 

[Monipeev]

Is the same information as the picture, if you check memory with a file explorer(Es file explorer for example)? On a computer what is the situation with memory?

 

[jufofu]

Is the same information as the picture, if you check memory with a file explorer(Es file explorer for example)? On a computer what is the situation with memory?

I noticed it on a computer initially. It showed 16 Gb instead of 32 Gb.

Now it shows something even worse! Total irrelevance.

 

[Monipeev]

It is absolutely illogical. In file explorer? What about if restart your phone? Any differents?

 

[jufofu]

No difference, reloading doesn't change anything.
I'm so puzzled.

 

[Poag]

Also getting this issue @ 16GB internal storage.
FWIW i'm using the XPower 3 debloat with the .253 kernal.

 

[Monipeev]

@jufofu, What will show if despite the small remaining space, continue to copy more information in the internal memory? Whether it will continue to collect more data in memory, which means just bad reporting of information on available memory ? Maybe factory reset or repair with Xperia Companion. If problem still there, then the option is service. If you decide to do this, copy your information from phone to computer before this steps.

 

[jufofu]

@Poag, was the problem there on the previous firmware? Do you have any ideas about its origins?
@Monipeev, it doesn't copy files from PC when the small memory is filled.
I will try to flash it again this week. If it doesn't work properly I'll have to restore TA backup and go the the service.

 

[Poag]

To be honest, i can't remember. I just flashed .224 from Flashtool wiping everything and TWRP reports only 8GB for internal.....booting into system atm....

Would someone with a 32GB internal mind posting a df?

[edit] Ok thats given me back my 32GB internal storage, currently sat on a freshly imaged device with 10GB of 32Gb used internal.

 

[MattyCurrann]

To be honest, i can't remember. I just flashed .224 from Flashtool wiping everything and TWRP reports only 8GB for internal.....booting into system atm....

Would someone with a 32GB internal mind posting a df?

[edit] Ok thats given me back my 32GB internal storage, currently sat on a freshly imaged device with 10GB of 32Gb used internal.

How did you go about fixing this?

I have the same problem.

 

[jufofu]

So this is supposedly a bug in .253? I'm glad that it can be solved by reflashing.
@MattyCurrann, you too got this problem after flashing .253?

 

[Poag]

So i

1- Downloaded the UK Customised 224 in Flashtool - XperiFirm
2- Flash this wiping everything in the 'Wipe' box.
3- Booted into Fastboot and flashed the .253+TWRP kernal listed in the XPower thread post #312
4- Booted in system and then set about resetting up the device from TitaniumBackups.

---------- Post added at 10:30 AM ---------- Previous post was at 10:23 AM ----------

How did you go about fixing this?

I have the same problem.

I dont think you have the problem. 22GB is were you are meant to be.

10GB is system 22GB is user space.

 

[zacharias.maladroit]

So this is supposedly a bug in .253? I'm glad that it can be solved by reflashing.
@MattyCurrann, you too got this problem after flashing .253?

nope, NOT a bug in .253,

afaik it's been there on Lollipop as well,

existed on Lollipop firmwares, 185, 224, 253 MM firmwares

(I got it too on Z5).

It sometimes occured during flashing Firmwares via XperiFirm + Flashtool or flashing new ones via TWRP,

really weird "bug"

 

[michuroztocz]

There is another thread regarding this bug:
http://forum.xda-developers.com/z5-compact/help/how-storage-t3398804/post67849319#post67849319

You can fix it without flashing anything - if you have TWRP recovery, just Repair /data partition in Wipe menu. If that doesn't help, try Repairing /system partition (that helped in my case).

 

[jufofu]

Another cases of the same issue: http://forum.xda-developers.com/xpe...-repack-stock-kernel-dm-t3301605/post67317647

Edit: posted it without refreshing the page, basically the previous post covers it all.

 

[yamin8000]

flashtools sucks nowadays!

 

[jufofu]

Repairing didn't help, but resizing /data works perfectly. I've got my memory back.

 

[SysGhost]

Repairing didn't help, but resizing /data works perfectly. I've got my memory back.

A little "how to" would be nice.

EDIT:
As TWRP kept giving me Errror 4. I did figure out what it meant by that.
It needs manual handling (answering questions) in cli.

I went on with "adb shell" on my computer while the device was started up in TWRP/recovery mode.
There I unmounted everything, and then I ran this command from adb shell:

e2fsck -f /dev/block/mmcblk0p42

There I had to answer a bunch of questions about orphaned inodes and other corruptions. (Tookl a while to answer them all. I could have used "-y").
Once done, the fs was marked as clean, and the rezise command in TWRP worked flawlessly. Problem solved.

Strange that it had so many corruptions/orphaned inodes, considering it was a new fresh flash made just recently with flashtool.

 

[YasuHamed]

how did you update your phone?