A brief background :
Was shooting a movie on my phone and it froze restarted twice . After that no luck mouting the ext4 partition.

-- How can I get an fsck done on the ext4 file system and let the allocation table know there are bad blocks
-- Is there some mechanism inbuilt in the card that detects bad blocks and corruption and will put the card in RO mode for 1 partition and other partition ext4 cannot be mounted on phone
-- Some place I read this means the card is on its last legs and after some write cycles it becomes RO. Some tech support suggested this happend. I am not prepared to beleive . I ts only 4 months old bought from Amazon and I CAN write to it ( as will confirm ahead in the rest of the story )
-- I have ADB driver and get to # prompt on adb. I can possibly mount p1 as RW . I can confirm on adb that P2 is seen but it will not mount it
-- How can I get app2sd to mount this and be back in biz.

-- I am able to mount both p1 and p2 as RW ( after explict command ) and only as Su. Normal user - its denied RO. SO on live ubuntu I CAN RW to both
-- Backed up P2 and then tried to DEL and format P2 ( gparted + fdisk manually ) - NO LUCK. Both give message its successful but after refresh they will show the SAME old partitions P1 and P2. Tried same on Window 7 - paragon partition manager - gives message its successful but after refresh they will show old configuration P1 and P2.
---Fsck

Loop through node list
Another try: grab all backup supernode list from testdisk log and loop through This is interesting... when I run esfsck -b <n> -B <N> /devpath I get same standard o/p below . No difference.

But when Loop through that list loaded from a file ( testdisk.log) - for certain nodes it will give a long o/p like it did some repair - a blink of hope ....after that I did a Linux REISUB shutdown and efsck again . NO LUCK

For those block numbers where it atttempted repair - on command line I tried to set those very backup superblocks - but it does NOT help- back to square one

if its a total dead horse then why can I mount and RW on live & Android backs off It looks like there is some kinda flag being set here if bad superblock or corrupt blocks are detected -to always load P1 as RO and P2 is not worth l oading. How do I clear that flag ? I have # via ADB for my android phone. Why can I mount on android like to do on Live ?

A brief background :
Was shooting a movie on my phone and it froze restarted twice . After that no luck mounting the ext4 partition.

-- How can I get an fsck done on the ext4 file system and let the allocation table know there are bad blocks
-- Is there some mechanism inbuilt in the card that detects bad blocks and corruption and will put the card in RO mode for 1 partition and other partition ext4 cannot be mounted on phone
-- Some place I read this means the card is on its last legs and after some write cycles it becomes RO. Some tech support suggested this happened. I am not prepared to believe . It's only 4 months old bought from Amazon and I CAN write to it ( as will confirm ahead in the rest of the story )
-- I have ADB driver and get to # prompt on adb. I can possibly mount p1 as RW . I can confirm on adb that P2 is seen but it will not mount it
-- How can I get app2sd to mount this and be back in biz.

-- I am able to mount both p1 and p2 as RW ( after explicit command ) and only as Su. Normal user - its denied RO. SO on live ubuntu I CAN RW to both
-- Backed up P2 and then tried to DEL and format P2 ( gparted + fdisk manually ) - NO LUCK. Both give message its successful but after refresh they will show the SAME old partitions P1 and P2. Tried same on Window 7 - paragon partition manager - gives message it's successful but after refresh they will show old configuration P1 and P2.
---Fsck

Loop through node list
Another try: grab all backup supernode list from testdisk log and loop through, This is interesting: when I run esfsck -b <n> -B <N> /devpath I get same standard o/p below . No difference.

But when I loop through that list loaded from a file ( testdisk.log) - for certain nodes it will give a long o/p like it did some repair - a blink of hope. After that, I did a Linux REISUB shutdown and efsck again . NO LUCK

For those block numbers where it atttempted repair - on command line I tried to set those very backup superblocks - but it does NOT help- back to square one!

If it's a total dead horse, then why can I mount and RW on live & Android backs off It looks like there is some kind of flag being set here if bad superblock or corrupt blocks are detected -to always load P1 as RO and P2 is not worth loading. How do I clear that flag ? I have # via ADB for my android phone. Why can I mount on android like to do on Live ?