Develop Bugs

[Dev Kernel] 2.6.29 Support for ext2/ext3/ext4/yaffs2

Here is the kernel with yaffs2 and MTD block support, I am missing some mtd util tools like nandwrite so i cannot continue. Those that have the tools like mkyaffs2image, nandwrite, flash_eraseall can try to create an image and mount it
here are the steps that i think should work:
# mknod /dev/mtd0 c 90 0
# flash_eraseall /dev/mtd0
# mkyaffs2image /data/data yaffs2.img
# nandwrite -p /dev/mtd0 yaffs2.img
# mkdir /data/data2
# mount -t yaffs2 /dev/mtdblock0 /data/data2
If you have the tools, please attach so we can continue.. Its getting late so I am going to bed, have fun
Download
yaffs2_support.tar

Oh my god! I was just about to post similar findings, what a coincidence!
I just had compiled a kernel with yaffs2 support. My idea was to modify /init.rc in the kernel to mount the partitions with yaffs2 instead of rfs. Problem: we can't just change the filesystem without backing up and restoring all the files inside. My idea was to do that inside the recovery. Mount a mountpoint, backup with tar to /sdcard, unmount, format with dd (in theory a partition filled with 0's is ok for yaffs2), mount again with yaffs2 and restore from tar.
I'm stuck at the point that I can't seem able to mount any partition with yaffs2 previously formatted (with /system/xbin/busybox dd if=/dev/zero of=/dev/block/stl10). If I mount (/system/xbin/busybox mount -t yaffs2 /dev/block/stl10 /dbdata) there is always an "Invalid argument" error. It happens with /dev/block/stl*, /dev/block/bml* and /dev/block/mmcblk*
I'm no kernel expert, neither I know a lot about yaffs2, but I think I read you can't mount a yaffs2 partition anywhere, it has to be an MTD flash device.
Anyway, I'm going to try with the tools you said. Wish me luck.

Thanks for your work rasdeep! Is it only YAFFS2 and MTD support that you added? Because the kernel already had support for EXT2 and EXT3.
darksnarfer said:
I think I read you can't mount a yaffs2 partition anywhere, it has to be an MTD flash device.
Click to expand...
Click to collapse
Does the kernel that rasdeep posted load the existng flash devices/partitions as MTD devices?
I think as a start you only have to worry about formatting the /dev/block/mmcblk0p2 device which is mapped to the /data directory. With the new lag fix we are only moving directories stored in /data and that is what gives a big performance improvement. RyanZA did tests and found that the /dbdata partition was already quite fast and I don't think we have to worry about the /system partition etc. because we don't really write to them.
I think after a new firmware flash the /dev/block/mmcblk0p2 (mounted as /data) will be safe to format into YAFFS2 without loosing anything important.
I think these are the steps we can do:
1. Flash new firmware with repartition option on to erase everything.
2. Boot into recovery and format /dev/block/mmcblk0p2 as YAFFS2 filesystem.
3. Copy on new a init.rc script which will mount /dev/block/mmcblk0p2 to /data as a YAFFS2 filesystem and not a RFS filesytem to get much faster speeds.

bub181 said:
Does the kernel that rasdeep posted load the existng flash devices/partitions as MTD devices?
Click to expand...
Click to collapse
Just checked, there isn't any /dev/block/mtd* so I guess the kernel still can't see them as mtd.

/data is on the internal SD not in NAND so will we be able to use yaffs2 at all? I was working on formatting to EXT4 and adding the init.rc to match as well as compiling with EXT4 support, but if yaffs2 works, I'm fine with that.

modifying the init.rc is secondary because that is easy.. the main problem now is to be able to manually setup yaffs2 to mount properly.. if everything works like it should, init.rc can be change in matter of seconds
its funny now u said mtd not found.. i know we can mknod /dev/mtd* but there should be /dev/mtdblock* when booting with kernel right? hmm.. something to investigate further..
keep suggestions and finding coming, we may hit something that i've missed
problem is im lacking those tools that will do write to flash directly.. for example nandwrite.. anyone has that can share so i can try more stuff?
also, are my steps for "preparing" yaffs2 partitions/image correct? if anyone familiar with yaffs, please give some insight

raspdeep said:
modifying the init.rc is secondary because that is easy..
Click to expand...
Click to collapse
Do you need to recompile the kernel to modify the init.rc? If not could you post some instructions on how to do it please? I would like to try some things in there before /data gets mounted as a RFS filesystem.

bub181 said:
Do you need to recompile the kernel to modify the init.rc? If not could you post some instructions on how to do it please? I would like to try some things in there before /data gets mounted as a RFS filesystem.
Click to expand...
Click to collapse
i'm afraid so for now until someone found a way to extract the initramfs from later kernel and restore it back after modification..

I think it would be easier to start out with EXT2 since we can easily format that. Just as a proof of concept. I'm planning to do so tonight. Then I'll add support for EXT4 formatting and try that.

raspdeep said:
problem is im lacking those tools that will do write to flash directly.. for example nandwrite.. anyone has that can share so i can try more stuff?
Click to expand...
Click to collapse
Have you seen these pages rasdeep? They seem to describe how to create the YAFFS filesystem. Also, are there any /dev/mtdblock* devices using the kernel that you created? According to what I read elsewhere it is supposed to create both /dev/mtd* and /dev/mtdblock*. I think we have to use /dev/mtdblock* to create the new filesystem.
http://processors.wiki.ti.com/index.php/Create_a_YAFFS_Target_Image
http://processors.wiki.ti.com/index.php/MTD_Utilities
http://processors.wiki.ti.com/index.php/Put_YAFFS_Image_to_Flash
Also, I know that the Nexus One uses YAFFS2 for its internal filesystem. Maybe someone has worked out a way to write a new image file for that and we can use what they have learnt?

Can we potentially use this kernal (with the right tools) to format the NAND in YAFFS2 instead of RFS? Then still have way of flashing firmware onto it?
If so, that would be awesome and it would seem to have the least draw backs.
Currently the A2SD lag fix requires an external microsd card, and the one click lag fix, mounts a EXT2 image ontop of the RFS NAND, and that could drastically affect NAND life.

This is great !!!
Thank you raspdeep and all the devs here, this is one step closer to a stable kernel and a permanent genuine solution for the lag problem as far as a n00b like me understands
cheers !

Daemos said:
Can we potentially use this kernal (with the right tools) to format the NAND in YAFFS2 instead of RFS? Then still have way of flashing firmware onto it?
If so, that would be awesome and it would seem to have the least draw backs.
Click to expand...
Click to collapse
Not if we can't mount the NAND as a MTD-device instead of STL-device.
Daemos said:
Currently the A2SD lag fix requires an external microsd card, and the one click lag fix, mounts a EXT2 image ontop of the RFS NAND, and that could drastically affect NAND life.
Click to expand...
Click to collapse
Say what? /data/ is mounted on the internal SSD, not the NAND. /dbdata/ is however mounted on the NAND. Just do a df -h and you can see all the mountpoints.
Also, mounting and using a ext2-image that reside on an rfs-partition will not damage your drive. The rfs filesystem is still the one used to store the image itself (the ones and the zeros), even though you write it inside an image that uses another filesystem.

I stumbled upon these documents while Googling for STL-devices:
http://www.samsung.com/global/busin...y/downloads/LinuStoreII_GPL Compliance_10.pdf
http://www.samsung.com/global/busin...ionmemory/downloads/RFS_130_Porting_Guide.pdf
I haven't had the time to read them through yet. But if there's a porting guide, there must be a way to reverse it
Go go reverse engineers!

Is it really necessary to format the NAND with another filesystem? /dbdata seems fast enough as it is. Wouldn't it be enough (and easier?) to only convert the internal SD to yaffs2?

Quote from someone that knows a lot more than I do:
yaffs2 won't work on a sdcard
Click to expand...
Click to collapse
http://twitter.com/wesgarner/status/20805997718
So right now we have /data that is mounted in the second partition of the internal sdcard (mmcblk0p2), where all the critical files are stored (data, dalvik-cache, etc..) but we can't use yaffs2 there because it's not MTD.
We could, however, format and mount the other partitions (/system, /dbdata, /cache, etc...) with yaffs2, but that might not help because there isn't many heavy read/write there. And we should figure out how to make the kernel see them as /dev/block/mtdblock* instead of /dev/block/stl*.
rasdeep, can you share the .config for the kernel you used? I managed to get some mtd devices (atleast in /proc/mtd) but they were virtual devices. Maybe we need some more options enabled in the kernel.
Also, anybody knows why there are /dev/block/stl* and /dev/block/bml* they seem the same though.

darksnarfer said:
Also, anybody knows why there are /dev/block/stl* and /dev/block/bml* they seem the same though.
Click to expand...
Click to collapse
According to http://www.samsung.com/global/busin...ducts/fusionmemory/Products_XSR_Brochure.html
STL and BML are independent layers for managing I/O to the NAND devices
STL manages the sector translations while BML manages the invalid blocks (whatever that means)

Did any of you notice that in init.rc there are many references to yaffs2 ? Perhaps in engineering Samsung did use it ?

Chainfire said:
Did any of you notice that in init.rc there are many references to yaffs2 ? Perhaps in engineering Samsung did use it ?
Click to expand...
Click to collapse
Yeah, I think they are just android standard (maybe they took them from a template) and commented to use their better(?) filesystem.

darksnarfer said:
Quote from someone that knows a lot more than I do:
http://twitter.com/wesgarner/status/20805997718
So right now we have /data that is mounted in the second partition of the internal sdcard (mmcblk0p2), where all the critical files are stored (data, dalvik-cache, etc..) but we can't use yaffs2 there because it's not MTD.
We could, however, format and mount the other partitions (/system, /dbdata, /cache, etc...) with yaffs2, but that might not help because there isn't many heavy read/write there. And we should figure out how to make the kernel see them as /dev/block/mtdblock* instead of /dev/block/stl*.
rasdeep, can you share the .config for the kernel you used? I managed to get some mtd devices (atleast in /proc/mtd) but they were virtual devices. Maybe we need some more options enabled in the kernel.
Also, anybody knows why there are /dev/block/stl* and /dev/block/bml* they seem the same though.
Click to expand...
Click to collapse
Ok, so what filesystem does the internal SD use currently? Would it help if we change that to EXT4? That would emulate the current mimocan fix, but without having to use an external SD card.

[Dev Q] mount 2nd ext partition as mmcblk0p3?

Hope this is in the right section, I need help from a developer on this as I don't quite understand what is needed to do this.
I use Gingervillain and the DT a2sd. What I want to do is move my /cache (not dalvik cache but the partition itself) to ext.
I have the commands all ready to do this and that aspect works fine (thanks to help from droidzone).
However, as its sharing the ext partition with DT, when I mount cache there, the apps don't work. Added to which if a market app is downloaded, it downloads the apk to the cache folder I created on ext fine. When it attempts to intall, it fails.
I assume (with my limited knowledge) that there is a conflict here due to multiple mounts on the same partition. I initially thought my mount cache command needed to with the same options that DT mounts, but cant find that reference in his script or the files it calls.
So I have created a 2nd ext partition, but I dont know how to use it. I thought it would automatically be mmcblk0p3, but I cant find it that way using adb.
I know data2ext uses multiple partitions for sqlite etc, but cant for the life of me work this out.
Can anyone point me in the right direction please?
The aim of this is to develop myself a cache2sd solution. I have searched around a lot but can't find one. I thought CM had one but cannot find that either.

Further to this, ls /dev/block lists mmcblk0p3
However,
Code:
busybox mount -o noatime,nodiratime -t auto /dev/block/mmcblk0p3 /system/sd
Returns
Code:
failed: Invalid Argument
but
Code:
busybox mount -o noatime,nodiratime -t auto /dev/block/mmcblk0p2 /system/sd
Works fine.

Does anyone have any idea how I can use the second EXT partition at all or any tips or info please?

format
rootSU said:
Does anyone have any idea how I can use the second EXT partition at all or any tips or info please?
Click to expand...
Click to collapse
format mmcblk0p3 in ext4 format and mount it

susmaz said:
format mmcblk0p3 in ext4 format and mount it
Click to expand...
Click to collapse
Better 2.5 years late than never
Although that would not have been the answer.

Why do you need this 2nd partition??
If i understnad correctly you want the cache on a ext partition, so the play store can download to this partition and than install the apk to intern bzw. The prim ext??

[Q] mounting errors (cant boot anything)

flashed an update to a ROM earlier (which i believe was just coincidental timing) but it stock on splash screen, pulled the battery, booted back into recovery, got tons of e:mount/cache/recovery/ errors which were followed by ending destinations like lastlog, log, etc. cant mount emmc, sd card will not mount so i am stuck. i tried the sd card in the desktop which said it had to be formatted before using which i believe may be because of ext4 partition. so i used a old card which still would not mount in device, put a fresh copy of CWM5 (PB image) on the sd card, it saw and flashed it (so the problem isnt hardware related) but i still had the same issues. i am considering attempting a stock image. hoping that will get me running, root again and be back on tract in an hour. however before i make any steps i was hoping to get some input cause search feature turned up little on this except in forums for some other device (dont remember which). i dont feel their issues was mine. thanks in advance.
edit: decided to go ahead with the RUU, felt sure that would work. well it didnt. phone boots up and runs just fine with my stock ROM. no way of flashing mods, no custom ROMs, cant clear cash, mount emmc, something has to give or i will be having to trade phones sooner than later.

So now that you ruu'ed you flashed cw again and it still wont let you clear or flash anything?

cmlusco said:
So now that you ruu'ed you flashed cw again and it still wont let you clear or flash anything?
Click to expand...
Click to collapse
Correct. I did the ruu. Ran revoked, booted into recovery(which was the old 2.?.?, which had the same issues as before this ever happened. Saw somewhere about a freak error that has happened when attempting to flash ROMs that somehow deletes the main factory partitions. Kinda sounded like mine. But I can not mount, data, cache, SD card, emmc, datadata. I can mount system tho, which does no good. Bootloader sees SD card files so I don't have a issue with corrupt card. I am on stock now which is rooted but nothing is working right cause whatever is going on is infecting it across the board. Apps say installed but don't, not getting messages but can call. Very strange. I know I am too spoiled to live with this tho. Lol.

bump. cant believe nobody has even a suggestion.

shorty1993 said:
bump. cant believe nobody has even a suggestion.
Click to expand...
Click to collapse
What version of hboot are you on?
Have you tried flashing the newest clockwork thru hboot?
When you ruued did you use the PB31IMG.zip method or the exe pc method?
From what i understand your phone does boot but then things dont work right. You say that you cant mount anything but system, but that is only in recovery right? Obviously those partitions are being mounted when booting otherwise it wouldnt boot, so your partitions are probably fine. I would try flashing the latest cw thru hboot, and then see if you can mount and wipe the partitions. If that still dosent work i would then try flashing amon ra recovery thru hboot and see if the wipe and mount options work there.

cmlusco said:
What version of hboot are you on?
Have you tried flashing the newest clockwork thru hboot?
When you ruued did you use the PB31IMG.zip method or the exe pc method?
From what i understand your phone does boot but then things dont work right. You say that you cant mount anything but system, but that is only in recovery right? Obviously those partitions are being mounted when booting otherwise it wouldnt boot, so your partitions are probably fine. I would try flashing the latest cw thru hboot, and then see if you can mount and wipe the partitions. If that still dosent work i would then try flashing amon ra recovery thru hboot and see if the wipe and mount options work there.
Click to expand...
Click to collapse
i am hboot .92. i cant remember for sure what method i used for the RUU but i am abou to try both methods again to be sure no changes depending on which is used.
yes it will boot but only with the stock rom. using file explorers i cant see any contents of data (except lost & found folder), nothing under emmc, datadata, etc. the sd card wont mount in recovery (along with anything else) but will recognize in hboot. cache wont even mount. i had entertained the idea that since different partitions were saying cant mount, it may explain the reason the things arent running just right. i sure shouldnt see barely usable performance on a stock rooted ROM. i have got to figure this out cause new device isnt possible at the time and i cant pay a bill for this thing.
EDIT: i have also swapped over to amon RA recovery with the same results so its not a CWM issue.

just did the PB31IMG RUU. booted as normal (obviously didnt try many functions), ran unrevoked and when it booted into recovery i got the following automatically.
E:Cant mount /dev/block/mmcblk0p2
(file exists)
E:Cant mount CACHE:recovery/command
E:Cant mount /dev/block/mmcblk0p2
(file exists)
E:Cant mount CACHE:recovery/log
E:Cant mount /dev/block/mmcblk0p2
(file exists)
this is just a message right out of the gate. going into mounts will not allow any of these items to be mounted. if attempting to mount CACHE simple "error mounting cache" appears.
system will mount
data shows mounted (but not datadata)
sd card mounting error give the following
E:Cant mount /dev/block/mmcblk1p1 (or /dev/block/mmcblk1)
(no such file or directory)
error mounting sd card
i will attempt to run the RUU with the exe but dont expect different results. any thoughts would be great at this point cause i am all out.

no changes regardless of which method of applying RUU is used.

I got your message bud, buy unfortunately i don't have good news for you... Ive had the same thing happen to 2 of my dincs and it is a hardware problem. The only thing you can do is send it in for a refurb or insurance... Good thing is you can run the the stock ruu in the mean time but fixing it isn't going to happen... Sorry man wish I had better news for you good luck

Check this thread out.
http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/page__st__20
Try going to page 3 as that's when your error starts.
Alternatively, let's try it this way first.
1. Go into recovery,use adb shell to shell into your phone.
2. Type parted /dev/block/mmcblk0
3. Type print.
4. Post output.
It should look like below:
Code:
(parted) print
print
print
Model: MMC HYNIX (sd/mmc)
Disk /dev/block/mmcblk0: 8095MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 8192B 797MB 797MB primary ext3
2 797MB 1007MB 210MB primary ext2
3 1007MB 8095MB 7088MB primary fat32 lba
Let me know from there so we can proceed.

tiny4579 said:
Check this thread out.
http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/page__st__20
Try going to page 3 as that's when your error starts.
Alternatively, let's try it this way first.
1. Go into recovery,use adb shell to shell into your phone.
2. Type parted /dev/block/mmcblk0
3. Type print.
4. Post output.
It should look like below:
Code:
(parted) print
print
print
Model: MMC HYNIX (sd/mmc)
Disk /dev/block/mmcblk0: 8095MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 8192B 797MB 797MB primary ext3
2 797MB 1007MB 210MB primary ext2
3 1007MB 8095MB 7088MB primary fat32 lba
Let me know from there so we can proceed.
Click to expand...
Click to collapse
i will get this soon as i can steal the laptop charger back from my oldest girl. something i believe got jacked up on my desktop in the path environment so i have never been able to run ADB. guess it will be a long night of learning something new. thanks alot. verizon isnt willing to send me another device, already had 2 without an warranty. which is stupid to void my warranty over a account change only.
bad time of year for things to break.

shorty1993 said:
flashed an update to a ROM earlier (which i believe was just coincidental timing) but it stock on splash screen, pulled the battery, booted back into recovery, got tons of e:mount/cache/recovery/ errors which were followed by ending destinations like lastlog, log, etc. cant mount emmc, sd card will not mount so i am stuck. i tried the sd card in the desktop which said it had to be formatted before using which i believe may be because of ext4 partition. so i used a old card which still would not mount in device, put a fresh copy of CWM5 (PB image) on the sd card, it saw and flashed it (so the problem isnt hardware related) but i still had the same issues. i am considering attempting a stock image. hoping that will get me running, root again and be back on tract in an hour. however before i make any steps i was hoping to get some input cause search feature turned up little on this except in forums for some other device (dont remember which). i dont feel their issues was mine. thanks in advance.
edit: decided to go ahead with the RUU, felt sure that would work. well it didnt. phone boots up and runs just fine with my stock ROM. no way of flashing mods, no custom ROMs, cant clear cash, mount emmc, something has to give or i will be having to trade phones sooner than later.
Click to expand...
Click to collapse
because I use MIUI,I have no idea,I come here to learn lol.

tiny4579 said:
Check this thread out.
http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/page__st__20
Try going to page 3 as that's when your error starts.
Alternatively, let's try it this way first.
1. Go into recovery,use adb shell to shell into your phone.
2. Type parted /dev/block/mmcblk0
3. Type print.
4. Post output.
It should look like below:
Code:
(parted) print
print
print
Model: MMC HYNIX (sd/mmc)
Disk /dev/block/mmcblk0: 8095MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 8192B 797MB 797MB primary ext3
2 797MB 1007MB 210MB primary ext2
3 1007MB 8095MB 7088MB primary fat32 lba
Let me know from there so we can proceed.
Click to expand...
Click to collapse
Model: SD SA08G (sd/mmc)
Disk /dev/block/mmcblk0: 7973MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 1049kB 7973MB 7972MB primary fat32 boot, lba
(parted)
from the standpoint of someone far less knowledgeable than i would like to be,,,,,,,,,,,,it appears i have some things missing.

can someone please offer any idea why when doing a push of six files, five show up and one wont regardless of how many attempts. i have also went ahead and done a ruu and fresh root before i started the process of attempting the fix the partitions via the link in this thread. any opinions will be great.

excuse me for bringing this back from the dead but hoping possibly that at this point somebody can shed some additional light on the subject. in desperate need of getting this device running for the wife. where i stand currently is:
*the device is rooted but does not seem to have busy box installed.
*when sd card is inserted it immediately notifies that sd card is safe for removal (can not be mounted thru system menu either)
*in SD and storage info device does not recognize that there is internal memory available either.
all i am need of making this thing do basic functions. as of now files have no where to save (even temps) in order to update or almost anything productive useful. space is not even available to save contacts. this thread above includes all that i have attempted and the outcomes thus far. i would so very appreciative for any and all advice.
thanks in advance
chris

[Q] Format /sdcard and /emmc as ext3?

Has anyone successfully reformatted either /sdcard or /sdcard/external_sd/ /emmc as ext3? I'm not talking about an Apps2SD partition, I'm talking about reformatting the whole volume as one partition, transparent to apps. I do not use Windows so I do not need interoperability, I am fine with ext filesystems.
My goal is to be able to use symlinks (not to mention a more robust filesystem) to redirect certain hard-coded items to store on a different storage volume than it defaults to, but symlinks are not permitted on vfat (FAT32) filesystems.
Thanks!

Anything that I look an answer for, is just not answered. :-(
I am looking for the same information. Wonder why the native ext file systems are not allowed, given that its a Linux kernel running.

You could format it to ext3 and see how it works. Worst case scenario is your phone will tell that sdcard to fu*k off. Given that our phones can and do read the ext format I'm sure you can do it. I'm just not sure how well it will work as far as mounting and such.
On top of that, Windows can read ext formats. You just need a program to do it. I use it all the time.

Thanks for reviving this thread. Surely there must be someone out there who has tried this, and I was hoping to hear from them before I gave it a go, but looks like I'll just have to give it a shot myself.
When I find the time to backup & wipe my sdcard to try and reformat & mount it, I'll report back here.

With my Galaxy Note N7000 I can format a USB Stick to EXT3, and the phone uses it perfectly well as USB Storage...
(rooted, w/w SpeedMod kernel)

[Q] HTC Desire partially broken

Hello!
While trying to install S2E i managed to partially ruin the functionality of my phone. I have an HTC Desire (GSM) running Cyanogenmod 7.1 stable release. I have S-off, root and ClockworkMod Recovery v5.0.2.0.
(I wanted to install a new SD card. In the process I managed to loose all my previous SD card data and I only have a 2 months old back-up from when I was running a different android version, so that will not be very helpful at recuperating many things, but even without the old SD card my phone was still operating correctly besides being unable to run the apps installed on the card. I presume this issue is unrelated to my current problem.)
Here is how I've think I've broken the phone:
- I used Gparted to format a new 8 GB microSD card (class 6) with 1 GB ext4 partition and a FAT32 partition.
- I installed S2E and checked all the options for the OS to use the external storage on the SD card partition.
- It turned out that my partition was not correctly identified by the OS (probably the issue was with using the built-in card reader of the laptop and not a stand alone USB card reader).
- I booted into Recovery Mode and re-formated the SD card with 1 GB of ext3, 32 GB of Swap and the rest as fat.
- After the restart the boot process took a very long time. When the OS finally booted I practically had a fresh install with none of my old settings available (shortcuts, wallpaper, apps etc.). Even the apps stored on the local memory disappeared (S2E, ROM manager, gmail, market etc.) and my home button no longer works. I am unable to receive phone calls since the phone automatically rejects incoming calls. I see incoming calls in the call log and I can make outgoing calls.
I presumed the issue is with mounting the sd-ext partition, but even if I tried to manually mount it after boot I see no change.
I followed these guides to install parted and use 32fsck to see if the partitions are corrupt. I think I have no problems.
Here are the code reports of running parted:
Code:
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: SD 00000 (sd/mmc)
Disk /dev/block/mmcblk0: 7965MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 32.3kB 6909MB 6909MB primary fat32 lba
2 6909MB 7933MB 1024MB primary ext3
3 7933MB 7965MB 32.0MB primary linux-swap(v1)
and e2fsck:
Code:
e2fsck /dev/block/mmcblk0p2
e2fsck 1.41.6 (30-May-2009)
sd-ext: clean, 1091/499712 files, 129331/999425 blocks
Here is my fstab as well:
Code:
/dev/block/mtdblock4 /cache yaffs2 rw
/dev/block/mtdblock5 /data yaffs2 rw
/dev/block/mtdblock3 /system yaffs2 rw
/dev/block/mmcblk0p1 /sdcard vfat rw
/dev/block/mmcblk0p2 /sd-ext ext3 rw
I presume that a fresh OS install will fix the issues. However I hope I can recover the settings stored on the ROM if I fix the sd-ext partition issue.
I will appreciate any suggestions you might have.
ps: adb push and fstab pull is working only when phone is in Recovery. If the CM7.1 is booted there is no fstab in /etc.

Had a similar issue sometime ago. Sorry to say couldn't fix it. In fact I would say the amount of time you spend trying to fix that issue will outway a fresh install.
If you can do a full backup still and save it to your pc you could do a fresh install and work on the issue without loss of phone functionality. Just my thoughts...

Thanks for your advice!
I ended up going for a fresh install with CM7.1 and S2E.
Thinks are ok now the only problem I have is that I don't see the 1 GB of available space reported correctly. Something like 152 MB is free and a negative value is reported as the used space. The CM option of using expanded internal storage is dimmed but I am not sure if that should be different.

mindcsrusher said:
Thanks for your advice!
I ended up going for a fresh install with CM7.1 and S2E.
Thinks are ok now the only problem I have is that I don't see the 1 GB of available space reported correctly. Something like 152 MB is free and a negative value is reported as the used space. The CM option of using expanded internal storage is dimmed but I am not sure if that should be different.
Click to expand...
Click to collapse
No problem. Glad you sorted the issue.
I know with a2sd using standard settings won't show the true size of the parition wont be reported. Something to do with the way it works. If it's working well and letting you install apps with no problems I wouldn't worry too much about