• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help CWM 5.0.2.7 E: Can't mount /cache/

G2now

G2now

Lurker
I have recently installed a few different ROMS. I've tried ctmod 3.1 and cyanogen 7.1. Recently now when booting into recovery CWM I receive errors

E: Can't mount /cache/recovery/command
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've followed this link http://forum.xda-developers.com/showthread.php?t=1284196 here to see if my eMMC chip is fried which its not.
While running the first command line: i received this

dmesg | grep mmc0
<6>[ 2.182373] mmc0: Qualcomm MSM SDCC at 0x00000000a0400000 irq 24,113 dma 8

<6>[ 2.182409] mmc0: 8 bit data mode disabled
<6>[ 2.182429] mmc0: 4 bit data mode enabled
<6>[ 2.182451] mmc0: polling status mode disabled
<6>[ 2.182478] mmc0: MMC clock 144000 -> 49152000 Hz, PCLK 100000000 Hz
<6>[ 2.182503] mmc0: Slot eject status = 0
<6>[ 2.182524] mmc0: Power save feature enable = 1
<6>[ 2.182554] mmc0: DM non-cached buffer at ffc11000, dma_addr 0x26caa000
<6>[ 2.182586] mmc0: DM cmd busaddr 0x26caa000, cmdptr busaddr 0x26caa300
<4>[ 2.568923] mmc0: host does not support reading read-only switch. assuming
write-enable.
<6>[ 2.568954] mmc0: new high speed SDHC card at address 8758
<6>[ 2.579704] mmcblk0: mmc0:8758 SD08G 7.42 GiB
~ #
Im not sure how to fix this. The previously mentioned link says I should clear my cache, which I tried, but am met with an error (can't mount cache, wiping skipped... format complete.) Can someone help lead to what I should be doing? Thanks.
 
G2now said:
E: Can't mount /cache/recovery/command
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
Click to expand...

I have the same problem, and was about to post in the CWM thread. I have tried to mount/format/wipe the cache, but I still receive the error. I've also used Odin twice, I've tried CWM versions 5.0.2.6 and 5.0.2.7, I've installed the rfscache.zip twice, installed CTMod three times, but the cache error is still there. Any help would be greatly appreciated.
 
thats the update for CWM 5.0.2.6 correct? If so, I have already applied the update. I have actually used Odin to unroot with EJ06 -stock, then reroot again as EJ06 w/ CWM, and still cannot remove the problem. My main concern is how bad is it if my cache partition is corrupted?
 
Bloodawn said:
try flashing this in CWM and see if it goes away

SPH-M820-CWM-5027-UPDT-FIXED2A.zip
Click to expand...

Unfortunately, the error is still there after flashing the new CWM fix. Thanks for the suggestion though Bloodawn.

It's strange because everything else seems to work perfectly on the phone. I've been ignoring the error for a while now, and it makes it impossible to create working backups with CWM. The backup will always fail on the cache, and trying to restore the backup gives an MD5 mismatch.
 
Koumajutsu said:
On the Prevail, CSC ended up mapped to the /cache partition.
If you swap to ext4 cache partitions (CTMod/CM7) the CSC ends up putting it back to RFS
Click to expand...

Worked like a charm, I see that this csc.tar file manipulates the format extension. I have a vague understanding of this stuff, thanks for the help. I understand a little more.
 
Thanks Kouma, that worked great! :) I have a few questions about it, though. Please forgive my noobness.

Is it alright to continue running EJ06 with this CSC? Does the CSC affect anything else on the phone? I wonder why it was not included in the rooted EJ06 Odin pack.
 
OuterHeaven said:
Thanks Kouma, that worked great! :) I have a few questions about it, though. Please forgive my noobness.

Is it alright to continue running EJ06 with this CSC? Does the CSC affect anything else on the phone? I wonder why it was not included in the rooted EJ06 Odin pack.
Click to expand...

it's just a raw image of the /cache partition
It wasn't included in anything prior to the FA19 image that I put out
I can't remember when it was exactly, but I was looking at the ops file and the mount structure of the phone and it made sense to me that csc was most likely our cache.

So, I risked the brick and tried it. It worked.

I added it to my Odin Image Creator because it made it quite easy to change settups from RFS based roms to EXT4 based roms and back

So, when FA19 came out I put it in there in case anyone was on an ext4 cache and was going back to stock
 
You must log in or register to reply here.
Back
Top Bottom