unable to mount /data
No idea what happened.
Woke up today.. phone seemed off .. tried to charge and reboot and could not.
Got into recovery, and tried to wipe caches etc.. could not..
This is the message I get in logs from TWRP.
I read in another forum about going into the console and typing a manual command to reformat the partition.
I have no idea if that command would be the same here..
ANYONE??? please?
You didn't post the command, but just from common knowledge I'd say the Linux command would be the same, but the partition you need to format might be/probably is named differently on this phone.
Incidentally, there is always the possibility of partial or full emmc failure. Your description of the symptoms sound consistent with hardware failure, so I wouldn't rule out that possibility.
I just had the same thing happen. Can't find the command to manually reformat as well. My external SD card was wiped as well, apparently. Or it won't read it. TWRP also says internal storage is 0 mb.
Related
I have an Incredible, rooted (and I have issues)... I appear to have repartitioned my internal memory area. Thankfully, the phone is useable, but it's not quite right as some programs don't work properly, the video recorder hangs hard, and I have either corrupt data or areas stomped on by other areas due to incorrect partition information. If certain files get touched, then the phone immediately protects itself by flagging the internal memory as read only. I did find a workaround to the phone automatically going into ReadOnly at boot by simply adding a ".nomedia" file in the root of MP3 (where some corrupt files happen to reside). As long as the system doesn't touch the files, the file system remains R/W.
I stupidly did this to myeself. I did it while using a Partitioning tool (specifically Acronis, making a "secure zone") on my PC while my incredible was charging in the USB port and I accidentally used the wrong drive. It was one of those "oh crap" moments. If I connect the phone to my PC, the internal drive comes up as being unformatted and windows asks if I want to format. Another disk utility (EASEUS) sees the drive, can show how its partitioned, and I can explore within the partitions to see that files exist.
I've been searching for a long while to find someone somewhere who might have info on how to fix the Internal SD partition information, but have yet to find anything. Reflashing the factory ROM, "factory reset", etc. appear to just repopulate the already partitioned areas. The closest thing I have found to my problem is a post called "Challenge to members... Help me fix internal partitions without recovery" on the Incredibleforums elsewhere (can't post external links yet). Unfortunately, trying those solutions doesn't fix the issue. That post deals with /dev/mount/mmcblk0p1 and /dev/mount/mmcblk0p2. My issue appears to be in /dev/mount/mmcblk0p3. Parted doesn't like that one much. I have attached a couple of files that show parted output for all of the drives that get mounted, per /etc/fstab & /etc/recovery.fstab. This was done in ADB while the phone was booted into recovery.
If anyone can point me in the right direction how to properly (and safely) repartition the *internal* areas back to how they should be, I'd really appreciate the help!
Thanks,
Blue
I ran across this:
http://talk.maemo.org/showthread.php?t=15746
.... hope it helps send you in the right direction anyway. Good luck!
Formating instructions i think it would be a better idea to try using the ruu.exe tool to reflash your phone and it should format that partition back and put all the old apps it came with back in proper order. Since the phone is use able right now you could also try a factory reset first if you don't want to try the ruu.exe.
Thanks for the link and tip for RUU.
sfdisk does not appear to be a useable command on my DInc. Is there an Android version/port? Also, that link suggests that the partition should be msdos, but isn't the boot sector type supposed to be ext2/3 or yaffs2 (?) on the DInc?
I have already tried the factory reset as well as reformatting the phone areas using CWM Recovery (3.0.0.8). I also reflashed a factory stock ROM found in the lastest RUU. I also flashed the 2nd to latest ROM from that RUU (2.1). All of these only reformatted and re-installed stock ROM. Unfortunately, doing so only reformats the existing partitions, but does not fix the screwed up partition sizing. As far as I can determine, setting my phone back to S-ON and running the RUU will do nothing different than what I did by placing the stock PB31IMG.zip in the root of my (external) SD card and flashing it from HBOOT.
If the RUU truly repartitions the internal memory, then I'm game to set S-ON and try that. However, all indications are that doing so will be no different than flashing PB31IMG.zip. Is that correct?
Thanks again,
Blue
I have a problem with my phone.
I believe that the internal partitions are messed up.
I have tried a couple of guides to fix this but no luck. I get "error formatting /data!" on recovery. I also tried using the formatting tools from adb shell (e2fsck, gparted).
The main problem is that when i restart my phone the /data partition gets wiped, and the phone reboots in blank, no apps no setting (some of them remain).
I wonder if i can solve this by setting my sd-card to be the new /data. I doesn't matter if i have to leave the sd-card on all the time. i mainly use this phone for developing apps.
Thanks.:good:
Felivel said:
I have a problem with my phone.
I believe that the internal partitions are messed up.
I have tried a couple of guides to fix this but no luck. I get "error formatting /data!" on recovery. I also tried using the formatting tools from adb shell (e2fsck, gparted).
The main problem is that when i restart my phone the /data partition gets wiped, and the phone reboots in blank, no apps no setting (some of them remain).
I wonder if i can solve this by setting my sd-card to be the new /data. I doesn't matter if i have to leave the sd-card on all the time. i mainly use this phone for developing apps.
Thanks.:good:
Click to expand...
Click to collapse
It could probably be done if you could get the sdcard to mount at boot, not sure if thats possible. You would need to create a flashable much like the ext4 mod, that edits the init.inc.rc file to mount the sdcard and /data to it. You would want to partition your sdcard with an ext3 or ext4 partition and use that for data.
Yes it can be done. That's how boot manager works, by modifying the ramdisk to load images from sdcard or emmc instead of the partition. I think I have an idea on how to make your request work.
Edit: If you feel like trying a project, what needs to be done is create a file data.img and mount it as loopback using busybox (ROM needs a working busybox).
Then the boot.img needs to be updated replacing the mount /data entry in init.inc.rc with the location of the loopback device and a loopback setup prior to this. The data.img created needs to be formatted ext3 or ext4. I know it's not too detailed but rather just a summary.
I have a KF1 v6.x (I believe since it was stock). Installed KFU 1.4a. Installed TWRP. Following a post in the [ROM-AOSP] Stock Jelly Bean 4.2.2_r1 for the Kindle Fire [02-12 4.2.2_r1] thread I wiped factory reset then wiped system PRIOR to moving the ROM to the sdcard. Now, there is no OS. I was able to put the ROM.zip on the root of the SD card but when attempting to install it I get "Unable to mount '/data'". I've tried several commands for adb to do partition stuff but didn't get anywhere with that. Not sure if FastBoot is working via KFU due to the following message.
hxxp://imageshack.us/photo/my-images/547/37437819.png/
What's my first step here? I can get into TWRP so hoping this KF isn't totally hosed
Looks like Fastboot is working?
hxxp://imageshack.us/photo/my-images/14/75434412.png/
http://forum.xda-developers.com/showthread.php?t=1949372
soupmagnet said:
http://forum.xda-developers.com/showthread.php?t=1949372
Click to expand...
Click to collapse
SUCCESS! :victory: Thanks soupmagnet! Pic of partition table attached showing /data is not mounted. When doing umount cmd received message "can't umount /data: invalid argument" which I guess is good since /data is not mounted in the partition table.
After removing, making, then naming the partion and quitting I received a message: Information: You may need to update /etc/fstab. 2nd pic shows /data correctly mounted.
Questions:
1) How/at what point did the /data partition get messed up?
2) Is it necessary to "update /etc/fstab"?
3) Who's the happiest KF1-working-again-user?
AnotherBrickedDroid said:
Questions:
1) How/at what point did the /data partition get messed up?
2) Is it necessary to "update /etc/fstab"?
3) Who's the happiest KF1-working-again-user?
Click to expand...
Click to collapse
1) It's hard to say really. For the sdcard, I always assumed it was from not "ejecting" it before unmounting, but I think that would be kind of hard to recreate with the data partition. If I were to speculate at this point, I would say it had to do with how certain versions of TWRP format those partitions, but I'm not sure. In either case it's pretty rare for it to happen.
2) From what I understand, you can't. Recovery is unpacked and run from active memory so any changes you make to fstab will be lost every time you reboot. But the filesystem should still be automatically checked every Nth mount.
3) Three guesses? The first two don't count?
Ok, here is the problem, i woke up today, my phone battery was empty, i connected the phone battery was loading, but i couldn't get to the system, after kernel load it stops, like there was no system installed. Everything worked fine day before,my configuration was: Doomkernel and Existenz_2.0.5 ROM.
So, i got to recovery (recovery works,CWM), and there i saw "can't mount cache" error. I got into shell with adb (this works too), and there is no way i can mount any system partition (/system, /cache, /data), what's more important /sdcard does not mount either. So, i'm in recovery, can't install or restore from sdcard,cause /sdcard does not mount.
I'v tried sideload, no go.
I've tried fastboot flash new kernel, and here's interesing thing, fastboot reported that flashing was ok, but i still have Doomkernel (i was trying to flash 6.0-TUX-Core-HD kernel. So seems like fastboot did not write anything at all.
I've tried flashtool with stock tft. It breaks with "final verification error", when i turn "final verification off" it goes all the way, says everything is installed, but when i restarted, still only Doomkernel.
Any ideas ? I take any advice.
Maybe you have already tried it, but format your phone's data, THEN the cache, and finally the internal storage (SD card). In XS's CWM, there's a bug, which causes sometimes an unformatable and unusable cache parition. But this method can be help on this. Maybe this problem causes those unformatable partitions.
Szatyor said:
Maybe you have already tried it, but format your phone's data, THEN the cache, and finally the internal storage (SD card). In XS's CWM, there's a bug, which causes sometimes an unformatable and unusable cache parition. But this method can be help on this. Maybe this problem causes those unformatable partitions.
Click to expand...
Click to collapse
Thank you for your reply. Haven't tried that but i have now and, unfortunately, no go. With /data and /cache seems like format was success but it didn't ( still can't Mount) and with /sdcard format fails (error mounting /sdcard).
Maybe my sdcard really died ?
qrto said:
Thank you for your reply. Haven't tried that but i have now and, unfortunately, no go. With /data and /cache seems like format was success but it didn't ( still can't Mount) and with /sdcard format fails (error mounting /sdcard).
Maybe my sdcard really died ?
Click to expand...
Click to collapse
Well, I don't think so. The "SD Card" is a part of the memory chip, which includes the system, the data and the cache partitions too. Because you cannot copy anything now to the internal storage, try to install a ROM from ADB Sideload if you can. Once it done, your phone can be boot maybe again. If it happens, try to format the internal storage by the Android. If it fails, connect the phone to your computer, and try to format with Windows or (it can be better) Linux to fat32 filesystem.
Szatyor said:
Well, I don't think so. The "SD Card" is a part of the memory chip, which includes the system, the data and the cache partitions too. Because you cannot copy anything now to the internal storage, try to install a ROM from ADB Sideload if you can. Once it done, your phone can be boot maybe again. If it happens, try to format the internal storage by the Android. If it fails, connect the phone to your computer, and try to format with Windows or (it can be better) Linux to fat32 filesystem.
Click to expand...
Click to collapse
Thank you for your ideas. Thing is, all i can start is cwm recovery. As i wrote, i can't install anything with sideload. And no partition is working. When i start parted /dev/block/mmcblk and try to list partitions, i get unrecognized disk label error, when i try to manually set disk label to msdos, there's I/O Error.
And i can't format sdcard, because when in recovery, phone is not detected by Linux nor Windows. But i tried formatting partitions internally, with mke2fs, and with fastboot command. No go.
I know that /sdcard is just a partition, but what i meant was that probably my phone memory chip died, like hardware died. but i'm still looking for new ideas i want to try everything before giving up.
qrto said:
Thank you for your ideas. Thing is, Alp i can start iż cwm recovery. As i wrote, i can't install anything with sideload. And no partition is working. When i start parted /dev/block/mmcblk and try to list partitions, i get unrecognized disk label error, when i try to manually set disk label to msdos, there's I/O Error.
And i can't format sdcard, because when in recovery, phone is not detected by Linux nor Windows. But i tried formatting partitions internally, with mke2fs, and with fastboot command. No go.
I know that /sdcard is just a partition, but what i meant was that probably my phone memory chip died, like hardware died. but i'm still looking for new ideas i want to try everything before giving up.
Click to expand...
Click to collapse
Then maybe it's a HW error really. But maybe just the partition table is corrupted. At this point, I don't know. I have only one suggestion left: Take the phone to the nearest SONY Center or GSM shop/service to investigation. But I think they will say you'll need to replace the phone's motherboard. Anyway, it's an too expensive solution I think, because this phone is a "retired" modell without any update, but with a "blacksheep (Snapdragon S3) SoC.
Hello Again, I have found a few threads with the same issue but something in the middle is different, this has happened on my Nexus 5 before, and it pissed me off because i never got it resolved.
I want to convert my HTC One M8 ATT to GPE later today, but first i'm on sense with NvROM.
The ROM isn't the issue since it's been working fine for a 2 weeks now, here is the story.
What i did-
Recovery (Wanted to try out CarbonROM)
Flashed LiquidSmooths kernel ontop of Carbon, got "Unfortunately phone has stopped".
Went to recovery again to attempt to flash liquidsmooth only.
E: Unable to mount /data
E: Unable to mount /system
E: Unable to mount /cache
E: Unable to mount /sdcard
E: Wiping /data /system /cache failed!
Now, i rebooted and those errors are non existent i can flash again.
But on LiquidSmooth , The Gallery can not find my Pictures.
The Music app can not find the music anymore.
Whenever i use a File Manager , magically my files are still there.
Anybody got ideas on this one? Thanks.
>Pics related<
Try to connect the phone to a PC, and use Device Manager to format the internal memory. Backup any personal data first, if needed (and if possible).
I've heard that , that causes the eMMc or internal storage to go into Read Only mode?
anyone correct me when i`m totally wrong here.
hasn't this something to do with the so called fused location of your sd-card ?
On my phone the locations of the sdcard is shown different then when i locate them trough recovery or shell.
In android the location is something like: /root/storage/sdcard (internal memory)
the real location in my case was shown in recovery as: /root/storage/emulated/0/
And i think because i had previously installed a cm11 based rom and kernel.
And when i completely wiped my phone for a newly rom, afterwards i still had all my data on my phone, because it didn't wipe the /emulated/0 location.
so all the files are still found with a file manager because the two location i mentioned before are fused. But your apps still has the old location in his settings somewhere..
You can try to do a media rescan so your phone search for new media.... But i believe that is also done when you reboot your phone.
I had that happen to me and I was able to fix it by using the "Format" option in TWRP recovery. That, of course, wipes everything on the device but everything will be mounted correctly and properly again.
Guys, I ended up fixing it.
TWRP format fixes it but i needed a backup. Also first attempt at formatting it on TWRP had issues. E:Can't format , E: Data isn't mounted.
Ended up just going ahead and doing the Google Play Edition Conversion and that fixed the whole issue, Thanks for your time!
@TarekElsakka @djmarkd @redpoint73
i4GS said:
Guys, I ended up fixing it.
TWRP format fixes it but i needed a backup. Also first attempt at formatting it on TWRP had issues. E:Can't format , E: Data isn't mounted.
Ended up just going ahead and doing the Google Play Edition Conversion and that fixed the whole issue, Thanks for your time!
@TarekElsakka @djmarkd @redpoint73
Click to expand...
Click to collapse
so wait, aren't you going to tell us what you mean by it fixed the whole issue? were you able to back up the data first?
I'm having a slightly different (maybe similar) issue.. my at&T m8 was working fine on insertcoin (previously viper/venom) and i decided to try a very stock AT&T debloated rom.
forgot to flash the firmware first, so booted into fastboot, and was going to do that.. but it wouldn't work, gave me an error..
booted back into recovery (TWRP 2.7.0.2) and my internal storage WILL NOT MOUNT. hence, nothing works... I can see microSD files, I can attempt to flash things ,but, due to the internal "sd" (not my microsd, just using old fashioned android terminology) not mounting, every operation fails. interestingly, I can mount / (root partition) and it has the correct structure, and even some vestiges of my files.. when i say mount, i mean in recovery on the device.. not on a computer via USB.
any ideas? i'm stuck
I know i can probably format the /media/data blahblah partition (the internal storage) but I have very important photographs of my best friend's wedding and my children's recent visit to their grandparents'.. so i really really want to restore those files.. I do this kind of thing (file forensics) on OSX, windows, and some linux drives, all the time at work.. I just don't know how to access the storage on an android phone, in order to run the forensics scans etc.
thanks!!
sneef said:
so wait, aren't you going to tell us what you mean by it fixed the whole issue? were you able to back up the data first?
I'm having a slightly different (maybe similar) issue.. my at&T m8 was working fine on insertcoin (previously viper/venom) and i decided to try a very stock AT&T debloated rom.
forgot to flash the firmware first, so booted into fastboot, and was going to do that.. but it wouldn't work, gave me an error..
booted back into recovery (TWRP 2.7.0.2) and my internal storage WILL NOT MOUNT. hence, nothing works... I can see microSD files, I can attempt to flash things ,but, due to the internal "sd" (not my microsd, just using old fashioned android terminology) not mounting, every operation fails. interestingly, I can mount / (root partition) and it has the correct structure, and even some vestiges of my files.. when i say mount, i mean in recovery on the device.. not on a computer via USB.
any ideas? i'm stuck
I know i can probably format the /media/data blahblah partition (the internal storage) but I have very important photographs of my best friend's wedding and my children's recent visit to their grandparents'.. so i really really want to restore those files.. I do this kind of thing (file forensics) on OSX, windows, and some linux drives, all the time at work.. I just don't know how to access the storage on an android phone, in order to run the forensics scans etc.
thanks!!
Click to expand...
Click to collapse
Sorry, but what i did was different, and MIGHT factory reset your internal storage, i can't verify 100%.
You can do two things,
Either flash the RUU
for 4.4.3 STOCK HTC [ATT]
or Flash Google Play edition RUU and revert back to sense which will fix it too.
SENSE: http://forum.xda-developers.com/showthread.php?t=2733523
GPE: http://forum.xda-developers.com/showthread.php?t=2708589