View Single Post
azad1top's Avatar
Posts: 84 | Thanked: 11 times | Joined on Aug 2012 @ iran
#88
Originally Posted by michaaa62 View Post
Looks good!
Reboot and then
Code:
sudo gainroot
mkfs.ext3 -L optfs -cc /dev/mmcblk0p2
hi michaaa62



After over 24 hours.

Consequently, the


Code:
BusyBox v1.10.2 (Debian 3:1.10.2.legal-1osso30+0m5) built-in shell (ash) 
Enter 'help' for a list of built-in commands. 

~ $ 
~ $ sudo gainroot 
Root shell enabled 


BusyBox v1.10.2 (Debian 3:1.10.2.legal-1osso30+0m5) built-in shell (ash) 
Enter 'help' for a list of built-in commands. 

/home/user # mkfs.ext3 -L optfs -cc /dev/mmcblk0p2 
mke2fs 1.41.3.maemo0 (12-Oct-2008) 
Filesystem label=optfs 
OS type: Linux 
Block size=4096 (log=2) 
Fragment size=4096 (log=2) 
524288 inodes, 2097152 blocks 
104857 blocks (5.00%) reserved for the super user 
First data block=0 
Maximum filesystem blocks=2147483648 
64 block groups 
32768 blocks per group, 32768 fragments per group 
8192 inodes per group 
Superblock backups stored on blocks: 
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632 

badblocks: Input/output error during ext2fs_sync_device 
Testing with pattern 0xaa: done 
badblocks: Input/output error during ext2fs_sync_device 
Reading and comparing: done 
Testing with pattern 0x55: done 
badblocks: Input/output error during ext2fs_sync_device 
Reading and comparing: done 
Testing with pattern 0xff: done 
badblocks: Input/output error during ext2fs_sync_device 
Reading and comparing: done 
Testing with pattern 0x00: done 
badblocks: Input/output error during ext2fs_sync_device 
Reading and comparing: done 

Block 0 in primary superblock/group descriptor area bad. 
Blocks 0 through 2 must be good in order to build a filesystem. 
Aborting.... 
/home/user #



What do you think?

Flash gets ؟؟؟