Mount points with 2.1 ROM

[Guest Simon O]

I'm trying to diagnose some issues with A2SD that have cropped up on my device. I've been looking at the a2sd code and it appears that the mount points are different to what is actually on my device.

My device:

df -h

Filesystem				Size	  Used Available Use% Mounted on

tmpfs					52.7M	 12.0k	 52.7M   0% /dev

tmpfs					 4.0M		 0	  4.0M   0% /sqlite_stmt_journals

/dev/block/mtdblock1	110.0M	102.3M	  7.7M  93% /system

/dev/block/mtdblock2	 80.3M	 20.3M	 59.9M  25% /data

/dev/block/mtdblock3	 20.0M	  1.1M	 18.9M   6% /cache

/dev/block/mmcblk0p2	457.9M	 13.6M	419.8M   3% /system/sd

#[/code]


Now before I go mad, could somebody running 2.1 please run adb shell and do the df -h command and let me know if it's pretty much like my device please? It seems that on 1.5 ROMs the system partition is /mtdblock3, data /mtdblock 5, and cache mtdblock4. This is what is confusing me. Is my device broken or are the mount points really that different under 2.1?

[Guest BigBearMDC]

I'm trying to diagnose some issues with A2SD that have cropped up on my device. I've been looking at the a2sd code and it appears that the mount points are different to what is actually on my device.

My device:

df -h

Filesystem				Size	  Used Available Use% Mounted on

tmpfs					52.7M	 12.0k	 52.7M   0% /dev

tmpfs					 4.0M		 0	  4.0M   0% /sqlite_stmt_journals

/dev/block/mtdblock1	110.0M	102.3M	  7.7M  93% /system

/dev/block/mtdblock2	 80.3M	 20.3M	 59.9M  25% /data

/dev/block/mtdblock3	 20.0M	  1.1M	 18.9M   6% /cache

/dev/block/mmcblk0p2	457.9M	 13.6M	419.8M   3% /system/sd

#[/code]


Now before I go mad, could somebody running 2.1 please run adb shell and do the df -h command and let me know if it's pretty much like my device please? It seems that on 1.5 ROMs the system partition is /mtdblock3, data /mtdblock 5, and cache mtdblock4. This is what is confusing me. Is my device broken or are the mount points really that different under 2.1?


I startet developing with Android 1.5, and I'm pretty sure that the system partition was mtdblock0 or 1.

I never mounted other partitions though.

I'll post my adb shell output later, but I think your partition layout is the normal one.

It might be that Huawei moved partitions because they made the system partition larger.

We'll see :lol:


Best regards,

BigBear

[Guest Tom G]

I've still got my 2.2 rom on my Pulse so no pretty busybox output, but it is the 1.5 partition layout (and look at all that free space).

# df

/dev: 54004K total, 12K used, 53992K available (block size 4096)

/mnt/asec: 54004K total, 0K used, 54004K available (block size 4096)

/system: 87040K total, 57756K used, 29284K available (block size 4096)

/data: 107776K total, 24884K used, 82892K available (block size 4096)

/cache: 20480K total, 1164K used, 19316K available (block size 4096)

# mount

rootfs / rootfs ro 0 0

tmpfs /dev tmpfs rw,mode=755 0 0

devpts /dev/pts devpts rw,mode=600 0 0

proc /proc proc rw 0 0

sysfs /sys sysfs rw 0 0

tmpfs /mnt/asec tmpfs rw,mode=755,gid=1000 0 0

/dev/block/mtdblock1 /system yaffs2 ro 0 0

/dev/block/mtdblock2 /data yaffs2 rw,nosuid,nodev 0 0

/dev/block/mtdblock3 /cache yaffs2 rw,nosuid,nodev 0 0

[Guest BigBearMDC]

From my output:

/dev/block/mtdblock1 /system

/dev/block/mtdblock2 /data

/dev/block/mtdblock3 /cache[/code]


Best regards,

BigBear

[Guest Simon O]

From my output:

/dev/block/mtdblock1 /system

/dev/block/mtdblock2 /data

/dev/block/mtdblock3 /cache[/code]




Best regards,

BigBear



Thanks guys. What's annoying me is that A2SD is having trouble with dalvik on SD. Something I've suspected but wasn't until I upgraded to 2.7 update 3 (which didn't work) that I looked into it. Update 3r1 works like Update 1 did (which I am using on FLB-MOD) but the dalvik-vm errors are always in logcat when dalvik cache is moved to SD.



Had a quick look at the a2sd code:



[code]/system/bin/busybox.a2sd echo "[ ] Mounting /system as read-write";

/system/bin/busybox.a2sd mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system;

/system/bin/busybox.a2sd echo "[ ] Mounting /data as read-write";

/system/bin/busybox.a2sd mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /data;

to me they are the wrong mount points. Elsewhere in the A2SD code it detects the mount points by looking for the mounted names rather that partition ID (is that the right way of saying this?) Basically the code looks for the /data partition, the /system partition as they are mounted by Android.

Seems that when dalvik cache is moved to SD it needs the ext partition mounting quite early in the boot process else dalvik-vm cannot find it's cache. Eventually after 3 or 4 retries the SD is mounted and dalvik is happy.

[Guest twrock]

(Sorry to interrupt. If this has nothing to do with this topic, please just ignore this, and I'll quietly go away. :lol: I'm just curious, and asking questions is usually a good way to learn.)

After recently updating to a newer 1.5 ROM (official), I could no longer use the AmonRA recovery using the command

fastboot boot recovery-RA-pulse-v1.5.2.img

from my PC. It would boot, but with errors about not finding partitions, and then I couldn't actually do anything with it.

I had to flash the AmonRA image onto the device before I could use it. But that did work. Previously I could boot it and use it without flashing it just fine.

Is this in any way related to your mount points question?

[Guest BigBearMDC]

(Sorry to interrupt. If this has nothing to do with this topic, please just ignore this, and I'll quietly go away. :lol: I'm just curious, and asking questions is usually a good way to learn.)

After recently updating to a newer 1.5 ROM (official), I could no longer use the AmonRA recovery using the command

fastboot boot recovery-RA-pulse-v1.5.2.img

from my PC. It would boot, but with errors about not finding partitions, and then I couldn't actually do anything with it.

I had to flash the AmonRA image onto the device before I could use it. But that did work. Previously I could boot it and use it without flashing it just fine.

Is this in any way related to your mount points question?

My theory is that this is related to the [eventual newer] bootloader, which boots those images in another way it used to do before.

[Guest TaiwanCHT8k]

It would boot, but with errors about not finding partitions, and then I couldn't actually do anything with it.

I had to flash the AmonRA image onto the device before I could use it. But that did work. Previously I could boot it and use it without flashing it just fine.

Is this in any way related to your mount points question?

try turning your phone on whilst pressing MENU & Red btn together

Edited June 28, 2010 by TaiwanCHT8k

[Guest twrock]

try turning your phone on whilst pressing MENU & Red btn together

That brings me into the stock Huawei recovery image, as it is supposed to.

I'm talking about "booting" into the AmonRa recovery image without first flashing it onto the device. I was able to do that in the past with my device's original ROM, but not since updating to the newer 1.5 ROM (B251).

[Guest Andy Veliz]

twrock, check this thread: http://android.modaco.com/content/t-mobile...m-without-root/

i think bUg. fixed the amonra recovery, with new kernel and everything...

[Guest Tom G]

Had a quick look at the a2sd code:

/system/bin/busybox.a2sd echo "[ ] Mounting /system as read-write";

/system/bin/busybox.a2sd mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system;

/system/bin/busybox.a2sd echo "[ ] Mounting /data as read-write";

/system/bin/busybox.a2sd mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /data;

to me they are the wrong mount points. Elsewhere in the A2SD code it detects the mount points by looking for the mounted names rather that partition ID (is that the right way of saying this?) Basically the code looks for the /data partition, the /system partition as they are mounted by Android.

You don't need both the dev and mount point for a remount. So for example you could write the /system command as 'mount -o remount,rw /system'. Why does it mount system as rw, and why does it remount data (its already rw)?

After recently updating to a newer 1.5 ROM (official), I could no longer use the AmonRA recovery using the command

fastboot boot recovery-RA-pulse-v1.5.2.img

from my PC.

I have never been able to boot a boot.img through fastboot (I'm using the December update bootloader). Does it work for anyone?

[Guest Andy Veliz]

used to work for me, i have a u8220-6 without december update... but since I flashed 2.1 swiss ROM i couldn't boot the recovery anymore, i had to flash the recovery image and use the MENU + RED + PWR

[Guest Simon O]

You don't need both the dev and mount point for a remount. So for example you could write the /system command as 'mount -o remount,rw /system'.

Why does it mount system as rw, and why does it remount data (its already rw)?

It no longer does this thankfully. Older version of A2SD

[Guest twrock]

twrock, check this thread: http://android.modaco.com/content/t-mobile...m-without-root/

i think bUg. fixed the amonra recovery, with new kernel and everything...

Thanks for the link.

I gave it a try, but no luck. The error message is different than before, but it still has errors.

E:Can't mount CACHE:recovery/command

E:Can't mount CACHE:recovery/log

E:Can't open CACHE:recovery/log

And it hangs when I try to do a nandroid backup. I thinking the official CHT8000 ROMs are a bit different than the rest.

Edit: Not good. My phone hangs on boot now. Looks like I'll have to install the AmonRA recovery to get things back to normal. Use that modified reovery image at your own risk. It did bad things here.

Edit #2: Yikes! Installing the AmonRA recovery image didn't work either. I had to reflash the ROM with an updata before I could even use the AmonRA recovery to restore.

Edited June 29, 2010 by twrock

[Guest BigBearMDC]

You don't need both the dev and mount point for a remount. So for example you could write the /system command as 'mount -o remount,rw /system'.

Why does it mount system as rw, and why does it remount data (its already rw)?

I have never been able to boot a boot.img through fastboot (I'm using the December update bootloader). Does it work for anyone?

It works using this command:

sudo ./fastboot-linux -c "mem=128M console=ttyMSM2,115200n8 androidboot.hardware=qcom console=ttyUSBCONSOLE0 androidboot.console=ttyUSBCONSOLE0" boot ./zImage

Best regards,

BigBear