Originally Posted by koznj

And after an hour of endless pressing of the y and repairing lots of stuff, it gets to a point that it stops..

Error deallocating inode 66809: Illegal doubly indirect block found
e2fsck: aborted
And if i run again fsck -r /dev/mmcblk0p2 it seems like, it is repairing the same things over and ovr

HTML Code:

Connect to /lost+found<y>? yes

Inode 65963 ref count is 2, should be 1.  Fix<y>? yes

Inode 65972 (...) has invalid mode (00).
Clear<y>? yes

Inode 65979 (...) has invalid mode (00).
Clear<y>? yes

Inode 65980 (...) has invalid mode (00).
Clear<y>? yes

Inode 65981 (...) has invalid mode (00).
Clear<y>? yes

Inode 65982 (...) has invalid mode (00).
Clear<y>? yes

Inode 65983 (...) has invalid mode (00).
Clear<y>? yes

Inode 65984 (...) has invalid mode (00).
Clear<y>? yes

Inode 65985 (...) has invalid mode (00).
Clear<y>? yes

Unattached inode 66207
Connect to /lost+found<y>? yes

Inode 66207 ref count is 2, should be 1.  Fix<y>? yes

Unattached inode 66297
Connect to /lost+found<y>? yes

Inode 66297 ref count is 2, should be 1.  Fix<y>? yes

Inode 66307 (...) has invalid mode (00).
Clear<y>? yes

WARNING: PROGRAMMING BUG IN E2FSCK!
	OR SOME BONEHEAD (YOU) IS CHECKING A MOUNTED (LIVE) FILESYSTEM.
inode_link_info[66317] is 5, inode.i_links_count is 0.  They should be the same!
Inode 66317 ref count is 0, should be 4.  Fix<y>? yes

WARNING: PROGRAMMING BUG IN E2FSCK!
	OR SOME BONEHEAD (YOU) IS CHECKING A MOUNTED (LIVE) FILESYSTEM.
inode_link_info[66318] is 3, inode.i_links_count is 0.  They should be the same!
Inode 66318 ref count is 0, should be 2.  Fix<y>? yes

WARNING: PROGRAMMING BUG IN E2FSCK!
	OR SOME BONEHEAD (YOU) IS CHECKING A MOUNTED (LIVE) FILESYSTEM.
inode_link_info[66319] is 4, inode.i_links_count is 0.  They should be the same!
Inode 66319 ref count is 0, should be 3.  Fix<y>? yes

Inode 66320 (...) has invalid mode (00).
Clear<y>? yes

Inode 66321 (...) has invalid mode (00).
Clear<y>? yes

Inode 66322 (...) has invalid mode (00).
Clear<y>? yes

Inode 66323 (...) has invalid mode (00).
Clear<y>? yes

Inode 66324 (...) has invalid mode (00).
Clear<y>? yes

WARNING: PROGRAMMING BUG IN E2FSCK!
	OR SOME BONEHEAD (YOU) IS CHECKING A MOUNTED (LIVE) FILESYSTEM.
inode_link_info[66325] is 3, inode.i_links_count is 0.  They should be the same!
Inode 66325 ref count is 0, should be 2.  Fix<y>? yes

Inode 66328 (...) has invalid mode (00).
Clear<y>? yes

Inode 66330 (...) has invalid mode (00).
Clear<y>? yes

Inode 66331 (...) has invalid mode (00).
Clear<y>? yes

Inode 66332 (...) has invalid mode (00).
Clear<y>? yes

Inode 66333 (...) has invalid mode (00).
Clear<y>? yes

Inode 66334 (...) has invalid mode (00).
Clear<y>? yes

Inode 66335 (...) has invalid mode (00).
Clear<y>? yes

Inode 66336 (...) has invalid mode (00).
Clear<y>? yes

Inode 66337 (...) has invalid mode (00).
Clear<y>? yes

Inode 66338 (...) has invalid mode (00).
Clear<y>? yes

Inode 66339 (...) has invalid mode (00).
Clear<y>? yes

Inode 66340 (...) has invalid mode (00).
Clear<y>? yes

Inode 66419 ref count is 6, should be 3.  Fix<y>? yes

Unattached inode 66427
Connect to /lost+found<y>? yes

Inode 66427 ref count is 2, should be 1.  Fix<y>? yes

Inode 66561 ref count is 6, should be 5.  Fix<y>? yes

Unattached inode 66617
Connect to /lost+found<y>? yes

Inode 66617 ref count is 2, should be 1.  Fix<y>? yes

Unattached inode 66693
Connect to /lost+found<y>? yes

Inode 66693 ref count is 2, should be 1.  Fix<y>? yes

Unattached inode 66794
Connect to /lost+found<y>? yes

Inode 66794 ref count is 2, should be 1.  Fix<y>? yes

Unattached inode 66795
Connect to /lost+found<y>? yes

Inode 66795 ref count is 2, should be 1.  Fix<y>? yes

Unattached inode 66797
Connect to /lost+found<y>? yes

Inode 66797 ref count is 2, should be 1.  Fix<y>? yes

Unattached inode 66799
Connect to /lost+found<y>? yes

Inode 66799 ref count is 2, should be 1.  Fix<y>? yes

Unattached inode 66800
Connect to /lost+found<y>? yes

Inode 66800 ref count is 2, should be 1.  Fix<y>? yes

Inode 66802 (...) has invalid mode (0160276).
Clear<y>? yes

Inode 66803 (...) has invalid mode (0160425).
Clear<y>? yes

i_faddr for inode 66806 (...) is 90226, should be zero.
Clear<y>? yes

i_blocks_hi for inode 66806 (...) is 16, should be zero.
Clear<y>? yes

Extended attribute block for inode 66806 (...) is invalid (842021155).
Clear<y>? yes

Unattached inode 66806
Connect to /lost+found<y>? yes

WARNING: PROGRAMMING BUG IN E2FSCK!
	OR SOME BONEHEAD (YOU) IS CHECKING A MOUNTED (LIVE) FILESYSTEM.
inode_link_info[66806] is 2, inode.i_links_count is 12593.  They should be the same!
Inode 66806 ref count is 12593, should be 1.  Fix<y>? yes

Inode 66808 (...) is an illegal block device.
Clear<y>? yes

Symlink ... (inode #66809) is invalid.
Clear<y>? yes

Error deallocating inode 66809: Illegal doubly indirect block found
e2fsck: aborted
/home/user #                 

Now what? (o:
Thank you for your time..