I get this error when i go to wipe dalvic cache:
"E: Cant mount /dev/block/mmcblk1p2
(file exists)
Dalvic Cache wiped"
This has been happening for a while and doesnt seem to be causing any problems...at least that i know of, im just curious why it does that, and if there is a fix for it. Ive searched and this has been reported on other phones and most say it has something to do with a bad portion or something...but ive never portioned my sdcard.
I used a root explorer and went to the file location and found there is no file named "mmcblk1p2". ive odined to stock a few times (not for this issue, just for fresh flashing purposes) and that has not fixed the problem
Sent from my SAMSUNG-SGH-I997 using Tapatalk
mg2195 said:
I get this error when i go to wipe dalvic cache:
"E: Cant mount /dev/block/mmcblk1p2
(file exists)
Dalvic Cache wiped"
This has been happening for a while and doesnt seem to be causing any problems...at least that i know of, im just curious why it does that, and if there is a fix for it. Ive searched and this has been reported on other phones and most say it has something to do with a bad portion or something...but ive never portioned my sdcard.
I used a root explorer and went to the file location and found there is no file named "mmcblk1p2". ive odined to stock a few times (not for this issue, just for fresh flashing purposes) and that has not fixed the problem
Sent from my SAMSUNG-SGH-I997 using Tapatalk
Click to expand...
Click to collapse
I think it may be an issue with cwm.
I see it regularly...doesn't seem to have any issues.
idk.
Its not an issue... it has said that everytime I've ever wiped dalvik.... it saying it can't mount the dev/block because its already mounted..
Sent from my SAMSUNG-SGH-I997 using xda premium
Same here it always says it.
Sent from my Zeused up Infuse 4G
Related
I think i messed something after flashing the EXT4 mod because when i booted into recovery the text under blue line is orange and yellow and i don't remember it being like that before? i can hit reinstall packages and it loads cwm fine as far as i can tell? this is what it says please let me know whats wrong and how i can fix it please. thanks
E:Can't mount /dev/block/stl11
(invalid argument)
E:Cant mount CACHE:recovery/command
#MANUAL MODE#
--Appling Multi-CSC...
Installing Multi-CSC
E:Can't mount /dev/block/stl11
(invalid argument)
E:Cant mount CACHE:recovery/recovery.log
E:Cant open CACHE:recovery/recovery.log
E:Can't mount /dev/block/stl11
(invalid argument)
it is a know issue after flashing ext4, you are still ok, just click on reinstall packages and it will take you to cwm
yeah I'm sure everyone who flashed EXT4 is experiencing the same thing, I am too. CWM still works as far as I'm concerned. I've done like two restores, and flashed trigger rom successfully. I think everyone is getting those mounting errors.
Nevertheless, the phone is ridiculousness fast and smooth !! big ups to dsexton702.
slapshotx2002 said:
it is a know issue after flashing ext4, you are still ok, just click on reinstall packages and it will take you to cwm
Click to expand...
Click to collapse
Crap now that i think about it the OP did mention something about an error botting into CWM i guess this is it right?is it a false alarm?? and how do i fix it? or is there no way to fix it? thanks for the quick reply.
Bryanb82 said:
I think i messed something after flashing the EXT4 mod because when i booted into recovery the text under blue line is orange and yellow and i don't remember it being like that before? i can hit reinstall packages and it loads cwm fine as far as i can tell? this is what it says please let me know whats wrong and how i can fix it please. thanks
E:Can't mount /dev/block/stl11
(invalid argument)
E:Cant mount CACHE:recovery/command
#MANUAL MODE#
--Appling Multi-CSC...
Installing Multi-CSC
E:Can't mount /dev/block/stl11
(invalid argument)
E:Cant mount CACHE:recovery/recovery.log
E:Cant open CACHE:recovery/recovery.log
E:Can't mount /dev/block/stl11
(invalid argument)
Click to expand...
Click to collapse
thats because the recovery on the rom is not compatable with ext 4 but clockwork is hence why u can still get into clockwork but not the stock recovery.
yes OP is correct as of now there is no way of fixing it. just ignore it and click install packages and it works just fine
Bryanb82 said:
Crap now that i think about it the OP did mention something about an error botting into CWM i guess this is it right?is it a false alarm?? and how do i fix it? or is there no way to fix it? thanks for the quick reply.
Click to expand...
Click to collapse
will be fixed along with the chargeing animation once we get more ext 4 roms.
thanks everybody i feel allot better now but one more question. Even if i reflash odin and then reflash bionix the ext4 mod will still be there right? or do i have to do the mod again?
Bryanb82 said:
thanks everybody i feel allot better now but one more question. Even if i reflash odin and then reflash bionix the ext4 mod will still be there right? or do i have to do the mod again?
Click to expand...
Click to collapse
if u odin it flashes back the stock file system u would have to reconvert.
RaverX3X said:
if u odin it flashes back the stock file system u would have to reconvert.
Click to expand...
Click to collapse
i fixed the battery issue but i cant fix the recovery AKA cache mount error in recovery
im still working on it, also i found a way to convert back to rfs so you wont have the recovery cache mount issue but you also wont have ext4
dsexton702 said:
i fixed the battery issue but i cant fix the recovery AKA cache mount error in recovery
im still working on it, also i found a way to convert back to rfs so you wont have the recovery cache mount issue but you also wont have ext4
Click to expand...
Click to collapse
Ive been screwing around trying to get my partition for ext4. And I was able to change my cache mount to mount and now I'm not receiving the cache error. Dont know that I did anything to help it along but my phone seems fine other than the OC problems which are minor
Sent from my SGH-T959V using XDA Premium App
GDofWR420 said:
Ive been screwing around trying to get my partition for ext4. And I was able to change my cache mount to mount and now I'm not receiving the cache error. Dont know that I did anything to help it along but my phone seems fine other than the OC problems which are minor
Sent from my SGH-T959V using XDA Premium App
Click to expand...
Click to collapse
WHAT!!! you fixed the error in red writing when you enter recovery before CWM!!!????
and what OC problems?
dsexton702 said:
WHAT!!! you fixed the error in red writing when you enter recovery before CWM!!!????
and what OC problems?
Click to expand...
Click to collapse
Yea I was going in and out of cwm trying to partition like Lenny hodapp and I noticed the red text error wasn't coming up so I went to mounts and cache was the only one that said unmount so I mounted it and I have not received that error since. If I see it come back I will let you know.
And my OC problems are things like xda app freezing and market sometimes makes the phone vibrate and back out of some screens on it's own. 1 or 2 fc's and that's about it. Also I turned off stability watch and still unstable at 1.5ghz. Should I increase internal voltage by +25 or +50?
Sent from my SGH-T959V using XDA Premium App
GDofWR420 said:
Yea I was going in and out of cwm trying to partition like Lenny hodapp and I noticed the red text error wasn't coming up so I went to mounts and cache was the only one that said unmount so I mounted it and I have not received that error since. If I see it come back I will let you know.
And my OC problems are things like xda app freezing and market sometimes makes the phone vibrate and back out of some screens on it's own. 1 or 2 fc's and that's about it. Also I turned off stability watch and still unstable at 1.5ghz. Should I increase internal voltage by +25 or +50?
Sent from my SGH-T959V using XDA Premium App
Click to expand...
Click to collapse
try 1400 instead of 1375 for the core and internal maybe to 1200
also might have to warm the rom up to OC'ing because my 1.5 was extremely stable but not till awhile with the rom
dsexton702 said:
try 1400 instead of 1375 for the core and internal maybe to 1200
also might have to warm the rom up to OC'ing because my 1.5 was extremely stable but not till awhile with the rom
Click to expand...
Click to collapse
Kool ill stretch this baby out on 1.2ghz and work my way towards something a little higher. Also I made a note to try those settings next time I try 1.5ghz. Its wild though at 1.2ghz my quadrant scores are in the 1800's all thanks to your easy to follow steps. Thank you sir
Sent from my SGH-T959V using XDA Premium App
I was also screwing around in the sd card yesterday night and noticed I had 3 nandroid back ups I deleted the 2 oldest and kept the newer one now I'm also not getting that mounting error in cwm and as far as OC goes I've notice that my phone is stable at 1.5ghz but depending on which of dr honks kernels I use it requires different voltages:
the 2.1 UV it's stable at core voltage 1400mv and internal 1175mv and the non UV Kernel it's stable at 1400mv and 1150mv. in either one of these settings the scaling need to be set to conservatiove or performance starting at 200mhz instead of 100mhz.
ssmokey727 said:
I was also screwing around in the sd card yesterday night and noticed I had 3 nandroid back ups I deleted the 2 oldest and kept the newer one now I'm also not getting that mounting error in cwm and as far as OC goes I've notice that my phone is stable at 1.5ghz but depending on which of dr honks kernels I use it requires different voltages:
the 2.1 UV it's stable at core voltage 1400mv and internal 1175mv and the non UV Kernel it's stable at 1400mv and 1150mv.
Click to expand...
Click to collapse
yea i noticed they needed to be changed also but i wasnt sure to what
so thank you very much smokey!
also your saying that your ext4 right now, but you dont have the recovery issue?
ive only made one back up and it was on my ext4 sgs4g and im still having the recovery issue even after making some cache adjustments like godofwar did
hmmm need to figure this out
GDofWR420 said:
Yea I was going in and out of cwm trying to partition like Lenny hodapp and I noticed the red text error wasn't coming up so I went to mounts and cache was the only one that said unmount so I mounted it and I have not received that error since. If I see it come back I will let you know.
And my OC problems are things like xda app freezing and market sometimes makes the phone vibrate and back out of some screens on it's own. 1 or 2 fc's and that's about it. Also I turned off stability watch and still unstable at 1.5ghz. Should I increase internal voltage by +25 or +50?
Sent from my SGH-T959V using XDA Premium App
Click to expand...
Click to collapse
just a fyi, when you SEE "unmount" that means what ever your looking at is "mounted" when you click on it and see "mount" that means its unmounted. I had to pm a dev for that info.
I had to odin my phone to KD1 then formatted the fs to ext4 then flashed Bionix frost from cwm I went to recovery and I had those erros in the page. I went into reinstall packages/ apply update from sdcard/ Yes - Install /sdcard/update.zip then rebooted recovery and I had no more mounting erros in the recovery page. I hope this helps
Do I need to format / wipe anything in the CWM screen before restoring a flashed backup?
This is my personal procedure evertime I install a new rom, or revert to a saved backup. I am a noob, so I don't know if it's necessary, but I do it by habit now, and it seems to work for me.
1.wipe dalvik (in advanced menu)
2.wipe cache
3.wipe data/factory reset x 2
4.wipe system (in mounts and storage menu) x 2
5.(optional) wipe dalvik,wipe cache
6. Install zip or backup depending on what my intention is
7. fix permissions
reboot
edit: Actually, this isn't "MY PERSONAL" procedure...this is what was recommended to me from other valued members of this forum. I have simply adopted it into my routine.
That's a whole lotta wiping... wont hurt anything but very redundant.
Sent from my LG-P999 using Tapatalk
I thought dalvik couldn't be wiped in Recovery- it gets an error message.
tgerbracht said:
I thought dalvik couldn't be wiped in Recovery- it gets an error message.
Click to expand...
Click to collapse
The unknown path error? I get that too... but then is says dalvik wiped... wondering about that myself...
Sent from my butt using XDA Premium App
BobbyDukes707 said:
The unknown path error? I get that too... but then is says dalvik wiped... wondering about that myself...
Sent from my butt using XDA Premium App
Click to expand...
Click to collapse
never heard of that, do u have internal or external recovery? i have external and never seen that parsing message once ..........and when i go from rom to rom i wipe data first then cache then dalvik and install new rom...........then if im just updating rom or puting akernel on it is same procedure for both and it goes wipe cache then dalvik and update rom or install kernel, and i never had problems this way never
el buho said:
Do I need to format / wipe anything in the CWM screen before restoring a flashed backup?
Click to expand...
Click to collapse
well when i restore a backup i always wipe everything, and it never fails me then i restore
sarni84 said:
never heard of that, do u have internal or external recovery? i have external and never seen that parsing message once ..........and when i go from rom to rom i wipe data first then cache then dalvik and install new rom...........then if im just updating rom or puting akernel on it is same procedure for both and it goes wipe cache then dalvik and update rom or install kernel, and i never had problems this way never
Click to expand...
Click to collapse
I have external recovery... I haven't updated CM maybe it will take care of it... could it be an SD card issue? I mean I haven't seemed to have had any issues... dunno...
Sent from my butt using XDA Premium App
el buho said:
Do I need to format / wipe anything in the CWM screen before restoring a flashed backup?
Click to expand...
Click to collapse
It depends on what the backup is. If the backup is just an older version of the same rom I will just flash right over sometimes. If you are trying to restore a gb rom over a froyo, you will have to wipe first. Any time you are in doubt, just wipe.
BobbyDukes707 said:
The unknown path error? I get that too... but then is says dalvik wiped... wondering about that myself...
Sent from my butt using XDA Premium App
Click to expand...
Click to collapse
x2 Yea. I always wondered that. I get the same thing all the time.
BobbyDukes707 said:
The unknown path error? I get that too... but then is says dalvik wiped... wondering about that myself...
Sent from my butt using XDA Premium App
Click to expand...
Click to collapse
I get the same path error to sd-ext. I've wondered what sd-ext even is, there is nothing in it and it is not my external or internal memory because they are in different directories.
basically i have an issue every time i wipe my data to flash a new rom, i think this is causing my roms not to work as well as they should. Basically it says its formating /data
formating /chache
formating /sd-ext...
E: formate_volume: Make_extf4fs failed on /dev/block/mmcblk0p2
formating /sdcard/.android_secure
data wipe complete.
What is this file that isnt being formated? Is there another way for me to remove this from my phone so that it is basically completely clean? Even after Odining back to stock i cant remove this.
Any feedback would be nice.
have you ever ran the ext4 converter? If so that might be it. If you really want to get rid of that than (only my opinion) run the rfs formatter.
Hope that makes sense
Sent from my SGH-T959V using XDA Premium App
If you try that and it doesn't work, try formatting your sd card, then odin to kc1. Now you will have a 100% fresh start. After you odin, let the phone sour for 10 min. When you get cwm again, run the ext4 converter, and then flash the rom. let it sit for another 15 min. And try wiping again and see what it says.
Sent from my SGH-T959V using XDA Premium App
what do you mean by kc1?
basically, odin to a stock rom. KC1 is the rom i usually recommend. im pretty sure following what i said before will get rid of this problem after you odin. check the bible for the files.
metalblaster said:
basically i have an issue every time i wipe my data to flash a new rom, i think this is causing my roms not to work as well as they should. Basically it says its formating /data
formating /chache
formating /sd-ext...
E: formate_volume: Make_extf4fs failed on /dev/block/mmcblk0p2
formating /sdcard/.android_secure
data wipe complete.
What is this file that isnt being formated? Is there another way for me to remove this from my phone so that it is basically completely clean? Even after Odining back to stock i cant remove this.
Any feedback would be nice.
Click to expand...
Click to collapse
do you own the sgs4g?
formate_volume: Make_extf4fs failed on /dev/block/mmcblk0p2
is the file system structure for the vibrant as the sgs4g diffrent
Hey guys, i didn't found my problem in other topics, so i opened a new .
So here is the deal, i have the Kisadworx ROM installed now in my Samsung galaxy 3 i5800, and already tried the Kyrillos and both of them have this same issue. When the phone shutdown for low battery, i put it to recharge and when i boot it, it wiped all i have saved. Apps, configs, widgets....just everything. i have no clue why...some one have faced this issue before?
Note: when i enter in recovery mode and try to wipe data/factory reset it shows a message:
E: can't mount /cache/recovery/log
E: can't open /cache/recovery/ log
E: can't mount /cache/recovery/last_log
E: can't open /cache/recovery/last_log
I don't know if this error is related but ok ....
Plz someone could help me?
I had this issue days ago, and it happened to me while I simply only turned off and on my phone.
This is probably caused by bad data and cache(?) partition or by bad (wrong) filesystem used. Try re-flashing STOCK rom eg. XXJPQ and over it custom rom of your choice. If the problem persists, try flashing custom kernel (g3mod) and convert file systems like this:
stl6 - ext4
stl7 - ext4
stl8 - ext2
I never had any issues with g3mod kernel's recovery with theese filesystems.
In gingerbread ROMs I had never issues with data or recovery.
bielmontes said:
Hey guys, i didn't found my problem in other topics, so i opened a new .
So here is the deal, i have the Kisadworx ROM installed now in my Samsung galaxy 3 i5800, and already tried the Kyrillos and both of them have this same issue. When the phone shutdown for low battery, i put it to recharge and when i boot it, it wiped all i have saved. Apps, configs, widgets....just everything. i have no clue why...some one have faced this issue before?
Note: when i enter in recovery mode and try to wipe data/factory reset it shows a message:
E: can't mount /cache/recovery/log
E: can't open /cache/recovery/ log
E: can't mount /cache/recovery/last_log
E: can't open /cache/recovery/last_log
I don't know if this error is related but ok ....
Plz someone could help me?
Click to expand...
Click to collapse
Do you have an ext partition on your phone?
I got into similar problems with the scripts related to ext partition long ago
I too get the recovery error and it is not of any problem to us . This is solved by using g3mod kernel
hey guys, i followed as twinky444 said and it apparently worked. I reinstalled the stock ROM but a got the samsung bootloop, then a tried again and i made it, after, i installed the kyrillos 10.5 and it''s currently working, with no problems of data lost. I think it was some corrupted data problem. Thank you very much guys
bielmontes said:
hey guys, i followed as twinky444 said and it apparently worked. I reinstalled the stock ROM but a got the samsung bootloop, then a tried again and i made it, after, i installed the kyrillos 10.5 and it''s currently working, with no problems of data lost. I think it was some corrupted data problem. Thank you very much guys
Click to expand...
Click to collapse
If u checked ur available memory when u had the problem, u probably had 0.00kb available. Just saying.
Sent from my GT-I9003 using xda app-developers app
bielmontes said:
hey guys, i followed as twinky444 said and it apparently worked. I reinstalled the stock ROM but a got the samsung bootloop, then a tried again and i made it, after, i installed the kyrillos 10.5 and it''s currently working, with no problems of data lost. I think it was some corrupted data problem. Thank you very much guys
Click to expand...
Click to collapse
If youre going from ROM that uses other filesystems than stock samsung's RFS filesystem such as ext2, ext4, so by flashing the stock ROM causes the bootloop WILL be there. (because the stock kernel doesn't support other filesystems than RFS) You need after flashing stock ROM pull the battery, reinsert it, reboot into recovery by pressing 3-keys combo and then "wipe data - factory reset" in recovery and then "wipe cache partition".
After this, the /data and /cache partition gets either mounted again or reformatted (not sure) with the rfs filesystem and the system will be able to boot.
BTW/little hint: You can see for couple of seconds after flashing the stock rom the phone boots into recovery, shows a couple of lines and there are 2 lines that are RED and say something like
DATA: blablabla... !
CACHE: blablabla... !
This process applies to the ROMs such as Purumod, Kyrillos and maybe others what have other filesystems used than the one used by the stock ROM (RFS).
Thats the description of the "bootloop" problem.
BTW... glad we could help and this has been fixed!
This is a really weird problem that i have come across.
I had crombi-kk installed in it. But because of some bugs, i decided to install cm10.2.
I booted up in twrp v2.7.1.1 recovery and chose to Wipe>format data. It started but never ended.
When about 20mins had passed it was still the same, i thought it had hanged so i rebooted.
Then i sideloaded cm10.2. After twrp installed the rom, it showed an error E: unable to mount /data.
I rebooted and it didnot go any further from cyanogenmod bootanimation.
I again rebooted into recovery and chose Factory Default, it failed and showed the above error and 1 more E: unable to mount internal memory.
Then I flashed cwm v6.0.4.7 and i sideloaded which resulted the same. Then i went to mounts and storage and chose mount usb.
But it didnot show up in my pc.
I searched over the net and found that this kind of problem occured when the sdcard was mounted as logical.
Ok, i get that, but now how do i fix this problem? The sdcard isn't showing up on the pc!!
-Ngu said:
This is a really weird problem that i have come across.
I had crombi-kk installed in it. But because of some bugs, i decided to install cm10.2.
I booted up in twrp v2.7.1.1 recovery and chose to Wipe>format data. It started but never ended.
When about 20mins had passed it was still the same, i thought it had hanged so i rebooted.
Then i sideloaded cm10.2. After twrp installed the rom, it showed an error E: unable to mount /data.
I rebooted and it didnot go any further from cyanogenmod bootanimation.
I again rebooted into recovery and chose Factory Default, it failed and showed the above error and 1 more E: unable to mount internal memory.
Then I flashed cwm v6.0.4.7 and i sideloaded which resulted the same. Then i went to mounts and storage and chose mount usb.
But it didnot show up in my pc.
I searched over the net and found that this kind of problem occured when the sdcard was mounted as logical.
Ok, i get that, but now how do i fix this problem? The sdcard isn't showing up on the pc!!
Click to expand...
Click to collapse
It takes about 2 hours to format data so you interrupted it in the middle.
You need to format the data again and this time let it finish please.
sbdags said:
It takes about 2 hours to format data so you interrupted it in the middle.
You need to format the data again and this time let it finish please.
Click to expand...
Click to collapse
Are you sure this would really work?
because it shows, E: Can't mount /data
E: Can't mount internal memory
sbdags said:
It takes about 2 hours to format data so you interrupted it in the middle.
You need to format the data again and this time let it finish please.
Click to expand...
Click to collapse
2 hours? Really? What does it do?
It just wipes the days, right.
Now don't say it recreates the partition
Sent from my Xperia M using XDA Premium 4 mobile app
rhar**** said:
2 hours? Really? What does it do?
It just wipes the days, right.
Now don't say it recreates the partition
Sent from my Xperia M using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No TWRP changed it a few versions back I think it fills every single piece of the emmc with 0000s. Which on mine took 90mins.
Reflash TWRP and see if it will let you do it again. Otherwise you may have to erase it from fastboot.
sbdags said:
No TWRP changed it a few versions back I think it fills every single piece of the emmc with 0000s. Which on mine took 90mins.
Reflash TWRP and see if it will let you do it again. Otherwise you may have to erase it from fastboot.
Click to expand...
Click to collapse
Okay. I haven't seen the source. But shouldn't be a problem on trwp 2.6.x, right?
And why did they change it to fill the whole block with 0's?
Sent from my Xperia M using XDA Premium 4 mobile app
rhar**** said:
And why did they change it to fill the whole block with 0's?
Click to expand...
Click to collapse
That was a change in the base Android libraries. It actually doesn't fill the device with zeros, it calls the "secure erase" command of the eMMC (aka the secure version of "trim"), and that is slow.