wd5gnr
Active member
I am stuck two versions back on BobZ's excellent ROM. The last two times I've flashed I can't get /sd-ext mounted. I looked at it more detail today.
I booted into recovery and mounted an adb shell. /dev/block showed the expected /dev/block/mmcblk0p? partitions (e.g., 1, 2, and 3 -- I have swap on 3 even though apparently the kernel isn't built for swap I didn't know that when I partitioned).
parted sees the partitions and e2fsck checks the partition ok.
But any attempt to mount sd-ext gives me a device does not exist message. It is there, it is clean, but it won't mount (using -t auto or -t ext3).
Since I knew from last time that restoring the backup would work, I restored just sd-ext, but that didn't change anything. Restoring from backup put it all to rights.
So the question is: can anyone get the new kernel to mount /dev/block/mmcblk0p2 with an ext3 file system? Or is it just me?
I have a2sd with a dalvik cache too big to fit on the phone, so having no sd-ext effectively bricks me until I repair it.
Update: On reflection, I have a feeling the problem is that I was in recovery. It is hard to do anything when not in recovery because the cache is always in use. Hmmm. So can CWM not mount ext3 maybe? That still doesn't fix my main problem which is that when I flash to a new version and wipe the dalvik I lose a2sd.
Update #2: Not clearing the Davlik seemed to do the trick. Doing a logcat during boot shows that DexOpt is rebuilding the cache so I guess it is smart enough to figure it out. Maybe I should be using a different recovery?
Update #3: Ok switching from CWM to RA recovery did the trick as far as why I could not mount sd-ext. We'll see how the next upgrade goes.
BobZ Thanks for making these phones more useful!
OK one more edit in case anyone is lurking and reading: I think the culprit is /system/etc/init.d/01mvdalvik
It does a bind mount to put /cache/dalvik-cache on top of /data/dalvik-cache and this upsets a2sd. So I'm not sure if this is a recent addition or if I just somehow got lucky before this. My solution was:
chmod 640 /system/etc/init.d/01mvdalvik
<reboot>
a2sd repair
Then off we go...
I booted into recovery and mounted an adb shell. /dev/block showed the expected /dev/block/mmcblk0p? partitions (e.g., 1, 2, and 3 -- I have swap on 3 even though apparently the kernel isn't built for swap I didn't know that when I partitioned).
parted sees the partitions and e2fsck checks the partition ok.
But any attempt to mount sd-ext gives me a device does not exist message. It is there, it is clean, but it won't mount (using -t auto or -t ext3).
Since I knew from last time that restoring the backup would work, I restored just sd-ext, but that didn't change anything. Restoring from backup put it all to rights.
So the question is: can anyone get the new kernel to mount /dev/block/mmcblk0p2 with an ext3 file system? Or is it just me?
I have a2sd with a dalvik cache too big to fit on the phone, so having no sd-ext effectively bricks me until I repair it.
Update: On reflection, I have a feeling the problem is that I was in recovery. It is hard to do anything when not in recovery because the cache is always in use. Hmmm. So can CWM not mount ext3 maybe? That still doesn't fix my main problem which is that when I flash to a new version and wipe the dalvik I lose a2sd.
Update #2: Not clearing the Davlik seemed to do the trick. Doing a logcat during boot shows that DexOpt is rebuilding the cache so I guess it is smart enough to figure it out. Maybe I should be using a different recovery?
Update #3: Ok switching from CWM to RA recovery did the trick as far as why I could not mount sd-ext. We'll see how the next upgrade goes.
BobZ Thanks for making these phones more useful!
OK one more edit in case anyone is lurking and reading: I think the culprit is /system/etc/init.d/01mvdalvik
It does a bind mount to put /cache/dalvik-cache on top of /data/dalvik-cache and this upsets a2sd. So I'm not sure if this is a recent addition or if I just somehow got lucky before this. My solution was:
chmod 640 /system/etc/init.d/01mvdalvik
<reboot>
a2sd repair
Then off we go...
Last edited: