[Q] e2fsck error

Hi there, sorry if this a report or double questions.

I have idiotically (if there is such a word) wipe my phone and resulted an eMMC Brick Bug,

now i have been recovering my phone ever since (3 weeks now). It was running smooth using nightlies and Omni. the only problems is when I installed Gapps for both versions. I have to restart my phone for the apps to works. And constantly rebooting my hang phone 3-4 times.

I have using the hg42's methods. and forest1971's methods as well. And my bad block seems to move here and there.

At this time while I'm writing this question, i'm running the e2fsck for my phone.

I wonder what does it means.

~ # e2fsck -f -c –y /dev/block/mmcblk0p10
e2fsck -f -c –y /dev/block/mmcblk0p10
e2fsck 1.41.12 <17-May-2010>
/dev/block/mmcblkop10: recovering journal
Error reading block 65536 <Attempt to read block from filesystem resulted in short read> while reading inode and block bitmaps. Ignore error? yes

Force rewrite? yes

and it keep giving me bad blocks (a few more or less) then it continues to

/dev/block/mmcblk0p10: Updating bad block inode.
Pass 1: Checking inodes, blocks, and sizes
Error reading block 134 <Attempt to read block from filesystem resulted in short read> while getting next inode from scan. Ignore error? yes

Force rewrite? yes

this continues to

Inode 7, i_blocks is 6104, should be 5624. Fix? yes
then

Error reading block 139 <Attempt to read block from filesyystem resulted in short read> while getting next inode from scan. Ignore error? yes

Force rewrite? yes

after giving a lots of block. My phone just reset itself.


Is this normal? what steps can i take to fix this. Please help? Thanks a lots.