$ sudo gainroot
Root shell enabled


BusyBox v1.19.3 (Debian 1.19.3power5) built-in shell (ash)
Enter 'help' for a list of built-in commands.

/home/user # fsck.ext3 -fnv /dev/mmcblk0p2
e2fsck 1.41.3.maemo0 (12-Oct-2008)
Warning! /dev/mmcblk0p2 is mounted.
Warning: skipping journal recovery because doing a read-only filesystem check.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Free blocks count wrong for group #2 (3639, counted=3638).
Fix? no

Free blocks count wrong (721614, counted=721580).
Fix? no

Free inodes count wrong for group #2 (4933, counted=4932).
Fix? no

Free inodes count wrong (215271, counted=215270).
Fix? no


/dev/mmcblk0p2: ********** WARNING: Filesystem still has errors **********


46873 inodes used (17.88%)
1071 non-contiguous inodes (2.3%)
# of inodes with ind/dind/tind blocks: 2485/36/0
326962 blocks used (31.18%)
0 bad blocks
1 large file

41536 regular files
3179 directories
0 character device files
0 block device files
2 fifos
0 links
2148 symbolic links (1301 fast symbolic links)
0 sockets
--------
46865 files
/home/user #

doesn't look good
try this:
you are likely to loose data as fsck after putting the data of bad blocks (and related files) into a found.000 file (if memory serves well) where it is as good as impossible to retrieve from, alas will mark the blocks as bad which makes them inaccessible

BusyBox v1.19.3 (Debian 1.19.3power5) built-in shell (ash)
Enter 'help' for a list of built-in commands.

~ $ sudo gainroot
Root shell enabled


BusyBox v1.19.3 (Debian 1.19.3power5) built-in shell (ash)
Enter 'help' for a list of built-in commands.

/home/user # umount /dev/mmcblk0p2
umount: can't umount /home: Device or resource busy
/home/user #

cant umout. why?

You can't just unmount /dev/mmcblk0p2. As it hosts /home, there are a lot of open files on it. That's why I told you to use Ubuntu in my posts. From there start a possible disk repair.

Because mmcblk0p2 is the /home/ partition, and you can't unmount it. Running fsck on it while it is mounted(and it is always mounted when using maemo) is also, to put it bluntly: stupid. Of course, you maybe couldn't know, but the people who suggest such things should better do their research first, too.

If you want my honest opinion:

1. Reflash Rootfs and EMMC (as described here) (but backup at least your data first!)
2. Switch to CSSU stable
3. Ask yourself if you really need Power Kernel.
3. Start with a clean, solid system, don't install every crap and especially, don't listen to some random guys on this forum.

"But I don't want to lose my apps" - well, sometimes you want. Reflashing is the easiest way to get rid of all those problems and I have my reasons to recommend it.

You might find this post useful to check the optfs partition from a linux-pc or via virtualbox from a windows-pc http://talk.maemo.org/showpost.php?p...6&postcount=80

BusyBox v1.19.3 (Debian 1.19.3power5) built-in shell (ash)
Enter 'help' for a list of built-in commands.

/home/user # fsck.ext3 -fnv /dev/mmcblk0p2
e2fsck 1.41.3.maemo0 (12-Oct-2008)
Warning! /dev/mmcblk0p2 is mounted.
Warning: skipping journal recovery because doing a read-only filesystem check.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

52703 inodes used (20.10%)
1121 non-contiguous inodes (2.1%)
# of inodes with ind/dind/tind blocks: 3155/45/0
419522 blocks used (40.01%)
0 bad blocks
1 large file

46494 regular files
3678 directories
0 character device files
0 block device files
2 fifos
0 links
2520 symbolic links (1627 fast symbolic links)
0 sockets
--------
52694 files
/home/user #

Problem Fixed. Yujuuuu Yipiiii

Pd. Someone can you tell me if you are correcting the errors of the system partitions?